XML Sitemap Validator
Validate XML sitemap syntax, count total URLs against Google limits, check lastmod dates, and search indexed links client-side.
| # | URL Location (<loc>) | Lastmod | Priority | Changefreq |
|---|
What is the NexTools XML Sitemap Validator?
The NexTools XML Sitemap Validator & URL Counter is a browser diagnostic tool engineered to verify XML sitemaps against official Sitemaps.org and Google Search Central technical specifications. It validates XML tags, counts URL entries against Google's strict 50,000 threshold, audits W3C datetime formatting, and identifies non-HTTPS URLs or broken characters before submitting your sitemap to Google Search Console or Bing Webmaster Tools.
Key Capabilities & Features
Google Limit Compliance
Verifies that your sitemap contains under 50,000 URLs and remains below the 50MB uncompressed ceiling to guarantee crawler acceptance.
XML Syntax Validation
Catches common XML syntax traps including unescaped characters (such as & instead of &), unclosed tags, and encoding mismatches.
Search & Filter Table
Search through thousands of indexed links right in your browser with real-time text matching and 1-click plain text exporting.
100% Client-Side Privacy
Processes XML data directly in browser memory via DOMParser. Unreleased staging sitemaps and private internal links remain offline.
Step-by-Step: How to Validate an XML Sitemap
- Input Sitemap: Upload your
sitemap.xmlfile or paste the XML text directly into the editor. - Review Diagnostics: Check the XML Syntax badge and review alerts for any unescaped characters or missing tags.
- Inspect URL Entries: Check total URL counts, ensure priority values are within 0.0 to 1.0, and verify lastmod timestamps.
- Export Clean List: Click Export Plain URLs to generate a clean .txt list for backlink analysis or crawling.
Frequently Asked Questions
What is the difference between <urlset> and <sitemapindex>?
A <urlset> file lists individual webpage URLs. A <sitemapindex> file is a master directory that points to multiple child sitemaps (used for websites with more than 50,000 pages).
Why does Google Search Console show a "General HTTP error" or "Sitemap could not be read"?
This almost always occurs due to XML syntax errors (such as unescaped query parameter ampersands in URLs) or trailing whitespace before the <?xml> declaration.
Is there any file size limit for validation?
Because this tool runs client-side inside your browser, it can parse files up to your device's memory limit (often dozens of megabytes) with zero network lag.