Measure
Search Console reports impressions, clicks, position and CTR per query and page. GA4 reports the sessions that follow. Movement is visible week over week.
The engine does the volume.
You hold the three decisions that matter.
Content is produced in bursts, and a person checks it before it advances. What ships is in your voice, accurate, and yours.
The engine handles research, drafting and formatting at volume. You hold the three decisions that decide whether the work is right: what gets built, whether it reads as you, and what goes live. Nothing moves past a checkpoint without you.
Three bursts, three checkpoints, then live.
The engine moves fast between checkpoints. You weigh in at the three moments that decide whether the work is right, reads as you, and is ready to ship.
Research and architecture
I find real demand and map it into clusters, grounded in the queries and pages you already earn.
YOU DECIDE
Approve what gets built.
Brief and draft
White space briefs, then drafts written to spec and in your voice, ready for your editorial read.
YOU DECIDE
Lock voice and accuracy.
Format and stage
Each piece is converted to your site's posting format and staged as a draft under your account.
YOU DECIDE
QC it and go live.
LIVE . the piece is published on your site, under your name, and starts earning
What happens inside each burst.
The detail matters, because it is where the difference between a library that compounds and a calendar that gets filled actually lives.
Research and architecture
I connect Search Console and GA4 first, so research starts from demand you already measure rather than from an external tool's guess.
- Analyse the site and surface content pillar opportunities
- Run keyword research per pillar, expanding into hundreds of candidates
- Reduce to the essential terms, grouped into clusters of roughly six articles
- Deduplicate against your live and in progress content, so nothing cannibalizes what you already rank for
Brief and draft
Every article is engineered to rank in Google and to be quoted by AI answer engines. Two standards do that work, and both go in from the first draft.
- White space briefs: title and meta, vetted external sources, internal links into your existing library, and the FAQ gaps your competitors leave open
- Answer first structure: a clear definition and an at a glance summary up top, then question style headings answered in their opening lines
- Clusters drafted in parallel, in your voice and to spec
- You run an editorial review in Word: read, edit, save
Format and stage
Publishing is the least interesting part of the process and the easiest to get wrong, so it is the part I automate hardest.
- Each article converted to your site's posting format
- Structured markup added per article, so search engines and AI answer engines can read what each page is
- Posted to your site as a draft, by you or by the engine through your own backend access
- You QC the draft and add the hero image
- You publish it live
What I handle, and what stays yours.
The engine handles
- Demand research and cluster architecture
- Briefs, drafting and structure at volume
- Schema, internal linking and answer first formatting
- Conversion and staging into your site
- Weekly measurement against your own baseline
You decide
- Which clusters and articles get built at all
- Whether the draft reads as you, and whether it is accurate
- What goes live, and when
- The hero image and the final read before publish
Publishing is not the finish line.
Once a cluster is live, three activities run continuously on the library you already have, and each one compounds on work already done.
Optimise
I find pages earning good impressions but low clickthrough, then rewrite the title and meta to lift it. No new ranking required, and often the fastest gain available.
Refresh
When a page that once ranked starts slipping I refresh it rather than start over: update the content, tighten the structure, re earn the rank.
The library is an asset I maintain, not a one time build.
The proving ground.
This process runs on The Gourmet Host, my own product, where a focused SEO and AEO strategy began on 22 February 2026. Search impressions in the latest 28 day window came to 600,569, against 59,643 in the window when the strategy began. Website users grew from 1,247 to 11,061 over the same pair of windows.
The pace varies by site. Domain age, competition, the shape of your search demand and your site health all move it, which is why every engagement opens with a diagnosis and every result is measured against your own baseline rather than mine.
I will show you the same read on your own site.
From your own Search Console and your own baseline, not mine. That read is the first thing we do together, and it decides what the engine gets pointed at.
Same process, same standards, three levels of involvement.
Pick the one that fits where you are. You can move up a tier mid engagement, and the work you have already done comes with you.
Done by you
For founders who run the engine themselves, with me coaching alongside.
- Working sessions where we build AI into your daily processes
- Coaching toward self sufficiency in your own analysis and content
- A range of capabilities stood up with you, from research through publishing
MOST POPULAR
Done with you
We run onboarding and the production cycle together.
- SEO, AEO and diagnostics
- Content strategy
- Website enhancement and redesign
- Brand aligned marketing design
- Delivered collaboratively, with client review as frequently as you want it
Done for you
I operate the engine on your behalf for a fixed term.
- Everything in Done with you
- I operate the suite end to end
- Monthly traction and growth scorecards
- Quarterly strategy reviews
- Full hand off at end of term