Content architecture
The public network groups educational guides by topic and audience, connecting relevant guides, calculators and specialist brands.
Case study 02 · Built and operated in-house
The Rate Family: four brands, one codebase.
A network of four Canadian insurance and mortgage education sites — built, run and maintained by Webhub4U on a single platform, with distinct brand identities, shared development patterns and an ongoing search programme.
The challenge
Four identities, one foundation.
Each brand needed its own look, voice and search identity. Four separate websites would have meant four codebases, four content systems and four sets of bugs to chase — for a team of one.
And the subject matter is money and insurance: content where accuracy and clear disclosure aren't optional. The platform had to make the careful path the default path.
What we built
A shared platform for four brands.
One app, four sites
The shared V2 codebase supports four brand identities through host-based theming, with separate visual styles and navigation for each brand.
Shared contracts, distinct brands
The V2 codebase separates its frontend, backend and shared contracts. A shared API client connects each brand to deterministic development data.
Search plumbing for a multi-domain network
Our search work covers metadata, canonical ownership, sitemaps and links between relevant pages. These foundations need ongoing checks and measurement as the network evolves.
Guardrails written as code
The V2 development environment explicitly marks quote and card fixtures as mock data. Tests and shared contracts help keep those fixtures distinct from live offers.
SEO work
Give useful content a clear structure.
Measurement comes next
Search Console impressions, non-brand clicks and qualified enquiries will establish the baseline. This case study does not yet report a ranking or traffic increase.
How it runs
Public websites. An evolving product.
The public education network is live. Its V2 application is a development environment with explicit limits:
- The public education websites and V2 development environment have distinct roles.
- V2 quote and card data are mock fixtures, not live offers.
- The V2 application does not provide a live purchase or bind service.
- Measured search and enquiry outcomes will be reported with dates and sources.
By the numbers
4public education brands
1shared V2 codebase
The four public brands and shared V2 codebase describe the scope of the work. Traffic, ranking and enquiry outcomes will be added once they are measured and shareable.
Next.jsReactTypeScriptNestJS (V2)Shared API contracts
What this means for your project
The same engine, pointed at your business.
Multi-location or multi-brand?
The same one-platform approach serves franchises, multi-location trades and holding companies — one codebase to maintain, separate identities for each brand.
Trust-sensitive industry?
Health, finance, legal, trades: source records and human review belong in the publishing workflow. Automated checks support that review; they do not guarantee accuracy.
Small team, big workload?
Shared components and contracts can reduce repeated implementation work. Editorial and automation workflows should keep explicit review steps.
Ready to look like the business you actually are?
Book a free 20-minute call. We'll look at your current online presence together and tell you exactly what we'd do — even if you don't hire us.