Rebuilding Master Plan
Private strategy doc. Enter hub password to continue.
That's not right. Try again.
Master Improvement Plan + Automation Blueprint
Early-bird ends Fri July 24 · cohort starts Sun Sept 20, 2026← Back to the Bob hub · Hub index
The whole strategy in one line: the grid scan proved Bob ranks #1 everywhere Google shows him, so this isn't a ranking problem, it's a radius and follow-through problem. We don't chase ranking tweaks. We widen the circle of people who see him and make sure nobody who's interested slips through a crack, all before the early-bird closes July 24 and the cohort starts Sept 20. This page consolidates every plan from the past week and shows how much of it can run without you touching it.
1. What the week actually proved
Four findings from this week frame everything below:
- Grid scan (Niwot, 2026-07-12): rank 1.0 wherever visible, but visible at only 88 of 225 points for the core keywords. He owns the center and disappears at the edges. Reach, not ranking. (see the heatmap)
- GA4 deep-dive: organic search beats direct traffic, the homepage hoards 73% of landings and doesn't pass authority down to the pages that would rank locally, and conversion tracking has been broken for two years (so we've been flying partly blind).
- GHL site re-audit: zero structured data, malformed meta, a live placeholder headline, a wrong footer ZIP. All real, all fixable, but all on a platform Bob may leave, so they become the next platform's launch checklist rather than work we sink into GoHighLevel now.
- Reviews: ~301 on the listing, 288 cleanly captured. A quick top-up makes "over three hundred 5.0-star reviews" bulletproof everywhere we say it.
2. The plan, by leverage (what moves Sept 20 seats)
Ordered by effect on filling the cohort. Tier 1 is the 11-day sprint to the early-bird deadline; Tier 2 widens the radius over the summer; Tier 3 quietly stops leaks.
Turn the early-bird deadline into a campaign
The $1,099 early-bird is the single best conversion lever we have, and it expires in 11 days. Everything here is written and ready; it needs one Bob approval and one browser session.
- Countdown email sequence to Bob's list: "10 days left" (now), "final days" (July 21), "last day" (July 24). Drafted, Bob approves once, loaded via GHL.
- Front-loaded GBP offer posts carrying the early-bird and the $30 intro workshop. Part of the 30-post bank (Section 3).
- The two Gmail drafts to Bob (analytics good news, graduate-roster favor) fold into this one approval ask so he says yes once, not three times.
Fix the reach gap the map showed
- Google Business Profile is the #1 radius lever (about 32% of local-pack rank) and it lives at Google, so it survives any platform change. Weekly posts, Q&A pre-seed, service-area towns, fresh photos, next secondary category ("Counselor"), and the Denver/Cherry Creek second listing when the venue locks. Primary stays "Divorce service" (verified, don't touch).
- Town pages for the towns where the map showed him fading: Boulder, Longmont, Louisville, Lafayette first, then the grid reorders the rest. "Areas served," never "class meets here." Drafts are being written now (Section 3).
- Article drip: the 24 divorce articles publish 2/week to Bob's blog on a 12-week calendar, each teased on GBP a week later. Zero new writing, three months of fuel. Ready, gated only on Bob's proofread.
- Citations + NAP cleanup: one canonical name/address/phone across the web, then Tier-1 directories (BBB, Yelp, Apple Maps, Bing) and therapist directories (Psychology Today, GoodTherapy). The Whitespark cleanup kicks this off.
- Monthly re-scan with the grid tool's delta mode, ~50 cents, so we measure the radius widening instead of guessing.
Stop losing people we already reached
- Reviews top-up to the full ~301 (one browser session).
- FDAS results email gap: Charlene's results email never arrived, which means low scorers may be getting silence. That's a lead leak. Investigate and fix. (Stage 1 fix ready: the one-session GHL runbook.)
- Reviews velocity loop: every graduating cohort invited to leave a Google review, owner responses within 48 hours. Keeps the moat alive and is itself a ranking signal.
3. Local SEO, consolidated (platform-proof vs. parked)
The local SEO work splits cleanly, which matters because Rebuilding may leave GoHighLevel. We do the platform-independent work now (nothing wasted if he migrates) and park the on-site technical work until the platform decision.
| Workstream | Platform-safe? | Status |
|---|---|---|
| GBP posts, Q&A, photos, categories, 2nd listing | Yes (lives at Google) | Post bank drafting now; cadence set |
| Reviews velocity + top-up | Yes | Top-up needs one browser session |
| Citations + NAP cleanup | Yes | Gated on Whitespark start |
| Town pages (content) | Content portable; publish step waits | 4 Tier-1 drafts writing now |
| Article drip (content + calendar) | Content portable | Ready, gated on Bob's proofread |
| Schema, meta fixes, homepage internal links | No (on-site, platform-specific) | Parked: becomes next platform's launch checklist |
| GA4 conversion tracking | Rebuild on next platform | Launch-day requirement, day one |
The old PLAN-ghl-seo-quick-fixes.md stays ON HOLD by your call. Its findings (zero JSON-LD, malformed meta, placeholder headline, wrong ZIP, "hundreds" review copy) aren't lost: they're the checklist we run the day the new platform goes live.
4. The automation blueprint (how little you touch)
You asked to not be the bottleneck: no hand-holding, no answering the same question twice. Here's the honest map of every recurring piece of this plan and who actually does it. The rule I'm designing to: anything that touches Bob's Google, GHL, or Facebook accounts needs your logged-in browser at least once, so we batch all of it into single sessions instead of many. Everything else, I automate or do myself.
| Task | How it runs | Your involvement |
|---|---|---|
| Article publishing to the blog | Scripted porter + scheduled push, auto-triggers the site rebuild. If Bob shares a GHL API key, fully scripted; otherwise a paste-ready queue. | Once Bob's proofread + a key or one paste session |
| GBP posts, 2/week | 30-post bank pre-written; loaded in one batch session, then I refill the bank monthly. | Once/mo one browser session to load |
| Monthly grid re-scan | Scheduled task, runs the scan + delta heatmap, ~50 cents, emails you the result. | Auto nothing |
| Daily-task email to Bob | Cloudflare Worker, already live, 6 AM MT. | Auto nothing |
| Reviews velocity loop | Graduation invite + owner-response drafts I write; Bob/Kathy hand out the link. | Auto I draft, they hand out |
| Town page + email drafting | I draft everything; you never write. | Auto nothing |
| Citations submission | Whitespark does the cleanup; I handle Tier-1 directory batch. | Once the signup itself |
| Early-bird / countdown emails | Drafted; loaded in the same GBP browser session. | Once Bob approves, one load |
Net: the recurring load on you drops to roughly one browser session a month (to load the GBP batch and any queued emails), plus a couple of one-time approvals from Bob. The scan, the daily email, and all drafting run on their own.
What I genuinely can't do for you
Two hard boundaries, by design: I can't create accounts or enter payment details (so Whitespark signup is yours, 90 seconds, I hand you the exact link), and I can't send anything on Bob's behalf or post publicly without your go-ahead in the moment. Everything up to that final click, I prepare.
5. The short decision queue
I've squeezed the things only a human can decide down to this. Nothing else is waiting on you.
You
- Whitespark Listings Service signup (~$80 one-time). I hand you the click-to-act.
- One browser session to load the GBP batch + countdown emails.
- One browser session for the reviews top-up (~15 min).
Bob (bundled into one ask)
- Proofread the 24 articles (unblocks the whole drip).
- Approve the countdown email sequence.
- GBP: confirm one canonical phone number; Denver venue timing.
- Who owns the
fdas100.rebuilders.workers.devworker (gates the score-email fix).
6. Source plans (this consolidates all of them)
This page pulls together, and supersedes as the single view of, the following working docs in the Rebuilding repo:
research-notes/organic-growth-strategy-local-2026-07-10.md(the master local strategy)strategy/01-local-seo-checklist.md(the tactical checklist)research-notes/article-drip-and-gbp-teaser-plan.md(the 12-week drip)research-notes/gbp-post-bank-2026-07.md(the new 30-post bank)content/town-pages/*.md(the new Tier-1 town pages)PLAN-ghl-seo-quick-fixes.md(ON HOLD, becomes the next-platform launch checklist)- the Niwot grid-scan findings and the tooling comparison
The one thing to hold onto: it's a radius problem. Bob already wins wherever he's seen. Every item above is in service of getting him seen by more of the right people before Sept 20, with as little of it landing on your desk as I can manage.