The audit as a sales tool

A prospect asks for an SEO audit before they sign. You run one, export the report, and send a PDF long enough to need a contents page. A week later they've gone quiet, and when you follow up they say they haven't had a chance to get through it. The audit that sells shows a founder what's broken, what it's costing them and what you'd fix first, on a page they can read between meetings. Thoroughness belongs in the report you keep in reserve.

Why the long audit loses the deal

A founder reading an audit wants to know whether this agency understands their site well enough to be trusted with it. A long PDF answers a different question, which is how many checks your tool can run. It hands the prospect the job of working out which findings matter, and most people faced with that job put the document down.

The long audit has a second cost. Everything you found is now a work list their current developer, or the next agency they talk to, can act on for free. Show enough of the diagnosis to prove you can see the problem, and sell the judgement about what to do with it.

Keep the full report. You'll need it in the meeting and again in the first month. The prospect just shouldn't be the one reading it cold.

The three things a prospect needs to see

What's broken. One or two findings, each with a real URL they can open, stated in terms of the effect. "Your service pages all share one title, so Google can't tell them apart" lands. "Duplicate title tags detected" doesn't.

What it's costing them. You don't have their analytics yet, so say what the affected pages are for and why a search engine struggling with them matters to the business. A broken canonical on a blog post nobody visits is a footnote. The same fault on the page that takes bookings is the headline. If you quote a traffic figure from a third-party estimate, call it an estimate in the same sentence; a founder who later opens Search Console and sees a different number will remember.

What you'd fix first, and what you'd leave. Naming the first fix shows judgement. Naming what you'd deliberately not touch yet shows more, because it proves you can tell big from small. The next lesson covers how to rank findings; for the sales version you only need the top item and the reason it's top.

Build the one-page version from the full report

1. Run the audit and skip the overall grade. A single number tracks change between audits; it doesn't tell anyone what to do. Read the discipline scores instead and take the lowest one that was actually measured.
2. Open that discipline's recommendations. A well-built report orders them worst first and names the affected URL, so the first few items are usually your candidates.
3. Verify each candidate yourself. Open the URL, view the source, and confirm the finding is real on the live page today. Never put a finding in front of a prospect that you haven't seen with your own eyes; one wrong item costs you the credibility of all the others.
4. Write the page. Three short sections: what's broken (a couple of findings, each with its URL), what it's costing (which pages and what they do for the business), and what you'd fix first. End with what you'd leave alone.
5. State the scope honestly. An audit checks the pages it crawled, which is a sample on any site of size, and it doesn't measure backlinks unless a backlink data source is connected. Say "on the pages we crawled" and say off-page wasn't assessed. Prospects trust the person who tells them what the audit didn't cover.

What to say in the meeting

Lead with the one finding, and show it live. Open the page in a browser, show the title or the canonical, and let them see the problem on their own site. A screenshot in a PDF is an assertion; a live page is evidence.

Then say what you'd do first, and why it's first: it touches the pages that earn them money, or it blocks everything else. Say roughly what it would take, in your effort and theirs. Then say what you wouldn't do yet. That sentence is often the one that closes, because every other agency they spoke to promised to do everything.

Don't promise positions or dates. Google doesn't publish a schedule for re-crawling a fixed page, and a founder who hears "page one next month" will hold you to it. Promise the fix, the re-audit that proves the fix landed, and the next thing after that.

What to take away

• A prospect is buying judgement, so the audit sells when it shows what's broken, what it costs and what you'd fix first, rather than everything the tool found.
• Verify every finding on the live URL before it goes in front of anyone, because one wrong item undermines the rest.
• Be explicit about scope: findings cover the pages crawled, and an audit that doesn't measure backlinks should say so.
• Keep the full report for the meeting and the first month; the prospect reads one page and sees the evidence through a link you control.

Next

Once the prospect says yes, every finding needs an order. Prioritising fixes by impact shows how to rank them so the client's developer starts with the right thing.