They share one memory, so nothing is said twice
Three layers: directive, orchestration, execution
A crawl, an issue taxonomy and a priority model, wired end to end — agentic SEO that produces the same artifacts every run, which is the only reason the numbers are comparable month to month.
The SOP, written down. Goals, inputs, the tools to use, the outputs and the edge cases — in plain language, versioned like code. When we learn an API limit the hard way it gets written here, so it is never learned twice.
The only probabilistic layer. It reads the directive, calls the tools in order, handles the errors and asks when something is genuinely ambiguous. It does not do the work itself.
Deterministic scripts. Same input, same output, every run. Ninety per cent accuracy per step is fifty-nine per cent over five, so anything that must be right lives down here instead.
Most audits describe the version of your site a browser eventually assembles. Yours is judged as search engines and AI crawlers actually receive it — which is where the expensive, invisible problems tend to live.
Also connects to
Read-only wherever read-only is enough. Nothing gets write access it doesn't need, and every write is logged.
The crawl reaches your whole site — URL coverage is verified against your sitemap before a single issue is scored.
Every issue is classified against the full taxonomy, so the report you read is the complete picture, not a convenient one.
The deck, the issue list and the prioritised backlog all arrive together, every time.
That consistency is the whole point. The same checks and the same artifacts on every run, so when a number moves you know it moved because your site moved — not because the method did.
| Spec | Standard | Deployable |
|---|---|---|
| Where it runs | Our infrastructure | Yours |
| Who holds the API keys | Us, scoped per client | You |
| Cadence | Monthly, or weekly | Any schedule |
| Raw data retention | Rebuilt each run | Your policy |
| Artifact delivery | Your Drive and tracker | Your choice |
| Source code access | — | Full |
| Runs unattended | Yes | Yes |
| Failure alerting | Slack and email | Your channels |
Deployable hands over the software, the hosting and the keys. You run it; we stay on for support.
Monthly by default, and weekly on Accelerate. Every run produces the same artifacts — the crawl, the classified issue list and the prioritised fix list — which is what makes one month comparable to the next instead of re-derived each time.
Severity crossed with traffic impact. A critical issue is P1 at any traffic level, and a high-severity issue on a page with real sessions or conversions is P2. Issues affecting a large share of the site escalate, so a hygiene problem across most pages does not sit quietly at the bottom of the backlog.
Yes, on every plan. The crawl exports, the classified issues and the prioritised backlog belong to you, and the audit is delivered as a deck plus a task list rather than a dashboard you lose access to when you leave.