Shopify store structure: collections, navigation and URLs that scale

Shopify store structure means four connected things: how products are grouped into collections, how they're described with tags and product types, how the menus expose that, and what URLs come out the other end. Get it right and the store still works at three thousand products. Get it wrong and you're writing redirects a year from now.

This is worth an afternoon on paper before you load a single product.

Collections vs tags vs product type

The most common confusion, and the source of most structural mess.

• Collections are pages. They have a URL, a title, a description, and they can be linked to and ranked in search. Use them for the groupings customers actually browse — the ones you'd put in a menu.
• Tags are labels. They don't create pages by default; they drive filtering and automated collections. Use them for attributes customers narrow within a collection — colour, material, size, season.
• Product type is a single classification per product. Useful for automation and reporting; not a substitute for collections.

The rule: if you'd link to it, it's a collection. If you'd filter by it, it's a tag.

Automated collections do the work

A manual collection is a list somebody has to maintain. An automated collection is a rule — "product type is Chairs and tag is Outdoor" — that maintains itself as the catalogue changes. For anything larger than a small catalogue, automated collections are the difference between a store that stays tidy and one that quietly rots as products get added by someone in a hurry.

Set the rules up front, and make the tags they depend on part of your product-data standard rather than something people invent per product.

Menu depth

Shopify supports nested menus. That doesn't mean you should use all the levels.

• One level works for a small catalogue and is the fastest to scan.
• Two levels is the sweet spot for most stores — category, then subcategory.
• Three levels needs a mega-menu and a good reason. Below three, people stop navigating and start searching, which means your search and filtering had better be good.

Whatever depth you choose, the menu is not the whole navigation. Collection pages that link to sibling collections, and products that link back up, matter as much — for customers and for how search engines discover the catalogue.

URLs

Shopify enforces its own URL structure — /collections/…, /products/…, /pages/…, /blogs/…. Within that you control the handle, and the handle is worth thinking about because it's the part that ends up in search results and in links.

Two rules. Keep handles short and human — outdoor-dining-chairs, not collection-outdoor-dining-chairs-2026. And do not change them casually after launch; every change needs a 301, and a store that accumulates redirect chains loses both crawl budget and ranking signal. If you're migrating in from another platform, matching handles to your old slugs makes the redirect map dramatically simpler.

Structure also determines what you can send to shopping channels — product feeds are only as good as the fields behind them.

Editorial content

Blog articles, guides and landing pages sit outside the product hierarchy but link into it, which is most of their value. Setting up a blog on Shopify covers the structure and its limits.

Where the structured data goes

Product attributes that aren't options and aren't browsing categories — material composition, care instructions, technical specifications, compatibility — do not belong in tags and definitely don't belong in the description as formatted HTML. They belong in metafields and metaobjects, typed and reusable, from the start. Retrofitting that across a live catalogue is one of the least enjoyable jobs in Shopify work.

A structure that survives growth

Sketch this before you build:

1. Top-level categories — the five to eight things you sell. These become your main menu.
2. Subcategories — how each splits. These become collections, usually automated.
3. Filter attributes — how a customer narrows within a subcategory. These become tags, with a fixed vocabulary.
4. Product data — everything else. These become metafields.
5. Editorial groupings — "new in", "sale", "gift guide". Automated collections on tags, so they maintain themselves.

Write the tag vocabulary down and give it to whoever adds products. Half of all structural mess in Shopify stores is one person typing Blue and another typing blue-ish.

Structure is the part of the build with no visible output and the highest cost of getting wrong. It is also the part clients most want to skip. Don't.