A store selling trail shoes has a few dozen products, a homepage, and a menu with one link that says "Shop". Behind that link sits one long listing, sorted by newest, a dozen products per page. A shopper and Googlebot reach the older shoes the same way: by paging through screens nobody reads. Your collection structure is the map Google uses to find, weigh and label every product you sell, and most stores are still using the map their theme came with.
Why structure decides what Google sees
Google finds pages by following links, and it comes back most often to the pages it reaches most easily. Your main navigation appears on every page of the store, so the links in it are the most frequently crawled links you own. A product that lives only on page four of one listing is found late and revisited rarely.
Structure also tells Google what a page is. The same pair of shoes, reached through "Running shoes", then "Trail running shoes", then "Women's", with a breadcrumb showing that path, is easier to classify than the same shoes floating in a collection called "All". The hierarchy is context, and context is part of how Google judges relevance.
Build the hierarchy the way buyers search
Start from searches, not from your stock system. Buyers type "trail running shoes", "waterproof trail shoes" and "trail shoes for wide feet", never your supplier's range name or this season's internal label. Each level of your hierarchy should match a search that real people make, in their words, from broad at the top to specific below.
A collection earns its place when three things are true:
- People search for it, which you check the way the search intent lesson describes.
- You can fill it with enough products that the page is worth landing on.
- You can write a short intro that says what's in it and who it's for, in a way you couldn't write for a neighbouring collection.
If a grouping fails the first test, it's a filter rather than a collection, and the filters lesson covers what to do with it. If it fails the third, it duplicates something you already have, and Google will keep one of the two and drop the other.
A workable shape for most stores is home, then category, then collection, then product. "Footwear" is a category. "Trail running shoes" is a collection inside it. Each collection page carries the buyer's phrase in its title tag, main heading and URL, and a paragraph of its own text above the grid, so it reads as a page about something rather than a list of thumbnails.
Keep every product close to the top
The second half is depth. A product should be reachable by following the menu to its category, then to its collection, then clicking the product. Three things quietly push products far deeper than that:
- A single "all products" collection that runs to dozens of pages, with the real collections missing from the menu.
- Pagination that only works through a "load more" button driven by JavaScript, so there's no page two URL for Google to fetch.
- Products assigned to no collection, so the only listing that links to them is the catch-all page.
Pagination is worth getting right because every collection relies on it. Google's pagination guidance for ecommerce sites asks for each page of a listing to have its own URL, for pages to link to each other with ordinary links, and for each page's canonical tag to point to itself rather than to page one. Google announced in 2019 that it no longer uses the old rel=prev and rel=next tags, so don't rely on them. If your theme uses infinite scroll or "load more", check that a paginated URL still exists behind it.
Navigation is the other lever. The main menu should carry your categories and the collections that matter most, and each category page should link to every collection inside it. A mega menu of hundreds of links spreads attention thinly; a short menu concentrates it. Breadcrumbs belong on every collection and product page, and marking them up with BreadcrumbList structured data earns one of the rich results Google's structured data gallery still supports.
Tidy the map your platform shipped
Themes and platforms generate pages you never designed. Shopify creates an "all products" collection and a page for every product tag. WooCommerce creates an archive for every product category and tag. Each either deserves a place in your hierarchy or doesn't.
An auto-generated page that matches a real search becomes a proper collection: give it a name in the buyer's words, an intro, and a link from its category. One that doesn't stays out of the menu, out of the sitemap, and usually out of the index, which the duplicate URLs lesson walks through. A product that belongs to several collections is fine, as long as it has one canonical product URL and one primary collection for its breadcrumb.
What to take away
- Google crawls the pages your menu links to most often, and it uses the path to a product to understand what the product is.
- Name categories and collections after the phrases buyers search, from broad to specific, and give each collection its own intro text.
- Every product should be reachable through menu, category and collection, with paginated listings that have real URLs and self-pointing canonicals.
- Auto-generated collections, tag pages and catalog pages either become real collections or stay out of navigation and the sitemap.
Next
With the hierarchy in place, the next lesson shows how to send the authority your guides and blog posts earn to the pages that make money, in Internal links to money pages.