A rebuild of hrgurus.com.au on a single design system — so every page looks like the brand, every landing page you make yourself comes out on-brand, and none of your search history is lost on the way.
“It's like a Frankenstein ugly baby we've just kept adding to.”
Emily
Everything rebuilds on one design system — your dark green, your fonts, your components. Every page, same DNA.
“You've got your templates, guys — off you go.”
Jessy
Templates for every page type, plus a Claude connection to your own site. You launch offers the day you think of them.
“We don't want to lose all of our current SEO stuff.”
Jessy
Every kept post moves with its history; every removed one redirects somewhere useful. Paul stays in the loop. Nothing rankable gets deleted.
“I don't think we need to over-engineer this.”
Emily
Agreed. No discovery phase, no committees. You've done the thinking — we build, you populate.
Three lanes, no waiting on each other. And as you said in the meeting — it's a really good test of whether you can self-manage it. We think you can.
This is the part you asked for — quick landing pages without waiting for a developer. It exists, it works on a copy of your own site, and here's the proof.
The walkthrough — Hilary builds a landing page on your actual staging site. Open in Loom if the player doesn't load.
Say what you want. “A landing page for the October leadership intensive — here's the copy.”
Claude designs it inside your design system — same colours, same fonts, same components as every other page.
Push to the site. The page appears with your real header, footer and menu — the bit your current DIY pages are missing.
Sale's over? Pull it down. One click. No developer, no waiting.
Your membership page today — heaviest page on the site
Our target for the same page on the new system — you'll see the real number on staging
Design system to change when you want a new look — not 63 pages, one by one
Already seen it? Meet the Gurus — the flip-photo page, live on the staging site.
Fixed scope from what we agreed on the call: four service pages, about + team + profiles, blog, landing template, fewer than 63 pages, shop and old builders gone. The investment and payment schedule are in the statement of work that comes with this proposal.
Your dark green + brand palette and fonts locked in as a system. Templates for home, the four service pages (identical-but-same, as requested), about, team + individual profiles, blog post + archive, and the reusable landing page. One “Get HR Help” CTA throughout, wired to your Zoho form. Built with accessibility in mind — for an HR business, a website everyone can use isn't optional polish.
Fresh WordPress build — nothing old carried over. The blog posts worth keeping (about 150 of 502) move across cleaned and re-linked; Avada, Elementor, WooCommerce, ClickFunnels, the shop and the old videos don't. Your plugin count drops from “20 billion” to a handful.
Every pruned post 301-redirects to the page that should inherit its value. One clean schema graph — so Google and the AI bots get a straight answer about who HR Gurus is. Coordinated with Paul's ongoing work, not across it.
One Google Analytics (not two), tracking that actually fires when someone calls, emails or submits the form — and the new bit: analytics set up to identify visitors arriving from ChatGPT and Gemini, which you told us is already where clients come from. Plus a simple UTM cheat-sheet for Jessy's QR codes and campaigns.
The Claude connection to your site, set up safely (keys locked in a vault, staging-first rules). Your design system lives on the site itself, so everyone's Claude builds the same way — and you can create new templates, not just fill existing ones. Pages published this way get their search titles, descriptions and schema written automatically.
Plain-English guides for the things you'll actually do — make a landing page, add a team member, launch an offer, pull a page down — right there in your site's admin, and updated whenever the site changes so they never go stale. Plus a hands-on training session with the team, recorded so anyone who joins later can watch it.
You're already on a care plan with us — security, updates, backups, monitoring all continue as they are. The rebuild adds a self-service support lane on top: when you're mid-page-build and want a hand or a sanity check, that's part of the arrangement, not an extra. And for the small stuff — a heading, a photo, a spacing niggle — you click the thing on the site, type a comment, and it becomes a task with everything attached. Ask your Claude to action it, or leave it for us. No screenshots in emails.
The blog earned four years of trust with Google. The rebuild is designed to concentrate that, not scatter it.
The ~150 posts doing the work move as-is. The dead 289 redirect into the pages they should have been feeding all along.
Right now one blog post gets more Google visits than all 16 service pages combined. Internal links finally point the blog's audience at the four things you sell.
You told us clients are already finding you through ChatGPT and Gemini. We set the analytics up to identify and report those visits — measurement instead of guesswork.
Redirect map and structure changes shared before anything moves, so nothing we do cuts across his work.
That's the goal you named at the end of the call — this is the machine that does it. The statement of work has the numbers. Send the design specs when you're back and we start.