Most audits are a crawler export with severity labels attached. Useful data, no diagnosis. We work the other way round: find the cause, prove it, then write the fixes in the order worth doing them.
Start a projectWhat you get
A three hundred page report tells you everything and prioritises nothing. Teams either freeze, or spend a quarter fixing low-impact warnings while the real cause, often rendering, cannibalisation or internal linking, stays untouched.
We diagnose first, then rank fixes by impact against effort and write each one so a developer can act without translation. You keep the document whether or not you work with us again.
What crawlers receive versus what users see, including client-rendered content, blocked resources and redirect chains.
Core Web Vitals measured across templates rather than the homepage alone, with the specific assets causing the damage named.
Pages competing for the same query, and which one should own it. One of the most common causes of stalled visibility.
Where authority is trapped, which commercial pages are under-linked, and what to change in navigation and body links.
Canonicals, noindex, parameter handling, sitemap accuracy and status codes, checked against Search Console reality.
Whether your pages are structured to be retrieved and quoted, plus a baseline of how assistants currently describe you.
Full crawl, rendered HTML samples, Search Console and analytics access, plus a short call on what changed and when.
We look for the cause behind the symptoms rather than listing every warning a tool produced.
Every fix is scored by likely impact against implementation effort, so the first week of work is the most valuable week.
A walkthrough call, the written document, and a follow-up window for questions while your team implements.
| Area | Typical approach | Our approach |
|---|---|---|
| Format | 300-page tool export | Ranked fix list with reasoning |
| Rendering | Raw HTML only | Rendered and raw compared |
| Ownership | Requires their retainer | Actionable by your own team |
| Follow-up | None | Walkthrough and question window |
Usually one to two weeks depending on site size and how quickly access is granted. Larger sites with complex templates take longer.
A ranked fix list with reasoning and evidence, developer-ready notes for each item, and a walkthrough call. No tool export dumped into a PDF.
No. The document is written so your own team or another agency can act on it. We can implement if you want us to, but it is not a condition.
In most cases yes, or it will narrow the cause to a short list with evidence. Where the likely cause is an algorithm update rather than a site issue, we say that plainly.
Search Console, analytics and ideally a staging or CMS view. We can audit without them, but the diagnosis is weaker.
Yes. We include an entity and answer-structure review plus a recorded baseline of how the major assistants currently describe your brand.
How long does an audit take?
Usually one to two weeks depending on site size and how quickly access is granted. Larger sites with complex templates take longer.
Usually one to two weeks depending on site size and how quickly access is granted. Larger sites with complex templates take longer.
A ranked fix list with reasoning and evidence, developer-ready notes for each item, and a walkthrough call. No tool export dumped into a PDF.
No. The document is written so your own team or another agency can act on it. We can implement if you want us to, but it is not a condition.
In most cases yes, or it will narrow the cause to a short list with evidence. Where the likely cause is an algorithm update rather than a site issue, we say that plainly.
Search Console, analytics and ideally a staging or CMS view. We can audit without them, but the diagnosis is weaker.
Yes. We include an entity and answer-structure review plus a recorded baseline of how the major assistants currently describe your brand.
Tell us what changed and when, and we will tell you what an audit would need to look at first.