How to report SEO to a board without talking about rankings
Reporting · 5 min read · Updated
Report SEO to a board the way you would report any other investment: what it cost, what it returned, what you expect next quarter, and how accurate your last forecast turned out to be. Rankings and sessions belong in the appendix as supporting evidence, not on the first slide. A board is not equipped to judge whether position four for a given phrase is good, and it should not have to be — it is equipped to judge whether £4,000 of work produced more than £4,000 of margin.
Why ranking reports fail in a board room
A ranking report asks the reader to do a translation the reporter has refused to do. It says a phrase moved from nine to four, and leaves the board to work out what that is worth, whether the phrase matters, and whether the movement was caused by the work or by a competitor's misfortune.
Boards handle this the way any sensible group handles an untranslatable report. They either nod it through without scrutiny, which is how unprofitable SEO budgets survive for years, or they discount it entirely, which is how profitable ones get cut. Neither outcome depends on whether the work was any good.
The test for any SEO slide: could a director who has never heard of a SERP make a budget decision from it? If not, it is a working document, not a board slide.
The four numbers on the first slide
| Number | What it answers | Where it comes from |
|---|---|---|
| Invested | What did this cost, all in? | Agency or salary cost, tooling, content, and the internal hours spent approving and implementing. |
| Returned | What revenue is attributable to organic, this period? | Analytics revenue on organic sessions, or lead volume × your own lead value where the sale happens offline. |
| Expected next period | What are we buying if we keep going? | The sum of the forecasts on work already approved, labelled a projection. |
| Forecast accuracy to date | Should you believe the third number? | Last period's forecast against last period's actual, as a percentage, including the misses. |
The fourth number is the one people leave out, and it is the one that earns the other three their credibility. A team that reports being 78% accurate is trusted with the next forecast. A team that reports only wins is, correctly, assumed to be selecting them.
What goes in the appendix
Everything that is evidence rather than conclusion. Rankings, impressions, click-through rates, crawl health, page speed, backlink counts, the list of changes made in the period. None of it is unimportant — it is how you would defend the first slide if challenged — but it is support, not the argument.
- The change log: what was applied, when, by whom, and what it was forecast to be worth.
- Per-page and per-cluster revenue, so a director who wants to pull a thread can.
- Rankings for the phrases that actually carry revenue, with the revenue beside them.
- Anything that moved against you, with your reading of why.
How to present a forecast you got wrong
Plainly, early, and with the reason separated from the excuse. "We forecast £1,200 a month from the category page rewrite and it has returned £340" is a sentence that costs you nothing if the next one explains what you learned and what it changes.
What does cost you is the alternative, which is a report that quietly stops mentioning the category page rewrite. Boards notice absences. The first time someone asks what happened to a forecast you have stopped reporting, every other number in the deck is re-read with suspicion.
01State the gap
Forecast, actual, difference, as one line. No preamble.
02Give the cause, if you know it
A competitor's new page, an algorithm update, a change implemented differently than specified, or an input that was wrong. If you do not know, say that instead of guessing.
03Say what it changes
Either the model's confidence for that change type, or the decision about whether to do more of it.
04Move on
One slide. A long apology reads as a bigger problem than the miss.
Making the report a by-product rather than a project
Most SEO reporting time is spent reassembling a story from tools that were not recording it. If the forecast is written down when the change is applied, the change is logged with who approved it, and the outcome is measured against the baseline captured at that moment, the board report is a query rather than a week's work.
That is a reason to keep the record even if nobody asks for a board pack. The discipline of recording a forecast before you know the answer is what makes the accuracy figure meaningful, and the accuracy figure is what makes the rest of the report worth reading.