Index management audit
Which URLs exist, which are indexed, which should be, and which are consuming crawl budget while ranking for nothing. The decision that governs everything else.
Why catalogue SEO is a different discipline
Because the unit of work is the template, not the page. A single category template governs thousands of URLs, so one decision propagates instantly across the catalogue. The central question is index management — which pages should exist, be indexable and be crawled — rather than how any individual page reads.
Faceted navigation is where this most commonly goes wrong, and the failure is spectacular when it does. Filters that generate crawlable URLs produce combinatorial explosions — colour by size by brand by availability — and a catalogue of ten thousand products can generate millions of near-duplicate URLs that consume crawl budget and rank for nothing.
The second recurring problem is that most e-commerce revenue ranks on category pages, not product pages, while most optimisation effort goes into products. Category pages target the terms with real demand; product pages target long-tail terms with high intent and low volume. Both matter, and the effort is usually distributed backwards.
Then there is the lifecycle problem nobody plans for. Products go out of stock, get discontinued, or are replaced by a newer model. Each of those is a decision — keep, redirect, consolidate or remove — and stores that never made the decision accumulate thousands of dead URLs that dilute the catalogue and frustrate visitors.
Thin and duplicate content is the fourth, and it is largely structural. Manufacturer descriptions used verbatim across every retailer selling the same item, variant pages differing by one attribute, and category pages with nothing but a product grid all produce pages engines have little reason to rank. That is fixable at template level, not one page at a time.
What the engagement covers
The engagement covers an index audit establishing what should exist and be crawlable, faceted navigation rules, category page strategy targeting real demand, a product lifecycle policy for stock and discontinuation, template-level content improvements, and crawl budget management across the catalogue.
Faceted navigation rules
Which filter combinations produce crawlable URLs and which do not, implemented at template level so the rule holds as the catalogue grows.
Category page strategy
Category pages built to target the terms with genuine demand, since that is where most catalogue revenue ranks and where effort is usually underweighted.
Product lifecycle policy
What happens when an item goes out of stock, is discontinued or is superseded — decided once as a rule rather than improvised per product.
Template content improvements
Fixing thin and duplicate content at the template that generates it, rather than editing pages individually across a catalogue of thousands.
Crawl budget management
Log analysis showing where crawlers spend time, so effort concentrates on the pages that earn rather than on parameter URLs nobody wants indexed.
How the engagement runs
The engagement opens with a fixed-scope index audit, because deciding which pages should exist governs everything downstream. Ongoing work then implements faceting rules, category strategy and a lifecycle policy, with crawl analysis confirming that effort is going where the revenue is.
- 01
Audit the index first
What exists, what is indexed, and what should be. On large catalogues this regularly finds an order of magnitude more URLs than anyone in the business expected.
→ An index and crawl audit by template
- 02
Fix faceted navigation
Rules for which filter combinations are crawlable, implemented in the template. This is the single change that most often reclaims a wasted crawl budget.
→ Faceting rules deployed
- 03
Build the category strategy
Category pages aimed at terms with real demand, with content that gives an engine a reason to rank them above a bare product grid.
→ A category targeting map, implemented
- 04
Set the lifecycle policy
One documented rule for out-of-stock, discontinued and superseded products, applied automatically rather than decided again for every item.
→ An automated product lifecycle policy
- 05
Verify with crawl data
Log analysis confirming crawlers now spend their time on pages that earn. Without this, index changes are assumed to have worked rather than shown to have.
→ Crawl distribution before and after
Where catalogue SEO differs from ordinary SEO
The differences here are structural rather than tactical. Ordinary SEO improves pages one at a time; catalogue SEO decides the rules that generate thousands. That makes index management the central discipline, and makes mistakes proportionally more expensive when they propagate across a catalogue.
| Ordinary SEO | Catalogue SEO | |
|---|---|---|
| Unit of work | The page | The template that generates thousands |
| Central question | How should this page be written | Which pages should exist at all |
| Biggest risk | A page underperforming | Faceting generating millions of URLs |
| Where revenue ranks | Wherever the page targets | Mostly category pages, not products |
| Content problem | Thin writing | Manufacturer copy duplicated across every retailer |
| Lifecycle | Rarely an issue | Stock, discontinuation and supersession need a rule |
Signals you need this now
You need this when Search Console reports far more URLs than you have products, when filter combinations are indexable, when discontinued products return errors or empty pages, or when product descriptions are manufacturer copy identical to every competitor selling the same item.
- Search Console shows far more URLs than you have products
- Filter and sort combinations generate indexable URLs
- Discontinued products return errors or empty pages
- Product copy is manufacturer text identical across retailers
- Category pages are a product grid with no other content
- Crawl stats show most activity on parameter URLs
- Nobody has decided what happens when an item goes out of stock
What clients see
Index and faceting fixes usually show fastest, because reclaiming crawl budget lets engines reach pages they were previously spending their time away from. Category strategy takes longer and typically produces the larger revenue effect, since that is where the commercial demand concentrates.
Where this fits
Related SEO services
Common in these sectors
The adjacent disciplines
Deciding between options
Questions about ecommerce SEO
Each answer is written to stand alone in 40 to 60 words — the shape an AI Overview or Perplexity citation lifts. Ships with FAQPage schema.
Should filter combinations be indexable?
Almost never by default. Faceted navigation generates combinatorial URLs — colour by size by brand — and a ten-thousand-product catalogue can produce millions of near-duplicates. A small number of high-demand combinations may warrant indexing; the rest should be blocked at template level.
Do product pages or category pages matter more?
Category pages carry most catalogue revenue because they target terms with real demand, while product pages capture high-intent long-tail. Most stores invest the reverse of that, which is why category strategy is usually where the largest available gain sits.
What should happen when a product goes out of stock?
It depends on whether it is returning. Temporarily unavailable items should keep their page with clear availability status; discontinued items should redirect to the closest equivalent or the parent category. What causes damage is having no rule and improvising per product.
Can we use manufacturer product descriptions?
You can, and every competitor selling the same item is using them too, which gives engines no reason to prefer your page. Rewriting the full catalogue is rarely viable, so we prioritise by revenue and fix the rest at template level.
How do we know if crawl budget is a problem?
Server log analysis. If crawlers are spending most of their time on parameter URLs, sorted variants and out-of-stock products, they are not reaching the pages that earn — and that is a measurable finding rather than a theoretical concern.
Does this cover shopping feeds and agents?
Feeds are adjacent and covered separately under our GEO work on shopping agents, since agents read structured attributes rather than pages. Most catalogue clients need both, and the underlying data quality work overlaps considerably.
Find out whether this is your constraint.
Thirty minutes with a senior strategist. We pull your live visibility while we talk and tell you plainly whether a ecommerce SEO is what you need — or whether your problem sits somewhere else.