Reference: 5 URL structure patterns for multi-vertical IA (A through E), with field-observed usage

Five URL patterns observed in field research, ranked by recommendation strength. From §8 of Research brief: Information architecture for service businesses with multiple verticals (piece 6 of 15).

Pattern A: /industries/<vertical>/ — RECOMMENDED DEFAULT

Examples: /industries/agriculture/, /industries/fleet/, /industries/construction/

Real-world use: Crowe (Crowe LLP: cleanest /industries// URL pattern in the sample (Audit/Tax/Advisory/Consulting × industries)), BDO USA (BDO USA: mirrors Crowe — /industries// pattern with separate /services/ namespace), HUB International variant (HUB International: parallel /industries/ + /products/ with industry sub-pages where complexity warrants).

Tradeoff: Adds a path segment, but gives a clean namespace for future vertical expansion. Easy to add /industries/agriculture/case-studies/ and /industries/agriculture/regulations/ later. Slightly longer URLs; per Mueller, keyword-in-URL is a minor signal — readability matters more.

Pattern B: /<vertical>/ flat — ACCEPTABLE FOR SMALL SITES

Examples: /agriculture/, /fleet/, /construction/, /residential/

Real-world use: E.H. Wolf & Sons (E.H. Wolf & Sons: closest direct B&J analog — "Industries We Serve" + 16 flat-root vertical pages), Coastal Mountain Fuels.

Tradeoff: Shorter URLs, but root namespace fills quickly. Once you use /agriculture/ as a content category, you can't later use /agriculture-services/ without confusion.

Recommended only if: committing to never adding /<service>/, /<location>/, or other root-level taxonomies.

Pattern C: /for-<audience>/ — NOT RECOMMENDED

Examples: /for-farmers/, /for-fleet-managers/

Real-world use: Common in SaaS (stripe.com/use-cases/), zero observed in 8-site service-business sample (see Field survey (May 2026): the /for-/ URL pattern was observed on ZERO of 8 multi-vertical service sites).

Tradeoff: Reads as marketing copy in the URL. Useful only for paid-traffic landing pages, never primary IA.

Pattern D: /services/<service>/<vertical>/ matrix — USE SPARINGLY

Examples: /services/delivery/agriculture/, /services/technical-advice/fleet/

Tradeoff: Encodes the matrix in URL space — powerful for SEO, but creates a combinatorial explosion. 4×4 = 16 pages: fine. 6×6 = 36 plus the canonical hubs: content burden is real. Per Google Search Central: faceted navigation creates combinatorial duplicate URLs; not search-friendly by default and Mueller on near-duplicate vertical/location pages: fold them into one stronger page unless each has something unique, each cell must have substantively different content or pages get folded.

Recommended only when: each cell has genuinely vertical-specific content (case studies, regulations, SKU lists).

Pattern E: /<vertical>/services/<service>/ — VERTICAL-LED MATRIX

Examples: /agriculture/services/delivery/, /agriculture/services/technical-advice/

Tradeoff: Same as Pattern D but signals "vertical is primary" to Google and users. Often the better choice for distributor and accounting-firm sites where vertical is the entry point.

Recommended progression for B&J: Start with Pattern A. If high-value matrix queries justify expansion later ("agriculture lubricant delivery Waterloo"), extend with Pattern E.