Shahid Ali.WhatsApp

how much of your sitemap is indexed

shahid ali › tools › sitemap index coverage

How much of your sitemap has Google actually indexed?

Your sitemap is the list of pages you want in Google. This tool reads that list, inspects every URL through the official Search Console API, and gives you one honest number: the share Google agreed to keep. Under it, the breakdown that explains the gap, and for a sitemap index, the table that shows which child sitemap is dragging the average down.

  • Nothing is uploaded. Your results exist in this browser tab and nowhere else.
  • No account here. You sign in to Google, not to me. I never receive the token.
  • Read only. The permission requested cannot change anything in your Search Console.

Run a coverage check

  1. Connect

    Sign in with Google. Read only.

  2. Property

    Pick the Search Console property.

  3. Sitemap

    Pick a known sitemap or paste a URL.

  4. Report

    Get the percentage and what makes it up.

  1. 01 Connect Search Console

    Read-only access, granted by you to your own account, in a Google popup. The token never leaves this tab.

    not connected
    Advanced: use your own OAuth client ID

    For anyone who would rather not grant access to my app at all. Create a Web application OAuth client in your own Google Cloud project, enable the Search Console API, addhttps://www.shahidali.co as an authorised JavaScript origin, and paste the client ID here. It is held in memory for this tab only.

  2. 02 Pick a property connect first

    Only properties this Google account is verified on will appear.

  3. 03 Pick the sitemap connect first

    Which sitemap to check

    The list loads by itself. A sitemap index is read child by child, and the report breaks coverage down per child sitemap.

    no sitemap chosen

    Browsers cannot read another site's sitemap, so sitemap XML is fetched by a reader on this domain that keeps no copy and writes no log. Your Search Console data never goes near it.

  4. 04 Run it connect first

    Every URL in the sitemap is inspected through the official URL Inspection API, paced automatically under Google's 600-a-minute limit. Failed requests get one retry when the run ends. URLs outside the selected property are skipped before any quota is spent on them.

How to read the number

The percentage is the headline, and the breakdown under it is the diagnosis. Two sitemaps can both sit at 60 percent indexed for completely different reasons, and the reasons decide what to do next.

  • A gap made of crawled, currently not indexed means Google fetched the missing pages and declined to keep them. That is a quality and trust decision, not a submission problem, and resubmitting changes nothing. The guide covers what actually moves it.
  • A gap made of discovered, currently not indexed means Google knows the URLs and has not fetched them. That is crawl priority: internal links, server speed, and what Google expects from the site. Different problem, different guide.
  • A gap made of unknown to Google on URLs your sitemap has carried for months is the quiet one: Google either never met them, or met them long ago and let the record go.The two cases need opposite fixes.
  • Redirects, alternates and noindex rows are often healthy. A sitemap should not list them, but their presence in the report is housekeeping, not an emergency.
  • An uneven per-sitemap table is the most useful shape of all. When the blog sitemap sits at 95 percent and the product sitemap at 40, the site does not have an indexing problem, the catalogue does, and that is exactly the situation store owners bring me most. The pattern behind it is in the store indexing guide.

Where your data actually goes

Same rules as every tool on this site. The Google sign-in happens in Google's own popup and the token stays in this tab's memory. Every inspection request goes straight from your browser to googleapis.com, and the report is built in the page, so reloading destroys it. Nothing is written to any server, mine included.

One honest exception: browsers are not allowed to read another site's sitemap, so the sitemap XML itself is fetched by a small reader on this domain that returns the file and keeps no copy, writes no log line, and never sees a Google token or a result. The only thing it handles is a sitemap address that is already public. Full detail on the privacy page.

The limits, stated plainly

  • 2,000 inspections per property per day. Google's cap, not mine. A sitemap bigger than that gets checked child by child, or across days.
  • Verified properties only. The coverage verdicts come from the URL Inspection API, which only answers for properties your Google account is verified on. Public sitemaps of other sites can be read, but not scored.
  • It measures, it does not submit. The API is read only. If the report shows a backlog worth fixing, submission still means the button in Search Console, roughly a dozen URLs a day, by hand.
  • Need the per-URL table instead of the rollup? Thebulk index checker runs the same API over the same sitemap and gives you every row, sortable and filterable.

Why this exists

Every indexing job I take starts with exactly this measurement: how much of what the client wants indexed actually is. On client properties I run it every morning against a tracked ledger, and thecase studies are built from those snapshots, catalogue by catalogue. This is the same first step, given away, because knowing the size and shape of the gap is the part you should never have to pay for. Closing the gap is wherethe actual work starts.

Straight answers

What does sitemap index coverage mean?

Sitemap index coverage is the share of URLs in your XML sitemap that Google actually holds in its index. A sitemap is the list of pages you want indexed; coverage is how much of that list Google agreed to. The two are rarely the same, because submitting a URL does not oblige Google to store it. This tool measures the gap URL by URL and tells you which statuses make it up.

Why is this different from the sitemap report in Search Console?

Search Console tells you a sitemap was read and gives you counts and reasons at the report level, but its example URL lists are capped, and the counts do not name which specific URLs are out. This tool asks the URL Inspection API for every URL in the sitemap individually, so the percentage comes with the per-URL evidence behind it, exportable as CSV. Same Google data, different resolution.

What percentage of a sitemap should be indexed?

There is no universal number, and anyone quoting one is guessing. On the client work behind this site, a small site with real pages sits near 100 percent, healthy blogs land in the 90s, and large store catalogues run lower because Google rarely stores every variant. What matters more than the number is the pattern beneath it: a gap made of crawled, currently not indexed is a content and trust problem, while a gap made of discovered is a crawl priority problem.

Does this tool spend my daily inspection quota?

Yes. Google allows 2,000 URL inspections per property per day, and every URL this tool checks uses one, the same pool as the bulk checker or anything else calling the API on that property. The tool tells you how many URLs a sitemap holds before it spends anything, and it refuses to start a run bigger than the daily quota.

Can I check a competitor's sitemap coverage?

No. Reading a public sitemap is easy; the coverage verdicts come from the URL Inspection API, which only answers for properties your own Google account is verified on. That constraint is Google's, not mine, and it is also the guarantee that nobody can run this tool against your site either.

Number lower than you expected? Send me the export on WhatsApp and I will tell you what the pattern is, free, before anyone talks about money.