XML Sitemap Validator

Fetch and validate your sitemap.xml file. Ensure the XML structure is correct and view exactly what URLs are being fed to search engines.

Evidence ASSESSED

Checked against: XML parsed against the sitemaps.org schema

RED TEAM 0 findings BLUE TEAM control did not hold

Sitemap Guidelines & Best Practices

A Sitemap is an XML file that lists URLs for a site along with additional metadata about each URL (when it was last updated, how often it usually changes). Search engines use this file to more intelligently crawl your site.

Strict XML: Even a tiny syntax error (like an unclosed tag or an invalid character in a URL like & instead of &) will cause Google to reject the entire file.
Size Limits: A single sitemap can be no larger than 50MB (uncompressed) and can contain a maximum of 50,000 URLs. If you exceed this, you must use a Sitemap Index.
Sitemap Index: A file that points to other Sitemaps. Example: sitemap_index.xml pointing to posts-sitemap.xml and pages-sitemap.xml.

Our Sitemap Checker retrieves your XML sitemap, validates it against the sitemaps.org schema, counts the URLs it contains, and flags the problems that cause search engines to reject or partially ignore it.

What is an XML Sitemap?

An XML sitemap is a file listing the URLs on your site that you want search engines to know about. It is a discovery aid: crawlers normally find pages by following links, and a sitemap supplements that by naming pages directly.

Each entry contains a location and may include optional metadata — when the page last changed, how often it changes, and a relative priority. In practice, search engines largely ignore changefreq and priority, and treat lastmod as a hint they will verify.

Large sites use a sitemap index: a parent file listing several sitemaps, each holding up to 50,000 URLs and no more than 50MB uncompressed. This is how sites with millions of pages stay within the limits.

Lists the URLs you want search engines to discover
Follows the sitemaps.org XML schema
Limited to 50,000 URLs and 50MB uncompressed per file
A sitemap index groups multiple sitemap files
Supplements link discovery rather than replacing it

Why XML Sitemaps Matter

Sitemaps matter most where link discovery is weakest: large sites, new sites with few inbound links, pages buried deep in the navigation, and content that is not well linked internally. For a small, well-linked site the benefit is modest.

Where they do harm is through inaccuracy. A sitemap full of 404s, redirects and non-canonical URLs signals low quality and wastes crawl budget on entries that lead nowhere. Search engines reduce their trust in a sitemap that repeatedly points at broken URLs, which undermines the reason for having one.

Most valuable for large sites and pages with few internal links
Helps search engines discover new content faster
A sitemap full of errors wastes crawl budget and erodes trust
lastmod values help crawlers prioritise genuinely changed pages
Listing non-canonical URLs sends contradictory signals

How This Sitemap Checker Works

The tool retrieves the sitemap and validates both its structure and its contents.

Validates the URL input against format and SSRF safety checks
Retrieves the sitemap file, following a sitemap index if present
Validates the XML against the sitemaps.org schema
Counts URLs and checks the file against the size and count limits
Reports structural errors and malformed entries

How to Use the Sitemap Checker

Enter your sitemap URL, usually https://example.com/sitemap.xml
Run the check to retrieve and validate the file
Confirm the XML parses without errors
Check the URL count against the 50,000 limit
Verify the sitemap is referenced from your robots.txt

Understanding Your Sitemap Results

The check reports on structure, size and content quality:

Field / Value	Meaning
`Valid XML`	The file parses and matches the sitemaps.org schema. A malformed sitemap is rejected in full, not partially processed.
`URL count`	How many entries the file contains. The limit is 50,000 per file. Beyond that, split into multiple files referenced from a sitemap index.
`File size`	Must not exceed 50MB uncompressed. Gzip compression is supported and recommended for large files.
`lastmod`	When the page last changed, in W3C datetime format. Useful when accurate. Setting every entry to today undermines its value and search engines learn to ignore it.
`changefreq and priority`	Optional hints that Google has stated it does not use. Harmless to include, but they change nothing.
`Sitemap index`	A parent file listing other sitemaps. An index may itself reference up to 50,000 sitemaps, which is how very large sites stay within the limits.

Common Problems & How to Fix Them

Every dead entry wastes crawl budget and erodes trust in the sitemap as a whole.

Generate the sitemap dynamically from your live content rather than maintaining a static file. If it is generated on a schedule, ensure removed pages are excluded on the next build.

A sitemap should list final destination URLs. Entries that redirect force an unnecessary extra request and signal that the sitemap is out of date.

Update the entries to the current URLs after any migration. This is the most commonly missed step when URLs are restructured.

Listing a URL whose canonical points elsewhere sends contradictory signals — the sitemap says index this, the canonical says index something else.

Include only self-canonical URLs. Parameter variants, session URLs and paginated duplicates should not appear.

Files over either limit are rejected entirely rather than truncated.

Split the content into several sitemaps, each under both limits, and create a sitemap index referencing them. Organising the split by content type also makes indexing coverage easier to diagnose per section.

Crawlers must discover the sitemap through search console submission alone, which delays discovery and misses crawlers you have not registered with.

Add the absolute URL to robots.txt:
Sitemap: https://example.com/sitemap.xml

A file where every entry claims to have changed today is worthless as a prioritisation signal, and search engines discount it.

Emit the genuine last modification time per page. If your CMS does not track it accurately, omitting lastmod entirely is better than supplying a false value.

Best Practices

Generate the sitemap dynamically from live content
Include only canonical URLs that return a 200 status
Keep each file under 50,000 URLs and 50MB uncompressed
Use a sitemap index for large sites, split by content type
Reference the sitemap from robots.txt with an absolute URL
Provide accurate lastmod values, or omit the field entirely
Regenerate after any content migration or URL restructure

Security Recommendations

Remember the sitemap is public and enumerates your URL structure for anyone who reads it
Never list administrative, internal or authenticated URLs
Review generated sitemaps for endpoints that should not be publicly enumerated, since automatic generation frequently includes more than intended
Be aware attackers fetch sitemaps early in reconnaissance as a complete site map
Ensure the sitemap generator cannot be manipulated to include arbitrary URLs through user-supplied content
Serve the sitemap over HTTPS so its contents cannot be modified in transit

Frequently Asked Questions

It is most valuable for large sites, new sites with few inbound links, and pages that are poorly linked internally. A small, well-linked site gains little, but a sitemap is inexpensive to provide and rarely harmful when accurate.

Up to 50,000 URLs and 50MB uncompressed per file. Larger sites split content across multiple sitemaps referenced from a sitemap index, which may itself list up to 50,000 sitemaps.

Google has stated it does not use either. They are part of the schema and harmless to include, but they have no effect on crawling or ranking. Accurate lastmod values are the only optional field that carries real weight.

Only canonical pages that return 200 and that you want indexed. Exclude redirects, parameter variants, noindex pages and anything requiring authentication. Accuracy matters more than completeness.

Conventionally at /sitemap.xml, though any location works provided it is referenced from robots.txt or submitted through search console. A sitemap can only list URLs on the same host from which it is served.

Whenever content changes. Generating it dynamically means it is always current. For a static file, regenerate on a schedule that matches how often you publish, and always after a migration.

No. A sitemap aids discovery; it does not compel indexing. Search engines still apply their own quality assessment, and pages they judge low value will remain unindexed regardless of being listed.