A catalogue should serve demand, not multiply URLs
Categories, products, brands and filters can compete for the same query. Define the job of each page type and which combinations deserve indexing before scaling the catalogue.
Store-specific scope
- Category hierarchy, search intent and navigation.
- Product attributes, variants, availability, images and canonical URLs.
- Filter demand, useful combinations, parameters and duplicates.
- Pagination, unavailable products and assortment changes.
- Accurate Product/Offer data matching visible prices and availability.
- Search, basket and measurement along the purchase journey.
Deliverables
A page-type map, indexing rules, product/category template specification, impact-based backlog and acceptance checks allow verified improvements to scale without copying defects across products.
Implementation sequence
- Audit representative categories, products, brands and filters.
- Map queries and define rules per URL type.
- Verify a bounded pilot.
- Apply proven changes to the relevant templates.
- Compare indexing, search visits and recorded orders.
Quote and dependencies
Template variety, source-data quality, languages and CMS constraints matter alongside catalogue size. Development, content and ongoing support require separately agreed scope.
AGROMACHINE: category-to-product architecture connects distinct category, brand and product entry points with a buying journey.
FAQ
Should every filter be indexed?
No. A filter needs relevant demand, a distinct useful offer and duplicate control; opening every combination is not a strategy.
What happens to unavailable products?
Consider whether stock will return, whether an alternative exists and whether model-specific demand remains. Redirecting every unavailable product to the homepage does not answer these questions.
FAQ
How is the quote determined?
By the agreed work, template complexity, data and implementation constraints. A fixed tariff is not presented before the task is established.
How do we verify completed work?
Compare changes with the deliverables and run agreed scenarios. Search impressions and enquiries require separate sources and comparable periods.
Does the whole website need a rebuild?
No. Preserve correct pages and integrations. Prioritise demonstrated problems; a full rebuild needs a separate justification.