CHECK THE INPUT BEFORE EXPLAINING THE RESULT

Sitemap XML analyzer

Check sitemap XML entries, duplicate URLs and lastmod fields. Learn what to compare in the GSC Sitemaps report; parsing success does not confirm indexing.

Start a check

Calculators and snippet preview run in your browser. Syntax checks send input to this server without publishing a result page. Do not paste tokens, passwords or private client data.

Result and scope

Waiting for input. No result is not zero.

Use the check to solve a problem

Collect the actual XML response.
Check intended canonical URLs and meaningful lastmod values.
Use the workspace for bounded URL checks and saved evidence.

Continue with the related guide →Save evidence, check language groups or create tasks →

Inspect the response, not just the filename

Open the sitemap URL and copy its XML response. A file named sitemap.xml can still return an HTML error or login page. This checker reads the pasted document and flags duplicate URL entries and lastmod issues; it does not fetch every listed page.

Before removing a duplicate, decide which canonical URL belongs in the sitemap. Use lastmod only when it reflects a real page update. A clean XML result says nothing about a listed URL's HTTP status, robots rules or content quality.

In Search Console, open Sitemaps and compare the submitted address, last read and processing status. If processing succeeds but a page is missing, use Page indexing and URL Inspection for that URL rather than repeatedly resubmitting the same XML.

Read a valid file without mistaking it for indexed pages

Paste the actual XML response, not a screenshot or HTML error page. Decide first which public canonical URLs belong in the file.

On a narrow screen, scroll the table sideways to read the verification column.

What you observe	What to do	What to retain or verify
Duplicate loc or unexpected URLs	Compare with the intended inventory; remove repeated entries and intentional redirects/noindex/private URLs.	Recheck actual destination and canonical separately; this XML parser has not fetched every loc.
XML parses but Google reports a fetch problem	Inspect the submitted URL, HTTP status, content type and actual Google access evidence.	Local syntax success does not establish Google fetch, processing or indexation.

Work through the distinction

Teaching XML: two identical loc entries represent one repeated address, not two pages. A fresh lastmod on every unchanged URL does not establish fresh content.