Site Architecture
Site architecture is the catalog organized as pages, the silent ranking system deciding what authority reaches.
What site architecture is
Site architecture is how the catalog is organized as pages: the hierarchy from homepage through categories to products, the paths between them, and how few clicks any item sits from the front door.
Why site architecture matters
Structure is the store’s silent ranking system: authority flows through links, so where a page sits decides how much it inherits, and products buried five categories deep rank like they’re hidden because, to a crawler, they are. Architecture also decides crawl efficiency at catalog scale, a clean hierarchy gets fully indexed while a tangled one leaves its long tail undiscovered.
Architecture that ranks and sells
- Shallow depth: important products reachable within a few clicks of home
- Category silos: related products and subcategories linked tightly, relevance concentrated
- One home per product: a canonical path, with breadcrumbs declaring it
- Demand-shaped taxonomy: categories mirroring how buyers actually search, not the org chart
Frequently asked questions
How deep is too deep for a product page?
When crawl and click data say so: pages many levels down get crawled rarely and visited less, and flattening, subcategory links, hub pages, in-content links, pulls them up without reorganizing the warehouse. Depth is measured in clicks from home, not folders in the URL.
Should the catalog structure follow search demand or internal logic?
Demand, translated politely: keyword research reveals the categories buyers think in, and the taxonomy that mirrors it ranks for terms the org-chart version never targets. Internal naming lives in the admin; the storefront speaks customer.