How it works.
One cycle, run continuously for your site: audit, propose, check, approve, apply, verify, measure, and start again. You decide how much of it waits for you.
The cycle, step by step.
Eleven steps, from the audit to the next round. Most run without anyone lifting a finger; the decision in step five is yours.
- [01]
Audit
On a schedule, or when you ask: every page read the way Google and AI assistants read it, and scored on 26 variables. - [02]
Record the cycle
Each audit opens a dated cycle that records the pages, rules and models used, so any result can be traced back. - [03]
Propose
Findings become specific fixes for specific pages. The same issue found twice never becomes two fixes. - [04]
Check first
Fixes that would break a rule, make an unbacked claim or need something your platform cannot do are dropped before you see them. - [05]
Approve
Each fix waits for you, or goes ahead under a rule you set. - [06]
Apply
Made through a route proven for your platform, with the original saved first. - [07]
Verify
Read back from your platform, then checked on the live page and in a real browser. - [08]
Hold or undo
If a check fails, the change is held or reversed automatically, and you see why. - [09]
Audit again
The pages that changed are audited again, so the score that should move is measured. - [10]
Measure
We record what moved: the variable's score, clicks from Google, mentions in AI answers, and the cost of the work. - [11]
Plan the next round
What worked on your site decides what we propose next.
Getting started takes one connection.
You connect your site once: our app on Wix or Shopify, our plugin on WordPress, or access to your code repository. Then we scan what we can and cannot do there.
The scan checks that
- Your connection works and has the access it needs
- The site we are connected to is the one you named
- We can read your pages and their current settings
- Your platform, app or plugin version is one we support
- Your site is reachable and safe for us to fetch
- Your rules allow each kind of fix
Then one page goes first
The first fix of each kind runs on a single page, chosen by the system. If it passes every check, that kind of fix is switched on for your site. If it fails, it stays off for your site and you see the evidence.
Nobody needs to test your site by hand, and we never propose a fix your platform cannot make.
You choose what waits for you.
Three settings, changeable at any time. Trust is earned per kind of fix: a clean record on titles never approves a change to robots.txt.
Review all
Every change waits for you
You see each fix before and after, and approve or reject it, one at a time. Nothing goes live without your yes.Safe auto
Small, reversible fixes go ahead
Fixes to one field on one page, such as titles and descriptions, go ahead on their own once that kind of fix has a clean record on your site. Everything else waits for you.Managed auto
We run it within your limits
Kinds of fix you have approved run within the limits you set. Site-wide and hard-to-reverse changes still ask first, and still run on one page before the rest.
Seven levels of checks.
A change is not done when it is sent. It is done when the checks its kind requires have passed. Titles and descriptions must pass the first six.
- V0Your platform accepted itThe platform, plugin or repository confirmed the change.
- V1Read back from your platformWe read the setting back from the source, not from our own records.
- V2Served on the live pageWe fetch the page as visitors and crawlers get it, allowing for caches.
- V3Rendered in a real browserFor anything JavaScript draws, we load the page in a browser.
- V4The problem is goneThe exact condition the audit found is now healthy.
- V5Nothing else brokeNeighbouring tags, the page's layout, its structured data and its links are as they were.
- V6What happened nextLater audits, clicks from Google and mentions in AI answers.
When something goes wrong.
Every way a change can fail has a planned answer, and none of them is to report success anyway.
The page changed after we wrote the fix
We write it again once from the new page. If it changes again, the fix is held for you.
Your platform cannot make it
It is never queued. We find another route, or tell you what would make it possible.
The change did not go through
We check what your platform actually holds before deciding, and never mark a fix done on a guess.
We cannot confirm it on the live page
It is held, not marked done, until the live page shows it.
Something else on the page broke
The change, and any batch it was part of, is reversed automatically.
An undo does not go through
Every change to your site stops, and we are alerted at once.
What you see in your portal.
Every fix has its own page: the before and after, the wordings, who decided and when, and the trail it has followed.
Proposed
(done)We show the change as before → after, on the exact page, with wordings to choose from.
Approved
(done)You approve or reject it, or a rule you set does. Every decision is logged and sealed.
Applied
(done)We make it through your platform's own tools, and save the original first.
Checked live
(current step)We read it back from your platform and check it on the live page, then watch what it does.
Measured, not promised
Clicks come from your Google Search Console; AI mentions from questions we track in each assistant.Each assistant on its own
ChatGPT, Claude, Gemini and Perplexity are tracked separately, never added into one number.No guarantees
We never promise rankings, traffic or citations. We show you what changed and what happened next.