Separate a product from its sellable variant
A T-shirt model and a T-shirt in one size and colour are different data levels. The sellable variant needs a stable SKU, price and stock quantity; shared photographs and descriptions may belong to the model. Decide how unavailable options appear and what happens when attributes change. Do not use product names as the only identifiers in integrations.
Build navigation around buying decisions
Categories should express recognisable choices and filters should distinguish meaningful attributes. Equipment may require compatibility and purpose; clothing needs size and material. Avoid adding empty filters just to fill the interface. Test no-result states, clearing selections, sorting and preserving state when returning from a product page.
Control addresses and product quality
Filter combinations can create many similar URLs. Decide which pages deserve search visibility and which are only interface states, then align canonical and crawling rules. Product pages need actual specifications, buying terms, images and availability rather than repeated category copy.
- Each variant has a stable SKU.
- Units agree with inventory records.
- Filters handle no-result states.
- Indexable URLs are deliberately selected.
Project questions
Should every filter combination be indexed?
No. Select useful landing pages based on distinct demand and content. Automatically indexing every combination creates duplication and unnecessary crawling.