SEO.co
← Free toolsavailableSM

Sitemap Validator

Enter a domain and the validator locates its XML sitemaps, parses them and flags the problems that make search engines trust a sitemap less: bad structure, oversized files, stale lastmod and URLs that should not be there.

Results open on app.search.co. Your first search is free with no account; further searches need a free search.co account.

Type a bare domain such as example.com. The request opens on app.search.co, where search.co's crawler looks for the site's sitemaps, typically by reading any Sitemap: lines in robots.txt and trying common locations like /sitemap.xml and /sitemap_index.xml. Exactly which paths it probes may vary, so if your sitemap lives somewhere unusual, make sure robots.txt references it. Each file found is fetched and validated.

You can validate one domain without signing up. Additional domains require a free search.co account, which takes a minute to create.

A sitemap is a hint, not a command. Google uses it to discover URLs and to decide what to recrawl, but it still picks canonicals and decides what to index on its own. That makes sitemap hygiene less about passing a schema check and more about sending a clean, consistent signal: every URL listed should be one you actually want indexed.

// what you get

What the validator checks.

The report covers two layers: whether each file is a valid sitemap at all, and whether the URLs inside it are good candidates for indexing.

  • Discovery: which sitemap files were found and where they were referenced from, so you can spot an old sitemap that robots.txt still advertises.
  • File type and structure: whether each file is a sitemap index (<sitemapindex>) pointing at child sitemaps, or a <urlset> listing pages, and whether the XML parses.
  • Size limits: whether any single file exceeds the protocol limits of 50,000 URLs or 50MB uncompressed.
  • lastmod values: whether dates are present, valid W3C datetime format, and plausible rather than identical across every URL.
  • URL quality: listed URLs that redirect, return errors, carry noindex, or declare a different canonical than themselves.
// structure

Sitemap index versus urlset, and how to split large sites.

A <urlset> file lists page URLs directly. A <sitemapindex> lists other sitemap files and nothing else; it cannot contain page URLs. Once a site approaches 50,000 URLs or 50MB in a single file, it needs an index with several child sitemaps. The index itself can list up to 50,000 sitemaps.

How you split matters more than the fact that you split. Segmenting by page type, for example products, categories, articles and locations, turns Search Console's per-sitemap indexing data into a diagnostic. If the products sitemap shows a far lower indexed share than the articles sitemap, you have localized the problem to one template. Splitting by arbitrary number ranges throws that insight away.

Every URL in a sitemap should be absolute and should share the protocol and host of the sitemap's location, unless you have verified cross-host submission. A sitemap at https://www.example.com/ that lists http://example.com/ URLs is sending mixed signals before a single page is evaluated.

// how to read it

Reading URL-level warnings.

Structural errors are binary: fix them and they go away. URL-level warnings take judgment, because each one says the sitemap disagrees with another signal on the site.

URL warnings and what they usually mean
WarningWhat it signalsUsual fix
URL redirectsThe sitemap lists an old addressReplace it with the final destination URL
URL returns 404 or 410Deleted content still listedRemove it; a sitemap is not the place to report removals
URL is noindexThe page asks not to be indexed while the sitemap asks for crawlingDecide which is intended and make both agree
Canonical points elsewhereThe listed URL is a duplicate variantList only the canonical version
lastmod identical on every URLDates are generated at build time, not edit timeEmit the real last content change per URL

A few stragglers on a large site are normal churn. A pattern, such as every product with a color parameter or every paginated archive, points at generator logic, and that is where the fix belongs. To see how robots rules interact with what the sitemap lists, run the same domain through the robots.txt tester; a URL that is both listed in a sitemap and disallowed is a contradiction worth resolving.

// signals

lastmod, changefreq and priority: which ones count.

Google has said it ignores <changefreq> and <priority>. You can leave them in, but tuning them is wasted effort. <lastmod> is different: Google uses it when it is consistently and verifiably accurate, and learns to disregard it on sites where it is not.

"Accurate" means the date reflects a meaningful change to the main content. Updating lastmod because a sidebar widget, copyright year or related-posts block changed trains search engines to ignore the field. So does stamping every URL with the current build time. A useful test: pick a handful of URLs, compare their lastmod to what actually changed on the page, and see whether the dates hold up.

// common mistakes

Sitemap mistakes that keep showing up in audits.

Most of these come from plugins and frameworks generating sitemaps from the database without checking each URL's indexing state.

  • Listing everything the CMS knows about: tag archives, attachment pages, internal search results and staging leftovers end up in the file.
  • Forgetting robots.txt: after a migration, robots.txt keeps pointing at a sitemap path that now 404s, or at the old domain.
  • Submitting and never rechecking: a sitemap is valid on launch day and drifts as pages are deleted, redirected or noindexed.
  • Treating a sitemap as an indexing guarantee: inclusion helps discovery; it does not override thin content, duplication or a noindex tag.
  • Relying on changefreq to speed up crawling: Google ignores it. Accurate lastmod and good internal linking do far more.
// workflow

Clean up a sitemap in five steps.

  1. Validate the domain

    Run the domain and confirm every sitemap you expect is discovered and parses without structural errors.

  2. Check the references

    Make sure robots.txt and Search Console point at the current sitemap index, not a retired file.

  3. Remove bad URLs at the source

    Fix generator rules so redirected, noindexed, non-canonical and error URLs are excluded automatically.

  4. Fix lastmod

    Tie the date to real content edits rather than build or deploy time.

  5. Revalidate

    Run the check again after deploying and spot-check a few URLs by hand.

// want a second opinion?

Get an expert read on your results

Tools give you the raw numbers. Tell us your site and an SEO.co strategist will email you what they'd prioritise and the next steps they'd recommend.

// faq

Sitemap validator questions.

How does the validator find my sitemap?
It checks for Sitemap lines in robots.txt and tries common default locations. If your sitemap uses a nonstandard path, add a Sitemap line to robots.txt so both this tool and search engines can find it.
What are the size limits for a sitemap?
Each sitemap file can hold up to 50,000 URLs and must be no larger than 50MB uncompressed. Larger sites split URLs across several files and list them in a sitemap index.
Does Google use priority and changefreq?
Google has stated that it ignores both. It does use lastmod when the dates are consistently accurate.
Should noindex pages be in my sitemap?
Generally no. A sitemap should list URLs you want indexed. Listing noindex pages sends contradictory signals and dilutes the usefulness of the file.
Can I use a gzipped sitemap?
Yes, the protocol allows gzip compression. The 50MB limit applies to the uncompressed size.
Is the first validation free?
Yes. One domain can be validated without an account, and a free search.co account covers further checks.

Indexing numbers not adding up?

SEO.co's technical audit reconciles sitemaps, canonicals, robots rules and Search Console coverage so the pages you care about get crawled and indexed.

Get a technical audit