When a Google update moves a client's traffic, the SEO work is only half the job. The other half is explaining it: to a marketing manager who has to brief the board, to a founder watching revenue, or to a finance team asking whether to keep paying for SEO. A vague message ("Google changed something, we're monitoring") erodes trust. So does a 40-slide deck full of jargon.
A good update report answers five questions in plain language: what happened, how big the impact is, what the evidence shows, what we are doing, and what to expect. It separates what Google confirmed from what the agency believes, and it never promises a recovery date Google itself does not give.
This guide gives you a reusable template for agency and in-house teams, with example wording, a table structure and the evidence to include. It works for core updates, spam updates and unconfirmed volatility alike.
Key Takeaways
- Structure every update report around five sections: what happened, scope, evidence, actions and expectations.
- Quote confirmed facts (update name and dates) from Google's Search Status Dashboard, and label everything else as analysis or observation.
- Google recommends waiting at least a full week after a core update completes before analysing your site in Search Console; send a short holding note first.
- Translate rankings into business metrics such as leads, sales or revenue, and show what share of the business is affected.
- Set expectations honestly: Google says improvements can take several months to be recognised, and there is no guarantee of recovery.
When to report, and how often
Timing matters as much as content. Report too early and you will be explaining mid-rollout noise; report too late and the client hears about it from someone else. A simple cadence works for most accounts:
- Day 0 to 2: holding note. When a confirmed update starts, send a short message: which update, when it started, how long Google said it may take, and that you are monitoring. No conclusions yet.
- During rollout: exception alerts only. Only contact the client if something serious appears, such as a large drop in leads or a manual action.
- One week after completion: full impact report. Google's documentation recommends waiting at least a full week after a core update completes before analysing. This is the main report.
- Monthly: progress updates. Track the actions you agreed and the metrics for affected page groups.
- Next core update: review. Compare against the original impact report and decide the next phase.
“We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console.”
— Google Search Central, Google Search's core updates and your website
The five-part report template
Use the same headings every time so stakeholders learn where to look. Keep the main report to a page or two, with detail in an appendix.
| Section | What to include | Example wording |
|---|---|---|
| 1. What happened | Update name, type and dates from the Search Status Dashboard; whether it is confirmed | "Google released the May 2026 core update on 21 May; it completed on 2 June." |
| 2. Scope | Change in clicks, leads or revenue; which sections, pages, countries or devices | "Organic clicks fell 18% week on week, almost entirely on the blog; product pages were stable." |
| 3. Evidence | Before/after comparison, query and page breakdowns, competitor changes, ruled-out causes | "No technical errors, manual actions or tracking issues found." |
| 4. Actions | What you will do, in priority order, with owners and dates | "Review the 40 most affected articles for depth and accuracy by end of month." |
| 5. Expectations | What you expect, what you do not know, when you will report next | "Google does not give recovery timelines; we will review progress monthly." |
The percentages in that table are illustrative wording, not benchmarks. Always use your client's real numbers.
Section by section
1. What happened
Take names and dates from the Search Status Dashboard, not from social media. If several updates overlapped, list them all. If nothing was confirmed, say so clearly and use the language from our guide on handling unconfirmed updates.
2. Scope
Stakeholders care about business impact, not average position. Lead with leads, sales or revenue from organic search, then show traffic. State whether the impact is site-wide or limited to sections; our post on page-level versus site-wide ranking drops explains how to tell. Separate branded from non-branded traffic where you can, because a stable brand line can hide a large non-brand drop.
3. Evidence
Show a before-and-after comparison using equal periods, as in our before and after core update comparison guide. Include the causes you ruled out (technical issues, seasonality, tracking, manual actions); Google's traffic-drop documentation lists these categories and is a good checklist. Add a simple chart with the update window shaded.
4. Actions
List a small number of prioritised actions with owners. Be explicit about what you are not doing and why. For core updates, Google advises against quick fixes and drastic changes to pages that are performing well, which is a useful line to quote when a client wants to rewrite everything.
5. Expectations
This is where trust is won or lost. Google's documentation says it could take several months for its systems to recognise improvements and that changes do not guarantee a noticeable impact. Say that plainly. Our posts on core update recovery timelines and Google's "no fix" guidance give you supporting language.
Metrics that belong in the report
| Metric | Why it matters | Source |
|---|---|---|
| Organic leads, sales or revenue | What the business actually feels | Analytics or CRM |
| Clicks and impressions (non-branded) | Shows search visibility without brand demand | Search Console |
| Affected page groups | Shows whether the issue is concentrated | Search Console page export |
| Top lost and gained queries | Makes the change concrete | Search Console query export |
| Competitors gaining | Shows who replaced you and why | Rank tracker and manual SERP checks |
| Recovery tracking | Progress after actions | Same metrics, monthly |
If you need a reporting framework beyond updates, our guides to SEO reporting and client marketing reports cover monthly formats, and building an SEO dashboard in Looker Studio shows how to automate the charts. Search Console's custom annotations, which Search Engine Land reported in November 2025, are also a handy way to mark update dates directly on the charts you screenshot.
Common mistakes
- Blaming Google for everything. If you did not rule out technical or tracking issues, say the analysis is incomplete.
- Presenting speculation as fact. Label observations from forums and trackers as unconfirmed.
- Leading with rankings. Executives want business impact first.
- Reporting mid-rollout as final. Numbers often shift before the update completes.
- Promising a recovery date. Google does not give one, and neither should you.
- Hiding good news. Gains in some sections matter too; they show what is working.
Related Guides
- Tracking Algorithm Updates With Search Console Custom Annotations
- Using Search Console's Branded Queries Filter to Isolate Update Impact
- Checking Crawl Stats and Indexing After an Algorithm Update
Frequently Asked Questions
How soon should I tell a client about a Google update?
Send a short holding note when a confirmed update starts, then a full impact report about a week after it completes, in line with Google's advice to wait before analysing.
What should an algorithm update report include?
Five parts: what happened (confirmed facts), scope (business impact), evidence (comparisons and ruled-out causes), actions (prioritised, with owners) and expectations (honest timing).
Should I promise the client their rankings will come back?
No. Google says improvements can take several months to be recognised and that changes are not guaranteed to have a noticeable effect. Commit to actions and review dates instead.
How do I explain an unconfirmed update?
State clearly that Google has not confirmed anything, show what your own data and trackers show, and explain any precautionary actions.
Which metrics matter most to stakeholders?
Organic leads, sales or revenue first, then non-branded clicks and impressions, affected page groups and top lost queries.
Conclusion
A clear update report protects the client relationship as much as the rankings. Stick to the five-part template, separate confirmed facts from analysis, lead with business impact and set honest expectations. If you would like help analysing an update or preparing a stakeholder report, our SEO services team can do the analysis with you, or you can request a quote.
