Free Sitemap Validator

Pages missing from the sitemap mostly never get discovered

We compared pages on the same websites, so a strong site cannot flatter the result. On the 78 websites with at least 10 pages inside the sitemap and 10 outside it, the difference was anything but subtle:

All page types, compared within each website.

That is a 42-point gap in getting found, against a 7.5-point gap once Google has actually crawled the page. A sitemap doesn't make Google like your pages more. It makes Google aware they exist. For blog articles, pages listed in the sitemap were indexed 42.4 percentage points more often than articles on the same site that were left out, and the gap held on 67 of the 78 websites.

For comparison, the classic on-page checklist barely registered in the same study. Word count, title length and Title Case made no measurable difference to whether a page got indexed.

Internal links alone are not enough

The common advice is that a well-linked site doesn't need a sitemap, because crawlers follow links. Google's own documentation says a small, comprehensively linked site might get by without one. Our data points the other way. A page that is not in the sitemap can only be discovered by following a link to it, and on the same websites, Google had never discovered 6 in 10 of those pages.

Internal links still matter. They tell Google which pages are important, help it crawl deeper, and pass authority to new content. But discovery is a queue, and a crawler only works through part of it on each visit. A sitemap puts every URL in the queue on the day you publish, instead of waiting for a crawl to stumble onto it. Use both: link to new pages from pages that are already indexed, and list every page you want indexed in the sitemap.

The more of your site is in the sitemap, the more of it gets indexed

Group websites by sitemap coverage, the share of their pages listed in their own sitemap, and indexation climbs step by step:

166 websites and 43,296 pages. Middle website in each group.

Fit a straight line through 246 websites and an empty sitemap predicts 23% of pages indexed, a complete one 67%. Sitemap coverage explained 16.3% of the difference in indexation between websites. Domain Rating explained 4.5%, and site size 0.6%. What you put in your sitemap predicted indexation more than three times better than your backlink authority did.

Incomplete sitemaps are common, too. 110 of the 362 websites we checked had more than 20% of their pages missing from their own sitemap, and 48 were missing more than half.

Most unindexed pages were never crawled at all

Follow the pages of the average website through Google's pipeline and the biggest loss happens before Google reads a single word:

Average of 246 websites with at least 20 pages, each website weighted equally.

Roughly one page in three had never been fetched by Google, not even once, while only 7.5% were crawled and then turned down. Google cannot reject a page it has never read. So before you rewrite a page that isn't indexed, check that it's in your sitemap and that Google has crawled it.

Your CMS changes discovery, not quality

Platforms differ a lot in how many pages Google never discovers, and hardly at all in what happens once Google reads a page:

Websites with at least 20 pages, each website weighted equally. Webflow and Wix are small samples, so read those rows as a signal rather than a verdict.

The share of pages Google never discovered ranges from 16% to 46% depending on the platform, while the share indexed once crawled stays between 87% and 91% everywhere. Shopify and WordPress generate sitemaps out of the box. On Next.js and custom stacks, the sitemap is whatever your code outputs, so a forgotten route or a stale build quietly leaves pages out, and Google never hears about them.

Give new pages 30 days before you judge them

Timing matters as much as the sitemap. On 68 websites with at least 10 articles checked at both moments, the typical site had 8% of its articles indexed when Google was asked within 7 days of publishing, and 90% when asked 31 to 90 days after. 80% of the articles checked in their first week came back as "URL is unknown to Google". A week-one report measures Google's queue, not your content.

XML sitemap format, with examples

An XML sitemap is a UTF-8 encoded file, usually at /sitemap.xml, that lists the URLs you want search engines to crawl. A minimal valid sitemap looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-09-20</lastmod>
  </url>
  <url>
    <loc>https://example.com/blog/xml-sitemap-guide</loc>
    <lastmod>2026-09-24</lastmod>
  </url>
</urlset>

Each <url> entry needs a <loc>. The optional tags behave differently than most guides suggest:

• <loc> is required: the full, absolute URL including https://, on the same host as the sitemap, with special characters escaped (an ampersand becomes &).
• <lastmod> is optional, and the only optional tag Google uses. It trusts the date when it is consistently accurate, so only change it when the content of the page actually changes.
• <changefreq> and <priority> are ignored by Google. You can leave them out.

One sitemap file can hold up to 50,000 URLs and 50 MB uncompressed. Past that, split the URLs into several files and list them in a sitemap index:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-articles.xml</loc>
    <lastmod>2026-09-24</lastmod>
  </sitemap>
</sitemapindex>

Search engines read the index, then fetch each child sitemap. This XML sitemap validator does the same: it follows nested indexes up to three levels deep, reads up to 50 child sitemaps per index, and adds up the URL count across all of them. Gzip-compressed sitemaps (.xml.gz) work too.

What this sitemap checker tests

Every check runs the way a search engine would see your sitemap, as an anonymous visitor fetching public URLs:

• Sitemap discovery. When you enter a domain, the tool reads the Sitemap line in robots.txt, then tries /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml.
• Valid XML. The file must parse, with a <urlset> or <sitemapindex> root element.
• Sitemap indexes. Every child sitemap is fetched and parsed, and any that fail to load are reported.
• URL count. The total number of URLs across all sitemaps, with a sample so you can spot the wrong domain or protocol at a glance.
• Content type. A warning when the server returns something other than XML.
• Empty sitemaps. A sitemap that parses but lists zero URLs, a classic sign of a broken plugin or build step.
• robots.txt. Whether robots.txt is reachable, declares a sitemap at all, and declares this one.

Common sitemap errors and how to fix them

These are the problems that most often keep a sitemap from working, whether the validator flags them or Search Console does.

Sitemap best practices: what to include and what to leave out

A valid sitemap is the starting point. A useful one follows a few rules:

• List every page you want indexed. Product pages, articles, categories, landing pages. Our data shows that the share of your site in the sitemap is the strongest predictor of how much of it Google indexes.
• Leave out everything else. Redirects, 404s, noindex pages, filter and parameter duplicates, and staging URLs don't belong in a sitemap.
• Use canonical, absolute URLs. One protocol, one host, and the same URL your canonical tags point to.
• Keep lastmod honest. Update it when the content changes, not on every deploy.
• Generate it automatically. From your CMS or at build time, so a new page is in the sitemap the moment it is published and a deleted one drops out.
• Split large sites by page type. Separate sitemaps for products, articles and categories let you filter the Search Console page indexing report by sitemap and spot the section Google is ignoring.

How to submit your sitemap to Google and Bing

1. Declare it in robots.txt. Add Sitemap: https://yoursite.com/sitemap.xml so every crawler that reads robots.txt can find it.
2. Submit it in Google Search Console. Open the Sitemaps report, paste the URL under Add a new sitemap, and click Submit. The report then shows when Google last read the file and how many pages it discovered.
3. Submit it in Bing Webmaster Tools. Bing also supports IndexNow, which notifies it of new URLs instantly. Google does not support IndexNow.
4. Don't rely on pinging. Google deprecated its sitemap ping endpoint in 2023. An accurate lastmod and a resubmission in Search Console are how you signal changes now.

Where to find your sitemap on WordPress, Shopify, Wix and Next.js

Most platforms generate a sitemap for you. If you don't know the URL, enter your domain in the validator above and it will look in these places:

How BlogSEO keeps your new pages discoverable

Publishing is only half the job if Google never finds the page. BlogSEO writes and publishes SEO articles to your CMS on a schedule, and once you connect Google Search Console, its auto-indexing resubmits your sitemap to Google every time a new article goes live. The dashboard then shows how many of your pages Google has indexed, using the same URL Inspection data behind this study. For the rest of your site, run our free Technical SEO Audit to check indexability and on-page basics, and the Google Rank Checker to see where your pages rank once they are indexed.