A prism does not invent colour. It splits one beam and shows the spectrum that was already there. Same with a brief: SEO that ranks, copy that sells, language that holds, a system that keeps producing. Nothing bolted on. Revealed and organised.
Most stalls are not a talent problem. They are a map problem, then a cadence problem. We fix both: which URLs must exist, what each one claims, and how the next batch gets written without another kickoff.
Split
One brief, three jobs
01
Map the search
Keywords, clusters, and the pages that actually need to exist. Suburb vs service vs proof. Each URL gets a job, a parent, and a reason Search Console should care.
We do not write twenty near-duplicates and hope Google sorts it. If two queries share intent, they share a page.
02
Write the claim
Copy with proof, not filler. On-page that Search Console can use, and a human can finish: headline, offer, objection, ask.
Homepages, service landings, product, thought leadership. Same standard: a sentence a buyer can repeat.
03
Automate the cadence
Pipelines so publishing does not stall after the first batch. Python audits, Groq publishing, Anthropic scripts when the process is the bottleneck.
The machine drafts to a template you already approved. You still own the claim. We do not ship a demo that nobody runs.
Run
How an engagement actually moves
01 Brief
White in
You send the offer, the market, live URLs, and what “done” looks like. Access to Search Console or a crawl export if you have it. We do not need a 40-page brand book.
02 Inventory
What exists, what is missing
Current pages, cannibalisation, thin URLs, gaps against the query map. You get a list with jobs, not a slide deck of “opportunities.”
03 Drafts
Spectrum out
First URLs in the cluster: titles, H1s, body, FAQs, internal links. You mark what is wrong in the claim, not in the adjectives. We revise against that.
04 Live
On the CMS you already use
WordPress, Shopify, or files you can paste. Meta, schema notes, and the on-page that the template actually supports. No mystery staging site unless you ask for one.
05 Cadence
The next ten are not a scramble
If the bottleneck is production, we leave a pipeline: briefs in, drafts out, a human pass, publish. Same voice, same map, fewer kickoffs.
You send
What we need to start
Offer and who it is for
Live site or sitemap
Competitors you actually lose to
Proof: reviews, jobs, numbers
CMS and who hits publish
You get
What leaves the studio
URL map with jobs
Copy ready to paste
On-page that matches Search Console
A publishing rhythm, if you need one
The catalogue as the case study
Out
What this method is not
Not
Keyword stuffing to a quota
If the page has no job, it does not get written.
Not
A strategy PDF that never ships
The artefact is live URLs, then the next batch.
Not
Unattended AI on your domain
Pipelines draft. You (or we) still approve the claim.