Is Google finally going to launch read-only guest accounts for Search Console?

Why does the demand for guest accounts keep coming up?

SEO agencies and independent consultants face a simple problem: to track a client's performance, they either need full property access to Search Console or must ask the client to manually export the data. The first option poses an obvious security risk, while the second quickly becomes unmanageable with several dozen clients.

The request for a read-only mode has been circulating in the SEO community for years. It would allow consulting reports without altering critical settings: no changes to robots.txt, no URL removals, no unwanted link disavowals by an overzealous intern. A guest account would also prevent access to sensitive data like detailed Core Web Vitals or manual penalty messages.

What exactly does Google say in response to this request?

The official response resembles a conditional yes without commitment. Google admits that the feature would be useful, but weighs it against other initiatives considered more urgent. Two examples mentioned: improving the strength of backlink reports and reducing the data update delay in Search Console.

This prioritization of needs is not neutral. It reveals that Google views the reliability of its reports as more critical than the operational needs of agencies. In other words: sharing tools will be offered when the shared data is truly reliable.

What workarounds are currently being used?

In the absence of native guest accounts, SEO practitioners have developed alternative workflows. The most common: creating a dedicated Gmail address for each client and linking all tools (Search Console, Analytics, Tag Manager) to it. The agency maintains control of the master account, while the client retrieves access at the end of the engagement.

Another option: automated CSV exports via Google Sheets and the Search Console API. This requires technical skills and a heavy initial setup, but provides fine granularity on shared data. The downside? These exports never give access to real-time alerts or Google messages in the interface.

• No announced timeline for the rollout of read-only guest accounts
• Stated priority: improvement of backlink reports and data freshness
• Current solutions: dedicated Gmail accounts or automated exports via API
• Ongoing risk: full access or no access at all, with no secure intermediate level

Does this response reveal a deeper issue at Google?

Let’s be honest: if Google is weighing guest accounts against the quality of backlink reports, it’s because those reports are still quite flawed. For years, Search Console has shown incomplete backlinks, with missing referring domains and absurd detection delays. The fact that Google is still prioritizing this issue indicates that the problem remains unsolved.

This statement seems like a preventive excuse. By saying, "we would love to, but we have other priorities," Google avoids committing to a timeline while appearing responsive. The risk? This feature could remain in limbo for another 2-3 years, like so many other unfulfilled promises.

Are SEO agencies really the target for this feature?

Not necessarily. Google might just as well target large corporations with fragmented marketing teams: an SEO manager who wants to give access to an intern or a temporary contractor without opening all doors. In this case, the read-only mode would primarily serve the internal governance of data.

Agencies, on the other hand, have already cobbled together their own solutions. They are not going to sit patiently waiting for Google to deign to launch the feature. This raises a question: if the demand has existed for so long, why hasn’t Google ever considered it critical? [To verify]: does the actual number of agencies affected justify the development cost?

Is this prioritization of backlinks justified?

Hard to say without knowing the exact state of internal projects. What we do know: backlink reports in Search Console are notoriously incomplete compared to Ahrefs, Majestic or Semrush. Google doesn't crawl everything, doesn’t report everything, and applies opaque filters on what it displays.

If the promised improvement concerns data freshness, that’s a real step forward. Nowadays, some backlinks can take weeks to appear in Search Console. But be cautious: Google doesn't say it will show more links, only that those it shows will be fresher. An important distinction.

What can you do while waiting for these hypothetical guest accounts?

The first option: continue using dedicated Gmail accounts for each client. This is the simplest solution if you manage fewer than 20 sites. Create an email like "seo-clientname@gmail.com," add it as an owner in Search Console, and keep the password secure in a manager like 1Password or Bitwarden.

The second option: automate exports via the Search Console API and Google Sheets. This requires some Python or Apps Script scripting, but you control exactly what data is shared. You can even create custom dashboards in Looker Studio that pull directly from the API without going through the Search Console interface.

How to secure current access without a read-only mode?

If you must give full property access, document everything. Create a modifications dashboard in Search Console: who has access, since when, for which project. Activate email notifications for any critical modifications (address change, URL removal, link disavowal).

Another precaution: limit access to domain properties rather than individual URL properties. This reduces the risk of an external provider accidentally changing settings for a sensitive subdomain. And above all, revoke access immediately at the end of the engagement, without waiting for the client to remember.

Should you wait for Google or develop your own tools?

Never bet on an unconfirmed Google timeline. If you manage more than 30 clients, invest in a bespoke solution or a third-party tool like Sitebulb Dashboard or AgencyAnalytics. These platforms connect directly to the Search Console API and offer granular access per client.

For medium-sized agencies, this technical complexity can quickly become a hindrance. Teams spend more time tinkering with exports than analyzing data. In this case, hiring a specialized SEO agency can be more cost-effective: they already have the API infrastructure and automated dashboards to manage dozens of properties without multiplying risky access points.

• Create dedicated Gmail accounts per client with secure passwords managed in a vault
• Enable email notifications for any critical changes in Search Console
• Limit access to domain properties rather than individual URLs
• Automate exports via the Search Console API if managing more than 20 sites
• Systematically revoke access at the end of the engagement
• Document who has access to what and why in a centralized log