Site Index Checker: How Many Pages Are Indexed

How many pages of your domain are indexed by Google and what is the coverage percentage relative to the sitemap.

0/3 today x3 limit

Website Index Checker — how many pages are in Google

Find out how many pages of your site are in Google's index and compare with the number of URLs in your sitemap.xml to get the index coverage percentage. A real whole-domain site: query via a secure proxy, just like in the PromoPilot SEO audit.

The real number of the domain’s pages in the Google index (site: query)

Counting the URLs in sitemap.xml (including nested sitemaps)

Index coverage, % (index / sitemap)

A clear interpretation of the result

Single URLs — in the page index checker

Free, with no installation or registration

How to Use

Enter the site address (domain)
Wait for the Google query and the sitemap analysis
Assess the index coverage and close the gaps

FAQ

How many pages of your domain Google keeps in the index (via the site:domain query) and what share that is of the URLs in your sitemap.xml. Low coverage means part of your pages is not being indexed.

Google does not index every page: some may be blocked by robots.txt or noindex, duplicated, of low quality, or simply not discovered yet. External links and a technical audit help increase coverage.

Here the whole site is assessed. To check a specific URL and the reasons it is not indexed, use the “Page indexing check”.

Without registration — 3 a day; after registration — 5. The limit exists because every check is a real Google query.

How the site index checker counts indexed pages

The tool reports three numbers. Pages in Google's index is the estimate Google returns for site:yourdomain — we run a real query through a proxy, with www. and any path stripped. Note that site:example.com also covers subdomains. URLs in sitemap.xml is the number of entries in /sitemap.xml at the site root; if that file is a sitemap index, up to eight child sitemaps are opened and their URLs added up. Index coverage is the first number divided by the second, capped at 100%.

Coverage	Tool verdict	What it usually means
80% or more	Excellent	Google takes almost everything you offer it
50–79%	Average	Some sections aren't getting indexed — find out which
below 50%	Low	A systemic issue: duplicates, weak internal linking, thin content or junk in the sitemap
n/a	No sitemap found	You get the indexed count only; there's nothing to divide by

Enter the address in any form — with protocol, www or a page path; the tool checks the whole domain either way. To track progress, log the three numbers once a month in one sheet. Growth in the indexed count after a sitemap clean-up shows the work paid off. A sudden drop by half or more is a reason to check robots.txt and template-level noindex straight away — the usual culprit is a release that shipped staging settings.

Only Google is checked; for Bing, use Bing Webmaster Tools. It's free: 3 checks a day without an account, 5 with a free account, 20 with Pro.

Why "indexed" and "in sitemap" don't match

There is almost always a gap, and not every gap is a problem:

An estimate, not a list. The site: number is approximate and can swing by tens of percent between queries. If Google returns no estimate, the count falls back to the results on the first page and comes out too low. Compare orders of magnitude, not exact figures.
More indexed than listed. Subdomains, filter pages, tags, pagination and old URLs show up in site: but not in your sitemap. Coverage near 100% can therefore hide index bloat.
Large sitemaps are counted partially. With more than eight files in a sitemap index, only the first eight are read — the denominator is too small and coverage looks better than it is.
Sitemap at another path. Yoast SEO serves /sitemap_index.xml, WordPress core /wp-sitemap.xml. The tool only reads /sitemap.xml and will report that no sitemap was found.
Junk in the sitemap. URLs that redirect, return 404, carry noindex or canonicalise elsewhere will never be indexed, and they drag coverage down for good reason. The sitemap analyzer shows what your file really contains.

How to find the section that isn't getting indexed

The tool counts the whole domain. When coverage is low, the next step is to find which section is lagging. You can do that by hand in Google with the same operator:

site:example.com/blog/ — indexed pages in one section. Compare with the number of posts in your CMS.
site:example.com -site:www.example.com — excludes www and shows which other subdomains are in the results.
site:example.com inurl:filter or inurl:? — checks whether filter and parameter URLs are bloating the index.
site:example.com intitle:"Page 2" — finds indexed pagination.

Section counts are as approximate as the domain count, but a gap like "400 products in the CMS, about 40 indexed" is obvious at a glance. Then dig into that section URL by URL.

Exact numbers: the Page indexing report in Search Console

Our check gives a quick estimate without account access, so it also works for competitors. For your own site, open Search Console → Indexing → Pages and filter by your sitemap — that shows coverage for exactly the URLs you care about. Below the chart, "Why pages aren't indexed" lists the reasons; work through them from the largest count down.

Reason in the report	Bulk fix
Page with redirect / Not found (404)	Drop these URLs from the sitemap and fix internal links pointing to them
Excluded by "noindex" tag	Make sure noindex is only on utility pages, and keep those out of the sitemap
Duplicate without user-selected canonical	Add canonicals for filters, sort orders and UTM copies
Discovered – currently not indexed	Strengthen internal links to the section, speed up server response
Crawled – currently not indexed	Merge thin and near-duplicate pages, add unique content

Typical coverage gaps by site type

Online store: thousands of product variants and filter pages in the sitemap. Keep categories and main product pages in it, and canonicalise filters to their category.
Blog: tags and date archives duplicate categories. Set them to noindex and remove them from the sitemap.
Multilingual site: language versions without hreflang may be treated as duplicates. Every version should reference all the others.
New site: low coverage in the first weeks is normal. Without external links, Googlebot visits rarely and the crawl queue is long.

How to raise index coverage

Clean the sitemap: only URLs that return 200, have no noindex and a self-referencing canonical.
Link sections together — a page four clicks from the home page gets indexed less reliably.
Merge thin pages with overlapping text into one strong page.
Earn external links to key sections; they bring Googlebot in more often.
Re-check in 3–4 weeks and compare coverage.

When coverage is below 100%, the tool estimates the pages missing from the index as "sitemap minus indexed" and offers paid submission for indexing, with a refund for pages that don't get indexed. How that queue works is explained in the article on indexing website pages.

From the whole site to individual pages

This check answers "how many", not "which ones". To find out whether a specific URL is indexed and what blocks it, use the Google index checker for a single page. To find every page with noindex, a wrong canonical or a redirect in one pass, you need a crawler — the SEO Audit technical crawl covers the whole site, with the first 100 pages free. The article on indexing issues in the audit explains how to read those findings.