You send the monthly report on the first, fourteen pages of charts and tables. The reply arrives ten days later and says thanks, looks good. Then at renewal the client isn't sure what they got for the money, and every answer they needed was sitting in reports nobody read. A report earns its keep only if it gets read, and the ones that get read put the whole month on one page, in the client's language, with the detail behind it rather than in front of it.
The report is written for the person it gets forwarded to
A monthly report has two readers. The first is your contact, the marketing manager or owner who hired you; they skim it, and their real use for it is internal, forwarding it or lifting a line to justify the spend to whoever approves budgets. The second reader is that person, and they read page one and nothing else.
So write the report for the forward. The test: hand page one to someone who has never spoken to you and see whether they can tell you what happened, whether that's good, and what you're doing next. If page one only works with you in the room, it fails at the exact moment it matters, the budget conversation you're not invited to.
That decides what goes first: the month's story, then the numbers that back it.
Write the sentence that explains the month
Page one leads with one plain sentence in three parts: what moved, your best explanation for why, and what happens next. For a fictional plumbing client: "Enquiries from search rose this month, most of them through the two boiler-repair pages that went live in June, and next month we're building the same structure for the drainage services." Nothing in it needs translating, and it survives being read aloud in a meeting.
The explanation is where your honesty lives. If you're confident the work caused the movement, say so and say why; if you're not, name what else changed that month. A flat month gets the sentence too, often "rankings are climbing but haven't yet reached the positions that earn clicks, which is normal at this stage". A client told the truth in a flat month believes you in a good one.
Under the sentence go the numbers, and which numbers is a decision made with the client at kickoff, not an export run at month end. Pick a handful as close to money as their tracking allows, enquiries, calls, orders, with organic traffic as the supporting act. Show each against the same month last year as well as last month, because month-on-month flatters or panics a seasonal business for no reason. Every number carries its definition in the same line, so "enquiries" says which forms and phone numbers it counts.
Cut what you can't explain in one sentence
Most reports are long because length feels like evidence of work. It reads as the opposite. The usual padding is the full keyword table, screenshots of dashboards, impressions presented as an achievement when clicks didn't follow, and blended figures like an average position across the whole keyword set, which moves when the tracked set changes even if no ranking did.
The test for every element is whether you could explain it in one sentence if the client pointed and asked what it means. If your answer would start with a definition, put the definition on the page or cut the element.
Cutting is not hiding: the detail moves to an appendix or stays in the live report for anyone who wants it. The list of work you did belongs after the results, one line per item, so it reads as how the numbers happened rather than as the product itself.
Explain the movement, especially the drops
Every chart carries one written sentence: what this shows and what changed. A chart without a sentence is a question you've left the client to answer alone, and they answer it with the most anxious reading available.
Drops get the sentence first. A report that shows a decline without comment teaches the client to stop trusting it, because it went quiet exactly when they needed it. The drop sentence names the fall, the most likely cause with your confidence stated, and the action already underway, before the client asks. Handling ranking drops covers the diagnosis, and reading rank movements honestly covers separating real movement from noise.
Jargon gets the same treatment. A canonical problem, a crawl block, an intent mismatch: each becomes one sentence about pages, customers or money, and presenting findings without jargon is the skill this rests on.
Send the snapshot and the living version
A PDF is true the day you export it: right for the monthly meeting and the client's records, wrong for everything in between. A read-only live link shows the current report whenever the client opens it, answering the mid-month "how are things going" moment without an email thread. Send both and say which is which: the PDF is the month's record, the link is the current state. Treat the link like a credential, since anyone holding it can read the report, and revoke it when the engagement ends.
What to take away
- The report is written for the person it gets forwarded to, and page one must work without you in the room.
- The month is explained in one sentence: what moved, your best explanation, and what happens next, with your confidence stated honestly.
- Page one carries a handful of numbers agreed at kickoff, each defined in its own line and compared against the same month last year.
- A drop explained before the client asks builds more trust than a good month displayed without comment.
Next
Sooner or later a client asks you to defend the money numbers on page one, and Proving ROI honestly shows how to connect rankings to revenue and survive the question in the room.