Query parameters vs path segments for facets
Faceted templates (filters, sorts) are the #1 source of index bloat. The fix is choosing the right URL form per facet.
1. Indexable facet (real demand, e.g. brand+category) → path segment. Gate: it has search volume and unique content.
2. Non-indexable facet (sort order, page size, view=grid) → query parameter + noindex or robots disallow.
3. Decision rule: a path says "this deserves to rank"; a parameter says "this is a UI state." Don't mix the message.
4. Guardrail: canonical every parameterized URL to its clean path version.
5. Guardrail: cap indexable facet combinations to 1-2 dimensions. Three-way facets explode into millions of thin URLs.
6. Gate: count generated indexable URLs before launch. If the number surprises you, it's too many.
Rollback: disallow the parameter pattern in robots.txt — instant bleed-stop while you fix templates.
Ship gate: don't publish until all boxes are checked.
Scale Engine SOP
@ScaleEngineSOP
Query parameters vs path segments for facets
Этот пост опубликован в Telegram-канале Scale Engine SOP. Подписаться можно по ссылке: @ScaleEngineSOP.