B2B SEO KPIs that survive a conversation with your CFO

A CFO asked one of our clients a question in a QBR that ended a two-year SEO program at a competitor and nearly ended ours: “You have shown me a traffic number. What did it cost per opportunity and how does that compare to paid?”

The traffic number was excellent. Nobody could answer the question. If you cannot answer it either, that is a reporting problem rather than a performance problem, and it is fixable in about three weeks.

Why the standard dashboard fails

Organic sessions, keyword rankings, and domain rating are inputs. They are useful to the people doing the work and close to meaningless to anyone allocating budget, because none of them convert into a currency the business uses.

Worse, they can all move in the wrong direction while the program succeeds. We regularly cut traffic deliberately by removing content. Rankings for terms we stopped caring about decline. A CFO looking at that dashboard sees a program getting worse.

The metrics that hold up are the ones expressed in pipeline and cost.

The four numbers worth reporting

Organic-influenced pipeline. Total value of open opportunities where at least one organic session appears anywhere in the contact’s history, not just as first or last touch. This is the headline number. In a five-month cycle with seven touchpoints, any single-touch model understates organic badly, because organic tends to sit at the beginning and the middle rather than the end.

Cost per opportunity, compared to your other channels. Total spend on the program divided by opportunities influenced. Then put it next to the same figure for paid search and outbound. This is the number that wins budget arguments, and organic usually wins it decisively after month eight while losing it badly before month five. Show both.

Commercial keyword coverage. How many of the keywords on your priority map sit in the top three, top ten, and nowhere. Not total keywords ranked, which goes up automatically as you publish and means nothing. Coverage against a fixed, agreed list of terms you decided were worth money.

Content-assisted win rate. Of deals closed this quarter, what share had an organic touch, and did those deals close faster or at higher value than deals without one. This is the number that changes how the sales team treats your content, and it is usually the most flattering thing in the deck.

Instrumenting it without a six-month data project

The plumbing is less work than people expect.

Capture the first landing page, the source, and the campaign into hidden form fields on every conversion form, and push them into the CRM as fields on the contact record. Most CRMs support this natively and most marketing sites already have the JavaScript half implemented and unused.

Add a free-text “how did you hear about us” field to the demo request form. It is self-reported and therefore unreliable, and it catches a meaningful share of what the tracking misses — dark social, a colleague’s recommendation, an article read on a phone six weeks ago in a different browser. On several clients this field surfaces organic attribution at roughly double the tracked rate.

Then, quarterly, take your closed-won deals and manually look at the page-level history for each. Twenty deals takes about two hours and produces the single most persuasive artifact in the whole reporting stack: a list of specific URLs that appear in deals worth specific amounts.

Things to stop reporting

Domain rating. It is a third-party estimate of a third-party model, it moves for reasons unrelated to your work, and reporting it invites a conversation about a number nobody can act on. Track referring domain count and quality instead, internally.

Total keywords ranked. Goes up with every page published regardless of value.

Average position. An average across a set that changes composition every month is not a comparable figure. Report coverage of a fixed list instead.

Bounce rate, on informational pages. A visitor who read your answer and left satisfied is a success, and the metric records it as a failure.

Impressions, as a headline. Useful as a leading indicator inside the team, misleading as a business metric because impressions in AI Overviews and other features inflate it without corresponding intent.

Forecasting, and being honest about the error bars

Every proposal we write includes a twelve-month forecast, and every forecast is wrong. The question is whether it is honestly wrong.

We build it bottom-up: for each keyword cluster, an estimated realistic position by month twelve, a CTR curve for that position, the cluster’s search volume with a haircut for tool inaccuracy, an assumed conversion rate from a comparable page we have already built, and the client’s own close rate and ACV.

Then we present three scenarios and say plainly that the middle one is a guess with maybe 40% error on it in the first six months. Clients respond much better to that than to a single confident line, and it means the month-seven conversation is about which assumption was wrong rather than whether we lied.

The assumptions that break most often, in order: search volume was overstated by the tools, the SERP had more competition than the difficulty score suggested, and the client’s publishing capacity was lower than planned. The third one is by far the most common and it is nearly always a review-cycle bottleneck rather than a writing one.

The report itself

One page. Four numbers with their trend. A short section on what we did. A shorter section on what did not work and what we are changing.

That last section is the one I would keep if I could only keep one. Clients who see an agency admit a mistake before being asked stop auditing every other number in the deck. It has done more for retention than any result we have produced.