The audit is not the work
Almost every technical SEO engagement starts with an audit. Almost none of them measurably move the dial in the next two quarters. That gap is rarely a knowledge problem — the audit usually lists the right issues. The gap is a shipping problem.
A 60-slide PDF that says "fix render-blocking JS" is not a fix. The fix is a PR merged to main that defers the third-party tag and a graph that shows LCP improving the next day.
Why audits stall in practice
Three reasons, in order of how often we see them:
- No engineering owner. The audit lands in a marketing inbox. The eng team has no quarter, no ticket, no relative-priority context.
- Findings without code-level reproduction. "Improve crawl budget" tells nobody what to do on Monday. "Add
rel=canonicalon faceted URLs matching this regex" does. - No measurement plan attached. If the audit doesn't tell you which dashboard line moves and how much, no one can prove the fix worked.
What we ship instead
We replace the audit-as-deliverable with three smaller artefacts that have to be true at the same time:
- A ranked backlog with code-level reproduction steps, opened as tickets in the client's tracker.
- A baseline snapshot of the metrics each ticket is meant to move — pulled from real tools, not the audit tool's own number.
- A shipping calendar with named engineering or content owners and dated checkpoints.
If we can't get the third artefact agreed inside the first two weeks, we tell the client the engagement will not move the dial and we re-scope or refund. That sounds dramatic. It is, in fact, just maths.
Two warning signs in an audit you receive
If you are evaluating an audit someone else delivered, check for two things:
If every finding cites a third-party tool's score with no code-level proof, treat the audit as a starting point, not a deliverable.
The second tell: an audit that is all about Core Web Vitals and says nothing about your CMS, your build pipeline, or your release cadence. That audit was generated. It was not researched.
How to score an audit before paying for one
Ask for three things before you sign anything:
- A sample PR or commit from a previous client. Real diff, not a screenshot.
- A sample ticket the audit produced — written for engineers, not marketers.
- The dashboard the team uses to track the work, including which lines moved.
If all three exist, the audit is probably a deliverable. If two of three are slide decks, it probably isn't.
A closing note
Audits aren't useless. They are the price of admission. What you pay an SEO partner for is what happens in the eight weeks after the audit lands — the PRs, the content rewrites, the redirects, the schema deployments. If your last engagement ended at the audit, you didn't buy SEO. You bought a PDF.