Ahrefs has made a small but useful collaboration change to Rank Tracker and its Google Search Console charts: user notes are now shared across the workspace. Instead of behaving like personal annotations visible only to the person who created them, notes attached to a shared project can now become part of the project's common SEO context.
The change appears in the official Ahrefs changelog for September 18, 2026. Ahrefs says that everyone with access to a project can see its Rank Tracker and GSC chart notes, while users with editing rights can update any note. The company's more detailed product-update documentation for shared user notes describes the same collaboration model: members with editing rights can edit notes, guests are limited to viewing them, and notes cannot be made private once they belong to this shared project context.
Annotations become part of the SEO project's history
Notes on performance charts are easy to underestimate because they do not change rankings, crawl data or traffic metrics themselves. Their value is contextual. An SEO team can mark the date of a site migration, content release, template change, technical fix, campaign launch or other event directly against the performance timeline. When rankings, clicks or impressions move later, the chart carries some of the operational history needed to interpret that movement.
Making those annotations workspace-visible turns them from an individual analyst's memory aid into shared project data. A teammate opening Rank Tracker does not have to know who originally created a note or ask that person what happened on a particular date. If the project has been shared with them, the annotation travels with the project and remains visible alongside the performance graph.
The change also applies to GSC charts
Ahrefs explicitly includes GSC charts in the update, which makes the feature useful beyond traditional rank monitoring. Ahrefs integrates Google Search Console data into its reporting environment so teams can review search clicks, impressions and related performance information alongside its own SEO datasets. Shared annotations allow the same event to be documented in the context where teams are investigating those trends.
This can be particularly useful when several people work on the same property. A technical SEO may annotate an indexing-related deployment, a content team may record a major publishing change, and another analyst can later interpret a shift in GSC performance without reconstructing the project's history from Slack messages, tickets or separate spreadsheets. The note does not replace those systems, but it places the relevant context directly on the chart where the change is being analyzed.
Visibility follows project access
The permission model is straightforward. Ahrefs says that when a project is shared, everyone in it can see the notes. Users with editing rights can modify any note, while view-only participants can see the annotations without changing them. Ahrefs' current workspace permissions documentation explains that its access model combines workspace roles with project-level sharing controls, so the new note behavior fits into the permissions already governing who can reach a project.
One consequence is that teams should treat notes as collaborative project records rather than private annotations. Ahrefs' documentation states that shared user notes cannot be made private. That is useful for transparency, but it also means users should avoid putting personal reminders or sensitive commentary into a project note if everyone with project access is not meant to see it.
A minor feature with practical agency value
This is not a headline SEO-data release on the scale of a new index, ranking metric or API. It does, however, solve a familiar operational problem: performance data often survives longer than the context explaining it. Team members change, projects move between agencies and in-house teams, and months later a spike or decline can be obvious on a chart while the reason behind it has disappeared into old messages.
Shared notes make the timeline more self-documenting. They can help teams distinguish an external search change from an internal deployment, remember when an experiment started, or record why a particular period should be interpreted cautiously. Because editors can update existing notes, the context can also be corrected or expanded as a team learns more about an event.
The September 18 update therefore fits a broader trend in professional SEO platforms: data tools are becoming collaboration environments as well as reporting interfaces. Ahrefs already organizes projects, keyword tracking and Search Console information around shared workspaces; making Rank Tracker and GSC annotations visible at that same level adds the human explanation layer to the shared dataset.
It is a modest release, but for teams that regularly annotate ranking and Search Console movements, the practical change is clear. The notes now belong to the shared SEO workspace rather than only to the person who wrote them, giving everyone working on the project a better chance of understanding not just what changed in the charts, but what the team was doing when it changed.