LogoTools
Runs entirely in your browser - nothing is uploaded

Checks a sitemap.xml file against the sitemaps.org protocol: well-formed XML, a recognized <urlset> or <sitemapindex> root, valid <loc> URLs, correctly formatted <lastmod>/<changefreq>/<priority> values, duplicate entries, and the protocol's 50,000-URL / 50MB-per-file limits. Paste the XML directly or drop in a file.

What it doesn't do

This examines the file's own structure and syntax. It never fetches any of the listed URLs to confirm they resolve. Doing that reliably for a sitemap with thousands of entries would be slow, and plenty of sites block automated URL-by-URL checking the same way they block other automated fetches (the SEO & Meta Tag Analyzer's notes on bot-protection challenges cover why). For link-liveness checking, a dedicated crawler is the right tool.

It also leaves a sitemap index's referenced sitemaps unchecked, on both existence and validity. Only the index file you paste in gets validated.

Frequently asked questions

Does this tool check if my URLs work (return 200)?

No, by design. It validates the XML structure and the protocol's formatting rules, and makes no network request to any URL listed in the sitemap. Checking thousands of live URLs is a crawler's job, well outside a fast client-side structural check.

Is my sitemap uploaded anywhere?

Nothing is uploaded. Parsing and validation both run in your browser using the native XML parser, and nothing is sent to a server.

What's the difference between a sitemap and a sitemap index?

A sitemap (<urlset> root) lists page URLs directly. A sitemap index (<sitemapindex> root) lists other sitemap files instead, which is what you need once a site carries more URLs than fit inside one file's 50,000-URL limit. This tool detects which one you've pasted and validates it accordingly.

Why does it warn about a namespace I didn't add?

The sitemap protocol requires the root <urlset>/<sitemapindex> element to declare xmlns="http://www.sitemaps.org/schemas/sitemap/0.9". Sitemaps generated without it often still work in practice, but search engines' own documentation specifies it, so a missing or wrong namespace comes back as a warning.

Learn More

Migrating a catalog to Shopify without losing search visibilityShopify decides part of your URL structure for you, so every product and category URL on an existing store is going to move. The redirect map is the artefact that decides whether the rankings move with them.Moving between Shopify and WooCommerce without losing the catalog or the rankingsTitles, prices and images move between Shopify and WooCommerce in an afternoon. Variants, collections, metafields and URLs do not, and the redirects have to exist before DNS changes. What maps, what has to be rebuilt, and the order to do it in.WooCommerce SEO: the structural decisions you cannot cheaply undoPermalink bases, category indexing, product schema ownership and filtered URLs are settled early on a WooCommerce store and expensive to change once indexed. Which decisions those are, how to make them, and what an SEO plugin leaves for you to do.Robots.txt, noindex, and canonical tags: which one actually keeps a page out of searchThese three get used interchangeably, and they do completely different things. Here's which one to reach for when you want a page gone from Google, and why the wrong choice usually makes it stick around.Structured data that actually gets picked up: what Google does with it, and what it ignoresJSON-LD is easy to add and easy to add wrong. Here's what schema markup genuinely influences in search results, what it never touches, and the mistakes that quietly invalidate it.Technical SEO audits that actually move rankings: five checks worth doing firstMost technical SEO audits produce a fifty-item checklist and no clear priority. Here are the five checks that, in our experience, correlate with ranking and traffic movement, and why the rest can usually wait.