Ecommerce Information Architecture
Ecommerce Keyword Clustering
Build a category tree that matches real intent, decide which facets deserve indexable pages, write PLP and PDP content that answers buyer questions, and plan seasonal clusters that compound every year.
Scope and principles
This guide covers clustering for ecommerce catalogs. We focus on category trees, facet strategy, the split between PLP and PDP content, and seasonal clusters. Local SEO is out of scope. The goal is a clean information architecture that scales and still feels helpful to shoppers.
- Google Search Central on helpful content
- Structured data basics on Search Central and Schema.org
- Core Web Vitals on web.dev
- Crawlable links and sitemaps on links and sitemaps
Category trees that mirror intent
Your category hierarchy is a cluster map. It must reflect how shoppers browse and search. Keep the depth small, the names natural, and the hubs descriptive.
Starter pattern
- Department → Category → Subcategory → Filters
- Each node has one job and a short definition
- Use shopper language in titles and slugs
Example: /men/shoes/running/ then filters like size, width, brand.
Tree hygiene
- No overlap between siblings
- Use consistent singular or plural in slugs
- Avoid empty nodes and dead ends
Sample tree and how it maps to queries
| Node | Example slug | Query intent | Notes |
|---|---|---|---|
| Department | /men/ | brand plus department | Landing and navigation only |
| Category | /men/shoes/ | men shoes, men footwear | PLP hub with ItemList schema |
| Subcategory | /men/shoes/running/ | men running shoes | PLP with buyer guide snippet |
| Facet combo page | /men/shoes/running/wide/ | running shoes wide | Index only if high value |
| PDP | /men/shoes/running/gel-2000/ | model searches | Product schema with offers |
PLP vs PDP content
PLPs help shoppers choose a set. PDPs help shoppers choose a product. Treat them as different jobs.
PLP must haves
- Short intro that defines scope and who the page is for
- Filters above the fold with readable labels
- Sort options like relevance, price, newest
- Helpful block under the grid with size guides or fit tips
PDP must haves
- Clear title, images, video, and feature bullets
- Specs table with consistent fields
- Availability, price, shipping and returns
- Cross links to sibling models and accessories
Copy split
- PLP answers which options, how to choose, what matters
- PDP answers is this the one, how does it fit, what do I get
- Do not paste the same buying guide on every PDP
Facets and filters
Facets are powerful. They also create crawl traps. Decide which combinations deserve their own indexable pages and which remain filters only.
Facet policy
| Facet type | Indexable | Routing | Notes |
|---|---|---|---|
| Primary intent facets like brand, material, fit | Sometimes | Clean path like /running-shoes/wide/ | Create only when demand and unique value exist |
| Price, availability, sort | No | Parameters | Keep crawlable UI but noindex or canonical back |
| Multiple facets combined | Rare | Static path for a few curated combos | Create landing pages for high demand sets only |
Safe defaults
- Use canonical to the base PLP for low value filters
- Block infinite combinations created by pagination plus filters
- Expose a few curated facet landings with real copy and links
Why it works
- Search engines want helpful pages not parameter noise
- Curated facet landings behave like subcategory pages
- Users still get a flexible UI for exploration
Keep links crawlable and predictable. See Google notes on crawlable links.
Sorting and pagination
Sort and pagination exist for shoppers. Treat them as UI states, not new indexable pages.
- Keep one canonical for the PLP page one
- Use parameters for sort and page, and avoid indexation on deep pages
- Provide a view all option only if performance allows
- Keep infinite scroll usable and crawlable with proper links to subsequent pages
Focus on usability and speed. Review Core Web Vitals on web.dev.
Indexation and canonicals
Declare one canonical per intent. Consolidate duplicates. Keep your sitemap clean.
Canonicals
- PLP page one self canonical
- Facet parameters canonical to the base PLP unless curated
- PDP self canonical with variants handled by one page or clean variant URLs
Sitemaps
- Include only canonical URLs
- Split large catalogs into multiple sitemap files
- Update promptly after major changes
See sitemaps overview.
What to avoid
- Thin search result pages in the index
- Endless parameter combinations
- Duplicate PDPs for color or size that add no value
Seasonal clusters
Seasonal demand repeats. Treat seasons like mini clusters that connect to evergreen hubs.
Structure
- Evergreen hub like /gifts/ or /back-to-school/
- Child pages for key themes or audiences
- Link back to core categories and top sellers
URL strategy
- Use persistent URLs for seasonal hubs
- Refresh content yearly and update dateModified
- Use banners and internal links to surface seasonal hubs from PLPs
Planning
- Publish at least 4 to 8 weeks before the peak
- Keep last year’s winners and update stock
- Retire pages with redirects only when themes change for good
Internal links and breadcrumbs
Internal links move authority and help users. Breadcrumbs explain where the shopper is in the tree.
- Every PDP links up to its PLP and to 2 or 3 sibling products
- Every PLP links up to its parent and down to key curated facet landings
- Use BreadcrumbList structured data and visible breadcrumbs
Keep links as normal anchor tags. See Google on crawlable links.
Structured data
Match schema to visible content. PLPs are lists. PDPs describe a product.
PLP ItemList example
{
"@context":"https://schema.org",
"@type":"ItemList",
"itemListElement":[
{"@type":"ListItem","position":1,"url":"https://example.com/men/shoes/running/gel-2000/"},
{"@type":"ListItem","position":2,"url":"https://example.com/men/shoes/running/peg-40/"}
]
}PDP Product example
{
"@context":"https://schema.org",
"@type":"Product",
"name":"Gel 2000 Men's Running Shoe",
"image":["https://example.com/img/gel-2000.jpg"],
"description":"Responsive cushioning, breathable upper, road-ready outsole.",
"sku":"GEL2000-M",
"brand":{"@type":"Brand","name":"Acme"},
"offers":{"@type":"Offer","priceCurrency":"USD","price":"129.00","availability":"https://schema.org/InStock","url":"https://example.com/men/shoes/running/gel-2000/"}
}Read structured data guidance on Search Central.
Monitoring and iteration
Measure by cluster and by folder. Adjust where shoppers struggle.
Track
- Clicks and impressions by category folder
- CTR on PLPs and PDPs for head terms and model terms
- Site search queries that suggest new subcategories
Improve
- Expand or prune curated facet landings
- Refresh PLP intros and PDP specs with clear language
- Speed wins through image compression and lazy load
Governance
- Change log for redirects and slug updates
- Quarterly audit of duplicates and thin pages
- Sitemap checks after large catalog changes
FAQ
Which facets should become indexable landing pages
Choose facets that match real search demand and that deserve a short buyer guide. Examples include fit, material, style, or brand in some categories. Keep a small set per category.
Should color or size get separate URLs
Usually no. Treat them as variants on the same PDP. Use one canonical PDP and update price and inventory dynamically on the page.
Can I list all combinations in the sitemap
No. Sitemaps should include canonical URLs only. Curated facet landings are fine if they are real pages with value.
How do I handle pagination for large PLPs
Keep page one canonical. Use parameters for page and sort. Make sure next pages are reachable with real links and that performance is acceptable.
Do I need buying guides on every PLP
Add a short block under the product grid with 3 to 5 tips and links to deeper guides. Keep it specific to the category.
Where do comparison pages live for brands
Under an alternatives or brands hub if comparisons help users choose. Keep tone factual and link back to PLPs and PDPs.