Start typing to search 227 tools.
Sitemap Validator
Validate XML sitemap syntax, structure, URLs, duplicates, namespaces, and optional metadata.
Sitemap looks good
What Sitemap Validator does
Sitemap Validator checks an XML sitemap before you submit or deploy it. The Sitemap Validator verifies that the XML is well formed, detects whether the document is a urlset or sitemapindex, checks the standard sitemap namespace, validates absolute URLs, finds duplicate locations, reviews HTTPS usage, and optionally checks lastmod values.
A technically valid sitemap does not guarantee indexing, but a broken sitemap can make discovery and diagnostics harder. This Sitemap Validator focuses on deterministic checks that can be performed directly on pasted XML without crawling the web or relying on an external API.
How to use
- Paste the XML sitemap. Use a complete
<urlset>sitemap or a<sitemapindex>file. - Choose validation options. Keep HTTPS checking enabled for modern production sites and enable lastmod validation when your sitemap includes modification dates.
- Run the Sitemap Validator. Trexmi parses the XML and summarizes the sitemap type, number of entries, URL validity, duplicates, namespace status, and date-format warnings.
- Review warnings separately from errors. Invalid XML and missing locations are errors. HTTP URLs, duplicate locations, or unusual lastmod values may require review depending on the site.
- Fix the source sitemap. Update the CMS, generator, or sitemap template that produced the issue instead of editing only a downloaded copy.
Why use Sitemap Validator?
Focused controls, predictable output, and a workflow designed around this exact transformation.
Readable validation
Turn XML into clear pass, warning, and error checks instead of scanning raw markup manually.
URL health checks
Validate absolute locations, HTTPS coverage, and duplicate sitemap entries.
Protocol awareness
Recognize urlset and sitemapindex documents and inspect the standard sitemap namespace.
lastmod review
Flag non-standard modification dates when lastmod validation is enabled.
Questions about Sitemap Validator
Practical details about input, output, privacy, limits, and the best way to use this tool.
01 What does the Sitemap Validator check?
It checks XML syntax, the sitemap root type, the standard namespace, entry count, absolute URLs, duplicate locations, HTTPS usage, and optional lastmod formatting.
02 Can the Sitemap Validator crawl every URL?
No. This tool validates the pasted sitemap document itself. It does not request the listed pages, test HTTP status codes, or determine whether search engines will index them.
03 Does every URL need a lastmod value?
No. The lastmod element is optional. If you include it, use an accurate modification date rather than changing it automatically when the content has not materially changed.
04 Can I validate a sitemap index?
Yes. The Sitemap Validator recognizes both urlset files containing page URLs and sitemapindex files containing links to child sitemap files.
05 Why are duplicate URLs a problem?
Duplicates add noise and can make sitemap maintenance harder. A clean sitemap should normally list each intended canonical location once per sitemap file.
How the Sitemap Validator checks XML sitemaps
An XML sitemap is a machine-readable list of URLs or a list of child sitemap files. A normal page sitemap uses the urlset root and places each page URL inside a url element with a required loc child. A sitemap index uses sitemapindex, with each child sitemap represented by a sitemap element and its own loc.
The Sitemap Validator first checks whether the XML can be parsed safely. It then identifies the root element, verifies the sitemap namespace, and collects each location. A malformed XML document should be fixed before any SEO interpretation because parsers cannot reliably read the rest of the sitemap.
Sitemap errors, warnings, and URL quality
The Sitemap Validator treats missing or invalid locations as serious problems because every sitemap entry needs a usable absolute URL. It also reports duplicate locations. Duplicate URLs are not usually useful and can indicate that a generator is combining overlapping sources or publishing the same canonical page multiple times.
HTTPS checks are shown separately because some migrations or legacy sites may intentionally contain HTTP addresses during testing. For a modern HTTPS website, the sitemap should normally contain the final canonical HTTPS versions of pages. Keep the URLs aligned with the canonical URLs published on those pages. You can verify individual preferred URLs with the Canonical URL Checker.
What lastmod means in a sitemap
The optional lastmod element should communicate when the represented page or sitemap was meaningfully modified. The Sitemap Validator checks whether supplied values look like ISO-compatible dates. It does not attempt to decide whether a date is truthful because that requires knowledge of the underlying content.
Do not update lastmod on every request simply to make a sitemap appear fresh. Accurate metadata is more useful than artificial changes. If your CMS generates lastmod values automatically, verify several representative URLs after template or plugin changes.
A practical Sitemap Validator workflow
Generate or export the sitemap from your CMS, application, or SEO plugin, then paste the complete XML into the Sitemap Validator. Fix XML syntax errors first, followed by missing or malformed locations. Review duplicates, HTTP URLs, namespace warnings, and lastmod issues. Once the document is clean, deploy the corrected source and submit the production sitemap through the search-engine tools you use.
The Sitemap Validator deliberately does not fetch remote pages. That keeps validation predictable and avoids confusing XML quality with live-page availability. For a full technical audit, combine sitemap validation with canonical checks, robots.txt review, server-status monitoring, and indexing diagnostics.
Related Trexmi SEO tools
Review crawler rules with Robots.txt Tester & Validator, inspect preferred page URLs with Canonical URL Checker, generate reciprocal localized sitemap annotations with Hreflang Generator, and inspect redirecting locations with Redirect Chain Checker.
Authoritative sitemap references
Review the official Sitemaps XML protocol and Google Search sitemap documentation when preparing production sitemap files.