Client Reporting: What to Include, What to Leave Out

The monthly report is the most-read piece of content your agency produces — treat it that way

Enric Ramos · · 7 min read
person using macbook pro on black table

The monthly SEO report is the most-read deliverable your agency produces. Audits get read once at delivery. Strategy decks get read once, then filed. The monthly report gets read 11 times a year by the main contact, forwarded to their boss, sometimes circulated to execs. It's the single most influential piece of client-facing content you make.

Most agency reports are vendor-facing data dumps — tool screenshots, dashboards, metrics tables, no narrative. Clients skim them and file them. The reports that retain clients are narrative, outcome-focused, and ruthlessly edited. This article covers what to include, what to cut, and how to frame the narrative.

What a client report is for

Three audiences, three purposes:

  1. Main contact (marketing manager / SEO lead): wants to know what's been done, what's next, whether to expect issues. Report is their source of truth for the month.
  2. Their boss (VP Marketing / CMO): skims for outcome. Cares about: is this investment working? Should we continue? Any bad news to surface?
  3. Executive readers (CEO / CFO, occasional): glance at first page only. Want: headline number, risk flags, budget alignment.

A report that serves all three reads:

  • Page 1: executive summary. Outcome-focused, numbers-first.
  • Pages 2-5: narrative. What was done, what we learned, what's next.
  • Pages 6+ (optional): supporting data, detailed analytics, raw tool exports.

Most reports invert this — data-dump first, narrative buried. Fix by inverting.

The executive summary page

One page. What belongs:

1. Headline metric movement.

One sentence: "Organic traffic up 23% month-over-month, driven primarily by rankings improvements on the new pillar content."

Specific, attributable, short.

2. Three outcome-framed highlights.

  • "Completed canonical migration; 17% of pages now consolidating signals to proper canonical URLs."
  • "Published 3 pillar articles in the cluster launched last month; together already driving 400 new organic sessions."
  • "Fixed CWV regression on the mobile product pages, restoring LCP to 'Good' threshold."

Not "we did X tasks." "We achieved X outcomes."

3. One risk / flag.

Transparency builds trust. "We're seeing a decline in impressions on Category X — investigating a Google Merchant feed issue. Will have diagnosis by mid-month."

Not hiding problems — surfacing them with context.

4. Next month's focus.

Two to four priorities with expected outcomes. Not tasks; outcomes.

  • "Ship the schema markup for the product catalog — expected CTR lift on top 50 PDPs."
  • "Begin internal linking audit for the Technical SEO cluster — expected crawl efficiency improvement."

The narrative section

After the executive summary, expand into narrative. Structure:

1. What we did this month

Not a checklist of tasks. A story of work:

"This month we focused on the canonical migration project that began in April. The work involved auditing 4,300 URL parameters across the catalog, mapping each to its canonical, and shipping the canonical tags in coordination with the engineering team. Alongside, we tackled three high-priority content gaps identified in the audit: articles on faceted navigation, product schema, and out-of-stock handling. Each has been delivered and is indexed."

Reads as a coherent account. The client learns what you did and why it matters.

2. What we learned

This is the most undervalued section. It builds trust because it shows you're paying attention:

"While setting up the canonical migration, we noticed that ~15% of your product URLs have dynamic session IDs appended by the CMS — this adds unnecessary variations to Google's crawl. It's not an emergency but it's inefficient. We've added it to the backlog for Q3."

Clients love this. It signals the agency is engaged, not just executing pre-defined tasks.

3. Results and data

Now the data. Metrics you're tracking:

  • Organic traffic (sessions): MoM, YoY
  • Organic conversions / revenue: MoM, YoY
  • Keyword position tracking: top 10 positions, movements
  • Impressions, clicks, CTR from GSC
  • Specific metrics tied to the strategy (e.g., article engagement if content is the focus)

Each metric in context:

"Organic traffic rose 23% from 45,000 to 55,000 sessions. The primary driver was the category pages that gained rankings after the canonical migration (+8,000 sessions), followed by the new pillar content (+1,500 sessions)."

Not "traffic = 55,000." Attribute the movement.

4. Next month's plan

Specific priorities, with expected outcomes and what's needed from the client.

5. Open questions / asks

Items where you need the client's input or action.

What to leave out

Most agency reports bloat because they include everything. The editing discipline:

Leave out: raw tool screenshots. Ahrefs dashboards, Screaming Frog outputs, raw GSC exports. Clients don't parse these. Summarize the insight; don't dump the tool.

Leave out: tasks without outcomes. "We did 40 hours of keyword research this month." Clients hear this as "you're billing us for work we can't see results from." Reframe: "Keyword research this month identified 23 new query targets, which shape Q3 content planning."

Leave out: minor tactical wins without strategic framing. "We updated 3 meta descriptions." If this is the highlight of the month, something's wrong. If it's one task of many, skip it.

Leave out: industry news. "Google announced X algorithm update." Not news — the client has seen it. Include only if it's directly relevant to their account with a specific recommendation.

Leave out: vanity metrics. Impressions without conversions. Rankings on queries that don't drive traffic. Flattering numbers that don't tie to business outcomes.

Structure: slides vs docs vs live dashboards

Slides (Google Slides, PowerPoint, Keynote):

  • Best for: executive audiences, quarterly reviews, presentations.
  • Typically 15-25 slides monthly.
  • Reads well on mobile.
  • Risk: slides encourage bullet-point fragmentation; narrative suffers.

Docs (Google Docs, Notion, PDF):

  • Best for: detailed monthly reporting with narrative.
  • 8-15 pages typical.
  • Forces prose structure — often results in better reports.
  • Risk: can become too long.

Live dashboards (Looker Studio, Databox, custom):

  • Best for: always-on metrics access.
  • Complements, doesn't replace, monthly reports.
  • Risk: replaces narrative with "look at the dashboard" — avoid.

Recommended default: monthly report as a doc, supplemented by a live dashboard for day-to-day metric access.

Reporting cadence

  • Weekly: quick Slack update or mini-report. 2-3 sentences on progress + one question or ask.
  • Monthly: full report (what this article covers).
  • Quarterly: strategic review. Reassess priorities; align on next quarter's plan.
  • Annually: year-end retrospective. Compare actual results vs expectations. Reset expectations for the next year.

Consistency matters. Clients notice when weekly updates drift to every other week, when monthly reports slip.

Tools and templates

Templates help, but they shouldn't dominate the content. A template ensures:

  • Consistent structure across months (client recognizes the shape).
  • Standard sections (executive summary, narrative, data, next month).
  • Agency branding and professionalism.

It shouldn't ensure:

  • Same content recycled month-over-month.
  • Generic observations padding actual insights.
  • Identical reports across different clients.

Each month's report needs fresh narrative. Template is the container; content is the work.

Common mistakes

Traffic-up-is-the-headline regardless of context. Traffic can be up for reasons unrelated to your work (seasonality, PR event, competitor's algorithm hit). Frame honestly.

Missing the negative story. Only good news in reports. Clients trust agencies that flag issues. Hiding bad news loses trust when the client finds out independently.

Pricing sheet at the end. Some agencies include hours billed / fees. Usually awkward; better handled as separate invoicing document.

Word-for-word repetition month after month. If last month's report reads identically to this month's (different numbers but same narrative), you're not communicating anything new.

Over-attribution to agency work. "Organic traffic up 40% because of our work!" When much is organic-algorithm, competitive dynamics, or client-driven. Be honest.

Frequently asked questions

How long should a monthly report be?

8-15 pages or 15-25 slides. Longer if the month had significant strategic content; shorter if it was maintenance month. Don't pad to hit a length.

Should I include rankings data every month?

Yes, but contextualized. "Top 10 rankings: 47 → 53 (+6)" is useful. Tables of 200 keywords with positions is noise. Report on ranking movement strategically.

What if I have nothing substantive to report?

Still send a report, even a short one: "This month was implementation-heavy. No big wins yet; foundational work continues. Next month we expect X to show initial results." Honesty builds trust more than padded reports.

How do I handle months where results declined?

Surface it with context: what happened, whether it was expected, whether it signals a problem. Clients appreciate transparency about declines when paired with analysis.

Should I include competitors' data?

Some reports do ("Competitor X's rankings"). Useful if your strategy is competitor-response; otherwise, focus on the client's own metrics. Competitor obsession often distracts from your actual progress.

Related articles

a person writing on a piece of paper

Migrating from Manual to Automated SEO Monitoring

Weekly manual SEO checks catch problems 3-7 days after they happen. Automated monitoring catches them in minutes. The migration from manual to automated isn't about replacing judgment — it's about catching regressions before they compound.

· 7 min read