Shopify Site Structure: The Architecture That Ranks (2026)

Published: August 24, 2026

Last updated: August 24, 2026

7 min read

Ask a store owner to draw their site structure and they'll draw a tree.

Home at the top. Categories below. Subcategories below that, products hanging like fruit.

Shopify doesn't have trees. Not in the URLs, anyway.

Every collection lives at /collections/name, every product at /products/name, all of them side by side in one flat plane, and you cannot change it.

Shopify did add nesting to the catalogue itself in July 2026, so a collection can now be built from other collections. Useful for merchandising. It changes nothing about your URLs, which stay resolutely flat.

Most structure advice ignores this and prescribes URL hierarchies the platform can't build.

Store owners either give up or fight the platform with hacks that break at the first theme update.

Here's the reframe that makes structure work on this platform: on Shopify, structure is navigational, not architectural.

Google learns your hierarchy from menus, breadcrumbs and internal links, not from slashes in URLs.

This is the architecture chapter of my complete Shopify SEO guide, expanded: what the flat platform actually gives you, the four layers that create hierarchy anyway, and the one-line rule that decides what every page on your store should be.

Short on time? Here are the key takeaways

Shopify URLs are flat and always will be: hierarchy lives in navigation, breadcrumbs and internal links.
One searched entity, one page, of the right type: that single rule decides what should exist.
Navigation is your strongest statement of what matters: spend it on money collections, by name.
Three clicks from home to any money page: through descriptive links, not a mega menu.

The flat platform, honestly assessed

First, stop mourning the URLs.

Google has been clear for years that URL depth isn't how it understands sites.

Google's own ecommerce structure guidance is about navigation and links: menus to categories, categories to products, with a page's internal links determining its relative importance.

Shopify's flat URLs are fine.

What the flatness actually costs you is defaults: the platform will never build hierarchy for you, so a store with no deliberate navigation design has no structure at all.

Just 400 URLs standing in a field.

Which means structure on Shopify is a design job you do once, in four layers.

Layer one: the entity map decides what exists

Before menus, decide what pages deserve to exist, and the rule is one line.

One searched entity, one page, of the right type.

The demand shape picks the page type:

Category demand becomes a collection: "golf hoodies", "togo sofa". The full playbook for these is my collection page SEO guide.
Model or exact-name demand becomes a product: the buyer already knows the item. Covered in the product page SEO playbook.
Research demand becomes a blog post: comparisons, buying guides, questions. That engine is the Shopify blog SEO guide, publishing alongside this piece.
Trust demand becomes a page: about, delivery, authenticity, contact. Nobody searches for these, everybody checks them.

Selling into more than one country repeats this whole map per market rather than replacing it, which is the subject of my international SEO guide.

Every URL on your store should trace to one of those four sentences.

When two pages chase one entity, you get cannibalisation. When one URL serves no entity, it's furniture.

At REHAUS I consolidated 113 collections that failed this test, and the plumbing for that cleanup is in my duplicate content guide.

The map usually fits on one sheet of paper.

A 20-product store like my own golf brand needs six collections and a blog, not an information architecture project.

Layer two: navigation is where the hierarchy lives

Since URLs can't declare importance, your menus do.

Google reads navigation as your statement of what matters. So does every shopper.

Spend it deliberately:

Header menu, money collections by name: your six to ten most valuable entities, named as searchers name them. "Golf Hoodies", not "Shop". A "Catalog" catch-all is a structural shrug.
Nested menu items create the tree Shopify won't: a "Sofas" menu item opening to Togo, Ploum and two-seaters tells Google those collections are siblings under a parent concept, flat URLs regardless.
Footer carries the trust layer: delivery, returns, about, contact, the pages buyers and AI agents verify before trusting you.
Nothing in navigation that isn't on the entity map: every menu slot spends link equity. Tag pages, half-dead collections and "New In" duplicates don't get paid.

One honest warning from client work: mega menus with ninety links don't make ninety pages important.

They make importance illegible. Curate like shelf space, because that's what it is.

Layer three: breadcrumbs, the tree made visible

Breadcrumbs are where your navigational hierarchy becomes machine-readable.

Home to Sofas to Togo Sofas to the product.

On Shopify, breadcrumbs are rendered by the theme from your navigation or collection context, and marked up with BreadcrumbList schema so the hierarchy appears in search results too.

Two checks, five minutes:

The trail reflects the entity map: if a product's breadcrumb jumps straight from Home to product, the middle of your structure is invisible on exactly the pages that need it.
One BreadcrumbList source: theme or app, never both, per the single-source doctrine in my schema markup guide.

Small layer, disproportionate clarity.

Machines and humans both stop guessing where they are.

Layer four: internal links are the bloodstream

Menus declare the skeleton. Internal links move the authority around it.

The flow on a store is always the same triangle.

Blog posts capture research demand and link down to collections. Collections present the choice and link down to products. Products convert, and link sideways to what pairs with them.

Run the triangle deliberately:

Every blog post links its target collection early: first half of the post, descriptive anchor. The post exists to feed that page.
Collections link their supporting guides: in the accordion layer, back up to the buying guide and comparisons. The loop closes.
Products link the parent collection and true pairings: breadcrumb up, cross-sell sideways. No orphans.
New pages get links on launch day: a collection nobody links to is invisible regardless of the map. The tactics live in my internal linking strategy guide.

The test for the whole layer: pick any money page and count clicks from the homepage.

Three or fewer through descriptive links and the structure is doing its job.

What structure moved at REHAUS

Structure is substrate, so it never gets a clean before-and-after of its own.

It gets receipts by proxy.

The REHAUS rebuild put the entity map, navigation, breadcrumbs and link triangle in place before most of the content shipped.

Average position moved from 24.2 to 10.7 across the engagement, and the collections placed into navigation, like the brand pages taking hundreds of monthly clicks each, are the pages that climbed hardest.

Foundations first, then everything built on them ranks faster.

The sequence is documented in the REHAUS case study.

However you weight the credit, the inverse case is unambiguous.

I have never audited a store with strong rankings and incoherent structure. Not once.

Final Thoughts

Structure is the least glamorous work in this whole cluster, and it decides how far everything else can climb.

The platform is flat. Fine.

Draw the entity map, spend the navigation like money, make breadcrumbs tell the truth, and run the link triangle until no page stands alone.

Do it once, properly, and every collection you launch, every product you add and every article you publish inherits a structure that already knows where it goes.

Structure is the first thing I map in a free SEO audit, because everything else in the report depends on it. Get in touch if you want yours drawn, or email me directly.

Findings within five business days.

Author Bio

Graeme Whiles is an independent SEO and AEO consultant at GWContent. He has worked with enterprise and SaaS brands, including Originality.ai, Connecteam, 6sense, Practice Better, and Peppr, growing organic traffic and AI search visibility across some of the most competitive categories in B2B. He also built Three Putt Golf Clothing from a blank domain as a live proof of concept for his methodology.

Shopify Site Structure Frequently Asked Questions

Can you create subcategories on Shopify?

Not as URLs. Collections can now be built from other collections in the admin, but /collections/sofas/togo still doesn't exist and won't. You create hierarchy through nested navigation menus, breadcrumb trails and internal links, which is how Google reads it anyway. The flat URLs cost you nothing once the navigational structure declares the tree.

Does URL structure matter for Shopify SEO?

Less than almost anyone believes. Google reads your hierarchy from navigation and internal links, not slash depth, and Shopify's forced /collections/ and /products/ prefixes are fine. Spend the energy saved on the entity map and menu design, where structure is actually decided.

How many collections should a Shopify store have?

One per searched entity you can genuinely serve: category, brand, model or use case. For most small stores, that's six to fifteen. More collections than entities means duplicates competing with each other. Fewer means demand you're not catching. The keyword map decides, not the admin's imagination.

What's the ideal click depth for ecommerce?

Every money page within three clicks of the homepage through descriptive links. Deeper pages get crawled less and convert less. On Shopify, you fix depth with navigation and internal links rather than URL changes, which makes it one of the cheapest structural wins available.