Ecommerce Site Architecture

How to structure an online store's pages so both shoppers and search engines can navigate it — flat vs. pyramid, click depth, URL structure, internal linking, breadcrumbs, mega menus, faceted navigation, and mobile-first nav. Google reads your link graph, not your URL paths.

First published: Jun 25, 2026 · Last updated: Jul 25, 2026 · Advanced
demand #4 in Architecture & Crawl Control#26 in Ecommerce SEO#339 on the site
1 evidence signal on this page

Ecommerce site architecture is how your store's categories, subcategories, and products are organized and linked. The biggest misconception is that flat is always better and that URL depth is what matters — neither is true. Google reads your internal link graph, not your URL paths, to work out hierarchy and importance. A reasonable pyramid (homepage → categories → subcategories → products) beats both a totally flat structure and a too-deep one. URL structure is barely a ranking factor; URL stability is the real risk. The commerce-specific failure points are faceted navigation eating crawl budget, products living in multiple categories, mega menus diluting link equity, and mobile nav being the nav Google actually crawls.

TL;DR — Google reads your link graph, not your URL paths, to infer hierarchy and relative importance — “Google generally doesn’t look at the structure of URLs… it analyzes the linkages between pages.” So a reasonable pyramid (homepage → category → subcategory → product) with strong internal linking beats both a flat structure (Mueller: a super-flat structure is not better than a reasonable pyramid) and a too-deep one (you don’t want to “click through a million times”). URL structure is barely a ranking factor; URL stability is the real risk. The commerce-specific failure points are multi-category products (canonical them), mega menus (link-equity dilution + crawlability), faceted navigation (crawl-budget killer — robots.txt > canonical), and mobile-first nav (your mobile nav is your SEO nav).

Evidence for this claim Google recommends linking menus to categories, categories to subcategories, and subcategories to products so Googlebot can follow the catalog hierarchy. Scope: Google ecommerce linking architecture. Confidence: high · Verified: Google Search Central: Ecommerce site structure Evidence for this claim Breadcrumb structured data communicates a page's position in site hierarchy and may support breadcrumb appearances in search. Scope: Google breadcrumb guidance. Confidence: high · Verified: Google Search Central: Breadcrumb structured data

Architecture serves two masters

Ecommerce site architecture is the hierarchical organization of a store’s pages — categories, subcategories, products, and supporting content — plus the navigation, internal links, and URL patterns that connect them. It has to satisfy two audiences at once: shoppers who want products in as few clicks as possible, and search engines that need to discover every page, understand how pages relate, and assign relative importance.

The whole topic comes down to one principle that most architecture guides bury or miss: Google reads links, not URLs.

This is the load-bearing fact. From Google’s ecommerce documentation:

“Google generally doesn’t look at the structure of URLs to work out the structure of a site. Instead, it analyzes the linkages between pages to gain insights about the relative importance of different pages on a site.”

And the mechanism for “relative importance”:

“the more links a page has to it within a site, the higher the relative importance of the page to other pages.”

So your internal link graph does the heavy lifting. Whether the URL reads /shoes/running/brand-x or /products/brand-x is secondary. The product that’s linked from your homepage, your top category, and three blog posts will get more crawl attention and more PageRank than a product two clicks deep with nothing pointing at it — even though the second one has the “shallower” URL.

The practical chain Google recommends:

“add links from menus to category pages, from category pages to sub-category pages, and finally from sub-category pages to all product pages.”

And the warning for large catalogs:

“If category pages don’t include direct links to all products in a category, Googlebot might not find all of your products by crawling alone.”

When direct linking to every product isn’t feasible at scale, fall back to XML sitemaps and (for products) a Merchant Center feed as secondary discovery paths — but those are a backstop, not a substitute for a crawlable link graph.

Flat vs. pyramid — the myth, busted

Nearly every competitor guide repeats some version of “flat is better” or “keep everything within three clicks.” That advice is half-right and badly framed. The nuance comes straight from John Mueller (Google, Feb 2, 2021 office-hours):

“On the other hand, kind of more the top down approach or pyramid structure helps us a lot more to understand the context of individual pages within the site.”

“So in particular, if we know this category is associated with these other subcategories then that’s a clear connection that we have between those parts.”

“So from my point of view, I think for a lot of sites it makes sense to have more of a pyramid structure.”

And the line that kills the myth outright:

“But it’s not the case that a super flat structure is going to be better than a kind of reasonable pyramid structure.”

Why a totally flat structure hurts: if every page is one or two links from the homepage, you’ve flattened the importance signal too. You’re effectively telling Google “everything here is equally important,” which strips away the context it uses to understand which categories own which subcategories own which products.

But don’t overcorrect into a deep tree, because Mueller capped that too:

“But at the same time you don’t want it to be such that it’s like you have to click through a million times to actually get to the actual content.”

So neither extreme wins. The target is a pyramid that’s shallow enough: broad categories at the top, narrowing to products, with click depth kept low for anything that matters. As a practical rule of thumb, aim for most products within ~3–4 clicks of the homepage on a large store, 2–3 on a small one — but treat that as a guideline, not a Google directive (see the click-depth note below).

The “3-click rule” is consensus, not a Google rule

You’ll see “every page must be within 3 clicks of the homepage” everywhere. It’s useful as a heuristic, but Google has not stated a specific click number. The real risk on a large catalog isn’t exceeding a click count — it’s orphaning pages (nothing links to them) or burying them so deep that crawlers rarely reach them. A long-tail product four or five clicks deep can rank fine if it sits in a logical hierarchy and appears in your sitemap. Click depth is a crawlability and PageRank-flow concern, not a direct ranking factor.

This is also why internal linking beats URL depth. A product five clicks deep in the hierarchy but linked directly from the homepage gets more crawl attention than a product two clicks deep with no inbound internal links. If you’ve got an important product sitting deep in the tree, the fix isn’t to re-architect the whole URL scheme — it’s to link to it from higher-authority pages.

URL structure: stability matters, depth doesn’t

Google’s URL guidance for ecommerce is mostly about hygiene, not hierarchy:

“use long-term, persistent URLs. Avoid internally linking to temporary parameters, such as session-IDs, tracking codes, user-relative values (location=nearby, time=last-week), and the current time.”

“Minimize the number of alternative URLs that return the same content to avoid Google making more requests to your site than needed.”

“Use ?key=value URL parameters rather than ?value, where possible. URL parameters allow Google Search to understand your site’s structure and crawl and index more efficiently.”

Notice what’s not there: any mandate about nesting depth. Google’s URL docs do not say /category/subcategory/product is better or worse than /product/slug. Depth is a site-structure decision, not a URL prescription.

Mueller has rated URL structure low (roughly 1 out of 7) as a direct ranking factor, and said making URLs artificially flat provides no SEO benefit. The takeaway for ecommerce: URL structure is barely a ranking factor, but URL stability is a real risk factor. Restructuring /category/subcategory/product into /product later causes redirect chains and temporary ranking disruption even if the end state is neutral. Pick a consistent, descriptive format early (/product/black-t-shirt beats /product/3243) and don’t churn it.

Multi-category products and the duplicate-content trap

The one place URL structure does bite you is products that live in multiple categories. If your URL encodes the category path, the same product can be reached at /shoes/running/brand-x and /sale/brand-x and /brand-x-page — three URLs, one product, duplicate content. Two fixes:

  • Flat product URLs (/products/brand-x) — one canonical URL regardless of which category path the shopper took to get there. This is the Ahrefs ecommerce guide’s recommended default, precisely to sidestep this problem.
  • Category-nested URLs with a canonical — pick one primary category, build the product URL under it, and canonicalize every other path to that primary.

Either way, you resolve the ambiguity with a single canonical. Then you restore the hierarchy signal — which the flat URL throws away — with breadcrumb schema (below).

Internal linking is the actual mechanism

PageRank and crawl attention flow through <a href> links, so your internal linking strategy is your architecture in practice. A few patterns that matter:

  • Link best-sellers and priority products from the homepage and high-authority pages. Google explicitly notes you can signal importance by linking popular products from the homepage, blog posts, or newsletters.
  • Category pages are link-equity distributors. They take authority from the homepage/nav and pass it down to products. A category page that doesn’t link to all its products leaves some undiscoverable by crawling alone.
  • Editorial → product links. Blog content that links to relevant products both passes equity and creates topical context.
  • Related products / “customers also bought” add cross-links across the tree so crawlers (and shoppers) don’t hit dead ends.
  • Breadcrumbs are internal links too, not just UX.

I’ve made the internal-links case for years. As I wrote in The Most Important Thing SEOs Overlook: Internal Links: “By adding internal links, you are directing the flow of your website authority to the best content, which in turn signals to search engines which pages you consider the most important.” And the part teams forget: “you may be frequently producing new pieces of content in which you add internal links, but are you remembering to go back to your older pieces” — on a store, that means linking new arrivals from existing category and editorial pages, not just publishing them and walking away. The reason this is worth the effort: “Links on your site are a lot easier to get than links from other sites, and they can be just as effective.”

For the full treatment, see internal links.

Breadcrumbs earn their keep three ways: they’re internal links, they give Google an explicit hierarchy signal, and they can render as a breadcrumb trail in the SERP. From Google’s structured-data docs:

“A breadcrumb trail on a page indicates the page’s position in the site hierarchy.”

Crucially, breadcrumbs let you communicate hierarchy even when your URLs are flat. A product at /products/black-t-shirt can still carry Home > Clothing > T-Shirts > Black T-Shirt via BreadcrumbList markup. And Google’s recommendation is to model the user path, not the URL:

“We recommend providing breadcrumbs that represent a typical user path to a page, instead of mirroring the URL structure.”

For products that belong in multiple categories, you can supply multiple BreadcrumbList markups for the different navigation paths. A BreadcrumbList needs at least two ListItem entries (each with position, name, and item) to be eligible for the rich result; the final crumb’s item is optional. (For what it’s worth, Mueller has said breadcrumb placement on the page doesn’t matter for SEO — so optimize it for users.)

Two separate issues live here: crawlability and link-equity dilution.

Crawlability. Google can only follow links that are real anchors:

“Google can only crawl your link if it’s an <a> HTML element with an href attribute.”

JavaScript is fine as long as the rendered DOM contains real anchors“Links are also crawlable when you use JavaScript to insert them into a page dynamically as long as it uses the HTML markup shown above.” What breaks is onclick-only handlers, routerLink-style attributes, or javascript: hrefs:

“Google can’t reliably extract URLs from <a> elements that don’t have an href attribute or other tags that perform as links because of script events.”

So a JavaScript mega menu can be crawlable — the myth that “JS menus can’t be crawled” is false — but only if it renders proper <a href> links.

Link-equity dilution. Every link in your global nav siphons a slice of the homepage’s authority. A 200-link mega menu spreads that authority thinly across 200 destinations. Mueller has also flagged that very large, frequently-changing mega menus can be hard for Google to interpret. The pragmatic move: keep the global nav to top-level categories (a manageable count, not the whole taxonomy), and let category pages handle the deeper subcategory and product navigation. That’s the pyramid expressing itself in the nav.

Faceted navigation: the crawl-budget killer

This is the single biggest crawl-budget leak on most ecommerce sites. Filters (price, color, size, sort order) each generate crawlable URLs, and the combinations explode — a modest catalog can hide millions of filtered URLs.

Google’s hierarchy of fixes, in their stated order of effectiveness:

“Use robots.txt to disallow crawling of faceted navigation URLs”

That’s the preferred method. The soft signals — notably rel=canonical — are acknowledged but “generally less effective in the long term than the previously mentioned methods.” (This is the reverse of what a lot of guides recommend, which lead with canonical.) Other levers:

  • URL fragments (#) for filter state passively avoid crawling, since “Google Search generally doesn’t support URL fragments in crawling and indexing.”
  • Return 404 for empty combinations: “If there are no green fish in the site’s inventory, users as well as crawlers should receive a ‘not found’ error.”

The strategy decision comes before the technical one: identify which filter combinations have genuine search demand (and deserve to be indexable landing pages) versus pure-UX filters (which should be blocked or built so they never mint a URL). This topic has its own deep dive — see faceted navigation — and it ties directly to crawl budget.

Mobile-first: your mobile nav is your SEO nav

Google indexes the mobile version of your site:

“Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.”

That has structural consequences. Content parity is required —

“Make sure that your mobile site contains the same content as your desktop site.” — and so is structured-data parity — “Make sure that your mobile and desktop sites have the same structured data.” And critically:

“Google won’t load content that requires user interactions (for example, swiping, clicking, or typing) to load.”

Evidence for this claim Mobile architecture must preserve primary content and crawlable navigation because Google indexes from the mobile version and does not load content that requires user interaction. Scope: rendered production pages, crawlable navigation, search results, analytics, and current documentation Confidence: high · Verified: Mobile-first indexing best practices

So if your mobile nav hides categories behind a hamburger that only renders links on tap (via JS click events rather than real <a href> links in the DOM), those category and product links may receive no crawl signal through navigation. Whatever hierarchy you built on desktop has to survive on mobile, as real anchors, with the same content and schema.

Those clusters of links that sometimes appear under your homepage result are sitelinks, and good architecture makes them more likely — but you can’t pick them. Google: “Our systems analyze the link structure of your site to find shortcuts.” And: “If the structure of your site doesn’t allow our algorithms to find good sitelinks… we won’t show them.” You influence quality through a logical structure, descriptive page titles and headings, and concise, relevant anchor text; you can’t specify which pages appear. If a bad one shows up, the lever is to noindex or remove that page.

Where this fits

This is one piece of the site-structure cluster under Ecommerce SEO. It connects directly to faceted navigation (the crawl side), category page SEO and product page SEO (the page types), and internal links (the mechanism). For how crawlers traverse all this, see crawling.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin an expert quote first.