Input Sitemap.xml
0 chars
Validation Results
0 errors
ToolkitBook
Identify XML syntax errors, protocol violations, and missing tags that prevent search engines from crawling your site. This validator detects duplicate URLs, incorrect date formats, size limit breaches, and character encoding issues. Get precise reports with line numbers and actionable fix suggestions. It supports standard sitemaps, sitemap index files, and specialized formats for images and video. Since all processing is local, your sitemap data never leaves your device—making it secure for use with staging or development environments. SEO professionals and developers use this tool to ensure their sitemaps are perfect before submitting them to Google Search Console or Bing Webmaster Tools.
The validator audits XML syntax, ensuring all tags are correctly matched, nested, and encoded. Every opening tag must have a corresponding closing tag, and elements must follow the hierarchical rules of the sitemap protocol. Special characters within URLs—such as ampersands (&), less-than (<), and greater-than (>) signs—must be properly escaped as `&`, `<`, and `>`. This tool highlights unescaped characters that would otherwise break search engine parsers.
Beyond basic syntax, the tool verifies protocol compliance. The `<urlset>` tag must include the official namespace declaration (`xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"`). Additionally, each `<url>` element must contain exactly one `<loc>` tag with an absolute URL, including the protocol (http or https). Relative URLs like `/page.html` are not permitted.
When present, `<lastmod>` dates are checked against W3C Datetime formats (YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+00:00). The `<changefreq>` tag is limited to specific values: always, hourly, daily, weekly, monthly, yearly, or never. The `<priority>` tag must be a numerical value between 0.0 and 1.0. Any invalid entries are flagged with specific suggestions for correction.
Sitemaps have strict constraints: a maximum of 50,000 URLs and an uncompressed file size limit of 50 MB. The validator counts your URLs and calculates file size, providing a warning if you are nearing these thresholds. It also scans for duplicate URLs; removing these is essential for efficient crawl budget management, as search engines should not be directed to the same content multiple times.
Non-ASCII characters in URLs must be percent-encoded. The tool identifies unencoded accented letters, non-Latin characters, and literal spaces (which should be represented as `%20`). It also checks for protocol consistency; if your site is secured with SSL, all URLs in the sitemap should consistently use HTTPS to avoid redirection issues.
The tool provides a summary showing the total URL count, error and warning counts, file size, and the detected sitemap type (standard, index, or extended). These metrics help verify the integrity of your file at a glance. For instance, a significantly lower URL count than expected might indicate a failure in your sitemap generation script.
Paste your sitemap.xml content into the input field and click Validate. Any issues found will appear in the results list with corresponding line numbers. Use the built-in editor to locate and fix errors directly, then re-run the validation to confirm the corrections. Once the sitemap is error-free, you can copy the corrected content or save the validation report.
Privacy is a priority. All validation logic is handled by your browser using JavaScript. Your sitemap data is never uploaded to a server, stored in a database, or tracked. This allows you to safely check sitemaps for internal development sites, staging environments, or confidential projects without risk of public exposure.
Once your sitemap passes validation, submit the URL via Google Search Console or Bing Webmaster Tools. Ensure the sitemap stays current as you add or remove pages. Only include canonical URLs; listing multiple versions of the same page can confuse search engines and dilute your ranking signals.
XML errors often cascade—one missing bracket can trigger dozens of subsequent warnings. Focus on fixing the first reported error and re-validating; often, the remaining issues will resolve themselves. For ampersands within URLs, ensure they are XML-safe (e.g., a URL parameter like `?a=1&b=2` must be written as `?a=1&b=2`). If your sitemap exceeds size limits, break it into smaller files and use a sitemap index to link them together.