04 / Communication
Client reporting is the regular update that shows what was done, what changed, and what happens next. Whether the audience is an agency client or an internal team, a good report builds trust by connecting activity to results and being honest about what is still uncertain.
This lesson covers reporting cadence, the structure of a monthly report, how to explain results and drops, attribution, automation, and communication habits that keep stakeholders confident.
1. Reporting cadence
| Report | Frequency | Contents |
|---|---|---|
| Status update | Weekly or per sprint | Work completed, blockers, next steps |
| Performance report | Monthly | KPIs, trends, wins, issues, next month's plan |
| Strategy review | Quarterly | Progress against goals, roadmap changes, new opportunities |
| Alerts | As needed | Critical issues such as sitewide noindex or outages |
Slack notifications and scheduled audits can deliver critical alerts between reports.
2. Monthly report structure
- SummaryThree to five sentences on performance, key wins, and concerns.
- KPIsA short table comparing this month, last month, and last year.
- Work completedFixes shipped, content published, and their expected effect.
- Results and insightsWhat changed, why it likely changed, and what it means.
- Issues and risksNew problems found and blockers needing decisions.
- Next stepsPlanned work with owners and dates.
3. Explaining results
Numbers need interpretation. For each notable change, give the observation, the likely cause, the evidence, and the action.
Explaining a change
Attribute changes carefully. Correlation with a fix is evidence, not proof.
4. Reporting drops and bad news
Report drops early and directly. Explain what happened, the likely cause, the scope, and the recovery plan. Check common causes first: algorithm updates, tracking changes, seasonality, site releases, and indexing changes. Stakeholders forgive drops far more easily than surprises.
Many apparent traffic drops are tracking problems, such as a missing GA4 tag after a redesign or a consent banner change. Confirm tracking with an audit before explaining a drop as an SEO issue.
5. Attribution and uncertainty
SEO results are affected by competitors, algorithm changes, seasonality, and other channels. Use annotations for releases and updates, compare against control sections that were not changed, and use language such as likely and contributed to. Formal testing methods are covered in the SEO Testing course.
6. Tailoring to the audience
| Audience | Focus | Format |
|---|---|---|
| Executives | Revenue, leads, risk, and direction | One page summary |
| Marketing managers | KPIs, campaigns, and content performance | Monthly report and dashboard |
| Developers | Technical fixes and acceptance criteria | Tickets and technical notes |
| Agency clients | Value delivered and next steps | Monthly report and call |
7. Automation and dashboards
Automate data collection, not interpretation. Dashboards built on Search Console, analytics, and crawl data save time, but every report still needs a human summary explaining what matters. SiteAuditLint reports and exports and crawl comparisons provide the technical section automatically.
8. Practical exercise: Write a monthly report
Client report checklist
0 of 9 tasks completed
Key takeaways
- Match cadence to purpose: status updates, monthly reports, quarterly reviews, and alerts.
- A monthly report covers summary, KPIs, work completed, insights, risks, and next steps.
- Explain changes with observation, cause, evidence, and action.
- Report drops early and verify tracking first.
- Be honest about attribution and uncertainty.
- Automate data collection, but write the interpretation yourself.
Knowledge check
You have completed SEO Reporting. Next, learn how to validate changes in SEO Testing.