XML Sitemap Checker & URL Extractor
The XML Sitemap Checker & URL Extractor parses a submitted sitemap, validates supported XML sitemap structure and returns up to 10,000 declared locations within bounded processing limits.
What the XML Sitemap Checker & URL Extractor checks
Distinguish well-formed supported sitemap XML from parser errors, unsupported root elements and missing required locations. The result identifies the visited document and failure class, while keeping an unavailable, oversized or interrupted response separate from an invalid sitemap verdict.
Return up to 10,000 declared loc values with their source sitemap document, normalized identity and declared lastmod value. Duplicate identities and malformed locations remain visible as entry evidence, without implying that any extracted page was fetched or accepted by a search engine.
Traverse supported sitemap indexes within explicit document, response-size, redirect, subrequest and runtime limits. The file summary shows visited documents and extracted counts, and identifies a capped or failed child traversal as partial rather than presenting the parent index as completely processed.
Report malformed locations, duplicate URL identities and invalid lastmod syntax with the source document and entry attached. A syntactically valid lastmod remains a publisher declaration, not verified freshness, page modification evidence or a promise that crawlers will revisit the location.
When to use this tool
Run the XML Sitemap Checker to audit a sitemap inventory, investigate malformed entries or verify a supported sitemap index before submission.
Example
Example: enter https://example.com/sitemap.xml to extract declared locations and flag malformed loc or lastmod values.
Issues and fixes
When parsing fails, use the reported document, failure class and parser evidence to correct the malformed XML, unsupported root or missing loc value. Preserve namespaces and required elements when regenerating the file. Publish the correction and rerun the checker; a network or size-limit failure must be resolved before XML validity can be concluded.
Correct a flagged lastmod value to a supported W3C date or date-time form, then regenerate the sitemap. The checker validates syntax only: a valid timestamp can still be stale or inaccurate, so freshness remains the publisher’s responsibility.
Extracted locations are declarations, not page audits. Use the Redirect Checker for redirect evidence, the Canonical Tag Checker for canonical declarations and the Robots.txt Tester for crawl rules. Do not remove a sitemap URL based on an unperformed secondary fetch.
What the result includes
The report separates parse status, visited sitemap documents, extracted locations, duplicates and entry-level issues without fetching every listed page.
Limitation: The checker fetches sitemap documents and parses supported XML; it does not fetch each extracted page. It returns at most 10,000 locations, reads up to 10 MiB of decoded XML per document and caps JSON responses at 5 MiB while retaining redirect, 40-subrequest and runtime limits. These lower limits protect the Worker’s 128 MB memory ceiling, CPU time, serialization and browser rendering. Large or interrupted sitemap-index trees are labelled partial with processed evidence rather than silently presented as complete. Fetch, compression, encoding and parser failures remain distinct. Successful parsing cannot establish that search engines discovered, crawled, selected or indexed any declared URL, and lastmod syntax cannot establish that the date is truthful.
Frequently asked questions
What are the XML sitemap file limits?
The sitemap protocol permits up to 50,000 locations and 50 MB uncompressed per file. This browser tool intentionally returns at most 10,000 records, reads up to 10 MiB of decoded XML per document and caps JSON responses at 5 MiB because Worker memory, CPU time, serialization and browser rendering remain bounded. A cap reached during index traversal produces a partial result rather than a false validation verdict.
Does a valid sitemap guarantee indexing?
No. A valid sitemap gives crawlers a structured list of declared locations, but it does not guarantee crawling, canonical selection or indexing. Use the extracted evidence to correct sitemap structure, then inspect page-level redirects, canonicals, robots rules and noindex directives with the related tools.
Monitor URLs over time
Turn a one-off diagnostic into ongoing index monitoring and change alerts.