How to Give an SEO Agency or Freelancer Access to Google Search Console (Safely)

Add a user to Google Search Console step by step, choose owner, full or restricted permission for your SEO agency, and remove access when the work ends.

TL;DR

To give an SEO agency or freelancer access to Google Search Console, the property owner opens Settings, Users and permissions, clicks Add user, enters the agency’s Google Account email and chooses a permission level. Full user fits ongoing SEO work, restricted user fits audits and reporting, and owner is almost never needed. Share the domain property when one exists, remove the user (and any verification tokens) when the contract ends, and if the agency connects an AI assistant, ask which Google account it uses and whether it runs read-only.

Here is the short answer for clients: you add the agency as a user of your Search Console property, under your own control, and you never hand over a password. It takes about two minutes. The rest of this page explains which permission level to pick, which property to share and how to take access back later.

If you are an agency or a freelancer, send this page to every new client during onboarding. It answers the questions they usually ask by email anyway.

Never share a Google password: add the agency as a user instead

Search Console has its own user management, so a shared login is never necessary. Each person signs in with their own Google Account, and the owner can change or remove that access at any time without resetting anything.

A shared password breaks three things at once: you cannot tell who did what, you cannot remove one person without locking out everyone, and the agency gets access to Gmail, Drive and every other Google service on that account.

A few limits from Google’s permissions documentation are worth knowing before you start:

  • A property can have up to 100 non-owner users (full, restricted and associate users together).
  • Email groups cannot be added. Every person needs their own Google Account email, which is also what makes removal clean.
  • Only owners can see the Users and permissions page, so the person doing this must be an owner of the property.

How to add a user to Google Search Console (the steps for the client)

Adding a user takes five steps, and only an owner can do it. Ask the agency for the exact Google Account email they want you to add before you begin.

  1. Open Search Console and select the property in the property selector.
  2. Go to Settings, then open Users and permissions.
  3. Click Add user.
  4. Enter the agency’s Google Account email address.
  5. Choose the permission level (see the next section) and save.

The agency will see the property in their own property selector the next time they open Search Console. Nothing changes on your website.

If Search Console shows the message “This user may only be added as ‘Owner’”, the person already owns a parent property, such as the domain property that contains this URL-prefix property. Google then gives them owner rights on the child property implicitly, and adding them at a lower level is not allowed.

Owner, full or restricted: what each permission level can do

Search Console has three levels people actually use: owner, full user and restricted user. Owners control users and settings, full users can see all data and take some actions, and restricted users get view access to most data. A fourth role, associate, is for linked services and cannot open Search Console directly.

Here is what each level can do, based on Google’s permissions table:

ActionOwnerFull userRestricted user
Performance report and other reportsYesYesYes
URL InspectionFullFullFetch only
Submit sitemapsYesYesNo
Remove URLs (Removals tool)YesYesView only
Disavow linksYesYesNo
Validate fixes in issue reportsYesYesNo
Add or remove users and ownersYesNoNo
Link a Google Analytics accountYesNoNo

Owners come in two kinds. A verified owner proved ownership with a token, such as an HTML file, a meta tag or a DNS record. A delegated owner was made an owner by someone else, with no token. That difference matters later, when you remove access.

Which permission level does an SEO agency really need?

For ongoing SEO work, give the agency full user. For an audit, a proposal or a reporting-only contract, restricted user is enough. Keep owner inside your own company.

Full user covers what an SEO retainer usually involves: submitting a new sitemap after a site change, validating a fix in an indexing report, using URL Inspection properly, and handling an urgent URL removal. A restricted user would have to ask you for each of those, which slows the work down and puts you in the middle of every small task.

Restricted user is the right call when the agency only needs to read. A pitch audit or a monthly report runs on the Performance and indexing reports, which restricted users can see. You can upgrade them later in the same menu.

Owner is the level we would refuse to hand out by default. An owner can add and remove other users, including other owners, and can link Analytics. If an agency asks for owner, ask what task needs it. If there is a real reason, make it a delegated owner (no token on your site) and make sure at least one verified owner stays inside your company. Without a verified owner, nobody can access the property.

Domain property or URL-prefix property: which one should you share?

Share the domain property when you have one, because it covers the whole site. A URL-prefix property covers only URLs that start with that exact prefix, so an agency given only https://www.example.com/ will miss data from other subdomains and protocols.

Google’s property guide defines the two types:

  • Domain property (for example example.com): includes all subdomains (www, m, shop and so on) and all protocols. It can only be verified with a DNS record.
  • URL-prefix property (for example https://www.example.com/): includes only URLs that begin with that exact prefix, protocol included. It does not include http://, the bare domain or other subdomains. It supports several verification methods.

Older accounts often have only URL-prefix properties, sometimes three or four for one site. Set up a domain property at onboarding: it needs one DNS record, and the agency then sees one complete picture instead of fragments.

Tell the agency the exact name of the property you shared. Tools and scripts treat sc-domain:example.com and https://www.example.com/ as different properties, and a mismatch is a frequent reason an agency’s tool reports a missing property or a 403 error.

How to remove Search Console access when the contract ends

Removing a user takes a minute. If they were a verified owner, you also have to delete their verification token, or they can verify again.

  1. In the property, go to Settings, then Users and permissions.
  2. Open the menu next to the agency’s account and choose Remove access.
  3. If a warning says the user may regain access, remove the ownership tokens it lists. You can also find them under Unused ownership tokens.

Tokens are where cleanup usually fails. If the agency’s developer verified ownership by uploading an HTML file, adding a meta tag or creating a DNS record, that token keeps working until someone deletes it. Google warns that a removed owner can re-verify with a leftover token, and all current owners get a notification when that happens. Check that no other Google service, such as Merchant Center, uses the same token before you delete it.

On the agency side, two more steps:

Put a removal date in the contract’s offboarding checklist. Access that nobody remembers to remove is how a former vendor ends up seeing client data years later.

Google Analytics 4 access works differently

GA4 has its own user list and its own roles, so granting Search Console access does not grant Analytics access, and removing one does not remove the other.

To add a user in GA4, Google’s steps are: Admin, then Access Management under Account or Property, click +, Add users, enter the email, tick Notify new users by email if you want, choose the role and click Add.

The GA4 roles that matter for an SEO agency:

  • Viewer: sees settings and data and can build their own explorations. Enough for SEO reporting.
  • Analyst: can also share explorations.
  • Marketer: manages audiences, events and key events.
  • Editor and Administrator: control settings; only Administrators manage users.

Account-level roles apply to every property in the account, so add the agency at the property level. GA4 can also hide sensitive numbers with the No Cost Metrics and No Revenue Metrics restrictions, which show those values as 0.

What access does an AI assistant get when the agency connects it?

When an agency connects Claude, ChatGPT or another assistant to Search Console, the assistant acts as the Google account that signed in. It can reach every property that account can reach, with that account’s permission level as the ceiling.

Google’s Search Console API has only two OAuth scopes: read/write and read-only. A scope applies to the whole Google account, not to one property. So the property-level permission you chose in Search Console is the real limit, and the connector’s own settings are the second limit.

That gives you two practical controls:

  • On the client side: if you add the agency as a restricted user, no tool acting as that account gets more than a restricted user’s rights. It cannot submit a sitemap, whatever the assistant is asked to do.
  • On the agency side: the connector should run read-only unless a task needs writes, and limit each analyst to their own clients.

Ask your agency two direct questions: which Google account does your AI tool use, and can it change anything in our property? Our MCP safety checklist covers tokens, revocation and prompt injection in more depth.

Where GSC Magic fits for agencies and freelancers

GSC Magic is a hosted MCP connector that lets Claude, ChatGPT, Cursor and other AI clients read Search Console, Bing Webmaster Tools and GA4 data through Google sign-in. Per the security page and pricing:

  • No passwords or key files. Sign-in happens on Google’s page and asks for Search Console and read-only GA4 access in one consent. You can revoke it from your Google account at any time.
  • Free plan is read-only. One site, and every tool that writes (sitemaps, IndexNow, Bing URL submission) is unavailable.
  • Pro ($19 a month, 10 sites) adds write tools, and the workspace owner can switch write mode off in Settings.
  • Agency ($35 a month, 25 sites, 5 seats) adds roles and client groups. Members are always read-only in AI agents, viewers get the dashboard only, and a client group limits each person and each connected agent to that client’s sites.

Every new account starts with a 7-day Pro trial with no card, and both paid prices are founding prices until 31 December 2026. A freelancer with a few clients usually fits Pro; see the setup for SEO freelancers. A team that needs to separate clients by person should look at the Agency plan and the guide to connecting multiple client sites to Claude.

The Google permission still comes first. GSC Magic can only see properties the connected Google account already has access to, at the level the client granted.

Frequently asked questions

Can I give Search Console access without sharing my Google password?

Yes. A property owner adds the agency’s Google Account email under Settings, Users and permissions. The agency signs in with its own account, and the owner can remove it at any time.

What permission should I give my SEO agency in Search Console?

Full user for ongoing SEO work, since full users can submit sitemaps, request removals and validate fixes. Restricted user is enough for an audit or reporting. Owner is rarely needed.

How many users can a Search Console property have?

Up to 100 full, restricted and associate users per property, and up to 500 verified and delegated owners combined. Email groups cannot be added.

Does removing someone from Search Console also remove their Google Analytics access?

No. They keep separate user lists. Remove the person in Search Console under Settings, Users and permissions, then in GA4 under Admin, Access Management.

Can an agency’s AI assistant change my Search Console settings?

Only if the agency’s Google account has a permission level that allows the change and the connector has write tools switched on. A restricted user cannot submit sitemaps, and a read-only connector cannot write at all.

Send this to your next client

The whole process fits in one onboarding email: “Please add agency@yourdomain.com as a full user on your domain property under Settings, Users and permissions.” Link this page under that sentence for the why, and write the removal step into your offboarding checklist the same day.

If you want the assistant your team uses to read that data without the risk of changing it, start with the free plan on one client site and check what the connector can and cannot do before you add the rest.

, Founder of GSC Magic

Łukasz builds GSC Magic, the MCP server that gives AI agents access to Google Search Console, Bing Webmaster Tools and GA4. He writes about using Search Console data with Claude, ChatGPT and coding agents, and about the SEO workflows those tools make possible.

lukaszblania.comgithub.com/lumizone

Give your agent your search data.

GSC Magic connects Claude, ChatGPT and Cursor to Google Search Console, Bing and GA4. Free plan, 7-day Pro trial, no card.

Start free