Two stores can sell the same products, publish the same quality of content, and end up with completely different search performance. Often the difference is not the pages themselves. It is how those pages are arranged and connected.
Site structure is the part of ecommerce SEO that gets the least attention, partly because it is invisible to shoppers when it works and partly because it feels like a decision you made once when the store was built. But structure determines what search engines can find, how much authority reaches each page, and which of your pages are considered important enough to rank.
Across ecommerce and international brands I have worked with, structural problems tend to sit underneath a lot of stalled rankings. The content is fine. The pages simply are not connected in a way that lets them perform.
What structure actually communicates
A search engine works out what matters on a site partly from how the site links to itself. Pages linked from many places, close to the homepage, read as important. Pages buried several clicks deep with a single link pointing at them read as marginal.
That is the whole mechanism, and it explains most structural decisions. Authority flows through internal links. Where you point those links is where the authority accumulates.
It also affects discovery. A page nothing links to is a page search engines may never crawl, no matter how good it is. Orphan pages are more common on ecommerce sites than most owners expect, particularly products that were added to a collection that has since been removed.
Tip: Products that have dropped out of every collection are a frequent source of orphan pages. They still exist, still load, and nothing on the site points at them any more.
Depth: the three click principle
A useful working rule is that no important page should sit more than three clicks from the homepage.
Homepage to category, category to subcategory, subcategory to product. That is three. A store that requires five or six clicks to reach a product has told search engines that the product is not a priority, and has made it harder for shoppers to find as well.
Large catalogues make this harder, which is exactly why the structure has to be deliberate rather than accidental. Good category organisation is what keeps depth shallow as a catalogue grows. Poor organisation is what pushes products further and further from the surface.
When a subcategory deserves its own page
This is the decision that shapes everything else, and it comes down to three questions.
Is there genuine search demand for the subcategory as a term in its own right? Keyword volume answers this. If people search for it as a distinct thing, a page can capture that.
Does the demand justify a page rather than a filter? Some distinctions people care about are better served by a filter on the parent category, because they are refinements rather than categories.
And do you actually have the products? A subcategory page with three items is a weak page. It gives a shopper very little and gives a search engine even less. The demand can be real and the page still be premature.
That last check is the one most often skipped. Stores create category pages for terms they want to rank for, without the range to support them, and end up with thin pages competing against competitors who have depth.
| Signal | Points towards a dedicated page | Points towards a filter |
|---|---|---|
| Search volume for the term | Meaningful and consistent | Low or seasonal only |
| How shoppers think about it | A category of product | A refinement of one |
| Products available | Enough to make a real page | A handful |
| Content potential | Genuine guidance to offer | Nothing beyond the product list |
Where internal links should point
Once the structure is right, linking is what makes it work.
Product pages link back up to the collection they belong to, using anchor text that describes the collection rather than saying click here. Where genuinely relevant, they also link across to related collections or complementary products. That helps shoppers keep browsing and passes relevance in both directions.
Collection pages link down to their products, which happens naturally through the product grid, and across to closely related collections where it makes sense for a shopper.
Blog content links to collections and products, but only on relevance. A post about choosing between two product types has a natural reason to link to both. A post that links to a collection because the collection needs links, rather than because the reader would want it, tends to read as forced and does less good than it appears to.
Tip: The anchor text is doing work. A link that says view our outdoor cushions tells a search engine what the destination page is about. A link that says click here tells it nothing.
Navigation, footers, and the pages nothing points at
The main navigation is both a UX decision and an SEO one, and it has to serve both.
Core collections and key pages belong in the navigation, because that gives them links from every page on the site. But navigation crammed with every possible category becomes unusable, and a menu that links to everything from everywhere flattens the hierarchy you built. The judgement is which collections genuinely deserve site-wide prominence.
Footers do useful work here. Core pages that matter but do not belong in the main navigation can sit in the footer, picking up a site-wide link without cluttering the primary menu.
An HTML sitemap page is worth considering on larger stores. Unlike an XML sitemap, which exists for search engines, an HTML sitemap is a real page linking to everything, which helps distribute authority and gives orphan pages a route back into the site. It is not a substitute for good structure, but it catches what structure misses.
What good structure looks like in practice
A well-structured store has a clear hierarchy from homepage to category to subcategory to product, with nothing important more than three clicks deep. Categories exist because there is demand and range to support them, not because someone wanted to rank for a term. Products link back to their collections with descriptive anchors. Navigation carries the collections that matter most, the footer catches the rest, and nothing sits orphaned.
None of that is visible to a shopper. What they experience is a store that is easy to browse, which is not a coincidence. Structure that reads well to a search engine usually reads well to a person, because both are trying to understand what the site sells and how it is organised.
Where the difficulty is
Understanding the principles is not the hard part. Applying them to a store that already exists is.
Restructuring a live catalogue means deciding what to merge, what to split, and what to remove, then handling redirects so the authority those pages built does not evaporate. Get it wrong and you lose rankings you already had. It gets harder again across multiple markets, where the same structural decisions have to hold in several regional versions without the markets competing with each other.
That is the work I do. If your store has grown organically and the structure has not kept up, my ecommerce SEO services page explains how I approach it. To see where your own store stands, request an SEO audit.
For the wider picture, start with my ecommerce SEO guide. For the pages this structure is built around, see how collection pages earn their rankings.
Frequently asked questions
What is ecommerce site structure?
Site structure is how the pages of a store are organised and connected, from the homepage through categories and subcategories to individual products. It determines what search engines can find, how authority flows between pages, and which pages are treated as important.
How many clicks from the homepage should a product be?
Three is a sound working limit. Homepage to category, category to subcategory, subcategory to product. Pages buried deeper are harder for both shoppers and search engines to reach, and tend to be treated as less important.
When should a subcategory be a page rather than a filter?
When there is genuine search demand for the term, shoppers think about it as a category rather than a refinement, and there are enough products to make a substantial page. Demand alone is not enough if the range cannot support it.
What is an orphan page?
An orphan page is one that no other page on the site links to. It may still load and still be listed in a sitemap, but with nothing pointing at it, search engines may not crawl it and shoppers cannot find it by browsing. Products removed from collections are a common cause.
Does an HTML sitemap help SEO?
On larger stores it can. An HTML sitemap is a real page linking to the rest of the site, which helps distribute authority and gives otherwise orphaned pages a route back in. It supports good structure rather than replacing it.
Aashish Maharjan is an SEO specialist focused on ecommerce and international organic growth across global markets. Learn more about my work or request an SEO audit.