← All free tools
FUKAMO · FREE TOOLS

XML Sitemap Checker

Discover the site’s sitemap and check URLs and dates within the fetched scope.

FREE PUBLIC URL CHECK

XML Sitemap Checker

Discover the site’s sitemap and check URLs and dates within the fetched scope.

Checks the fetched HTML of a public URL.
BEFORE YOU CHECK

Know what you are checking.

An XML sitemap lists URLs you recommend for discovery. It should represent accessible canonical pages intended for indexing, rather than every technically possible address.

When to use this check

Build the sitemap from content that is actually published. It helps discovery on large or new sites, while internal links and indexing decisions still need separate attention.

A practical example

<url>
  <loc>https://example.com/services/repair</loc>
  <lastmod>2026-09-09</lastmod>
</url>

A common mistake

A fresh date on unchanged content is not evidence of freshness. Sitemap inclusion is not confirmation that Google indexed a page.

Use the result

Compare entry counts with published canonical pages and fetch a sample of destinations. Check processing and indexing exclusions in Search Console.

What to check next
  1. Generate URLs from the same source as published content.
  2. Exclude errors, redirects, noindex pages and unfinished content.
  3. Use absolute HTTPS URLs on the preferred host.
  4. Update lastmod after a substantial content change, not every build.
  5. Reference the sitemap in robots.txt and submit it in Search Console.

Understand the result. Make the right change.

Which URLs belong in an XML sitemap

The sitemap generator should know which pages are published and intended for search. Exporting every router path can include drafts, filters and retired products.

  • Compare published canonical pages with sitemap entries in both directions.
  • Remove entries that redirect, fail or intentionally use noindex.
  • Investigate missing important pages separately from redundant variants.
How to check the URLs listed in a sitemap

An XML entry can look valid while pointing to staging or an obsolete slug. Test the destination, not just the generator’s string format.

  • Use the preferred host and final public URL.
  • Check the target’s status and canonical declaration.
  • For a sitemap index, open each linked child sitemap as well.
When to update lastmod in your sitemap

A new deployment does not mean every article changed. lastmod should come from a significant page update that you can identify.

  • Changing the main content, structured data or meaningful links can justify an update.
  • Changing only the copyright year does not.
  • Test one edited and one untouched page; omit the optional date when it cannot be reliable.
Why an accepted sitemap does not confirm indexing

Search Console accepting a sitemap confirms file processing, not indexing of every listed URL. Read the individual exclusion reasons before rebuilding the file.

  • Check that the endpoint returns sitemap XML, not a 200 HTML error.
  • Correct redirects in the inventory; investigate duplicates through canonical rules.
  • Keep useful internal links to important pages even when they appear in the sitemap.

Google Search Central — build a sitemap ↗

Primary reference: developers.google.com ↗

Frequently asked questions

Should redirects and filtered URLs be in a sitemap?

List preferred URLs you want indexed. Replace redirecting addresses with their final destinations and remove excluded pages. Include a filter only when it represents a useful, distinct landing page. Update lastmod for substantive content changes rather than every build or automated deployment.

When the task is complete

Sample sitemap entries must return accessible content with consistent canonicals and indexing intent. A successful sitemap submission confirms processing of the file, not indexing of every listed page.

FUKAMO / PRIVACY

Your privacy, your control.

These choices cover cookies and browser storage. The audit works just as well without optional storage.

Privacy policy ↗Cookies and third parties ↗