SEO change log: the document that answers "what happened in March?"

When a client's traffic moves, the first question is always "what changed?". Without an SEO change log, the answer is a week of digging through emails, deploy notes and memory. With one, it takes five minutes.

Key takeaways

  • An SEO change log records every change that could affect search: deploys, content, redirects, CMS updates, Google updates.
  • Keep one shared log per client with date, change, owner, pages affected and expected effect.
  • Mirror key entries as annotations in Search Console and GA4, so charts carry their own context.
  • Check Google's Search Status Dashboard and add confirmed updates to the log.

An SEO change log is the cheapest insurance an agency can buy. On the dealership fleets and large stores we have supported, most traffic questions were answered by one line in a log: a template change, a plugin update, a redirect rule or a Google update that started the same week. This guide explains what to record, where to record it and how to use it with clients, as part of the delivery process behind white label SEO. When something does drop, the log feeds straight into our guide on how to diagnose a client's traffic drop.

Why should agencies keep an SEO change log?

Because traffic changes rarely have one obvious cause, and memory fails after a few weeks. A log ties each movement in the charts to dated events: releases, content work, migrations, outages and Google updates. It shortens diagnosis, protects the agency when someone else changed the site and shows the client the work done.

The second benefit is accountability. Clients' developers, other vendors and the client's own team change sites too. A shared log that everyone writes in makes it clear who changed what, without blame.

What changes should go in an SEO change log?

Anything that can change crawling, indexing, rankings or conversions: code deploys, theme and plugin updates, CMS migrations, redirects, robots.txt and sitemap changes, title and template edits, new or removed pages, internal linking changes, link building milestones, tracking changes, server outages and confirmed Google updates. Small copy edits on single pages can be grouped weekly.

FieldExample (hypothetical)Why it matters
Date (and time for deploys)2026-03-04 14:00Lines up with daily charts
TypeDeploy, content, redirect, Google updateFilter by cause
ChangeNew product title template on all categoriesWhat actually happened
Pages affected/category/* (about 1,200 URLs)Scope for comparisons
OwnerClient developer / agency / white label partnerWho to ask
Expected effectHigher CTR on category pagesWhat to check later
Result and check dateReviewed 2026-04-01Closes the loop

Can you add annotations in Google Search Console?

Yes. Search Console added custom annotations to the Performance report in late 2025. You right-click the chart on a date and add a note of up to 120 characters. Each property allows up to 200 annotations, they are deleted after 500 days, they cannot be edited and every user of the property can see them.

The rules are in Search Console Help's page on Search Console annotations. Owners and full users can add or delete them; restricted users can only view. Because annotations are shared, Google asks you to avoid personal information such as names or phone numbers. With a 200 limit, keep annotations for major events and leave the detail in the log. Use the same wording so the log and the Performance report match.

How do annotations work in GA4?

GA4 lets users with Analyst access or higher add annotations to reports with line charts. You right-click a point on the chart, add a title of up to 60 characters, a description of up to 150, a date or a date range and a color. Each property can hold 1,000 annotations, and Google may add its own system annotations.

These details come from Analytics Help, About annotations. Annotations appear on every line chart report, which makes them useful for conversion questions that Search Console cannot answer. A practical rule: every log entry marked "major" becomes an annotation in both tools on the same day.

How do you track Google algorithm updates in the log?

Use Google's own sources. The Google Search Status Dashboard lists ranking updates relevant to site owners and incidents affecting crawling, indexing or serving, with a history kept for five years and an RSS feed. Add confirmed updates with start and end dates to every client log, so nobody blames a site change for a Google update.

The dashboard is described in Using the Google Search Status Dashboard. For documentation changes, such as a rich result being retired, check Google's latest documentation updates. How to respond to updates with clients is covered in Google algorithm updates for agencies.

  • Subscribe to the Search Status Dashboard RSS feed in the team channel.
  • Add each confirmed update once to a shared "Google events" tab, then link it from client logs.
  • Record outages and incidents too; they explain odd data days.
  • Do not log rumors as updates; note them as unconfirmed if at all.

Where should the change log live?

Somewhere every party can reach and nobody can lose: a shared spreadsheet, a project management board or a tab in the client folder. Pick one per client and link it from the monthly report. The format matters less than the habit: log changes on the day they happen, with a named owner, and review the log in every monthly call.

Ask the client's developers to add deploys, or give them a short form. Before launches and redesigns, log the planned changes in advance, as in our website redesign SEO checklist. Our approach to SEO project management shows where the log sits in the weekly workflow, and the white label SEO reporting guide shows how to summarize it for clients. Or book a 30-minute call.

Frequently asked questions

Should the change log be shared with the client?

Yes. A shared log builds trust and gets the client's own changes recorded too. Include changes made by developers, designers or other agencies, so every update is in one place. This makes it easier to explain changes in traffic and avoid blame when something goes wrong.

How detailed should each entry be?

One clear sentence, the pages affected, the owner and what to check later is enough. Add links to the pages or tickets when helpful, and note the date so results can be compared before and after. Short, consistent entries make the log easy to search and use.

Do Search Console annotations replace a change log?

No. They are short, limited in number and expire after 500 days; use them as pointers to the log. Keep the full details in the log, including what changed, who made the change and why. Add an annotation in Search Console that points to the matching log entry.

What if we inherit a client with no log?

Rebuild the last year from release notes, emails and the Search Status Dashboard, then log going forward. Ask the client and their developers about major changes, such as redesigns, migrations or platform updates. Even a partial history helps explain past traffic changes and plan future work.

Who should own the log in a white label setup?

The agency owns it; the white label partner and developers add their own entries. Use one shared document or tool where everyone records changes in the same format. This keeps the history complete and makes it easy for the agency to explain results to the client.

Juan José Giraldo, senior white label SEO specialist

About the author

Juan José Giraldo is a senior SEO specialist with 5+ years of experience. He works on technical and local SEO for 600+ US car dealerships and supervises the SEO of 18 US e-commerce stores. He runs White Label SEO LATAM from Medellín, Colombia, and delivers white label SEO for agencies in the US, UK, Canada and Australia. Read more · LinkedIn.

Want these agency guides first? Choose White Label SEO LATAM as a preferred source on Google, and my articles are more likely to show up for you in Top Stories.

Follow on GoogleAdd as a preferred source

Sources

  1. Search Console Help, Search Console annotations
  2. Analytics Help, About annotations
  3. Google Search Central, Using the Google Search Status Dashboard
  4. Google Search Central, Latest documentation updates
  5. Search Console Help, Performance report (Search results)

Ready to test a pilot client?

Book a 30-minute call. You get an honest read on fit, scope and price, with no obligation.