Information architecture for an online store determines whether a user finds the desired product in 3 clicks or abandons in frustration after 30 seconds. It doesn't matter how good the design is or how competitive the price — if the category structure is confusing, the navigation ambiguous, and the internal search inefficient, the conversion rate will suffer. This guide covers everything you need to know, from category hierarchy to URLs and sitemaps, with concrete examples for stores ranging from 50 to 10,000 products.
Category Hierarchy: The 3-Level Rule
An online store's category hierarchy should never exceed 3 levels of depth — beyond this threshold, users get lost and Google's crawlers consume indexing budget inefficiently. This is the fundamental rule of e-commerce architecture.
The ideal structure
Level 1: Main category (e.g., Clothing)
Level 2: Subcategory (e.g., Dresses)
Level 3: Sub-subcategory (e.g., Evening dresses)
→ Products
How many categories at each level?
| Catalog size | Level 1 | Level 2 per category | Level 3 per subcategory |
|---|---|---|---|
| 50-200 products | 4-6 | 3-5 | 0-3 |
| 200-1,000 products | 6-10 | 5-8 | 3-5 |
| 1,000-10,000 products | 8-12 | 8-12 | 5-8 |
The MECE Principle
Categories must be MECE (Mutually Exclusive, Collectively Exhaustive):
If a product can belong to two categories, use tags and cross-collections, not duplicate categories.
Practical example: furniture store
Sofas (Level 1)
├── Sofa beds (Level 2)
│ ├── 2-seater sofa beds (Level 3)
│ └── 3-seater sofa beds (Level 3)
├── Corner sofas (Level 2)
└── Fixed sofas (Level 2)
Beds (Level 1)
├── Upholstered beds (Level 2)
├── Storage beds (Level 2)
└── Bunk beds (Level 3)
Faceted Navigation
Faceted navigation allows users to filter products by multiple attributes simultaneously — it's the mechanism that transforms a catalog of 5,000 products into an efficient shopping experience. Without it, a store with over 100 products per category becomes unusable.
What are facets?
Facets are product attributes that serve as filters:
Correct technical implementation
Faceted navigation creates parameterized URLs that can generate major SEO problems if not managed correctly:
The problem: store.com/dresses?color=red&size=M&price=100-200 creates thousands of URL combinations with similar content — one of the most common sources of duplicate content that hurts SEO.
The solution:
Need an online store with professional architecture? See our web development services.
Facets on mobile
On mobile, facets must be handled differently:
Breadcrumbs: Essential Secondary Navigation
Breadcrumbs are the second most important navigation element after the main menu — they communicate to the user where they are in the hierarchy and provide Google with structural context through BreadcrumbList schema markup. Their correct implementation improves both UX and SEO.
Correct format
Home > Clothing > Dresses > Evening dresses > [Product name]Implementation rules
BreadcrumbList schema markup on every page> or /, not → (rendering issues on some devices)Breadcrumbs for products in multiple categories
If a product appears in the "New arrivals" collection and in the "Evening dresses" category, the breadcrumb must reflect the main category, not the collection. Consistency in breadcrumbs helps Google understand the site hierarchy.
Internal Search: The Underestimated Element
Internal search is the feature that generates the highest conversions — users who search on a site convert 1.8-2.5 times more than those who browse through categories. A weak search means directly lost revenue.
What a good search should offer
Technical solutions
| Solution | Price | Suitable for |
|---|---|---|
| WooCommerce default + SearchWP | 300-500 lei (one-time) | Under 500 products |
| Algolia | 50-200 EUR/month | 500-50,000 products |
| Elasticsearch (self-hosted) | Server cost | 10,000+ products |
| Typesense (open source) | Server cost | 1,000-100,000 products |
Analyze what users are searching for
Internal search data is a goldmine:
Mega Menu: Navigation for Large Catalogs
The mega menu is the optimal solution for online stores with over 200 products and more than 6 main categories — it replaces classic dropdowns with a wide panel that displays all options simultaneously, reducing the number of clicks needed.
Structure of an effective mega menu
┌──────────────────────────────────────────────────────┐
│ Category 1 │ Category 2 │ Category 3 │ 🖼 │
│ ───────── │ ───────── │ ───────── │ │
│ Subcategory │ Subcategory │ Subcategory │ IMG│
│ Subcategory │ Subcategory │ Subcategory │ │
│ Subcategory │ Subcategory │ Subcategory │ CTA│
│ View all → │ View all → │ View all → │ │
└──────────────────────────────────────────────────────┘
Best practices
Mega menu on mobile
On mobile, the mega menu becomes a hierarchical navigation:
URL Structure
An online store's URL structure must be predictable, clean, and hierarchical — both the user and Google should be able to understand a page's place in the architecture just by reading the URL.
Recommended format
store.com/category/subcategory/product-name/Concrete example:
store.com/furniture/sofa-beds/oslo-grey-sofa-bed/URL rules
?p=1234 — no)-), not underscores (_)/categories/furniture/ — redundant)Pagination
Pagination URLs must be handled correctly:
store.com/dresses/ — first page (canonical)store.com/dresses/page/2/ — subsequent pagesrel="next" and rel="prev" between pages/page/1/Build an online store with a structure optimized for conversions and SEO. Contact us.
XML Sitemap for Online Stores
An online store's XML sitemap must be hierarchically structured, automatically updated, and segmented by content type — products, categories, static pages, and images. A correct sitemap helps Google discover and efficiently index all important pages.
Recommended segmentation
sitemap-index.xml
├── sitemap-products.xml (or multiple if you have over 10,000 products)
├── sitemap-categories.xml
├── sitemap-pages.xml
├── sitemap-posts.xml
└── sitemap-images.xml
Rules
lastmod updated on every real change (not auto-generated on every request)Submission
robots.txt: Sitemap: https://store.com/sitemap-index.xmlCommon Mistakes in Online Store Architecture
Information architecture mistakes are the most costly errors in an online store — they simultaneously affect UX, SEO, and conversion, and are difficult to fix after launch.
Top 7 mistakes
?product_id=4567&cat=89 instead of descriptive slugsHow to avoid them
Plan the architecture before starting development. Card sorting with real users (even 5 people is enough), tree testing for validation, and complete documentation of the hierarchy in a spreadsheet before the first line of code. If you don't have in-house expertise for IA planning, a professional web agency can deliver the complete architecture as part of the development project.
Frequently Asked Questions
How many main categories should an online store have?
Between 5 and 12 main categories, depending on catalog size. Under 5 categories — not granular enough. Over 12 — the menu becomes hard to scan. The rule: if a category has fewer than 10 products, it probably doesn't deserve to exist as a main level.
How do I organize products that belong to multiple categories?
Choose a main category (for the URL and breadcrumbs) and use tags, attributes, or collections for visibility in secondary categories. Don't duplicate the product across multiple categories — you'll create duplicate content.
What's more important: category navigation or internal search?
Both are essential, but they serve different users. Users who "browse" prefer categories. Users who know what they want prefer search. Statistically, users who search convert 1.8-2.5x more.
How do I structure URLs for a WooCommerce store?
Recommended format: domain.com/category/product-name/. In WooCommerce, set it from Settings → Permalinks → Product permalinks → Shop base with category. Make sure slugs are short, descriptive, and without diacritics.
How many products should I display on a category page?
Between 24 and 48 products per page, with pagination. Under 24 — the user makes too many clicks. Over 48 — the page loads slowly. On mobile, infinite scroll with lazy loading works better than classic pagination.
A well-structured online store converts more with the same traffic. Request a free consultation for your online store development and build an architecture that sells.
