Inspect a sitemap

Audit a sitemap document: the entry set and its kind, per-entry protocol fields (loc, lastmod, changefreq, priority), duplicate and trailing-slash variants, and…

sitemapXMLSEOText

Questions people ask

What does the audit check on each entry?: The four protocol fields: loc must be present; lastmod must be a W3C date (date-only or a full ISO timestamp with zone); changefreq must be one of the documented values (always, hourly, daily, weekly, monthly, yearly, never); priority must be a number between 0.0 and 1.0. Invalid values are counted and named by entry ordinal, and the entry itself stays in the totals.
Does it visit the URLs?: Never. Inspection is structural: the tool reads and reports the document you uploaded. Whether the listed pages respond is a separate check with different tooling; the report says the same thing.
How are duplicates and variants counted?: Exact loc duplicates are counted, and the first few are named because sitemap URLs are public listing data. URLs that differ only by a trailing slash are counted separately as same-page variants, since crawlers may treat them as different pages.
What about gzip sitemaps and big files?: Gzip input is recognised by its header and inflated for reading, with a 64 MB cap on the inflated size. The upload itself can be up to 16 MB. Entries beyond 200,000 are counted but not field-audited; the report says when that cap engaged, and a document over the protocol's own 50,000 entry cap is flagged.
Is a sitemap index treated differently?: The root element decides the kind: urlset audits url entries, sitemapindex audits sitemap references. An index entry may carry lastmod and it is checked the same way. Nested indexes are listed, not followed; the tool never fetches the referenced sitemaps.
What happens to my file?: The upload is deleted as soon as processing finishes; the report stays downloadable for about 10 minutes, then is deleted automatically.

About this tool

A structural read of the sitemap protocol with the safety rails stated plainly: entity declarations refuse the run (entities are never expanded), gzip is inflated under a cap, the structure walk is iterative and depth-capped, and entries beyond 200,000 are counted without a field audit. Malformed XML refuses with the parser's line and column, and a root element that is neither urlset nor sitemapindex refuses as not-a-sitemap. Technical details: namespace prefixes are stripped, so documents carrying the standard sitemap namespace audit identically to bare ones. Per-entry field rules follow the sitemap protocol: a missing loc is a malformed entry counted by ordinal; lastmod accepts W3C dates; changefreq accepts the seven documented values; priority must fall between 0.0 and 1.0. Exact duplicates are listed (the first few, truncated), and URLs differing only by a trailing slash are counted as same-page variants. The report is one JSON file with every counter and the first named findings. Honest limits: inspection is structural only. It never requests the listed URLs, never follows nested indexes, and says nothing about whether a page responds. An entry carrying an invalid field is counted and named; it is not dropped from the totals, and the tool takes no view on whether the listed content is reachable.

File limits

Exactly 1 file per job
Each at most 16 MiB
Result at most 8 MiB

Supported formats

XML XML Text GZIP X-GZIP

Capabilities

sitemapXMLSEO

Privacy & processing

Your file is processed in an isolated job on Tooley's own infrastructure. No third-party services are involved and nothing is stored beyond the result window.

Uploads are removed as soon as processing finishes. Results stay available for about 10 minutes, then they are deleted automatically.