How Do You Report SEO Progress Before the Rankings Move?

Four months into a programme, somebody senior asks the only question they care about: is this working? The rank tracker shows three terms up, two down and the rest unchanged. The traffic line is flat. Nothing on the screen looks like progress, and yet the site is in demonstrably better condition than it was in January. That gap between the work and the evidence is where most engagements quietly lose their funding.

Rankings are a lagging indicator, and a report built only on them says nothing for the first two quarters. That is not a reason to hide the numbers. It is a reason to report the measurements that move first, in a structure that shows the mechanism connecting them to the outcome you were hired for.

There are five worth reporting: indexation coverage of the URLs you care about, crawl efficiency, internal link depth to the pages that earn money, page experience for real users, and published coverage of the questions your buyers actually ask. Each one can be measured this month, each one can go down as well as up, and each one has a route to the outcome you can describe out loud.

What follows is how to tell an indicator that genuinely leads from one that is merely early, the five we report, the monthly structure we use, and what to take out of the report entirely.

Why rankings are the last thing to move

A change you ship today has to survive a chain of events before it can affect a position. The page must be discovered, fetched, rendered, evaluated and stored. Then it has to be selected for a query, ranked against everything else that could answer it, and hold that place long enough for anyone to notice. Every link in that chain carries its own latency, and the early ones are the only ones you control. This is the practical reason the crawl, render and index order matters more to a monthly report than any position table.

Two further things make position data a poor progress signal. It is relative, so you can improve substantially and still slip because somebody else improved faster. And it is heavily averaged across devices, locations and personalisation, which means the number in your tracker summarises many different results, none of which any particular person saw.

None of this makes rankings useless. It makes them the scoreboard rather than the play. Report the scoreboard honestly, and explain the game with something else.

What makes an indicator leading rather than just early

Plenty of numbers move quickly and mean nothing. An indicator earns a place in the progress section only if it passes three tests.

First, can we change it this month by doing the work? If it moves only when a third party decides something, it belongs in context rather than in progress. Second, can you state the mechanism in one sentence without hedging? “Pages that are not indexed cannot receive traffic” survives that test. “Higher authority scores correlate with better rankings” does not, because it names a correlation instead of a mechanism. Third, and this is the one everybody skips: can the number go down while you are the one reporting it? An indicator that only ever rises is a decoration.

The five leading indicators worth reporting

Indexation coverage

Not “how many pages are indexed”, which rewards publishing rubbish, but what share of a named priority list is indexed and serving. Write that list first: the pages that make money, the pages that answer buying questions, the pages that support them. A sitemap is your declaration of which URLs you consider canonical and worth indexing, so it should agree with that list exactly, and a submitted sitemap full of redirects and dead ends is itself a finding. Reconciling the two is ordinary technical SEO work, and it produces the fastest visible movement of anything in this list.

Crawl efficiency

Two measurements, both from server logs rather than from a tool that guesses. How long between publishing or changing a page and the first fetch of it. And what proportion of crawl activity lands on things you never wanted crawled: parameter permutations, redirect chains, missing pages, printer variants, faceted filter combinations that multiply forever. Improving the second improves the first, which shortens the delay on every future change you make. It is the compounding item in the report.

Internal link depth

Take the priority list and measure how many clicks separate each page from the home page, and how many internal links point at it from genuinely relevant places. Orphan pages, pages reachable only through a paginated archive on page nine, and money pages sitting four levels down all show up immediately. This is entirely within your control, needs no external cooperation, and can be improved in a fortnight. It is also the indicator clients grasp fastest, because a diagram of it explains itself.

Page experience for real users

Report field data from actual visitors, not a lab score from one run on a fast laptop on a fast connection. Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, segmented by template and by device class, because an average across a whole site hides the one template that is failing. The connection to the outcome is not mystical. Slow, unstable pages lose people before they convert, and heavy pages cost more to crawl.

Published coverage of buyer questions

Keep a list of the questions your buyers actually ask, gathered from sales calls, support tickets and the site search box rather than from a keyword tool alone. Then report, month by month, how many of them have a published page that answers them properly. You cannot rank for, or be quoted in, an answer you never wrote, which is the same underlying point as getting your pages quoted in AI answers. Coverage is the input. Being cited is the output.

When coverage stalls, the cause is almost never the writing. It is the distance between an approved draft and a live URL. If publishing needs an engineer with a spare afternoon, the queue becomes the strategy, which is what our parent company describes in where drafts live and what stops them. A structured workspace such as Acrosite removes that step by generating the files, committing them and triggering the deployment, so the publishing rate stops depending on somebody else’s sprint.

One more measurement earns a place if you inherited an audit: the rate at which real defects get closed, counted by impact rather than by ticket. Ten trivial items closed while three structural ones sit open is a worse month than the reverse, which is the whole argument behind treating severity and priority as different questions.

The monthly report, in this order

Order matters more than content here, because the order tells the reader what you think the report is for. Ours runs like this.

1. What shipped, with dates. A plain list of changes made to the site this month, each with the date it went live. This is the only section that proves work happened, and it is the section most often left out.
2. Leading indicators, with direction. Each one against last month and against the baseline. Direction and size, not a traffic-light colour somebody chose.
3. Lagging numbers, unspun. Clicks, impressions and positions for the priority set. If they are flat, say flat. If they fell, say fell, and put the explanation underneath the number rather than in place of it.
4. What we learned that changed the plan. A month with no learning is a month spent executing last quarter’s assumptions. Name the assumption that turned out to be wrong.
5. Next month, and the condition that would stop it. State what would make you abandon the current approach. A plan with no exit condition is a belief.
6. Blockers, ours and yours. Approvals waiting, access not granted, deployments not scheduled. Written down every month, these stop being awkward and start being a shared queue.

That structure is deliberately hard to fake, because sections one and six can be verified by anybody with access to the site. It also gives the analytics and strategy side of the work somewhere to live: measurement definitions, segment choices, and the annotations that explain why a line moved on a particular Tuesday.

What to take out of the report

Removing things is most of the improvement. Each of these looks like evidence and functions as noise.

• Rank screenshots for terms nobody buys from. Position one for a phrase with no commercial intent is a fact, not a result.
• Average position across every query. It moves when you gain impressions on weak queries, so improvement can look like decline and confuse everyone in the room.
• Impressions without the query set behind them. A number nobody can decompose is a number nobody should act on.
• Volume of output. “We published eight articles” describes effort. Coverage of eight named questions describes progress.
• Third-party authority scores. They are somebody else’s model of the web rather than a measurement of your site, and no mechanism connects them to your revenue.

Surviving a sceptical reader

Assume the person reading has been sold something before and did not enjoy it. Two habits do more than any amount of design polish.

Report the misses first

Open with what did not work, what slipped and what you got wrong. It costs nothing, because the reader will find those things anyway, and it buys the rest of the document credibility it cannot otherwise earn. Everything after an honest first section is read more generously, and everything after a flattering one is read with suspicion.

Name the counterfactual

Whenever a number moves, say what else could have moved it: seasonality, a competitor’s change, an update to how results are selected, a campaign running elsewhere in the business. Then say which of those you can separate and which you cannot. Being explicit about the limits of attribution is the most persuasive thing in the whole document, and it sits close to what ninety days can honestly show, which is less than most proposals imply.

A report that only contains good news is not a report. It is marketing, addressed to the person paying for marketing.

The concession this piece owes you: every leading indicator can improve while traffic stays flat. Sometimes the demand is simply not there and the keyword research flattered it. Sometimes the pages are technically correct and unremarkable, which no amount of crawl efficiency repairs. Leading indicators tell you the machine is working. They cannot tell you the offer is interesting. When every input has been healthy for two quarters and the output has not moved, the honest conclusion is that the problem was never technical, and the report should say so in those words.

When the lagging number finally moves

Movement usually arrives unevenly: a handful of pages at once, often the ones fixed earliest, and often on queries nobody was tracking. That is why the report keeps the full query set rather than a chosen list. When it happens, the useful work is diagnostic rather than celebratory. Which pages moved, what was done to them, and how long ago? That interval is the closest thing to a measured feedback loop you will get, and it turns next quarter’s forecast into something better than a guess.

The same discipline applies when the movement is downward, and downward movement has the small advantage of a usually identifiable cause. A migration, a template change, a redirect map applied carelessly. Falls of that kind are recoverable when the reporting is good enough to date the change precisely, which is the mechanism behind recovering organic traffic after a redesign. Without dated change logs you are reduced to theorising in public.

Where the first report starts

Do this before writing anything. Name the priority URLs, in a list, with the person who agrees they are the priority. Take the baseline for all five indicators and store the raw exports. Write down the questions your buyers ask, gathered from people who talk to them rather than from a tool. Then agree, in advance, what would count as evidence that the approach is failing.

That last agreement is what separates a report from a performance. If nobody has stated what failure looks like, every month can be presented as progress, and eventually somebody stops believing all of it at once. The same principle governs how an audit should be read: a finding is only useful when it carries a decision, an owner and a date.

And when the rankings do move, resist making them the headline. They are the lagging confirmation of work that was already visible three months earlier to anyone reading the right numbers. A report that swaps back to positions the moment positions look good has taught its reader that everything before was filler.

If you have a monthly report you suspect nobody reads, send it to somebody who will argue with it. We will read yours and tell you which sections are carrying weight and which are decoration.