SEO & PageSpeed
Search Console Annotations: The Website Change Log That Explains Your Next Traffic Drop

Everyone says the same thing about website traffic: if it drops, you will know why. After all, you made the changes, so surely they will stick in your mind. They will not. Neither will they stick in mine, and keeping records is a large part of my job.
Google released its November 2026 core update on 10 November, and the Google Search Status Dashboard says the rollout may take up to two weeks [1]. Over that fortnight, a lot of small business websites will see their Search Console charts move. Some will rise and some will fall. Most owners will open the Performance report, look at the line, and try to reconstruct from memory everything that happened to their site in the same period. That reconstruction is almost always incomplete.
Search Console has a feature built for exactly this problem, and very few owners use it. Since November 2025 you can pin your own notes, called custom annotations, directly onto the Performance chart [2]. Each one is a short line attached to a date. Together they form a change log that sits on top of your traffic data, which is the only place a change log is genuinely useful. Five beliefs stop most owners from keeping one, and each of them falls apart under a little scrutiny.
Myth 1: You Will Remember What You Changed
Memory is the weakest record in any operation. Ours included.
I learned that the slow way. Early in my career I spent most of a morning chasing a performance fault on a server, only to trace it back to a configuration change I had made myself two days earlier and never written down. Every change on our platform gets a timestamped entry now, and the habit costs seconds.
Your website has the same problem, with more people involved than you might think. Consider who can change it in a typical month:
- You, editing a page in the evening when the shop is quiet.
- WordPress itself. Since version 5.5, administrators can switch on automatic updates plugin by plugin and theme by theme, and WordPress runs those auto-updates twice a day by default [3]. A plugin can change at 4am without anyone touching a keyboard.
- Staff or family, updating opening hours, prices or a menu.
- Anyone you pay, such as a marketing freelancer adding a pop-up or a tracking script.
- Google, which ships core and spam updates on its own schedule.
Then there is the time lag. Google's guide to debugging traffic drops suggests reviewing the last 16 months of Performance data to rule out a yearly pattern [4]. So ask yourself what you changed on your website in July of last year. Which week, precisely?
Nobody can answer that from memory. A log can.
Myth 2: Search Console Already Shows What Happened
It shows what happened to your clicks and impressions. It does not show why.
Search Console does add some notes of its own. Google's help page describes system annotations, generated automatically to flag data processing and reporting issues on Google's side [2]. They help when Google's own data had a glitch. Your homepage rewrite, the plugin that updated overnight and the week you closed for a family wedding are not on there. Those appear only if you put them there.
How custom annotations work
The mechanics are simple, and Google's help page sets out the rules clearly [2]:
| What | The rule |
|---|---|
| Adding one | Right-click the Performance chart, choose Add annotation, pick the date, write the note |
| Length | Up to 120 characters per note |
| How many | Up to 200 annotations per property |
| How long they last | Annotations older than 500 days are deleted automatically |
| Who sees them | Everyone with access to the property; owners and full users can add or delete, restricted users can only view |
A few practical points follow from those rules:
- Write for a stranger. Because the whole property shares your annotations, your accountant, your web person or a new member of staff may read them too. Google advises keeping personal information such as names, phone numbers and addresses out of them [2]. A note saying the delivery page was rewritten is fine. A customer's name is not.
- Spend the 120 characters well. One change per note, past tense, with enough detail to find it again later: "Homepage headline and main photo replaced. Old text saved in shared drive."
- Do not ration them. Two hundred notes works out at roughly two a week for two years, more than most small sites will ever need. The 500-day expiry is also a little longer than the 16 months of history the Performance report holds, so your notes outlast the data they describe.
The limits worth knowing before you rely on it
Annotations cannot be edited at present. If you get a date wrong, the only fix is to delete the note and add it again [2]. They also do not appear in comparison mode or the 24-hour view, which are precisely the views many owners reach for when something looks off. Switch back to the standard chart to see your notes.
More importantly, an annotation records coincidence, not cause. A note sitting the day before a drop is a lead to follow up. It is not a verdict.
If you also use Google Analytics, it has its own separate annotations, with a 60-character title, a 150-character description and up to 1,000 per property [5]. The two tools do not share notes. Pick one as the master record, or copy the important entries into both.

Myth 3: When Traffic Drops, It Is Google
This is the belief the November core update will reinforce, because it gives everyone something convenient to blame.
Google's documentation on debugging traffic drops lists six broad causes: algorithmic updates, technical issues, security issues, spam issues, seasonality and changing interests, and site moves and migrations [4]. Only one of those six is Google changing its ranking systems. Several of the others begin with something someone did to the website.
Four changes in one November week
Consider a composite scenario, built from a pattern that turns up every winter rather than from one business's history. A Christmas tree farm in Kildare that delivers across the county switches its homepage over to tree ordering in the second week of November. The same week, a delivery postcode plugin auto-updates overnight, and a family member rewrites the delivery page to mention the new cut-off date. Then Google's core update starts rolling out.
Two weeks later, ordering enquiries are down on last year. Which of the four events caused it?
Without a log, the owner guesses. The likeliest guess is Google, because the update is in the news, so the farm waits for it to settle. Meanwhile the postcode checker has been rejecting valid Eircodes since the night it updated, and the most important weeks of the selling season go by while the real fault sits in production.
What four dated notes would have changed
With four annotations on the chart, the questions get sharper. Did the drop start on the night of the plugin update, or a few days later when the core update began? Is it across every page, or concentrated on the delivery page? Search Console can filter by page and by date range, so a dated note turns a guessing exercise into a comparison you can verify.
Seasonality hides problems as well as causing them
Google's debugging guide uses the example of food-related searches that peak every November, and suggests checking your main queries against Google Trends over several years [4]. A tree farm's traffic should climb sharply from mid-November whatever it does. A rise that is smaller than last year's can hide a real fault behind a healthy-looking chart, which is exactly when a dated note earns its keep.
When this update finishes, Google's guidance is to wait at least a full week after it completes before analysing, then compare a week after the update with the week before the rollout began [6]. Add two annotations for it: one on 10 November, and one on the day the dashboard marks it complete. You will then know exactly which weeks to compare.
For the wider diagnosis, from stray noindex tags to manual actions, our walkthrough on working out why your Google traffic dropped takes the checks in order.
Myth 4: Only Big Changes Are Worth Writing Down
Big changes are the ones you remember anyway. The small ones cause the conflicts nobody can trace.
A useful rule from operations work: log anything that changes what a visitor or Google sees, or how the site behaves. For a small business website, that list looks like this:
- Plugin, theme and WordPress updates, including automatic ones. WordPress emails the site's admin address after auto-updates by default [3], so treat each of those emails as a prompt to add a note.
- Page changes: renamed pages, deleted pages, new pages, rewritten headlines, new menu items.
- Commercial changes: prices, delivery charges, opening hours, offers starting and ending.
- Anything layered on top: pop-ups, chat widgets, cookie banners, tracking scripts, booking widgets. Each adds weight to the page, and our complete guide to WordPress performance explains why that weight shows up in how visitors behave.
- Hosting and domain events: a move to new hosting, a domain renewal problem, an outage.
- Outside events: a radio mention, a newspaper piece, a closure for refurbishment, a storm day, the first and last day of an advertising campaign.
- Google's own updates, dated from the Search Status Dashboard [1].
The outside events matter more than people expect. A spike after a local radio interview looks like an SEO win if nobody wrote down the broadcast date. The owner then spends money chasing a ranking improvement that never happened.
Two minutes, once or twice a week. That is the whole cost.

Myth 5: A Change Log Is Just Paperwork
A log on its own fixes nothing. Its value appears the moment you need to reverse a change, because a rollback needs a date.
Go back to the composite tree farm. Once the owner can see that the drop began the night the postcode plugin updated, the fix is to restore the site to its state just before that update. Without a dated record, the likely outcome is a rollback of the wrong thing: the homepage rewrite that was actually working gets undone, while the plugin conflict stays in production. That is another week of peak-season orders lost on top of the week already gone.
So what should the hosting side give you, so that the log has something to act on? A sound setup has four things:
- A restore point taken automatically before every update, so an overnight plugin change can be rolled back to the minutes before it ran.
- Dated nightly backups you can line up against your annotations.
- A staging environment, a separate copy of the site where you verify a change before you deploy it to production, which means fewer surprises in the log at all.
- Restore without a ticket queue, so the rollback happens when you decide, not when someone gets to it.
Web60 meets all four as standard. Every site gets automatic nightly backups with one-click restore, safety snapshots taken automatically before updates and before restores, and one-click staging environments, all included in Web60's €60-a-year managed WordPress platform. When your annotation reads "postcode plugin updated overnight" and the chart dips the following morning, you roll back to the pre-update snapshot rather than guessing which nightly backup is clean.
What a rollback cannot give back
A restore returns the whole site to a moment in time. Orders, enquiries and account sign-ups made after that moment are not in the restored copy. The pre-restore snapshot keeps the state you rolled back from, so nothing is destroyed, but bringing recent orders back across is manual work. This is one more reason to log precisely: the closer your rollback point sits to the actual change, the less real business you have to reconcile afterwards.
When a heavier process makes more sense
Search Console annotations are a lightweight tool. If you run a large online shop with a development team shipping changes every week, a proper release process, with version control and deployment logs of the kind premium managed WordPress providers build around developer workflows, is the better record. A 120-character note on a chart is no substitute for that. Very few owner-operated businesses work that way, though. For a site that one or two people look after, the annotation is the right size of tool.
Start the Log This Week
The core update is rolling out as this goes up, which makes the next fortnight a sensible moment to begin. Open Search Console, go to the Performance report, and add three notes: 10 November for the core update, the date of your last significant website change, and anything you already have planned for the Christmas period. Add the update's completion date once the dashboard shows it.
From then on, one note per change. If you are still building your site, or moving it, Web60 handles the snapshots and backups while you keep the notes. Either way, when the chart next moves you will be comparing dates rather than memories, and the decision about what to keep, what to fix and what to roll back will rest on evidence you wrote down yourself.
Frequently Asked Questions
What are Search Console annotations?
They are short notes you attach to a date on the Search Console Performance chart. Each one holds up to 120 characters and appears as a marker on the chart, so you can see website changes, Google updates and outside events alongside your clicks and impressions. Google launched custom annotations in November 2025.
Can I edit an annotation in Search Console?
Not at present. Google's help page says editing is not currently available. To correct a mistake, click the annotation marker, delete it, and add a new one with the right date or wording.
Who can see my Search Console annotations?
Everyone with access to the property. Owners and full users can add and delete annotations, while restricted users can view them but not change them. Keep personal information such as customer names, phone numbers or addresses out of them.
Why can I not see my annotations on the chart?
Annotations do not appear in comparison mode or in the 24-hour view, so switch back to the standard Performance chart with a normal date range. Notes older than 500 days are also deleted automatically, so very old entries will no longer be there.
Do Search Console annotations show up in Google Analytics?
No. Google Analytics has its own annotation feature with separate limits, and the two do not sync. Choose one as your main record, or copy the important entries into both.
How long should I wait after a Google core update before judging my traffic?
Google recommends waiting at least a full week after the rollout completes, which you can confirm on the Google Search Status Dashboard, and then comparing that week with the week before the update began. The November 2026 core update started on 10 November and may take up to two weeks to finish.
Sources
Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.
More by Ian O'Reilly →Ready to get your business online?
Describe your business. AI builds your website in 60 seconds.
Build My Website Free →More from the blog
Changing Your Business Phone Number: Every Place the Old One Still Hides
Changing your business phone number? Find every copy of the old one on your website and Google listing, from call buttons to schema, before calls go missing.
Deleting Old Pages for SEO: The Clear-Out That Cost a Business Its Best Page
Deleting old pages for SEO feels like progress during a Google core update. Google calls it a last resort. How to decide which pages to keep, fix or redirect.
