How to Validate a Sitemap XML File Before You Submit I

Paste and parse the XML locally

Open the [FinderPress Sitemap XML Checker](/utilities/sitemap-checker) and paste the sitemap or sitemap-index XML. The checker runs in the browser and reports malformed markup, duplicate URL entries, and invalid date values without fetching or storing the listed pages. Fix parse errors first because later checks cannot reliably interpret a broken document.

If the live sitemap is generated by a CMS, copy the exact public response rather than an editor’s template. A proxy, cache, plugin, or error page can change what crawlers receive.

Review every URL class

Sample URLs from articles, pages, categories, products, media, locales, and paginated sections. Exclude internal search results, faceted combinations, session or tracking parameters, admin routes, preview URLs, soft-404 pages, and duplicate protocol or host variants. A URL that redirects should generally be replaced by its final canonical destination.

For very large files, validate representative groups and use server-side crawling or search-console exports to find response problems. The browser checker intentionally does not request every URL.

Use lastmod honestly

The optional lastmod value should represent the last significant modification of that URL’s content. Do not set every URL to the current time on each deployment, health check, or sitemap request. Search engines may learn to disregard dates that change without corresponding page updates. Use a valid W3C datetime value and keep the timezone explicit when including time.

A template deployment that does not materially change page content is not automatically a reason to rewrite thousands of modification dates.

Respect protocol limits

A single sitemap is limited to 50,000 URLs and 50 MB uncompressed under the standard protocol. Split larger sets into bounded files and reference them from a sitemap index. Keep all referenced files accessible to the intended crawler and avoid an index that recursively points to itself. Compressing with gzip reduces transfer size but does not increase the uncompressed protocol limit.

Separate sitemap groups can improve diagnostics—for example, articles, tools, developers, and images—but creating a file for every filter adds maintenance without helping discovery.

Submit and monitor

Publish the file at a stable HTTPS URL, reference it from robots.txt when appropriate, and submit it through the search engine’s console. Reopen the exact URL outside your admin session. Confirm the status, content type, encoding, and caching behavior. Monitor discovered URLs, read errors, indexing reasons, and server logs.

When a report shows zero discovered URLs, inspect the child sitemap response, not only the green status of the top-level index. Query strings, authentication, HTML error pages, and incorrect nesting can all produce confusing results.

Source and editorial note

References: Sitemaps XML protocol and Google Search Central sitemap overview. The FinderPress checker performs bounded text validation; it does not crawl listed URLs or guarantee discovery, indexing, or ranking.