Index bloat is when search engines have indexed a large number of low value pages from your site that you never intended to publish: tag archives, paginated duplicates, attachment pages, filtered URLs and search results. They compete with your real pages, dilute the signals pointing at them, and waste the crawl budget that should be spent on content you care about.
Finding it takes about ten minutes.
How to check
Search Google for site:yourdomain.com. Note the approximate number of results.
Now count the pages you actually meant to publish. Service pages, articles, the about and contact pages. On a typical small business site that is somewhere between fifteen and sixty.
If Google reports several times that number, the difference is bloat. A forty page site showing four hundred indexed URLs has a problem, and it is usually four or five patterns repeated many times rather than four hundred separate mistakes.
Search Console’s Pages report gives you the same information with far more detail, and it is where this should be examined properly.
The usual culprits
Tag archives
WordPress creates an archive page for every tag. A site with sixty tags has sixty archive pages, most listing one or two posts, all of them thin duplicates of content that exists elsewhere. This is the single most common source.
Attachment pages
WordPress generates a page for every uploaded image. A site with three hundred images in the media library has three hundred near empty pages, each containing one picture. They serve no purpose and they are indexable by default.
Pagination
Page two, three and four of your blog archive. These are legitimate for crawling and rarely worth indexing, because nobody searches for the second page of a listing.
Filtered and parameter URLs
Anything with a query string that produces a variant of an existing page. Sorting, filtering, session parameters, tracking parameters. Each variant can be treated as a separate URL, and a handful of filters combine into thousands of them.
Internal search results
If your search results pages are indexable, every search anyone performs can become an indexed URL. Google’s guidelines are explicit that these should not be indexed.
Why it costs you
Crawl budget is the honest but secondary reason. For a small site, Google will generally get around to everything eventually.
The real cost is dilution and confusion. When five URLs on your site cover roughly the same topic, search engines have to pick one, and the internal links, relevance signals and any external links spread across all five instead of concentrating on the one you want ranking. On competitive terms that difference decides the outcome.
There is also a quality dimension. A site where most of the indexed pages are thin is a site being assessed partly on those pages.
Fixing it
Set thin archive types to noindex. Tags and attachment pages are almost always the right call, and the fix is a single setting or a few lines in the theme.
Redirect attachment pages to the media file itself, or disable them entirely. Most modern setups do this by default and older sites frequently do not.
Handle parameters properly with canonical tags pointing back to the clean URL.
Then be patient. Removing thousands of URLs from an index takes weeks or months of recrawling. It is not an overnight change and you should be suspicious of anyone promising it will be.
What this site does
palmprojects.com publishes a deliberately small index. Author archives redirect, because a one person site does not need them. Date archives redirect for the same reason. Search results are noindex. There are no attachment pages. The Under the Hood page covers the rest of the structural decisions, and this is part of standard technical SEO work rather than an optional extra.
Questions
Should I use tags at all?
You can, as an internal navigation aid, with the archives set to noindex. The value of tags is helping readers find related material, and that works whether or not the archive is indexed. This site uses a small number of categories and no tags, because seven categories cover the ground and each has enough articles to be worth landing on.
Will noindexing pages lose me traffic?
If those pages were receiving meaningful traffic, do not noindex them. Check first in Search Console. In practice thin archives almost never receive meaningful traffic, which is precisely why they are safe to remove.
How long until I see a difference?
Index counts fall over weeks. Ranking improvements, if the dilution was material, tend to follow over a couple of months.
