Index Bloat: When Having More Pages Hurts You

TL;DR: Index bloat is when search engines have indexed far more pages than you have valuable pages. On a typical WordPress contractor site, the culprits are tag archives, author pages, attachment pages, paginated series, and filter URLs. Cleaning it up rarely produces a dramatic ranking jump, but it makes everything else you do work better.

Table of Contents

• What bloat looks like in Search Console
• The usual culprits on a WordPress site
• Noindex, canonical, or robots.txt
• Deciding what deserves an index slot
• Doing the cleanup safely
• Measuring the result

What Bloat Looks Like in Search Console

Start with one comparison. Count the pages you’d actually want someone to land on — services, cities, blog posts, about, contact. For a typical local service business that’s somewhere between 30 and 150.

Now open Search Console → Pages and look at the number under “Indexed.”

If those two numbers are close, you don’t have a bloat problem. If Search Console says 1,400 and you have 60 real pages, you do.

Two more places to look:

Pages → “Crawled – currently not indexed” and “Discovered – currently not indexed.” Large counts here mean Google is spending crawl effort on URLs it then declines to index. That’s your crawl budget being consumed by pages that produce nothing.

Performance → Pages, sorted by impressions ascending. Scroll the bottom of the list. You’ll find URLs you didn’t know existed — tag archives, attachment pages, feed URLs — each with a handful of impressions and zero clicks.

A useful additional check: site:yourdomain.com in Google, then page through the results. It’s a rough sample rather than a count, but the shape of what shows up is informative, and you’ll usually spot the pattern within two pages.

The Usual Culprits on a WordPress Site

Almost every case comes from the same short list.

Tag archives. Someone tagged 200 posts with 400 tags, and each tag generates an archive page. Most have one post on them. Individually harmless, collectively hundreds of near-empty pages.

Category archives you don’t use. Sometimes useful as hub pages if curated. Usually not curated.

Author archives. A single-author site generating an author page that duplicates the blog index.

Attachment / media pages. WordPress creates a page for every uploaded image by default. A photo-heavy contractor site can generate several hundred of these, each containing one image and nothing else. This is the most common single cause we find.

Date archives. /2023/07/ listing the posts from that month. Duplicates blog index content.

Paginated series. /blog/page/2/ through /blog/page/14/. These should generally be indexable but they shouldn’t compete with anything; problems arise when pagination is combined with filters.

Search result pages. /?s=plumber getting crawled and indexed. Infinite variations possible, zero value.

Filter and parameter URLs. ?orderby=, ?filter=, tracking parameters like ?utm_source=. Each generates a distinct URL of the same content.

Feed URLs. /feed/, /comments/feed/, per-post feeds.

Thin city pages. The one on this list that’s actually content: forty city pages with the same 300 words and a swapped place name. Bloat with a strategy attached, which makes it harder to delete and just as unhelpful.

Noindex, Canonical, or Robots.txt

Three tools, routinely used interchangeably and wrongly. They do different things.

The critical rule, and the one most commonly broken: do not block a page in robots.txt if you want it de-indexed. If Google can’t crawl it, it can’t see the noindex tag, and a URL already in the index can stay there indefinitely — sometimes shown with no description. Correct sequence: apply noindex, wait for the pages to drop out, then optionally block in robots.txt to save crawl.

Applied to the culprit list:

• Attachment pages → redirect to the parent post (most SEO plugins do this in one setting) or noindex
• Tag archives → noindex, unless you’ve genuinely curated them
• Author archives on a single-author site → noindex
• Date archives → noindex
• Search results → noindex, and disallow in robots.txt afterward
• Parameter URLs → canonical to the clean URL
• Feeds → generally leave alone; they’re not usually indexed and they serve a purpose
• Thin city pages → consolidate or improve. Don’t noindex your own strategy; fix it or delete it.

Deciding What Deserves an Index Slot

One test, applied honestly to each page type:

Would a person searching for something be satisfied landing here?

If a page can’t be the answer to any query a real person would type, it doesn’t need to be indexed. A tag archive with one post is not the best answer to anything. An attachment page containing a single photo of a truck is not the best answer to anything.

Two secondary tests:

Is it substantially different from another page you already have indexed? If not, canonical it.

Would you link to it from a service page? If it isn’t good enough to link to internally, it isn’t good enough to index.

Applied consistently, this typically cuts the indexable surface of a bloated WordPress site by 60–90%, and none of what’s removed was earning anything.

Doing the Cleanup Safely

Order matters. Bulk noindexing without checking is how sites lose pages they wanted.

1. Export before you touch anything. Search Console Pages report and Performance report by page, 12-month window. This is your undo reference.

2. Check whether any “bloat” page is actually earning. Sort your Performance export by clicks. Occasionally a category archive ranks for something real, or an attachment page has picked up links. Anything with meaningful clicks or backlinks comes off the noindex list.

3. Handle it by pattern, not page by page. Most SEO plugins let you noindex entire archive types with one toggle. Do that rather than editing hundreds of pages.

4. Change one category of pages at a time, spaced a week or two apart. If something unexpected happens, you know what caused it.

5. Update your sitemap. It should list only indexable pages. A sitemap containing noindexed URLs sends contradictory signals.

6. Fix internal links to removed pages. If your posts link to tag archives you just noindexed, that’s fine but pointless. Point them at something useful.

7. Don’t request removal in bulk. Let it happen through normal recrawling. The URL removal tool is for emergencies, and it’s temporary anyway.

Measuring the Result

Set expectations honestly: this is hygiene, not a growth lever. What you should see over four to eight weeks:

• Indexed count declines toward your real page count.
• “Crawled – currently not indexed” declines, because you stopped asking Google to evaluate pages that were never going to make it.
• Crawl stats shift. In Settings → Crawl stats, the distribution of what Google requests should move toward your real content.
• Impressions may dip slightly, then recover. Those junk pages were picking up a handful of impressions each. Losing them looks like a decline in the total impression graph and means nothing.

What you should not expect is a ranking jump on your money pages the week after. The benefit is indirect: crawl effort concentrated on pages that matter, no near-duplicate competition, and a cleaner site for every subsequent change you make.

The strongest version of this argument is what it prevents. A site with 1,400 indexed pages and 60 real ones is a site where nobody can tell what’s working. Cleaning that up makes your reporting legible, and legible reporting is what lets you make good decisions for the next two years.

Quick Recap

• Compare Search Console’s indexed count to your real page count. A large gap is bloat.
• Usual culprits: attachment pages, tag archives, author and date archives, search results, parameter URLs, thin city pages.
• Noindex to remove from search, canonical to consolidate duplicates, robots.txt only to save crawl — and never robots-block a page you want de-indexed.
• Index test: could this page be the best answer to a query someone would actually type?
• Export first, check for pages that are quietly earning, work by pattern, and change one category at a time.
• Expect hygiene benefits and legible reporting, not an immediate ranking spike.

Frequently Asked Questions

Does having more indexed pages help me rank for more things?
Only if the pages are substantively useful. Volume of thin pages doesn’t create coverage; it creates competition among your own URLs and spreads crawl effort thin.

Will noindexing pages hurt my traffic?
Not if you’ve checked that the pages weren’t earning clicks. That check is the entire safety procedure — do it before, not after.

How long does it take for pages to drop out of the index?
Days to a couple of months, depending on how often Google crawls that URL. Low-value pages are crawled rarely, so they leave slowly. That’s normal, not a failure.

Is index bloat a penalty?
No. It’s an efficiency and clarity problem, not a punishment. Nobody de-ranks you for it; you just get less value from your crawl and less clarity in your data.

What about ecommerce sites with thousands of legitimate products?
Different situation. Thousands of real product pages aren’t bloat. The bloat there comes from filter and sort combinations, which should be canonicalized or blocked depending on whether they have any search demand.