Research brief: Information architecture for service businesses with multiple verticals (piece 6 of 15)
Created 2026-05-22
Status: Research material, not finished article. Compiled May 2026.
TL;DR
- The
/industries/<slug>/URL pattern is dominant among multi-vertical B2B service firms (Crowe, BDO USA, HUB International, Dentons via/industry-sectors/, Grainger). The/for-farmers/pattern was observed on zero of 8 sampled multi-vertical service sites — it belongs to SaaS marketing, not service business IA. - NN/g's primary finding on audience-based navigation is a warning, not an endorsement. Audience-based nav "will often degrade usability" — works only when categories are mutually exclusive, jargon-free, with substantially unique content per section. Small service businesses rarely meet that bar.
- The dominant working model is an Industries × Services matrix with both axes in the top nav. RelaDyne, Crowe, HUB International, Dentons, E.H. Wolf all use this shape.
- Google consolidates duplicates; it doesn't penalize them. Mueller: near-duplicate vertical pages get folded together unless each has "something unique." Vertical pages without genuinely vertical-specific content will not rank.
- Multi-step forms outperform single-step only above ~7 fields. Below that, the lift evaporates (Zuko). Above that: 13.9% vs 4.5% (Formstack 2014, n=450k+); up to 300% in Venture Harbour's portfolio testing; 743% on one 11-field B2B SaaS form (Numinam).
- For small service businesses, the IA pattern that scales is hub-and-spoke: one hub page per vertical, shared services pulled in via blocks — not a full matrix of vertical × service pages. The matrix is an enterprise pattern; the hub-and-spoke is a 4-10-person-firm pattern.
How this brief decomposes
Strongest atomic claims (sources C1-C32) are filed individually. Synthesis recommendations (S1-S18) become rules where prescriptive. The decision matrix (§7) and URL pattern guide (§8) become their own reference entries since they're reusable frameworks. The Boucher & Jones implication is preserved in Boucher & Jones IA recommendation: Pattern A + hub-and-spoke, NOT enterprise matrix.
Honest gaps and caveats
- The "13.9% vs 4.5%" multi-step stat is from Formstack 2014 — a self-published account-level report across 450k+ accounts, not a controlled experiment. Industry consensus, not primary evidence. Treat as directional.
- The "300% lift" multi-step claim is widely misattributed to ConversionXL/CXL. Correct primary attribution: Venture Harbour (Marcus Taylor) portfolio testing.
- The "~12 item mega-menu trigger threshold" attributed to NN/g in earlier drafts does not exist in NN/g's primary literature. The real NN/g guidance is qualitative: mega menus are appropriate "for bigger sites with many features."
- NN/g and Baymard have no dedicated article on the "industries we serve" pattern specifically. Closest is the audience-based-nav warning, which addresses adjacent but not identical territory.
- The Gartner six-jobs framework + 77% / 6-10 stakeholders / 95% revisit figures all trace to a single 2019 CSO Update report. Widely cited; treat as Gartner-attributed industry consensus.
- The polar bear book (Rosenfeld/Morville/Arango 4th ed., 2015) is foundational but pre-mobile-first-indexing. Principles current; examples dated.
- Schema.org best practice for multi-audience services has limited primary documentation beyond type definitions. Practitioner blogs (Aubrey Yung) fill the gap as single-source.
- Mobile navigation patterns for multi-vertical sites are underexplored in current research. NN/g mobile guidance applies, but no 2024-2026 study tests multi-vertical service-business mobile nav specifically.
Editorial direction
- Lead with the URL convention finding (
/industries/<slug>/is the dominant pattern) — it's the most concrete, immediately actionable claim. - Treat the Decision Matrix (§7 → Reference: which IA pattern to use, by business shape (decision matrix)) as the deliverable readers save.
- NN/g's audience-nav warning is the contrarian hook — most agency writing treats audience-nav as a best practice; the actual research says the opposite.
- The hub-and-spoke vs matrix distinction is the small-business-vs-enterprise honesty. Don't pretend a 4-person firm should build Dentons IA.
Related
- reference NN/g: audience-based navigation "will often degrade usability" (Laubheimer, Aug 14 2022)
- reference NN/g: five recurring problems with role-based navigation (Laubheimer, 2022)
- reference Jakob Nielsen: "Mega menus show everything at a glance, so users can see rather than try to remember"
- reference NN/g mega-menu hover protocol: wait 0.5s before showing, then display within 0.1s
- reference NN/g: "On large screens, don't cover the entire screen when megamenus are open" (Apr 30 2023)
- reference NN/g: use labels with strong information scent; avoid vague verbs and conversational tone in nav (Apr 16 2023)
- reference Information Architecture: For the Web and Beyond, 4th ed. (Rosenfeld/Morville/Arango, O'Reilly 2015) — the canonical IA reference
- reference John Mueller: Google does NOT penalize duplicate content for localized websites — it consolidates
- reference Mueller on near-duplicate vertical/location pages: fold them into one stronger page unless each has something unique
- reference Google Search Central: faceted navigation creates combinatorial duplicate URLs; not search-friendly by default
- reference John Mueller on internal linking: "one of the biggest things that you can do on a website"
- reference Gartner: B2B buyers complete "six buying jobs" in non-linear "looping" order
- reference Gartner: real B2B buying journey looks "like a big bowl of spaghetti" (pull quote)
- reference Gartner: typical B2B buying group is 6-10 decision-makers; ~95% revisit earlier decisions (CSO Update, 2019)
- reference Gartner: 77% of B2B buyers say their latest purchase was "very complex or difficult" (CSO Update 2019)
- reference Formstack 2014: multi-step forms 13.9% vs 4.5% single-step (n=450k+ accounts) — directional, not RCT
- reference Venture Harbour: multi-step forms up to 300% better than single-page — correctly attributed (NOT CXL/ConversionXL)
- reference Numinam (2024): 11-field B2B SaaS form 0.96% → 8.1% via multi-step (+743% lift)
- reference Zuko: multi-step forms only outperform single-page above ~7 fields; below that, neutral or worse
- reference Schema.org: Service.audience accepts Audience | PeopleAudience | BusinessAudience with audienceType as free-text
- reference Schema.org canonical pattern: one Service entity with audience: { type: Audience, name: ... } + areaServed
- reference Aubrey Yung: "audience captures relevance; areaServed captures coverage"
- reference RelaDyne: /products-solutions/<industry>/ namespace, ~19 verticals, multi-axis IA ("By Industry / Product / Brand / Service")
- reference E.H. Wolf & Sons: closest direct B&J analog — "Industries We Serve" + 16 flat-root vertical pages
- reference Crowe LLP: cleanest /industries/<slug>/ URL pattern in the sample (Audit/Tax/Advisory/Consulting × industries)
- reference BDO USA: mirrors Crowe — /industries/<slug>/ pattern with separate /services/ namespace
- reference Dentons: explicit Industries × Practices matrix at /find-your-dentons-team/ — "organized around your business agenda"
- reference Fastenal: NO /industries/ IA at all — product+service-first nav. The steel-manned alternative.
- reference HUB International: parallel /industries/ + /products/ with industry sub-pages where complexity warrants
- reference Field survey (May 2026): the /for-<audience>/ URL pattern was observed on ZERO of 8 multi-vertical service sites
- reference NN/g: split buttons unreliable on touch (fat-finger conflicts) — use sequential menus or accordions on mobile
- reference Reference: which IA pattern to use, by business shape (decision matrix)
- reference Reference: 5 URL structure patterns for multi-vertical IA (A through E), with field-observed usage
- reference Boucher & Jones IA recommendation: Pattern A + hub-and-spoke, NOT enterprise matrix
- rule RULE: Default to /industries/<slug>/ for multi-vertical service business URLs. Never /for-audience/ as primary IA.
- rule RULE: Don't use audience-based primary nav unless audience categories are mutually exclusive, jargon-free, with substantially unique content
- rule RULE: Every vertical page carries substantively vertical-specific content (case studies, regulations, vocabulary). Generic content gets folded.
- rule RULE: Expose Industries and Services as two orthogonal axes in the top nav. Don't hide one behind the other.
- rule RULE: One Service schema per vertical when offerings genuinely differ. Multi-audience Service when offering is identical.
- rule RULE: Forms under ~7 fields stay single-step. Multi-step only when total fields cross the threshold.
- rule RULE: 4-15-person service businesses use hub-and-spoke IA, not enterprise matrix. Don't pretend to be Dentons.
- rule RULE: Mega menu hover delay 500ms before show, 100ms reveal. Mobile uses accordion / sequential, not the same mega menu.
- reference Research brief: Structured content as a competitive advantage (piece 2 of 15)
- reference Research brief: Owning your stack — why agency-managed platforms cost more than they save (piece 4 of 15)