Google will give you three different answers to "how many of my pages are indexed", and none of them is the complete truth. The Page Indexing report, a site: search and your sitemap report each count a different thing, and Google documents limits on two of the three that make an exact total impossible to obtain. The number most people chase does not exist in the form they imagine.
That is why our Bulk Google Index Checker reports per-URL status rather than a headline count: a total tells you nothing you can act on, while a list of which specific URLs are missing tells you exactly what to do next. The more useful reframe, and the one this article argues for, is that a rising indexed count is not automatically good news.
How many of my pages are indexed by Google?
The closest thing to an answer is the "Indexed" total in Search Console's Page Indexing report, for the property you have verified. It is the only figure that comes from Google's own index rather than being inferred, and it is the one to quote if someone demands a number.
Treat it as an order of magnitude rather than a count. It updates on Google's schedule with a lag of days, it covers only the property you are looking at, and a domain property and a URL-prefix property for the same site can legitimately report different totals because they cover different URL sets.
What it will not do is tell you which pages are missing. The report groups URLs by status and, per Google's documentation, its example URL lists are "limited to 1,000 items" and are not guaranteed to show every URL in a status even when there are fewer than a thousand (support.google.com, checked August 2026). On a 5,000-page site, the gap between the total and the list you can actually see is where your problem is hiding.
Why do the three numbers never match?
Because they measure different things, and two of them are documented as incomplete. Once you see what each one is actually counting, the disagreement stops being alarming.
| Comes from Google's index | Complete | Per-URL detail | Lag | |
|---|---|---|---|---|
| Page Indexing report | Totals yes, lists capped at 1,000 | Days | ||
| Sitemaps report | Only URLs in that sitemap | Days | ||
| URL Inspection API | ✓ within the daily quota | Live |
The site: operator is the one to stop trusting first. Google's own documentation says it "doesn't necessarily return all the URLs that are indexed under the prefix specified in the query", and that even for an indexed URL, appearing in those results "is not guaranteed" (developers.google.com, checked August 2026). It was built for searchers, not site owners.
The Sitemaps report is narrower than people assume in a useful way: it counts only URLs discovered through that sitemap. If your indexed total is far higher than your sitemap total, that difference is usually pages Google found some other way, which is worth investigating on its own.
Is a higher indexed count better?
Not necessarily, and this is where the metric misleads people most. A site with 40,000 indexed URLs and 400 real pages does not have a hundred times the visibility; it has an index full of filter combinations, tag archives and attribute permutations that dilute crawling and rank for nothing.
Google is direct about the cost. Its crawling documentation states that when many URLs are duplicates or unwanted, "this wastes a lot of Google crawling time on your site", and advises you to "eliminate duplicate content to focus crawling on unique content rather than unique URLs" (developers.google.com, checked August 2026).
So the count moving up can mean either of two opposite things: you published good work that got indexed, or your store started generating URL variants nobody should ever see. The number alone cannot distinguish them, which is the strongest argument for tracking a list rather than a total.
The inverse case is worth naming too. A count that suddenly drops is genuinely worth investigating, because pages leaving the index is rarely benign, and it is one of the few movements in this metric that reliably means something. The causes are surprisingly few, and why Google deindexes pages is almost always mechanical rather than punitive.
How do I get an exact per-URL answer?
Through the URL Inspection API, which returns the same verdict as the manual tool for any URL you ask about, one at a time, with no sampling. It is the only route to "which of my 5,000 pages are not indexed" rather than "roughly how many".
The constraint is throughput rather than accuracy: 2,000 inspections per property per day, and 600 per minute. A 500-page site fits comfortably in one day. A 20,000-page site takes ten days for a complete pass, which is why any sensible tooling works newest-first and lets you filter to a section. The arithmetic behind that ceiling, and the one legitimate way to double it, is in the URL Inspection API's 2,000-a-day limit.
For a single page you do not need any of that. Search Console's URL Inspection tool answers in about ten seconds, and it is authoritative because you are querying Google's index directly rather than inferring from search results. The method, and why the shortcut everyone reaches for first is the wrong one, is covered in how to check if a page is indexed by Google.
Should I worry about crawl budget?
Almost certainly not, and Google says so more plainly than the SEO industry repeats. Its crawl budget guide opens by telling most readers to leave: "If your site doesn't have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don't need to read this guide."
The thresholds Google gives for who the guide is actually for are 1 million or more unique pages, or 10,000 or more unique pages with rapidly changing content. A 300-page WordPress site publishing twice a week is not near either. If pages on a site that size are not being indexed, crawl budget is not the explanation, however often it gets offered as one.
That matters because "crawl budget" has become the default answer for any indexing question, and it sends people to optimise something that was never the constraint. When a page is genuinely not being fetched, Google attributes it to something else entirely, which is the subject of "Discovered, currently not indexed": it's your server, not your content.
What number should I actually track?
Track the count of pages you care about that are not indexed, not the total that are. It is a smaller number, it is actionable, and it goes down when you fix things, which a total never reliably does.
Building it takes one decision: define the set that matters. For most sites that is the URLs in your sitemap, minus anything you deliberately exclude from search. Check that set, and the pages missing from the index become a work list rather than a statistic.
Two derived numbers are worth watching alongside it. How many indexed URLs are not in your sitemap, which surfaces index bloat and orphaned pages. And how many pages have fallen out of the index since the last check, which is the only movement in this whole metric that should ever interrupt your week. A page dropping out has usually broken, been redirected, or picked up a noindex tag, and Google's guidance on the crawled-and-declined case is that resubmitting achieves nothing, as what "Crawled, currently not indexed" actually means sets out.
FAQ
Why does Search Console show fewer indexed pages than a site: search?
Because they measure different things and neither is complete. The Page Indexing report counts URLs in Google's index for the property you verified, updated on Google's schedule with a lag of days. A site: search is a search feature that Google documents as not necessarily returning all indexed URLs, with appearance in those results explicitly not guaranteed. Differences of a few percent are normal and not worth investigating; treat the Search Console figure as the more reliable of the two and stop reconciling them.
Is it bad if Google indexes too many of my pages?
It can be. A store generating thousands of filter, tag and attribute URLs ends up with an index full of near-duplicates that rank for nothing and consume crawling. Google's own crawling guidance says duplicate and unwanted URLs waste crawling time, and advises eliminating duplicate content so crawling focuses on unique content rather than unique URLs. A rising indexed count is only good news if the new URLs are pages you meant to publish.
How do I find which specific pages are not indexed?
Through the URL Inspection API, which returns a per-URL verdict with no sampling, at up to 2,000 inspections per property per day. The Page Indexing report cannot do this reliably: Google documents its example URL lists as limited to 1,000 items and not guaranteed to show every URL in a status. Feed your sitemap through the API and the missing pages become a work list rather than a number you cannot act on.
Does crawl budget affect how many of my pages get indexed?
For most sites, no. Google's crawl budget guide states that if your site does not have a large number of pages that change rapidly, or if pages are crawled the same day they are published, you do not need to read it. The thresholds it gives are 1 million or more unique pages, or 10,000 or more with rapidly changing content. Below that, crawl budget is rarely the reason a page is missing, despite being the most commonly offered explanation.