Production urlset with lastmod
- <urlset>
- <url><loc>https://example.com/</loc><lastmod>2026-05-25</lastmod></url>
- </urlset> -> Valid
web validator
Sitemap XML Validator
Validate sitemap.xml launch and indexation signals locally: urlset/index roots, absolute loc URLs, lastmod hygiene, and crawler discovery readiness.
Results
Paste input and validate locally.- Status
- Ready when you validate.
- Indexing QA details
- Ready when you validate.
- URL/index entries
- Ready when you validate.
- First invalid loc
- Ready when you validate.
How to use this validator
- Paste the sitemap.xml or sitemap index response body you plan to expose to crawlers.
- Run validate to confirm the root type, count entries, and catch missing or malformed absolute loc URLs.
- Fix relative loc values, wrong roots, empty indexes, or stale staging hosts before submitting the sitemap in Search Console or robots.txt.
Rules & checks
Requires <urlset> for URL entries or <sitemapindex> for grouped sitemap files.
Ensures every <url><loc> or <sitemap><loc> is an absolute HTTP/HTTPS URL that crawlers can discover from robots.txt or Search Console.
Keeps indexation QA focused on structure and URL format before you submit the sitemap to Google, Bing, or a CDN edge cache.
Runs fully client-side; no URL fetching, uploads, server-side logging, or sitemap storage.
Best for typical sitemap QA payloads; split very large exports into sitemap indexes for browser review.
Inputs explained
Sitemap XML
Paste the rendered sitemap.xml body, not the URL. Include the complete <urlset> or <sitemapindex> output from production, staging, your CMS, or your static build artifact.
When to use it
- Pre-launch sitemap.xml QA for new sites, redesigns, and platform migrations
- Indexing recovery checks after Google drops submitted or discovered sitemap coverage
- CMS/static-site-generator sitemap audits before Search Console submission
- Sitemap index QA when large catalogs, blogs, or programmatic pages are split across files
Common errors
- Root element is not urlset or sitemapindex after a CMS/plugin update
- loc values are relative, malformed, or still point at staging/preview hosts
- Empty sitemap indexes or missing loc entries leave crawlers with nothing to discover
- robots.txt points crawlers at a different sitemap URL than the XML you validated
Limitations
- Structure and URL-format check only; does not fetch or verify live URL status codes.
- Does not confirm robots.txt discoverability, Search Console submission state, or Google index coverage.
- Does not validate lastmod freshness, changefreq/priority semantics, or canonical-tag alignment.
- Very large sitemaps may be slow in-browser; split exports or validate in CI for huge files.
Tips
- Use canonical production URLs in loc values, not redirecting apex/staging/preview hosts.
- Keep individual sitemap files within search engine limits (50k URLs or 50MB uncompressed).
- List the canonical sitemap URL in robots.txt and submit the same URL in Search Console.
- Refresh lastmod only when content materially changes; noisy deploy-time timestamps can dilute crawl signals.
Examples
Sitemap index for a larger site
- <sitemapindex>
- <sitemap><loc>https://example.com/sitemap-products.xml</loc></sitemap>
- </sitemapindex> -> Valid
Relative or staging loc
- <url><loc>/pricing</loc></url> -> Invalid URL (must be absolute)
- <url><loc>https://staging.example.com/</loc></url> -> Valid format, but review before production submission
Deep dive
This sitemap XML SEO validator checks urlset and sitemapindex roots, entry counts, and absolute loc URLs entirely in your browser so you can catch indexing blockers before Googlebot or Bingbot crawl a launch.
Use it alongside the robots.txt validator to verify that crawler discovery points at the same canonical sitemap URL you plan to submit in Search Console.
It is especially useful for CMS migrations, static-site builds, programmatic SEO inventories, and Google update recovery work where stale staging URLs or empty sitemap indexes can waste crawl budget.
FAQs
- Do you fetch URLs in my sitemap?
- No. This is browser-local structure and URL-format validation only; no network calls are made.
- Will this tell me if Google indexed the URLs?
- No. Use Search Console for submitted/discovered/indexed status. This tool catches sitemap XML issues before submission.
- Should I validate sitemap indexes too?
- Yes. Paste the sitemapindex XML to confirm every child sitemap loc is absolute and reviewable before crawlers discover it.
- Is my sitemap stored?
- No. It stays in your browser and clears on refresh.
Related validators
web
robots.txt Crawl Control Validator
Validate robots.txt crawl control rules, sitemap hints, and staging-to-production indexing directives locally before launch.
web
Meta Robots / X-Robots-Tag SEO Validator
Validate page-level indexability signals across meta robots, X-Robots-Tag headers, canonical targets, snippet controls, and launch noindex cleanup.
web
Canonical & hreflang Validator
Validate canonical URLs, hreflang alternates, x-default fallbacks, absolute target URLs, and duplicate-content signals before search engines cluster or localize pages incorrectly.
web
URL Validator & HTTP Link Parser
Validate HTTP and HTTPS URLs locally, parse host/path, and catch malformed links before publishing, importing, or sending them to APIs.
format
XML Validator
Validate XML with a real parser, surface well-formedness errors, and keep markup private in your browser.
format
RSS & Atom Feed Validator
Validate RSS or Atom feeds client-side—check required fields and item counts without uploads.
web
Open Graph & Twitter Card SEO Validator
Validate rendered Open Graph and Twitter/X card tags for search-result snippets, social previews, share-card images, absolute URLs, and launch QA before publishing.
Browser-local sitemap validation only. Your URLs, staging paths, and private launch XML are not uploaded, logged, or stored.
Sitemap structure-only SEO QA; does not fetch live URLs or verify Search Console indexing status.