Sitemap Validator
Validate sitemap XML structure, URLs, lastmod values, duplicates, namespace, deployment scope, entry limits, and size.
Used to review the Sitemap protocol's default URL scope and sitemap-index location relationships. Nothing is fetched.
XML/parser status, sitemap namespace, entries, lastmod, duplicate URLs, deployment scope and protocol-limit findings will appear here.
Well-Formed XML Is Only the First Gate for a Sitemap
An XML parser can happily build a document whose root is <products>, whose sitemap tags have no namespace, or whose loc values use relative URLs. That makes it XML, not a valid Sitemap protocol document.
Validation covers the XML layer and then the Sitemap layer: correct root type, protocol namespace, direct entry elements, required loc values, optional field shapes, duplicates, file limits and deployment scope.
The Namespace URI Is Part of the Meaning
Correct protocol namespace: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> Not equivalent: <urlset>
The two roots have the same visible local name but not the same XML expanded name. Core protocol entries are recognized by namespace as well as local tag name, and only direct children in the Sitemap namespace are treated as core entries.
Where the Sitemap Is Published Defines Its Default Scope
Under the base protocol, a sitemap belongs to one site and its location can restrict which URL paths it can list. A sitemap at https://example.com/catalog/sitemap.xml naturally describes URLs under /catalog/; moving it to the site root broadens that default path scope.
Search engines can support verified cross-site sitemap workflows, so an out-of-scope URL is reported as something to review rather than silently removed. The optional deployment URL makes this check possible without fetching the file.
lastmod Is Valuable Only When It Is Trustworthy
For a URL entry, lastmod means the last significant modification of that page. It is not the time the sitemap generator ran. Google says it can use lastmod when the values are consistently and verifiably accurate.
In a sitemap index, the same element has a different object: it describes the referenced sitemap file's modification time. Do not copy a page-publish date into every child-sitemap lastmod just to populate the field.
changefreq and priority Are Protocol Fields, but Google Ignores Them
The Sitemap protocol defines valid changefreq values and a priority range from 0.0 through 1.0, so their syntax is still checked when present.
Google Search documentation states that Google ignores both values. That makes them poor fields to spend engineering time updating if Google discovery is the only consumer. Accurate URLs and trustworthy lastmod values usually matter more.
50,000 Entries and 50 MB Are File Limits, Not Site Limits
One sitemap file is limited to 50,000 URLs and 50 MB uncompressed. A sitemap index can organize many sitemap files, and its own entry count is also limited. Large sites do not need to choose between “one gigantic invalid sitemap” and “no sitemap.”
Compression reduces transfer size but does not increase the uncompressed protocol limit. The pasted source is measured after UTF-8 encoding.
Duplicate loc Values Waste Capacity and Can Hide Generator Bugs
A duplicate URL does not make the same page “more submitted.” It consumes an entry and often indicates that pagination, route normalization, slash handling, source feeds or CMS joins are producing the same canonical URL more than once.
The validator normalizes parseable loc URLs enough to remove fragments and compare their serialized URL form, then reports repeated locations with the first entry number.
Sitemap Indexes Organize Sitemap Files, Not Page URLs
A <sitemapindex> contains <sitemap> entries whose loc values point to child sitemap files. A page URL belongs inside a child urlset instead.
This sounds obvious until a generator accidentally feeds page URLs into both formats using the same template. Namespace-aware root/entry validation prevents that file from passing just because every loc is an absolute URL.
Image, Video, News and Hreflang Markup Are Sitemap Extensions
Real sitemaps can contain additional namespaced elements for specialized search features and alternate-language relationships. Those extensions should not be mistaken for unknown core sitemap tags simply because their local names are unfamiliar.
Non-core namespace URIs are listed while detailed validation stays with the relevant extension documentation rather than imitating every search vertical incompletely.
A Valid Sitemap Does Not Make a URL Indexable
A listed URL can redirect, return 404, be blocked from crawl, carry noindex, canonicalize elsewhere, require authentication, or contain low-value/duplicate content. Sitemap submission is a discovery and canonicalization signal, not an indexing command.
After protocol validation, use Search Console and targeted URL inspection when the actual question is whether Google discovered, selected and indexed a particular page.