GSC "Failed to Add User: Email Not Found" Error When Adding a Service Account

· About

GSC "Failed to Add User: Email Not Found" Error When Adding a Service Account

If you've recently tried to add a Google Cloud Service Account as a user in Google Search Console (GSC) and encountered the error "failed to add user: email not found", you're not alone. As of May 2026, a growing number of developers and site owners are reporting the exact same issue — and it appears to be an ongoing, unresolved problem on Google's end.

What's the Issue?

When attempting to add a Service Account email (e.g., your-service-account@your-project.iam.gserviceaccount.com) to Google Search Console via Settings > Users and permissions > Add user, the process fails immediately with the error message:

"failed to add user: email not found"

This is particularly frustrating because the same Service Account email works perfectly fine in other Google products such as Google Analytics 4 (GA4) and Google Drive. The issue appears to be isolated specifically to Google Search Console.

Who Is Affected?

This issue is not limited to a specific region or setup. Reports have surfaced across multiple community forums, including the official Google Search Central Help Community, WordPress plugin support threads, and SEO-related blogs. Users are experiencing this regardless of:

  • The Google Cloud project type or configuration
  • Whether the Service Account has domain-wide delegation enabled
  • The GSC property type (Domain property vs. URL-prefix property)
  • The account's role or permission level

Root Cause

The exact root cause has not been officially confirmed by Google as of May 2026. However, based on community discussions, it is strongly suspected that Google Search Console's user management system does not fully recognize Service Account emails as valid Google account identities, even though such accounts are standard in the Google Cloud ecosystem.

This may be related to a recent backend change or policy update on the GSC side that broke the previously working flow of adding Service Accounts as users.

Current Status

As of May 2026, there is no official fix or workaround confirmed by Google. The issue has been reported in the official Google Search Central Help Community forum, but has yet to receive an official response or acknowledgment from a Google staff member.

Many users who depend on Service Accounts for automated GSC data access — such as pulling Search Analytics data via the API — are blocked from setting up their integrations properly.

Possible Workarounds (Not Guaranteed)

While no definitive fix exists, some users have suggested the following as potential alternatives:

  • Use a regular Google account (human account) instead of a Service Account and authenticate via OAuth 2.0.
  • Use the GSC API with a Service Account via domain-wide delegation without adding the account through the UI (though this depends on your use case and GSC property type).
  • Try adding the Service Account from a different GSC owner account.

Note: These are community-suggested workarounds and may not work for all configurations.

What You Can Do

If you are affected by this issue, consider taking the following steps:

  1. Star or upvote the existing thread in the Google Search Central Help Community to increase visibility.
  2. Submit feedback directly through Google Search Console using the feedback button.
  3. Monitor the community thread for any updates or official responses from Google.

We will continue to monitor this issue and update this post if a fix or official statement becomes available.

Related Links