Ecommerce SEO
Faceted navigation control
The job here is specific: let the valuable filter combinations rank and keep the rest out of the index.
Faceted navigation control: what it is and what it is not
Let the valuable filter combinations rank and keep the rest out of the index. In practice that means mapping which facet combinations have real search demand, and then the harder half: deciding indexable, crawlable and blocked status per facet dimension.
Why this work exists
Teams tend to buy the visible part of this discipline and skip this, then wonder why the visible part underperforms.
Ecommerce SEO holds the whole discipline. This page is one defined piece of it.
The nearest piece of work to it is finding the bestsellers that no page is built to capture demand for. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
The useful version ends with a decision somebody can act on this month, not a report somebody files.
The gap between that and where most accounts start is why this is scoped as faceted navigation control rather than as a line inside something larger. Making the stock feed and the site agree before the customer finds out is the usual second step once it is in place.
When this is the right work
The signs that this is where the problem sits:
- Indexed URL count is many times the product count
- Filter combinations compete with each other for the same query
- Crawl logs show the budget going to parameter URLs
If none of those is true, something else is probably the constraint, and the Ecommerce SEO overview maps the alternatives. The usual neighbours are making the category pages earn their position instead of listing products and fixing the product feed, which decides more in Shopping than the website does.
What the work covers
Four things get done:
- Mapping which facet combinations have real search demand, usually the first thing to show a result, so it goes early.
- Deciding indexable, crawlable and blocked status per facet dimension, usually the first thing to show a result, so it goes early.
- Implementing the rules consistently across robots, canonical and internal links. Slow, unglamorous, and the reason the rest holds up.
- Monitoring index bloat so a new facet does not quietly multiply the problem. Boring, necessary, and the first casualty when a deadline moves.
How it runs
How this gets done without the usual two-month discovery phase.
Testing on the awkward cases
Whatever gets built is checked against the messy real examples rather than the clean ones, because the clean ones were never going to be the problem.
Writing it down for the next person
The reasoning gets recorded alongside the result, so a decision taken in March can still be defended in September by somebody who was not there.
Deciding what not to do
A list of things deliberately left alone, with the reason for each. It saves the same conversation happening four times over the following year.
What each part runs into
Taken one at a time, against real markets:
- Mapping which facet combinations have real search demand: the Austin version of this has to deal with a decision made by somebody who never visits the site
- Deciding indexable, crawlable and blocked status per facet dimension, where a Singapore engagement contends with a procurement step nobody accounted for
- Implementing the rules consistently across robots, canonical and internal links – working in Delhi NCR this means accounting for a measurement baseline that was never taken
- Monitoring index bloat so a new facet does not quietly multiply the problem, and in Bengaluru the constraint on it is a language mix the content has to match rather than assume
What not to do
Blocking all facets in robots.txt. Blocked URLs can still be indexed from links, and the ones with real demand lose the chance to rank.
Naming it upfront is the difference between a result and a report about effort.
How it is measured
Indexed URL to product ratio, and impressions from indexable facet pages. That measure is agreed before the work starts, so there is no argument about the result afterwards.
It is reported against the same definition every month, because a metric that is redefined is a metric nobody trusts.
What you end up with
In concrete terms the output is a facet rule specification per dimension, implemented consistently, with index monitoring.
Versioned, so the next pass starts from this one rather than from scratch.
How it differs by sector
What this becomes in practice depends on who it is for:
- Ecommerce and retail: the thing that changes the scope here is that margin per order decides everything, and the product feed is usually the weakest asset.
- For Manufacturing and industrial, low volume, high value, and a specification sheet that decides the deal. and that shapes how far this can go.
- B2B services brings its own limit: a buying committee, a long cycle, and attribution that has to survive both.
The industry pages carry the rest of that detail. Ecommerce and retail and Manufacturing and industrial are the two where this piece of work most often decides the outcome.
Common questions
Which facet combinations should be indexable?
Ones people search for as a phrase, which is usually a single-dimension filter within a category, such as a colour or a size. Combinations of three or more dimensions almost never have independent demand and almost always create near-duplicates. The test is whether anyone searches for it, which keyword data answers.
Is robots.txt the right way to control facets?
Not on its own. A URL blocked in robots.txt can still be indexed if it is linked, and it then appears with no content because the crawler cannot read it. The usual combination is canonical for near-duplicates, noindex for pages that must stay accessible to users, and robots.txt only for genuine crawl traps.
What happens if it does not work?
We report that it did not, with the reason. Indexed URL to product ratio, and impressions from indexable facet pages agreed before the work starts makes that an honest conversation rather than an argument.
Who does the work on faceted navigation control?
A practitioner rather than an account manager, and the same person throughout. Indexed URL to product ratio, and impressions from indexable facet pages is their number, which is the only arrangement under which the reporting stays honest. Should we block AI crawlers? goes one level down from here, and Should we use a website builder or WordPress? two.
Is the work transferable to our team?
That is the intent. A facet rule specification per dimension, implemented consistently, with index monitoring. Written for somebody who was not in the room, because the alternative is a dependency rather than a result. The common mistake is covered in Medical content standards; the expensive one in Micro-conversion.
Ask about faceted navigation control
Send what you know. We will come back with what we would check and roughly what it involves.
Start with an honest read on the gaps
One call, no sequence of follow-up emails afterwards. If the timing is wrong we will leave you to it.