Index bloat is the share of your indexed pages that earn effectively no impressions. On healthy sites it sits under 20 percent. On sites demoted by a core update or the helpful content system it is usually 40 to 70 percent, and that ratio is itself the signal, because site-level quality systems judge the composition of a domain rather than its best pages. Paste your Search Console Pages export below to measure yours. Nothing is uploaded.
Free tool
Index bloat ratio
Paste the Pages export from Search Console Performance. The tool works out what share of your indexed pages earn effectively no impressions, which is the single clearest signal of a site-level quality problem. On demoted sites this figure is usually 40 to 70 percent. Nothing is uploaded.
- Search Console, then Performance, then Search results.
- Set the range to the last 3 months, then open the Pages tab.
- Export as CSV and open the file called Pages.csv.
- Paste it below. Include the header row.
Why the ratio matters more than the page count
A 50,000 page ecommerce site is not bloated because it is large. A 300 page blog can be badly bloated. What matters is the proportion of the index that does nothing, because that is what a site-level quality judgement responds to.
This is the idea Panda introduced in 2011 and every site-level system since has inherited. Weak pages do not simply fail on their own, they affect how the domain as a whole is scored. That is why pruning works as a recovery tactic, and it is also why improving your best pages while leaving the archive untouched so often changes nothing. The lineage is covered in the Google Panda update.
How to read your ratio
| Ratio | Band | Measurement (what it means for a drop) | What to do |
|---|---|---|---|
| Under 20 percent | Healthy | Composition is unlikely to be your problem | Look at technical, click displacement or competitive causes |
| 20 to 40 percent | Some drag | A contributing factor, rarely the sole cause | Consolidate opportunistically, do not prioritise it |
| 40 to 60 percent | Significant bloat | The range I see most on core update and HCU demotions | Consolidation and pruning become the core of the work |
| Over 60 percent | Severe bloat | Almost always the primary cause on a demoted site | The composition has to change, not just the writing |
A high ratio on a site that never lost traffic is not an emergency. Plenty of sites carry large dormant archives and rank fine. It becomes the explanation when a site-wide drop coincides with a core update, which you can confirm with the drop analyzer.
The 1,000 page export limit
Search Console exports at most 1,000 pages, which quietly distorts this measurement on any larger site. If you have 8,000 indexed pages and the export lists 1,000, the missing 7,000 are by definition the ones earning the fewest impressions, so they belong in the dead column rather than being ignored.
That is what the total indexed pages field is for. Take the number from Indexing, then Pages, then the Indexed count in Search Console, and the tool folds the unlisted pages in. Without it, a large bloated site can score misleadingly well.
What to do with a high ratio
- Consolidate before deleting. Why: Merging five thin pages into one good one keeps the links, history and any residual authority that deletion throws away permanently.
- Check why the page exists before removing it. Why: Some zero-impression pages are necessary. Checkout steps, policy pages and support documentation serve users without ever ranking, and removing them helps nobody.
- Look for the structural cause. Why: Tag archives, faceted URLs, pagination and programmatic templates generate bloat automatically. Fixing the generator matters more than clearing the output once.
- Noindex rather than delete where the page has a purpose. Why: Author archives and internal search results often need to exist without being indexed.
- Redirect only where a relevant target exists. Why: Mass redirecting removed pages to the homepage is treated as a soft 404 and gains nothing.
The full decision process, including how to choose between merge, noindex, redirect and delete, is in the content pruning strategy. If the drop was site-wide and matched a core update, the recovery sequence is in the helpful content recovery guide.
Frequently asked questions
What is index bloat?
Having a large share of indexed pages that earn no impressions and serve no purpose. It matters because site-level quality systems judge the composition of a domain, so pages that do nothing still affect how the pages that matter are scored.
What is a normal index bloat ratio?
Under 20 percent is healthy. Sites demoted by a core update or the helpful content system typically sit between 40 and 70 percent, which is why the ratio is a useful diagnostic on its own.
Does deleting pages improve rankings?
Removing genuinely worthless pages can help a site-level judgement, but consolidation is usually better because it preserves links and history. Deleting pages that had value permanently loses that value.
Should I noindex pages with no impressions?
Only if the page serves users but does not need to rank, such as internal search results or author archives. Noindexing pages that could be improved trades a fixable problem for a permanent one.
Why does my export only show 1,000 pages?
That is the Search Console export limit. Enter your total indexed page count from the Indexing report so the tool can account for the pages that did not make the list, which are the lowest performing ones.
High ratio and a site-wide drop?
Knowing the ratio is the easy part. Deciding which specific pages to merge, noindex, redirect or remove is where the work is, and getting it wrong costs a full reassessment cycle. Send your Search Console access and within 48 hours I will tell you which part of your index is dragging the rest down. Free, no obligation.
Get free recovery audit