The cycle
Slow enough to be measurable. Fast enough to compound.
The hard part of improving a website automatically is not making changes. It is knowing which change caused which result — and that means deliberately going slower than the technology could.
-
Phase 01 · every day
Measure
Look at everything. Change nothing.
What people search
The words people typed, how often you appeared, how often they clicked, and roughly where you sat in the results — straight from Google's own figures for your site.
What visitors do
How many people arrive, whether they stay, and whether they get in touch — matched up to the page they landed on, so you can see where interest turns into enquiries.
What is broken
Every page checked: links that lead nowhere, error pages, pages nothing links to, duplicated headlines, and labels that have stopped working.
Speed, for real people
Not a score from a testing tool, but what your actual visitors experience on their own phones — measured against the speeds Google says a page has to hit.
Whether AI is reading you
Which AI assistants came to your site, which pages they read, and whether anyone arrived from one. Nobody can measure this properly yet, but this is the closest anyone can get.
What rivals answer
Questions you get shown for but do not actually answer, where a competitor does. Gaps found this way are real demand, not somebody's opinion about your website.
-
Phase 02 · weekly
Decide
Sort by what it is worth, not by how easy it is.
Each possible change is scored on how many people it could reach, how much room there is to improve, and what happens if we have got it wrong. That produces a list in order, and only the top few are allowed anywhere near your site in a given week.
Every one of them has to come with a written prediction first. If we cannot say "we expect this to improve, because of that", the change does not happen. Not out of fussiness — a change nobody predicted can never be judged fairly afterwards.
-
Phase 03 · weekly
Ship
One change at a time, each one undoable on its own.
The safe mechanical changes we simply make. Everything else we send to you first, showing exactly what would change, why, and what we expect to happen — and then we wait until you say yes.
Your website is built so that the text lives in clearly defined slots with rules attached. If a change breaks a rule — a headline too long for Google to display, a missing summary, a date that makes no sense — the change is rejected automatically and never reaches your live site.
-
Phase 04 · 28 days
Prove
Compare against the pages we left alone.
Once a page is changed, we leave it completely alone for 28 days. Then we compare how it moved with the pages we deliberately never touched — which went through the same Google updates and the same quiet weeks as everything else.
Anything that beat the untouched pages stays, and we do more of it. Anything that lost gets put back, and we publish that just as prominently as the wins.
Guard rails
What stops it running away
A limit on how much can change
Only a small, fixed number of pages can change at once. Going beyond that needs a person to agree, no matter how confident the system is.
An automatic emergency stop
If visits or enquiries drop sharply, everything stops on its own and the last change is put back — without waiting for anybody to notice.
One change per page at a time
A page that has just been changed cannot be changed again until we have finished measuring it. Otherwise we could never tell which change did what.
An off switch
One instruction stops everything, immediately. It does not depend on any particular person being available to do it.
Questions
How it works in practice
Why change things weekly if you check every day?
Because a page has to sit still long enough to be measured. Google takes weeks to settle after a change, and the figures arrive a few days late anyway. Something editing pages every day would be chasing random wobbles and could never tell you which change caused what. So we watch daily, change weekly, and then leave that page completely alone while we measure it.
What information do you look at?
The free search figures Google already gives you as the site owner: what people searched for, how often you appeared, and how often they clicked. Your visitor statistics. Every page on your site, checked for anything broken. How fast pages really load for real people on real phones. And which AI assistants have been reading you. We look at far more than we ever change.
Do you need the passwords to my hosting?
No. We work the same way a web developer on your team would: through whatever system already publishes your website. Your existing approvals and permissions still apply, and everything we do is recorded under our own name, so you can always see exactly what came from us.
What if I want it stopped?
Tell us, and everything stops immediately — it does not depend on one particular person being at their desk. Everything built stays yours: the site, the improvements and the full record of what was done. And if you would rather go back to how your site was before we started, we kept a copy of that too.
Put your site on Autopilot
Start with a free review. We go through your whole site once and send you a plain list of what we would fix and why — whether or not you ever buy anything.