Wireframe Plan · for review
→ Read the v1 copy draft for these pages
Core pages we'll expand off the homepage
Section-by-section structure for the service pages, About, Case Study and Contact — built so the
three service pages double as SEO templates (websites-for-plumbers, websites-for-electricians, …). This is structure, not final copy.
Nothing here is built yet — confirm or change it and I'll build.
Global — built once, used everywhere
Per-service — differs Websites vs SEO vs Ads
Per-trade — the SEO knob (plumbers/sparkies/…)
Page-unique — one-off content
Each block below is colour-coded by how much it's reused. The more
gold/global and blue/per-service, the less work each new page is.
1 · The templating idea (why this saves months)
Every service page is the same template with three layers swapped in. A trade variant
("websites for plumbers") is the Websites page with only the green layer changed — so a new
SEO page is ~20 minutes of data, not a rebuild.
Global
Nav, footer, reviews strip, FAQ shell, final CTA (form + calendar), trust bar.
Built once as shared components. Identical on every page.
Per-service
The value props, the "what's included / pricing" table, the process, the cross-sell.
Written once per service and shared across all that service's trade variants.
Per-trade
The H1 + page title + meta, the answer-first intro, example Google searches,
trade words & examples. ~15% of the page — this is all that changes per trade.
The Service × Trade matrix → URL pattern
Generic -for-tradies page ships first; trade variants are
generated from a data file (one row per trade) using the same template.
| Service ↓ / Trade → | tradies (generic) | plumbers | electricians | + builders, roofers, … |
| Websites | /websites-for-tradies | /websites-for-plumbers | /websites-for-electricians | /websites-for-{trade} |
| SEO | /seo-for-tradies | /seo-for-plumbers | /seo-for-electricians | /seo-for-{trade} |
| Google Ads | /google-ads-for-tradies | /google-ads-for-plumbers | /google-ads-for-electricians | /google-ads-for-{trade} |
Build order I'd suggest: ① shared global blocks → ② Websites generic → ③ SEO + Ads generic (clone the template) →
④ About, Case Study, Contact → ⑤ switch on trade variants from a data file once the generic three feel right.
We prove the template on one page before multiplying it.
2 · Service-page master template
One template powers Websites, SEO and Google Ads — and every trade variant of each.
Tags show what swaps. The blue blocks carry each service's unique payload (next section).
Service page/{service}-for-{trade}
e.g. Websites for plumbers · same skeleton for all 9 service×trade combos
1
Hero
Keyword H1 + subhead, trust pills (5.0 Google · AU-based), primary CTA → book a call.
▭ H1 swaps per trade · layout shared
Per-trade
2
Answer-first intro (GEO/AI-search)
40–60 word answer under a question H2 ("What makes a good plumber website?") — wins AI Overviews & ChatGPT cites.
¶ question H2 + short answer
Per-trade
3
Why ours / Standards
3 icon-left value cards. The 3 props differ per service; trade examples slot in.
▢ ▢ ▢ (3 cards)
Per-service
4
What's included / Pricing
The big differentiator — a table. Websites: inclusions. SEO: 2 tiers. Ads: cadence + tiers.
▤ comparison / pricing table
Per-service
5
Proof / mini case study
Reuses the homepage before/after card. Trade-matched case if one exists, else the generic Mr Loo result.
◧ before/after slider + metric
Global*
6
Process — 4 steps
Reach out → Plan → Build → Live. Same shape as homepage "How it works"; copy barely changes.
①→②→③→④
Shared
7
Pairs / cross-sell
Links to the other 2 services ("what Google Ads add", "what SEO adds"). Keeps people in the funnel.
▢ ▢ (2 cross-links)
Per-service
8
Reviews strip
The homepage testimonials carousel, reused verbatim.
★ swipeable reviews
Global
9
FAQ
Answer-first Q&As (also schema). Mostly per-service; a couple swap per trade.
▾ accordion
Per-service
10
Final CTA
Form + GHL calendar — the exact homepage block (already wired to GHL).
▤ form | 📅 calendar
Global
*Proof is a shared component; the case it shows can be swapped per trade when we have a matching one.
3 · What's unique per service
Only blocks 1–4, 7 & 9 carry different content between Websites / SEO / Ads. Everything else is shared. Here's the payload for each.
Websites
Hero angle: "Found on Google, built to win clients, live in 2 weeks."
3 Standards: custom-built · built to be found · builds trust before they call.
Table: what's included (pages, 95+ Lighthouse, CRM lead capture, hosting, no lock-in).
Pairs → Google Ads + Local SEO.
SEO
Hero angle: "Rank page 1 in the areas you actually work."
3 Standards: compounding free leads · local rankings · no ad spend.
Table: 2 pricing tiers (Managed Monitoring $300–400/mo · Flagship $1–1.5k/mo). + extra Results/ranking block.
FAQ adds: "How long does SEO take?" · Pairs → Ads + Websites.
Google Ads
Hero angle: "Leads landing this month, not in six."
3 Standards: leads now · daily management · no learning-phase excuses.
Table: cadence (daily/weekly/monthly) + tiers (from $2k+GST/mo → multi-state).
Pairs → SEO + Websites.
Per-trade swap (all 3 services): H1 + title + meta description, the answer-first intro, example searches
("emergency plumber [suburb]"), and trade words/examples. Everything else is inherited. That green layer = one data row per trade.
4 · About page /about
Founder-led, text-first (B2B — no stock portraits). Carries the Person schema that helps AI engines trust the brand.
About/about
"Who runs KINGTRADIE?"
1
Hero — who runs it
Founder-led headline + answer-first intro. Text, not portrait.
▭ headline + lede
Unique
2
Founder story
Carpenter-values origin → why KT exists. The 5-part story (already drafted in vault).
¶¶ narrative
Unique
3
How we're different
Anti-"WordPress agency" positioning · values · no lock-in. 3–4 points.
▢ ▢ ▢
Unique
4
Proof — reviews + numbers
Reviews carousel + counters (clients, reviews). Reused.
★ + #s
Global
5
Person schema (invisible, SEO)
name, jobTitle, sameAs chain (IG/FB/ABN). Surname/credentials = [TBD with you].
{ } JSON-LD
Unique
6
Final CTA
Form + calendar.
▤ | 📅
Global
5 · Work index + Case study /work · /work/{client}
The nav "Work" link needs a home (index grid), and each result needs a detail page. The case study is itself a
small template — one data set per client.
Work index/work
Grid of case-study cards (replaces old /results)
1
Hero
"Real work, real results." Short.
Unique
2
Case-study card grid
One card per client → links to detail. Template grid.
▢ ▢ ▢ / ▢ ▢ ▢
Template
3
Reviews + Final CTA
Reused.
Global
Case study/work/{client}
e.g. /work/mr-loo · one data set per client
1
Hero — client + headline metric
"$120k extra work in 3 months." Logo + trade.
Template
2
Snapshot bar
Trade · location · services · timeframe.
▤ chips
Template
3
Challenge → What we did
Before state + workstreams (site/SEO/ads). Per client.
Per client
4
Before/after slider
The homepage compare component, client images.
◧ slider
Global
5
Results + client quote
Metrics + their Google review (reused from reviews data).
Template
6
Final CTA
Form + calendar.
Global
Note: the homepage review cards + case-study "See more" currently point at /results.
When this ships they'll repoint to /work & the per-client pages (tracked in RESTORE-LINKS.md).
6 · Contact page /contact
Mostly the homepage CTA block as a standalone page + direct details. Light by design.
Contact/contact
Book a call or reach us directly
1
Hero — "Let's talk"
Short headline + reassurance ("AU team, reply within 1 business day").
Unique
2
Form + GHL calendar
The exact homepage CTA block — already wired to GHL.
▤ form | 📅 calendar
Global
3
Direct details
Phone · email · Instagram · ABN · hours.
▤ list
Unique
4
Mini FAQ (optional)
A few objection-handlers. Subset of the FAQ component.
▾ 3–4 Qs
Optional
7 · Defaults I picked — change any of these
- URL pattern = /{service}-for-{trade} (matches the existing /websites-for-tradies, best for exact-match SEO). Alt: subfolders like /plumbers/websites.
- Trade list to target first: plumbers, electricians, builders, carpenters, roofers, landscapers, painters, HVAC. (From your $1–3m ICP.)
- "Work" not "Results": renamed the case-study area to /work with real per-client detail pages. Old /results grid is replaced.
- About stays text-led (no stock photos) per the B2B call. A real founder photo is optional, not blocking.
- Pricing shown on service pages (websites from $10k, SEO tiers, Ads from $2k) — flag any number you don't want public yet.
- Trade variants come last — we prove the generic 3 first, then switch them on from a data file.
Your call: build it out now as planned, or tell me what to change first. If green-lit, my order would be:
shared blocks → Websites (generic) → SEO + Ads → About → Work + Case study → Contact → then trade variants.