When Search Console says "couldn't fetch", the problem is usually the XML itself: a mistyped namespace, an empty loc, a lastmod of month 13 day 45. Paste your sitemap here for item-by-item checks - structure, field value ranges, duplicate URLs, domain distribution - with errors pinned to line numbers, so you fix it before submitting, not after.
Pasted content is validated in this page's memory only - nothing is uploaded and there is no account; "Fetch by URL" fires only when you enter an address and click. Interface options live in this browser's localStorage; Clear my data in the footer removes them.
| Input | Full sitemap XML (urlset or sitemapindex) pasted; or fetched by URL (same-site / CORS-open only); up to 1MB |
|---|---|
| Output | Stat cards (total/dupes/errors/warnings/domains) + domain distribution bars + findings list (severity with line:column) |
| Key parameters | No options; findings capped at 200 (truncation noted); ?url= deep-links a fetch |
| Processing | Hand-written parser validating in your browser; pasted content never stored or uploaded; "Fetch" fires one GET only when you click |
| Limits | 1MB per run; up to 50k URL entries (protocol limit); 200 findings |
| Known limits | Does not verify URLs are reachable (no HEAD requests); gzipped .xml.gz unsupported (decompress first); a BOM before the declaration is tolerated with a note; sitemapindex gets structure checks only, no recursive child fetches |
Assembled from the sitemaps.org 0.9 protocol and the common Search Console rejection reasons - each rule earned its place the hard way:
urlset (or sitemapindex); a misspelled or wrongly-cased name is an immediate error.xmlns must be http://www.sitemaps.org/schemas/sitemap/0.9 (https is tolerated with a note).<url> needs a non-empty <loc>; the protocol demands absolute URLs (with scheme), relative paths error.YYYY-MM-DD, YYYY-MM-DDThh:mm:ss+zz:zz and friends; well-formed but impossible dates like 2024-13-45 or 2024-02-30 error.always / hourly / daily / weekly / monthly / yearly / never are accepted; anything else errors.1.5, -0.2 or high all error.Google's validation needs a Search Console login and verified ownership; third-party online validators ship your sitemap off to their servers. Staging-environment sitemaps and unreleased domains pasted into a third-party validator are self-inflicted leaks. This page parses everything browser-locally - it works offline, and only you know what you pasted.
Since 2019 Google honors lastmod only when it matches the page's real modification time, and ignores it wholesale once bulk-faking is detected. Auto-refreshing every lastmod to today's date daily is self-deception - skipping the field beats faking it. My take: lastmod is better absent than fake; only genuine CMS timestamps carry value.
Structure: the root must be urlset (sitemapindex is accepted too), the 0.9 namespace is checked, every url requires a non-empty loc with a valid absolute URL. Fields: lastmod against W3C formats (YYYY-MM-DD is the common one), changefreq restricted to always/hourly/daily/weekly/monthly/yearly/never, priority between 0.0 and 1.0. Plus duplicate-loc dedup, URL totals and domain distribution.
Yes, with a caveat: browser same-origin policy means only same-site sitemaps or public ones served with open CORS can be fetched. Most sites do not send CORS headers, so the main path is view-source, copy, paste - nothing less. Failed fetches report honestly; the page never pretends a sitemap passed.
An error, located by line number. Month 13, day 45 is not a real date; 2024-02-30 (no February 30) fails the same way. Well-formed but impossible dates are the classic hand-written sitemap trap - search engines ignore the whole lastmod field over it.
No. Validation runs entirely in this device's browser; pasted content is never stored or uploaded. Fetch by URL fires only when you type an address and click, and what it fetches stays in memory. Clear my data in the footer removes local interface options.