map Technical SEO

Sitemap Checker

Validate XML sitemaps, count URLs, and detect broken entries.

Fetch and validate your XML sitemap for format errors, oversized files, cross-domain URLs, and stale lastmod values.

build_circle Try the free tool
star

Key takeaways

  • check_circle XML sitemaps are discovery hints; they do not guarantee indexation without crawl access and quality.
  • check_circle Malformed XML, wrong namespaces, or oversized files may be ignored silently in Search Console.
  • check_circle Sitemaps should list canonical 200 URLs, not noindex, redirect, or 404 destinations.
  • check_circle False lastmod timestamps on every URL reduce trust in freshness signals.
  • check_circle Split before hitting 50,000 URLs or 50MB uncompressed per sitemap file.
  • check_circle Sitemap indexes must resolve every child sitemap with valid XML.
  • check_circle Align sitemap URLs with robots.txt and canonical strategy to avoid conflicting signals.
map

What is Sitemap Checker?

An XML sitemap is a machine-readable list of URLs you want search engines to discover and recrawl efficiently. The sitemaps.org protocol defines loc elements, optional lastmod, changefreq, and priority fields, plus index files that point to child sitemaps for large properties. Google, Bing, and many AI-assisted discovery workflows consume sitemaps as hints, not commands. URLs still need crawl access, indexable content, and consistent canonical signals.

HeyLead Sitemap Checker fetches your sitemap or index URL, validates XML structure, counts entries, detects duplicate loc values, and flags URLs that return non-200 status codes, redirect unexpectedly, or live on the wrong host. It highlights plugin defaults that stamp identical lastmod on every URL and bloated feeds that waste crawl budget on thank-you pages, internal search results, or infinite faceted parameters. The output is a prioritized punch list for SEO and engineering.

Sitemap hygiene matters most on ecommerce catalogs, publishers, and programmatic SEO sites where one template change affects tens of thousands of loc lines. A single broken index reference can stall discovery for an entire product line after migration. Clean sitemaps also support AI visibility indirectly: when search engines index your canonical facts pages faster, retrieval systems have fresher public HTML to cite.

Use the checker after permalink changes, SEO plugin updates, headless CMS launches, and quarterly technical audits. Pair it with robots.txt validation and canonical checks so you are not simultaneously blocking paths you advertise in sitemaps. Treat sitemap maintenance as part of release management alongside internal link updates when new sections ship.

Publisher and ecommerce stacks regenerate sitemaps hourly, which multiplies small template bugs into thousands of bad loc lines. The checker quantifies damage: duplicate loc values, wrong protocol hosts, and URLs returning 403 for Googlebot smartphone. Compare sitemap inventory to internal link graphs; URLs only in sitemaps without nav links may be low priority for Google yet still consume crawl quota. After international expansion, validate hreflang extension blocks if your plugin emits them. Pair sitemap pruning with Search Console coverage exports to confirm excluded URLs leave the index over time when combined with noindex or redirects. Headless teams should validate API-driven sitemap builders with the same rigor as WordPress plugins because custom code lacks community QA.

insights

Why XML sitemap validation matters

Broken sitemaps do not always trigger obvious alerts. Search Console may show fetched with errors while teams assume discovery is healthy. Bloated sitemaps full of noindex or parameter URLs dilute priority for money pages that need fast recrawls after pricing updates. Inaccurate lastmod teaches crawlers to ignore freshness signals site-wide. For large sites, sitemap indexes are load-bearing infrastructure. When a child sitemap 404s after deploy, new SKUs or localized pages may sit undiscovered for weeks. Validation catches structural failures before they become revenue incidents, especially when migrations compress timelines and manual QA skips edge cases. Sitemaps communicate which URLs you consider important enough to name explicitly. Polluted feeds train crawlers to request thank-you pages, internal search results, and retired campaign paths. That noise delays recrawl of pricing and documentation you need AI and search systems to read after updates. Finance and ops teams feel sitemap failures indirectly when new SKUs or regions stay invisible for weeks. Validation is cheap insurance compared to emergency firefights after migration weekends. Clean sitemaps also make crawl stats interpretable when debugging indexation drops. SEO leads can use validation reports in monthly stakeholder updates to show crawl efficiency improvements tied to revenue sections. Consistent sitemap hygiene helps new hires trust crawl data when they inherit legacy plugins.

arrow_forward Accelerates discovery for new sections, SKUs, and localized pages.
arrow_forward Prevents silent XML errors that make entire feeds unusable.
arrow_forward Reduces crawl noise by excluding toxic or duplicate URLs at scale.
arrow_forward Improves trust in lastmod when tied to real publish events.
arrow_forward Supports post-migration coverage comparisons between old and new hosts.
arrow_forward Gives developers actionable URL lists to fix or exclude from feeds.
play_circle

How to use this tool

  1. 1

    Submit sitemap URL

    Usually /sitemap.xml or your SEO plugin endpoint.

  2. 2

    Parse entries

    Count URLs and spot duplicates or wrong hosts.

  3. 3

    Prune low value URLs

    Remove thin or noindex URLs from the sitemap feed.

fact_check

What this tool checks

verified

HTTP response and content-type

Confirms sitemap URLs return valid XML with correct headers.

verified

Entry count and size limits

Warns when approaching 50,000 URL or 50MB uncompressed caps.

verified

Cross-domain URL detection

Flags URLs on unexpected hosts or protocols.

verified

Duplicate URL entries

Lists repeated loc values within and across files.

verified

lastmod plausibility

Highlights suspicious uniform timestamps.

verified

Extension sanity

Basic validation on image and hreflang extensions when present.

engineering

Technical guide

Signals, standards, and what to fix when checks fail.

code

XML structure validation

Checks well-formedness, namespaces, encoding, and protocol size thresholds before Search Console silently ignores files.
code

URL hygiene inside sitemaps

Probes sample loc URLs for 200 responses, redirect loops, and canonical host alignment.
code

lastmod accuracy

Flags suspicious uniform timestamps and plugin defaults setting today on unchanged pages.
code

Index and child linking

Recursively validates sitemap indexes and counts total URLs across children.
school

Deep dive

code

XML structure and protocol compliance

Validators enforce namespaces, UTF-8 encoding, and size caps. Errors at byte one can void an entire feed. Run checker after plugin upgrades that regenerate sitemaps automatically.

Index recursion

Each child must be reachable and valid XML; broken children stall whole sections.

Compression

Gzip sitemaps are acceptable when served with correct headers and size limits.

cleaning_services

URL hygiene inside sitemaps

Only include URLs you want indexed that return 200 on canonical host. Remove noindex, redirected, and soft 404 URLs at the source generator.

CMS filters

Configure SEO plugins to exclude taxonomies and archives you noindex sitewide.

Headless feeds

API-driven sitemaps need the same status checks as WordPress exports.

schedule

lastmod credibility

Uniform lastmod undermines freshness. Tie updates to publish webhooks or content hash changes. Google ignores changefreq and priority for most practical purposes.

Bulk imports

Avoid setting today on thousands of unchanged SKUs during migrations.

News sitemaps

Google News sitemaps have stricter time windows; separate from standard indexes.

psychology

Sitemaps and AI discovery

AI systems lean on search indexes and live fetch. Faster discovery of canonical fact pages improves the HTML corpus available for citations after indexation.

Pair with llms.txt

Highlight the same strategic URLs you prioritize in sitemaps.

Prune low value

Fewer high-signal URLs beat encyclopedic sitemap dumps.

compare

Examples

thumb_up Strong examples

Clean index structure

sitemap_index.xml lists page-sitemap.xml and product-sitemap.xml, both return 200 application/xml

Index chains resolve so Google can recurse into section feeds.

Canonical product URLs only

<loc>https://example.com/products/widget-pro/</loc> without tracking parameters

One loc per indexable product aligned with on-page canonical.

Honest lastmod

lastmod updates only on posts with real content edits from CMS webhooks

Crawlers trust freshness signals instead of ignoring uniform timestamps.

Split large catalog

Four product sitemaps with 10,000 URLs each under one index

Stays under 50,000 URL and 50MB limits with room to grow.

thumb_down Weak examples

Noindex URLs included

Thank-you and cart URLs listed alongside product pages

Suggests crawl on pages you do not want indexed.

Redirect loc entries

<loc>https://example.com/old-slug/</loc> returns 301 to unrelated category

Wastes discovery slots and confuses canonical consolidation.

Malformed XML

Unclosed <url> tag causes parser failure for entire file

Google may drop the whole sitemap until fixed.

Facet explosion

50,000 filter combinations indexed via auto-generated sitemap

Drowns strategic URLs and triggers crawl bloat penalties.

rule

Best practices and common mistakes

check_circle Best practices

  • done Split oversized sitemaps before Search Console warnings appear.
  • done Automate lastmod from real publish and update events in the CMS.
  • done Submit sitemap indexes in Search Console after domain migrations.
  • done Exclude noindex, cart, and internal search URLs at generation time.
  • done Use canonical URLs without tracking parameters in loc elements.
  • done Revalidate sitemaps weekly on active commerce properties.

cancel Common mistakes

  • close Including every tag and filter URL from ecommerce faceting.
  • close Pointing loc entries at tracking parameters instead of canonical URLs.
  • close Leaving broken child sitemaps in indexes after deploy rollbacks.
  • close Assuming sitemap inclusion forces indexation.
lightbulb

Common use cases

task_alt

Audit Yoast or RankMath output after permalink structure changes.

task_alt

Clean ecommerce sitemaps bloated with filter combinations.

task_alt

Validate multilingual indexes after hreflang expansions.

task_alt

Compare old versus new sitemap coverage during migrations.

task_alt

Give developers a punch list of toxic URLs to exclude from feeds.

groups

Who should use this

person SEO leads managing large catalog or publisher sites with multiple sitemaps. person Ecommerce managers fighting index bloat from faceted navigation. person Developers implementing custom sitemap generation in headless stacks. person Agencies performing monthly technical health checks on retainers.
dictionary

Glossary

loc
Sitemap element containing a fully qualified page URL.
lastmod
Optional ISO date indicating last significant modification.
Sitemap index
XML file listing child sitemap URLs for large sites.
50k limit
Maximum URLs per sitemap file per sitemaps.org guidance.
changefreq
Optional hint Google largely ignores; focus on lastmod accuracy.
priority
Optional relative hint; does not control ranking positions.
Discovery
How search engines find URLs via links, sitemaps, and feeds.
hreflang extension
Optional sitemap module listing language alternates per URL.
quiz

Frequently asked questions

Ready for a deeper audit?

HeyLead reviews your site, competitors, and growth opportunities with no sales pressure.

Auditoría gratuita arrow_forward