House of RunganoWebsite Structure — Find a [Service] · local discovery — search, map, straight to booking
Optional Announcement — one timely line, an offer, a launch, or a notice ×
LogoTagline
[Primary Offer] [Secondary Offer] Why [Brand] About TeamContact Blog & News [Community] Join [Community]Resource Library OptGuides OptEvents OptMembership Opt Primary action
01 — Page banner
H1 · Page heading

Find [Offer] near you

02 — Search, map & locations
Search · location — the field accepts whatever the country uses: postcode, ZIP or city
Enter your locationSearch
Map — every location pinned; the search filters pins and cards together
Results · one card per location
H3 · Location

[Location name]

[Street address] · [Phone]
[Opening hours] · [Distance from search]
Book at this location
H3 · Location

[Location name]

[Street address] · [Phone]
[Opening hours] · [Distance from search]
Book at this location
H3 · Location

[Location name]

[Street address] · [Phone]
[Opening hours] · [Distance from search]
Book at this location
We build the discovery; the client’s booking platform takes the booking — each card’s button links straight out to the booking page for that location — or, where per-location pages are built, the card links to that location’s own page first. Every card carries the location’s full NAP; the per-location pages carry the schema and Google Business Profile links, which makes them the strongest local-search assets on the site.
03 — Lead magnet & community Optional
Lead magnet · genuinely useful

Download our [Lead magnet]

[One line making the value explicit — what they get and why it helps]
Email addressDownload
Community Optional

Join to access [Community / VIP / Resources] for [Transformation]

[The low-commitment reason to join before buying]
Join freeJoin
For the visitor who searched but is not ready to book — captured into the nurture sequence instead of lost.
04 — Objections & FAQ
H2 · Section headline

Before you [Action]

H4 · Sub-headline

Everything to know before you [Action]

[Real “near me” or location question searched for this service]
[Real “near me” or location question searched for this service]
[Real “near me” or location question searched for this service]
Two question sets live here: the searched “near me” and location questions for this service, and the practical booking questions — times, parking, what to bring, how to choose a location. FAQPage schema on what is visible here only, never duplicated from the offer page.
05 — Final CTA
H2 · Closing invitation · Join [Brand] to [Mission outcome]

Join [Brand] to [Mission outcome]

Format · Join [Brand] to [Mission outcome]. The close restates the mission as an invitation rather than a demand; the button repeats the page’s one action — book at a location.
[Action] + [Offer]
Find a [Service] · Section 01

Page banner

What this page is for

Local discovery. It catches the “[offer] near me” searches, lets the visitor find their location, and hands them straight to the client’s booking system. One of these exists per offer where the client is local or multi-location.

H1 format
Find [Offer] near you

Two targets — the offer term and the near-you modifier, exactly how the search is typed.

Built from
H1Offer + near-you modifier
LocationsThe Locations field
Find a [Service] · Section 02

Search, map & locations

Format
Search field → map with every location pinned → one card per location: [Name] · [NAP] · [Hours] · Book
Rule

We build the discovery; the client’s booking platform takes the booking. The search filters the pins and the cards together, and each card’s Book button links out to that location’s booking page. Every location carries its own LocalBusiness schema and Google Business Profile link — this is the strongest local-search page on the site.

Built from
LocationsLocations field — name, NAP, hours per site
BookingThe client’s booking system URLs
Find a [Service] · Section 04

Objections & FAQ

Rule

Both question sets: the searched near-me and location questions, plus the practical booking questions (times, parking, what to bring, choosing a location). Schema only on questions visible here, never duplicated from the offer page.

Built from
QuestionsSearched near-me set + client FAQ link
Persistent

Header, nav & tagline

Navigation

Five to seven items. About and Community open dropdowns. Community’s Resource Library, Guides and Events are sections of the Community page — the dropdown jumps straight to them — and show only when the client has that content. Hiring and shop live on external platforms (ATS, storefront) linked from the footer. Lower-intent links go to the footer, not the bar.

Logo & tagline

Logo top-left with the enduring tagline beneath it. The tagline is never the H1 — the H1 is page-specific, the tagline is not.

CTA colour

One colour, used only on CTA buttons so it always signals "action". It must contrast strongly with the page and stand out — ideally a colour used nowhere else on the site. Warm, high-contrast hues (orange, green, a confident blue) tend to convert best, but the exact hue matters less than that it pops, stays consistent, and passes contrast for legibility.

Optional add-ons

Switched on by the client's model, not shown in the bar by default:

ShopEcommerce only
Find a ServiceNational providers — a CTA, or a nav dropdown when multi-location
Work With UsService providers — usually a CTA
Find a [Service] · Section 03 · optional

Lead magnet

Rule

For the visitor who searched but is not ready to book. Topic-matched to the service; the download is the Brandi platform’s capture form and names the nurture sequence it enters. The section is V1 — the identical pair from the homepage: magnet card plus the optional community card. Never a lone card; if the client runs no community, the community card hides and the magnet card keeps the same width and position. Sits between the locations and the FAQ so the blue capture band stays clear of the blue close.

Built from
MagnetLead magnet field
Section 12

Footer

The forms — a site-wide rule

Every form on the site — the newsletter here, every magnet download, the contact form, the community join — is the Brandi platform’s CRM capture form, embedded and styled to the design system. Every submission lands in the CRM tagged with its source and enters its named sequence. Never a mailto link, never a third-party form.

Baseline line
© [Year] [Brand] · [Address] · [Contact]
Address & local search

Consistent name, address and phone across the web is what local search scores. When a brand won't publish a street address, the footer carries city or region only, and the full details live on the Contact page with local business schema and a Google Business Profile. The signal is kept; the street address is not forced into the footer.

Sensitive fields

In care, health or youth sectors, a care or crisis resource in the footer is required, not optional.

Built from
DescriptorElevator pitch
AddressLocations
ContactBusiness phone / email
LabelsFixed nav — never keyworded
Optional · live chat Chat with us
Sticky mobile CTA · optional Primary action ?
On phones, the one primary action stays pinned as the visitor scrolls. Switched on where mobile traffic and a single clear action make it worthwhile.
Social rail · from the Socials field Instagram Facebook LinkedIn YouTube