XML Sitemap Validator
Paste a sitemap's XML to check it in your browser: well formed, the right root and namespace, a loc on every entry, absolute URLs, duplicates, dates and the 50,000 URL limit. It does not fetch the URLs.
How to use the sitemap validator
Paste the XML, fix what it flags, then see what Google indexed.
Open the sitemap
Load the sitemap URL named in your robots.txt Sitemap line or submitted in Search Console, view the source and copy the XML. This tool reads URL sitemaps, which start with <urlset>, and sitemap index files, which start with <sitemapindex>.
Run the validation
Select Validate Sitemap. The XML is parsed in your browser and every <url> or <sitemap> entry is checked against the sitemaps.org protocol. Nothing is uploaded.
Read the summary and entries
Errors are things a parser cannot use, such as broken XML or a missing or relative loc. Warnings cover duplicates, malformed lastmod dates and out-of-range changefreq or priority values. The first 20 entries show by default.
Check the result in Search Console
Submit the sitemap in the Sitemaps report, then filter the Page indexing report by that sitemap to see how many of its URLs Google has indexed and why the rest are not.
What does an XML sitemap do?
An XML sitemap lists the URLs you want search engines to crawl, with optional dates showing when each last changed. It is a discovery aid: Google calls submitting one "merely a hint", and its sitemap overview says a sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed." The format comes from the sitemaps.org protocol, and Google documents its own limits on top of it.
Not every site needs one. Google says sitemaps help most when a site is large, new with few external links, or heavy in video, images or news, and that a site of "about 500 pages or fewer" that is "comprehensively linked internally" may not need one. Our glossary entry on XML sitemaps has the short definition; this page covers the rules the validator above checks and the ones it cannot.
What are the sitemap size limits?
One sitemap file can hold 50,000 URLs or 50MB uncompressed, whichever it hits first. Past that, split the URLs across several files and list them in a sitemap index, a file whose root element is <sitemapindex> instead of <urlset>. The other hard rules come from the protocol: every data value must be entity-escaped, so & in a URL becomes &, and "all URLs in a Sitemap must be from a single host."
| Limit | Value | Source |
|---|---|---|
| URLs in one sitemap | 50,000 | |
| Size of one sitemap | 50MB uncompressed | |
| Length of a loc value | Under 2,048 characters | sitemaps.org |
| Sitemaps listed in one index file | 50,000 (and 50MB) | sitemaps.org |
| Sitemap index files per site in Search Console | 500 | |
| Encoding | UTF-8 |
Location matters as well. A sitemap at the site root can cover every URL on the site, while one in a folder affects only URLs beneath that folder unless you submit it through Search Console, according to Google's guide to building a sitemap.
Does Google use lastmod, changefreq and priority?
It uses lastmod and ignores the other two. Google's documentation says it "ignores <priority> and <changefreq> values", and a June 2023 Search Central post repeated that Google "still doesn't use the changefreq or priority elements at all." Lastmod helps Google schedule recrawls of URLs it already knows, but only when it is "consistently and verifiably" accurate. The date should mark the last significant change, which Google defines as the main text, structured data or links, not a sidebar or footer, and the dates have to "consistently match reality." A CMS that stamps every URL with the day the sitemap was generated fails that test.
The validator still checks changefreq and priority against the protocol, which allows seven changefreq values and priorities from 0.0 to 1.0 with a default of 0.5, because a malformed value is a protocol error even when Google skips it. The same post deprecated the sitemap ping endpoint, which Google said would stop working six months later, so submit through Search Console or a Sitemap line in robots.txt instead.
Which URLs belong in a sitemap?
The ones you want in search results. Google says to "include the URLs in your sitemap that you want to see in Google's search results," and its guide to consolidating duplicate URLs counts sitemap inclusion as a weak canonical signal. That rules out URLs that redirect, carry noindex, are blocked in robots.txt or duplicate another page through parameters, since listing them contradicts the redirect, the noindex or the canonical. Write every URL in full, protocol and host included; Google asks for "fully-qualified, absolute URLs". The robots.txt validator checks that the Sitemap line pointing here is a full URL too.
What this validator checks, and what it cannot
It parses the XML with your browser's own parser, so broken markup and unescaped ampersands fail at once. It then checks the urlset or sitemapindex root and namespace, a loc on every entry, absolute URLs, loc length, exact duplicates, lastmod format, changefreq and priority values, and the 50,000 entry limit. A sitemap index is reported as an index, with each child sitemap listed and its loc and lastmod checked; paste each child sitemap to check the URLs inside it. Lastmod passes in any of the W3C Datetime forms, from a year alone (2026) or a year and month (2026-11) to a full timestamp. It does not measure file size or encoding, fetch the listed URLs, or check that they are canonical and indexable.
For the live picture, submit the file in Search Console's Sitemaps report, which shows a status of Success, Has errors or Couldn't fetch and a count of discovered pages, then filter the Page indexing report by that sitemap to see how many of its URLs are indexed. The sitemap section of our technical SEO audit checklist sets those checks next to the crawling and canonical work that decides whether submitted URLs get indexed.
XML sitemap questions.
Limits, lastmod, pinging, indexing and whether a small site needs one.
How many URLs can one sitemap hold?
Up to 50,000 URLs or 50MB uncompressed, whichever comes first, according to Google's sitemap documentation. Larger sites split their URLs across several sitemaps and list them in a sitemap index file, which under the sitemaps.org protocol can itself list up to 50,000 sitemaps.
Does Google use priority and changefreq?
No. Google's documentation says it ignores both, and a June 2023 Search Central post said Google "still doesn't use" them at all. Google does use lastmod to schedule recrawls of URLs it already knows, but only when the dates are consistently and verifiably accurate.
What date format does lastmod use?
W3C Datetime, which allows a plain date such as 2026-11-14 or a full timestamp with a time zone such as 2026-11-14T15:30:00+00:00. The date should mark the last significant change to the page, meaning its main text, structured data or links, not a sidebar, footer or copyright year.
Can I still ping Google when my sitemap changes?
No. Google deprecated the sitemap ping endpoint in June 2023 and said it would stop working six months later, after which requests to it return a 404. Submit the sitemap in Search Console or add a Sitemap line to robots.txt, and Google refetches it on its own schedule.
Will a sitemap get my pages indexed?
Not by itself. Google says a sitemap does not guarantee that the URLs in it will be crawled or indexed, and the Sitemaps report counts discovered pages, not indexed ones. Filter the Page indexing report by sitemap to see how many listed URLs are in the index and the reason given for each that is not.
Do small sites need a sitemap?
Often not. Google says a site of about 500 pages or fewer that is comprehensively linked internally may not need one, while large sites, new sites with few external links and sites heavy in images, video or news benefit most. If you keep one on a small site, keep it accurate, since sitemap entries count as a canonical signal.
Valid sitemap, pages still not indexed?
A clean sitemap only gets URLs discovered. Whether they are indexed depends on robots rules, canonicals, redirects and the pages themselves. Our technical SEO audit checklist covers each, in the order problems block rankings.
What to do next.
Run these next
All 25- Robots.txt ValidatorValidate your robots.txt syntax and crawl directives
- Canonical Tag CheckerVerify canonical URL implementation and detect duplicate content issues
- Redirect Chain CheckerDetect redirect chains and loops that waste crawl budget
- Internal Link AnalyzerMap internal link structure and find orphaned pages
Read next
Every page, not one
Check the whole site
The monthly plan crawls every page of the site and prices each fix by what the page earns, so the one that matters comes first.
See the monthly plan