Search Console Annotations: 2026 Guide

Administrator in Search Engine Optimization Sep 28 / 2 weeks ago

Three months after a template change, very few people on a team can still say which day it went live. The traffic chart moves, someone asks why, and the answer sits in a chat thread nobody can find. On Monday, November 17, 2025, Daniel Waisberg and Tsahi Edri of the Search Console team announced custom annotations on the Search Central blog and called the feature "a personal notebook for your Search data." This guide explains how Search Console annotations work in 2026, from the two types to the hard limits and the quiet rules that trip teams up.

It is written for site owners, in-house teams and agencies in the United States, Europe and South Korea who share one property. You will get the official rules, a naming system and a fair way to read impact. If you are new to the tool, start with our practitioner guide to the core Search Console reports.

What are Search Console annotations?

Search Console annotations are short, dated notes on the Performance report chart. The Search Console Help page lists two types. System annotations are generated by Search Console to show issues with data processing and reporting. Custom annotations are notes you write yourself to mark events on your property, such as a feature launch or a bug fix.

The launch post explains the need well: "it can be tough to remember exactly when you made a specific change, or when something that affects your search traffic happened." A dated note keeps that memory right where the data lives.

How are system annotations different from custom annotations?

System annotations come from Search Console itself and flag issues with data processing and reporting, so they explain changes that come from the reporting rather than your site. Custom annotations are notes you write about your own changes and events. The Help page gives add and delete steps only for custom notes, and both types sit on the chart on a set date.

A related Help page, Data anomalies in Search Console, records "known issues in the last 3-16 months that might affect your data." As of May 7, 2026, for example, FAQ rich results stopped appearing in Google Search, so reported FAQ impressions dropped. A logging error also cut impressions in the Generative AI report in Search for data from August 13 to August 17, 2026, and an August 21 update says the data was restored.

Neither page says every anomaly gets a system annotation, so check both before you blame your own work. Our decision tree for finding the real cause of an organic traffic drop covers the rest of that diagnosis.

How do you add and delete a custom annotation?

Open the Performance report, right-click the chart on the date you want, pick the date in the date picker, type a note of up to 120 characters, and click Add. To delete, click the marker, choose Delete and confirm. You cannot edit a note, so fixing a typo means deleting it and adding it again.

1. Open the Performance report and right-click the chart on your date.
2. Pick the date in the date picker and type a note of up to 120 characters.
3. Click Add, then click the marker to read the note later.
4. To remove it, select Delete in the pop-up and confirm.

These steps come from the Search Console Help page on annotations, which says plainly that "Editing annotations isn’t currently available." The Help page describes no undo either, so agree who deletes notes before the first one goes in. If your team mostly reads the Search Console Insights report and its summary cards, switch to the Performance report for this work.

What are the limits of Search Console annotations?

The Search Console Help page sets four hard limits. A note holds up to 120 characters, a property holds up to 200 annotations, notes older than 500 days are deleted, and editing is not available. Annotations also do not show in comparison mode or in 24-hour views, which catches people out when they compare two date ranges.

Every row below comes from the Search Console Help page or the Analytics Help page for GA4, and "Not described" means the source is silent.

How many annotations can you add before you hit the cap?

The Search Console Help page allows 200 annotations per property and deletes notes after 500 days. Divide 500 days by 200 notes and you get 2.5 days. So if you add one note every 2.5 days on average, you sit right at the cap, and anything faster will fill it before old notes expire.

Here is the working. Each note is deleted once it is older than 500 days, so live notes settle at your daily rate times 500. Staying at or below 200 means a rate of 200 divided by 500, which is 0.4 notes a day, or one note every 2.5 days. A team that logs every small edit several times a week runs faster than that and will fill the cap before its oldest notes expire. My opinion is simple: Search Console annotations are for releases, not edits, and the fine detail belongs in your own change log.

How should you name a 120-character annotation?

Start each note with a short prefix for the type of change, then say what changed, where it changed and how many pages it touched. A fixed pattern keeps notes readable at a glance and easy to copy into a spreadsheet later. Leave out personal names, because the Help page treats annotations as business data that everyone on the property can see.

My prefix set is REL for releases, MIG for migrations, SEO for SEO work, CNT for content changes, EXT for outside events and TRK for tracking or consent changes. Here are six example notes for imaginary sites, each counted against the 120-character limit.

• A US retailer: "REL: Black Friday landing page live at /black-friday, US store, one URL, linked from home page" (94 characters).
• A UK team: "MIG: UK shop moved to new domain, every old URL 301 to its new URL, sitemaps resubmitted" (88 characters).
• A German site: "TRK: new consent banner on German site /de/, bottom bar replaced by full-screen pop-up, all pages" (97 characters).
• A Korean section: "REL: Korean section /ko/ launched, all KO pages, hreflang added to EN and KO versions" (85 characters).
• A WordPress blog: "SEO: switched WordPress SEO plugin, titles and canonicals regenerated on all posts" (82 characters).
• An agency start: "SEO: new agency starts, first month is audit only, no site changes shipped yet" (78 characters).

What changes should you annotate in Search Console?

Google's launch post names four kinds of events. They are infrastructure changes such as a template update or site migration, SEO work such as a new plugin or agency, content changes aimed at a different user intent, and external events such as a holiday. Start with those four and skip small edits that will not move a chart.

For a UK team, a new domain is the classic infrastructure note, and our playbook for redirects and site migrations covers the launch-day checks. A US store that swaps plugins should date the switch and then review the WordPress SEO plugin settings that actually matter.

For content, our guide to content refresh, pruning and decay helps you pick the pages worth a rewrite. Black Friday in the United States, Boxing Day in the United Kingdom and Chuseok in South Korea all deserve EXT notes, and our peak season calendar for the US, Europe and Korea helps you plan for them. Keep typo fixes, routine posts and anything that names a person off the chart.

How do you read a change's impact after you annotate it?

Compare two equal windows on either side of the note, built from whole weeks so both hold the same days of the week. Look at clicks, impressions and position for the pages the note names rather than the whole site, and check for system annotations or data anomalies before you credit or blame your change.

1. Click the marker and write down the date, because the marker vanishes in the next step.
2. Switch to comparison mode and set two equal windows of whole weeks that meet at that date.
3. Filter to the page, folder or country that the note names.
4. Read clicks and impressions first, with average position as support.

The first step exists because the Help page says annotations do not show up in comparison mode, so your markers vanish the moment you compare. Average position also moves when the query mix changes, which our guide on why rank trackers and Search Console positions disagree explains. When you need proof rather than a before and after reading, run a controlled test, as our guide to SEO A/B testing describes.

How long should you wait before you judge an annotated change?

My advice is to wait until the after window is as long as the before window you plan to use, and longer for big changes such as a migration. Early readings bounce around, and one strong week can fool you. The note makes waiting easier, because the date stays on the chart for 500 days.

Set the expected range before the change with our method for forecasting SEO traffic from your own Search Console data. Then present the result with our guide to SEO reporting KPIs that prove ROI.

Should you add the same note to GA4 annotations?

Yes, for any change that affects both search visibility and behavior on the site, such as a migration or a template release. Google Analytics 4 has its own annotations with different rules, and neither Help page describes a sync between the two. Put tracking and consent changes in GA4 first and search changes in Search Console first.

The table above shows the GA4 rules, which are roomier on length, count and dates, and GA4 notes can also be created through the Admin API. Search Console annotations are the tighter of the two, so write the short version there and the full one in GA4.

For the German consent banner, the GA4 note carries the weight, and our guide to measuring search performance with first-party data covers how consent shapes what you can see. If you track AI assistants as a channel, our guide to tracking AI referral traffic in GA4 shows where that traffic lands.

Why keep a change log outside Search Console?

Because the Search Console Help page says annotations older than 500 days are deleted, and it describes no export. A chart that reaches back two years will find its notes gone. An off-platform change log, even a shared spreadsheet, keeps the full history, holds detail that 120 characters cannot, and survives an accidental delete.

I think Search Console annotations and the log do different jobs. The chart is the alert that prompts the right question, and the log is the record with the full detail, URLs and market. Since 500 days is about 16 months, last year's peak notes stay on the chart, but the season before that will be gone.

How should US, European and Korean teams handle annotations?

Annotations belong to one property, and the Help page says they show regardless of filters. If your US, European and Korean sections sit in separate Search Console properties, a shared release needs a note in each one. If they share one property, write the market into every note so it reads correctly under any filter.

Some international sites verify each regional folder as its own property, a setup our guide to hreflang and international SEO discusses, and that choice decides where your notes live. Korea adds a wrinkle. Naver traffic never appears in Search Console, so record a Korean launch in your own change log too, next to your Naver Search Advisor data. Our Naver SEO guide for ranking in Korean search covers that side.

What should you do first with Search Console annotations?

Pick six prefixes, write them at the top of a shared change log, and add a note for the last big release your site shipped, dated to the day it went live. Then agree who may delete notes. It is a short job, and it turns Search Console annotations into a record your whole team can trust.

Go back to the template change nobody could date. With one note on the chart, the next person who sees the dip starts from a fact instead of a guess. Search Console annotations will not keep that fact forever, so the change log is the other half of the habit. The launch post invited feedback on LinkedIn and in the Search Central Community, so I expect the feature to grow. Which change on your site would you most like to date right now?

Frequently asked questions about annotations

Are Search Console annotations visible to everyone on the property?

Yes, within the property. The Search Console Help page says annotations are shared across the property, so any owner or full user can add, view or delete any annotation, and a restricted user can view them but cannot add or delete. The Search Central launch post makes the same point and advises against sensitive personal information. So an agency, an in-house team and a freelancer on one property all see the same notes, and each note should make sense to a stranger.

Why can't I see my annotations when I compare date ranges?

Because the Search Console Help page says annotations do not show up in comparison mode or in 24-hour views. The notes are not deleted, and they show again on a normal date range. The fix is a habit rather than a setting. Click the marker first, write down the date and the note, and only then switch on comparison mode. A shared change log outside the product makes this even easier, because every date is already listed in one place you can search.

Do annotations change my Search Console data?

No. Nothing in the Search Console Help page suggests that a note changes clicks, impressions, CTR or position. A custom annotation is context for people reading the chart, and a system annotation is Google flagging an issue with data processing or reporting. That second type still matters, because it tells you a dip or bump may come from the reporting rather than from your site. The Data anomalies page, which records known issues from the last 3-16 months, is the place to confirm the details.

Can I annotate a date range in Search Console?

The Search Console Help page and the launch post both describe a note tied to a specific date, and neither describes a date range. That is a real difference from Google Analytics 4, where the Analytics Help page allows a single date or a date range. For a change that rolls out over several days, my advice is to add one note on the start date and, if the rollout is long, a second note when it finishes. Keep the full timeline in your change log.

What happens to annotations after 500 days?

The Search Console Help page says annotations older than 500 days are deleted, with no action from you. Five hundred days is roughly 16 months, so notes from last year's peak season survive, but notes from two seasons back will be gone. The Help page does not describe an export, so copy each note into an off-platform change log the day you add it. That log is also where you keep ticket links and the longer context that does not fit into 120 characters.

How do I fix a typo in an annotation?

You cannot edit it in place. The Search Console Help page says editing annotations is not currently available, so the only fix is to click the marker, select Delete in the pop-up, confirm, and then add a corrected note on the same date. Copy the text from your change log rather than retyping it, so the new note matches your naming system exactly. If the typo is in the date rather than the text, the same delete and re-add routine applies.

Should I annotate Google core updates?

My view is yes, as an external note, but only for updates that Google has announced and only on the date the rollout began. Write it plainly, such as EXT plus the update name, and add nothing that guesses at the effect. The launch post lists external events as a use case, and a public update is exactly that. The risk is blame. A note that says an update hit you on day one tends to end the analysis too early, so keep the note neutral.

Can I put client or staff names in an annotation?

I would not. The Search Console Help page says annotations are considered identifiable business data, are shared with other users on the property, and should not include personally identifiable information like names, phone numbers or addresses. The launch post gives the same advice about sensitive personal information. Use roles or ticket numbers instead, such as a release number from your own system. For teams in Europe, I also see this as sensible GDPR hygiene, though that is my opinion rather than anything the Help page says.

Should small sites bother with Search Console annotations?

Yes, and small sites may gain the most. A one-person site in the United Kingdom or a small store in Germany rarely has a release process or a ticket system, so the chart note may be the only record of when something changed. The cap of 200 notes per property, from the Search Console Help page, is plenty for a site that ships a few meaningful changes a month. Start with migrations, template changes and big content rewrites, and add holidays that matter to your market.

When did Google launch custom annotations?

Google announced custom annotations on the Search Central blog on Monday, November 17, 2025, in a post by Daniel Waisberg and Tsahi Edri of the Search Console team. The post describes the feature as a way to add contextual notes to performance charts, with notes of up to 120 characters on a specific date. It also invited feedback on LinkedIn and in the Google Search Central Community. The Search Console Help page covers the detailed rules, including the 200-note cap and the 500-day deletion.