Multibrand: brand pages vs. category pages - who wins the ranking fight
The multibrand retailer's second headache is architectural: your search demand splits between category queries ("linen shirts," "white sneakers") and brand queries ("Les Deux overshirt," "[brand] [style name]") - and the two fronts have completely different competitive dynamics, different winnable spaces, and different page types. Stores that don't architect for the split end up with brand pages cannibalizing category pages, product pages fighting both, and - the classic - auto-generated vendor pages quietly representing the brand front with zero investment.
The brand front: fighting the brand itself, and the other stockists
On brand queries you're competing against the brand's own site (which usually wins its head terms, as it should) and every other stockist (who usually haven't tried, which is the opening). The winnable space: brand + category ("Les Deux shirts"), brand + product-line/style names (real query volume, often underserved because the brand's own site buries its archive), and brand + your differentiators ("brand X sale," size/availability queries). The asset for this front is a real brand page - not Shopify's bare /collections/vendors auto-page, but a built collection per meaningful brand: brand intro written by someone who can say why you stock them (your buying perspective is literally unique content - no other stockist has it), the brand's range in your taxonomy's sub-collections, and the enriched product data from last lesson underneath (which is what lets your product pages win brand+style long-tail against stockists running supplier text - the entry-fee economics, compounding per brand). Expectation-setting for the front overall: you're playing for the brand's long tail and local/availability intent, not their head terms - budget attention per brand accordingly, weighted by each brand's share of your revenue and search volume (your GSC brand-query data, Phase 3, makes this allocation empirical rather than political).
The category front: your actual home turf
Category queries are where multibrand structurally wins - you have selection breadth no single brand matches, which is exactly what category intent wants (Phase 4's collection logic, with multibrand's advantage attached: "white sneakers" searchers want choice, and you have forty brands of it). The category front therefore gets the primary investment: the full Phase 4 collection treatment on your taxonomy's pages, with multibrand's specific edge rendered visible - cross-brand filters that actually work (the intake vocabulary from last lesson, cashing out), comparison-friendly data density, and category content that leverages the multi-brand vantage ("the five best oxford shirts we stock, compared" is content a monobrand store cannot write - and it's precisely the committed, comparative content AI assistants cite, Phase 6).
The armistice lines: stopping the internal fight
The cannibalization risks are predictable and preventable: brand pages vs. category pages resolve by intent - brand pages own brand-modified queries, category pages own generic ones, and the internal linking reflects the hierarchy (brand pages link into category pages as the primary surfaces, not compete with them); brand+category intersections ("Les Deux shirts") get a dedicated sub-collection only when demand justifies it (the Phase 5 facet-promotion rule, applied to the brand dimension - otherwise it's a filter state, canonicalized away); and vendor auto-pages - audit them (they're in your sitemap, Phase 5) and either build them into real brand pages or noindex/redirect them into the structure, because a bare auto-page ranking for a brand query is your worst page representing your brand-front war effort. Two fronts, one architecture, each page type knowing its job - the multibrand version of the lesson this academy keeps teaching: rankings follow structure, and structure is a decision.