Free Tool
    Updated 6 June 2026

    Sitemap Checker

    Inspect your XML sitemap. Find it, check its basic sitemap structure, count URLs, detect sitemap indexes, and flag suspicious or broken sub-sitemaps.

    By Deepak Shukla — Founder & CEO, Pearl Lemon

    Part of Sitemap monitoring — the full answer, the facts and the alternatives in one place.

    What This Tool Checks

    • Sitemap presence at /sitemap.xml, /sitemap_index.xml, /wp-sitemap.xml, and other common paths
    • Sitemap URL declared in robots.txt
    • Basic sitemap XML structure (urlset vs sitemapindex)
    • Total URL count per sitemap
    • File size and HTTP status of every sub-sitemap
    • Suspicious patterns (external sitemaps, dynamic generation, abnormal structure)

    Why This Matters

    A sitemap helps search engines discover the URLs you consider important, especially on large, new, or complex sites. It does not guarantee crawling or indexing, but a malformed or missing intended sitemap can make discovery and diagnosis harder.

    How to Fix Issues

    1. 1.Make sure /sitemap.xml exists and returns valid XML
    2. 2.List your sitemap in robots.txt: `Sitemap: https://example.com/sitemap.xml`
    3. 3.Use a sitemap index when you have >50k URLs (Google's limit per sitemap)
    4. 4.Include accurate `<lastmod>` values when you maintain them
    5. 5.Resubmit the sitemap in Google Search Console after fixing

    A sitemap is a machine-readable list of the URLs you consider important. It can help search engines crawl large, new, or complex sites more efficiently, but it does not guarantee crawling or indexing. This checker auto-detects the sitemap locations your domain exposes — by trying standard paths, parsing robots.txt, and following sitemap-index references — then checks basic sitemap structure and counts URLs.

    Where Google looks for your sitemap

    1. The URL declared in robots.txt via a Sitemap: directive
    2. Standard paths: /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml, /wp-sitemap.xml, /sitemap-1.xml
    3. URLs submitted manually in Google Search Console

    If your sitemap is elsewhere and is not declared in robots.txt or submitted in Search Console, search engines may still discover URLs through links, but they have no explicit signal for the sitemap you intend them to use.

    Sitemap index vs single sitemap

    A single sitemap file has hard limits: 50,000 URLs and 50 MB uncompressed. Above either limit, you need a sitemap index — a parent XML file that references child sitemaps. Many CMSes generate sitemap indexes automatically; if you maintain sitemaps yourself, split them before you exceed the protocol limit.

    Why suspicious patterns matter

    We flag sitemaps that:

    • Live on a different domain (someone else's sitemap injected via robots.txt — possible defacement)
    • Are dynamically generated with unusual structure (could be a misconfigured plugin)
    • Are abnormally large or small for the listed URL count

    These aren't always wrong, but they're worth investigating. The most common case is a CMS plugin generating malformed sitemaps that Google quietly ignores.

    lastmod — the underused signal

    Every <url> entry can include <lastmod>2026-06-06</lastmod> to report when the linked page last changed. Use the page's actual modification date, not the date the sitemap was generated. Search engines may use this information alongside other crawl signals, so inaccurate values are less useful than omitting the field.

    What to do after fixing

    1. Add the sitemap URL to robots.txt
    2. Submit the sitemap in Google Search Console (Sitemaps section)
    3. Review the sitemap report in Search Console over the following days or weeks
    4. Re-run this check after a major site change

    Methodology

    We probe seven common sitemap paths at your domain, fetch each one with a 10-second timeout, and inspect the response for sitemap or sitemap-index XML markers. We also fetch robots.txt and follow every Sitemap: directive declared there. For each sitemap discovered we capture the HTTP status, file size, URL count, and suspicious indicators such as an external host or dynamic suffix. The result is an inspection aid, not a guarantee of which sitemap a search engine will choose or a substitute for full XML schema validation.

    Frequently Asked Questions

    This tool also answers

    How do I find the sitemap of a website?

    Enter the domain above and the tool probes the standard locations — /sitemap.xml, /sitemap_index.xml — and reads robots.txt for any declared Sitemap: line, which is where most sites point crawlers at a non-standard path.

    How do I validate a sitemap XML file?

    The checker inspects the response for sitemap XML markers, identifies `urlset` or `sitemapindex` files, and reports response status, URL counts, file size, and suspicious sitemap locations. Use Search Console or a dedicated XML validator when you need full schema validation.

    Monitor this continuously with LemWatch

    A one-off free sitemap checker shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    HTTP Status Code Reference

    Understanding HTTP status codes helps you diagnose issues found by this tool: