E-commerce
Rebuilding a Faceted-Navigation E-commerce Catalog
This sample case study walks through how we'd approach a common e-commerce SEO and performance problem: faceted navigation generating thousands of duplicate, unindexable URLs on a mid-size catalog store.
Challenge
A catalog store's filter combinations (size, color, price range, brand) were each generating a unique, crawlable URL with near-identical content, diluting crawl budget and creating duplicate-content signals across the category structure.
Objectives
- Stop faceted navigation from generating unbounded crawlable URLs
- Preserve filter usability for shoppers without sacrificing SEO
- Improve category and product page load speed on mobile
Strategy
Separate the SEO-relevant category structure (a defined set of canonical category and subcategory pages) from the filter UI, which uses client-side state and query parameters that are explicitly excluded from indexation via canonical tags and a crawl directive.
UX/UI
Filter interactions redesigned to feel instant (client-side state) while the underlying URL strategy stays clean for search engines — no perceptible change in shopping experience for the end user.
Development
Next.js storefront with statically generated canonical category pages, a client-side filter layer, and canonical tags pointing filtered views back to their parent category page.
SEO
Product schema added for price, availability, and aggregate rating; internal linking restructured so canonical category pages — not filter permutations — carry the primary link equity.
Technical Implementation
- Canonical tag logic tied to the category taxonomy, not the current query string
- Robots directives excluding filter-parameter URLs from crawl where canonicalization alone wasn't sufficient
- Product structured data validated against Google's Rich Results test
How We'd Measure This
In a real engagement, we'd track indexed-page count, category page crawl frequency, and organic entrances to category pages before and after, using Search Console and log-file analysis — not final traffic or revenue numbers, which depend on factors outside the technical work itself.
Lessons
The technical fix (separating canonical structure from filter UI) is usually less risky and faster to ship than a full replatform, and it's worth ruling out before assuming a catalog needs to move platforms entirely.