How to Prove Your SEO Work Is Worth Paying For

Published 2026-10-22 · 8 min read · by the isaeo team

The lag problem

You fix things in month one. Engines re-crawl over weeks. Rankings settle over more weeks. Traffic follows. Revenue follows that. Realistically you're three to six months from a number a finance person recognises.

The client's patience is shorter, and their question arrives in week six: "what are we getting for this?" Answering "SEO takes time" is true, unfalsifiable, and indistinguishable from what someone says when nothing is happening. It's the sentence that precedes churn.

The way out isn't better excuses or faster results. It's reporting things that are true now, verifiable now, and honestly connected to the outcome later.

Four leading indicators

1. Pages recovered into the index. The strongest one available, because it's binary and consequential. "Eleven of your product categories were excluded from search in March. They're indexable now." A page that engines wouldn't index earned nothing; one that they will can. No ranking claim needed.

2. Score movement, with the method stated. A health score going 64 → 79 is a summary a non-technical reader can hold. Two conditions: state what moves it so it isn't a black box, and never quietly change the method — a score that jumps because you switched tools destroys the trust the number was for. See what moves a health score.

3. Issues closed, verified by re-crawl. Not your checklist — the crawl's verdict. "Fixed on staging" and "live in production" are different states, and verifying against a re-crawl is what makes the claim auditable rather than self-reported.

4. AEO readiness. Increasingly the one clients ask about unprompted, because they've noticed AI answers. "Thirty-one of your pages now carry structured data and a quotable answer" is progress on a channel they're worried about, reported before anyone has a citation dashboard. Which AEO metrics to track.

What these share: each is measured, each is checkable by the client, and none requires you to claim a ranking you can't attribute.

Report the catches

The most under-used item in agency reporting, and the one that most changes how your retainer is perceived.

When monitoring catches a regression, say so explicitly and in detail: "Your 19 March release added a noindex tag to the blog template. We caught it on the 20th and it was reverted the same day. Left alone, those 340 pages would have dropped out of search over the following weeks."

That paragraph does something no fix list does. It converts your retainer from a project — which finishes — into insurance, which doesn't. Clients cancel projects that seem complete; they don't cancel the thing that caught the incident last quarter.

Two rules. Report the catch even when it was the client's own developers, but neutrally — you're documenting a process working, not assigning blame. And don't inflate it: if the effect would have been small, say so. One overstated catch costs you more credibility than ten honest ones earn.

This only works if you have detection, and detection means a stored previous crawl. Without one, catches don't happen and you have nothing to report.

What not to report

• Activity. "Audited 340 pages, reviewed 12 templates." Your effort, their invoice. Nobody approves budget for volume of work.
• Raw issue counts as progress. "1,400 issues down to 900" sounds like progress and usually isn't — 400 missing alt attributes are worth less than one noindex. It also invites the obvious question of why 900 remain.
• Rankings you can't attribute. Claiming a position change caused by an algorithm update is a debt. It'll be called in when the next update reverses it.
• Vanity crawl stats. Crawl budget, average response time, pages per second. Real diagnostics, meaningless to a client, and they make the report feel padded.
• A 40-page PDF. Length reads as effort to you and as unread homework to them. One page, five numbers. See reports clients understand.

The month-three conversation

It will happen. Handle it with a page, not a defence.

The third row is the one that matters — it translates a score into a business statement without claiming revenue you can't yet prove. And the fifth row is doing quiet work: it makes the client's own delivery visible in the report, which is both fair and effective at unblocking things.

Then when traffic does move in month five, you have a documented causal chain rather than a coincidence. That's the difference between a renewal conversation and a justification.