House of RunganoWebsite Structure — Blog index · a feeder page that routes search traffic to the offers
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

[Topic] advice & guides for [Ideal Client]

Search · every query is logged — unanswered searches become the next articles
Search articlesSearch
Intro · why this content is worth their time

[Topic] for [Ideal Client], from the team at [Brand]

02 — Posts
H2 · Section headline

Latest [Topic] articles

Filters Optional · each filter needs its own indexable page, not a query string
All[Category][Category][Category][Category]
[Category]
H3 · Post title

[Post title]

[Excerpt — the first lines of the article, pulled automatically]
[Date] · [Author] Optional
[Category]
H3 · Post title

[Post title]

[Excerpt — the first lines of the article, pulled automatically]
[Date] · [Author] Optional
[Category]
H3 · Post title

[Post title]

[Excerpt — the first lines of the article, pulled automatically]
[Date] · [Author] Optional
123Next
Capture · style V2, the slim strip — always three supporting magnets, topic-spread for a browsing reader
[Lead magnet description] Download [Lead magnet description] Download [Lead magnet description] Download
03 — Topic FAQ
H2 · Section headline

[Topic] questions, answered

[Topic-level searched question no single article owns]
[Topic-level searched question no single article owns]
[Topic-level searched question no single article owns]
Topic-level questions only — the ones too broad or too small for their own article. Article-level questions stay on their articles, FAQPage schema is never duplicated, and every answer links on to the article or offer that goes deeper.
04 — 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 — a mission “to help young people find their voice” becomes “Join [Brand] to find your voice” — with the joining verb tuned to the brand’s voice. The button repeats the page’s one action, so the close asks nothing new.
[Action] + [Offer]
Blog index · Section 01

Page banner

What this page is for

A feeder page. Its job is not to convert directly but to catch search traffic and route it to the offer pages. Judge it on how many readers reach an offer page, not on time on page.

H1 format
[Topic] advice & guides for [Ideal Client]

Two targets — the topic term and the audience. The nav label (“Blog & News”) stays the menu’s fixed, never-keyworded label; the H1 does the ranking work. The breadcrumb keeps the nav label so orientation still matches the menu.

Search

A search bar sits in the banner. Every query is logged: searches with no good result are the content plan’s next articles.

Built from
H1Topic + ideal client
SearchSite search, query logging on
Blog index · Section 01b

Intro

Format
[Topic] for [Ideal Client], from the team at [Brand]
Rule

No CTA here. The reader arrived to read, and the ask comes later at the magnet.

Built from
IntroTopic + ideal client
Blog index · Section 02

Post list

Format
H2 · Latest [Topic] articles
Card · image on top, [Category] label, H3 [Post title], excerpt — [Date] and [Author] optional per brand
The filter rule

Category filters must resolve to their own indexable pages with their own H1 and meta, not query strings. A filter that only exists as a query string means every one of those terms has no landing page, which is the commonest way a content library wastes its own search value.

Pagination

Paginated pages stay crawlable. Each page needs a self-referencing canonical, never one pointing back to page one.

Built from
PostsThe article collection, newest first
FiltersArticle categories
Blog index · slim strip

Repeat capture

Rule

Blog’s one capture: three supporting magnets, topic-spread because a browsing reader could match any of them. The main magnet’s V1 card lives on the homepage and the deep pages (Article, Find, Location) — a page holds either the card or the strip, never both; only the homepage carries both. Placed after the posts, in learning mode, before the FAQ so asks never stack against the close.

Built from
MagnetsAdditional lead magnet fields
Blog index · Section 03

Topic FAQ

Format
H2 · [Topic] questions, answered
Rule

Earned by the keyword-led H1: the index now owns a topical primary, so it carries the topic-level searched questions — the ones too broad or too small for a single article. Never duplicates an article’s questions or its schema; every answer links to the article or offer that goes deeper.

Built from
QuestionsTopic-level rows of the FAQ-by-page research tab
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
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