As the property owner in Google Search Console, if you need to add users to Google Search Console, the process is easy. The part that can bite you later is choosing the wrong permission level, because that can hand someone the keys to settings you never meant them to touch.
In this step-by-step guide, I’ll walk through the exact process to invite a teammate or collaborator into Google Search Console. You’ll see where you’ll go to manage existing access, and how to think about the three permission options so you don’t create problems for yourself later. Oh and if you need to log into Google Search Console, here’s the link: https://search.google.com/search-console/about
If you’re more of the read it type, here’s my full breakdown of how to add users in Google Search Console & set the right permissions for them.
Adding Users to Google Search Console (and Why User Permissions Matter)
My goal is simple: I want the right person to see the right search property in Google Search Console, with the right level of access. That means I’m doing three things:
First, I’m logging into the correct Google Account (this matters more than people think). Next, I’m choosing the exact website property I want to share. Finally, I’m inviting a user and selecting the permission level that matches what they actually need.
If you’ve ever heard, “I added you, but you can’t see it,” like the performance data, there’s almost always a boring reason behind it, either the wrong Google account, or the invite went to the wrong email, or the wrong property got selected.
Login to Google Search Console the Fast Way
I log in through Google Search Console’s official page, Google Search Console login page. If I’m moving quickly, I’ll also just search Google for “Google Search Console login” and use the sign-in result.
Once I’m in, I should land on the Search Console dashboard to view data. From there, everything is driven by which property I have selected. That’s why I don’t rush this step, even though it feels obvious.
One more small thing that saves time: I make sure I’m already signed into the Google Account I intend to use before I start clicking around. If I’m signed into the wrong one, I can waste a few minutes inviting people to a property list that isn’t even the one I manage.
Double-Check You’re Using the Right Google Account
I juggle multiple Google Accounts, toggling between them often, and I’m willing to bet you do too. That’s why I pause here and confirm I’m logged into the Google Account that already has access to the Google Search Console properties I need after ownership verification.
If someone can’t see the property after they accept your invite, the most common cause is that you invited them from the wrong Google account, or you picked the wrong property.
This is also why I keep my workflow boring and repeatable. When I stay consistent, I don’t accidentally invite a contractor to a client Google Search Console property from some other Google profile I used once on a laptop years ago.
Choose the Correct Property Before You Invite Anyone
After I’m in the right Google Search Console account, I select the specific website property I want to share. This is the site (or property) that a teammate, developer, agency, or collaborator needs access to.
I treat this like handing someone a key. I don’t want to hand them a key to the wrong house, even if the permission settings are perfect.
Once I pick the property, I can see the main Google Search Console view with the big insights and reports. That’s my sign that I’m in the right place, and now it’s time to head to the property settings.
Find User Access Settings in Search Console
Google doesn’t put user invites on the main dashboard front and center. Instead, I scroll down the left-side navigation until I see property settings at the bottom in Google Search Console.
When I’m explaining this to someone on my team, I say it like this: Property, then Settings. That’s the path.
From the property settings, I can get to the area where I can manage users, add someone new, or clean up access that’s gotten messy over time.
Open “Users and Permissions” and Review Existing Access
Inside Settings, I open Users and permissions. This page is the control room for who can see what.
Before I add anybody, I take ten seconds to scan the list of current users. That quick review helps me avoid two common mistakes: inviting the wrong email because it looks familiar, or sending an invite that’s already been sent (and then wondering why nothing changed).
If I need to remove someone or change what they can do, I use the three dots menu next to their name. That’s where Google lets me adjust their permission level or remove access entirely.
Add a User and Pick the Right Permission Level
To invite someone new, I click the Add user button. Google prompts me for an email address, and I enter the email address for the person I’m inviting (in the video example, it’s something at [email protected]).
Then comes the part that matters most: Picking the right permission level is key in Google Search Console.
Here’s how I think about each option:
- Owner: This is rare for me, whether it’s a Verified owner or Delegated owner. Owner access gives someone the ability to change settings and invite new users themselves. If I wouldn’t trust them to manage access for the whole property, they’re not an owner.
- Full user: This lets a Full user take actions inside Search Console. It can include things like URL inspection and uploading disavow files, so I’m careful with this option.
- Restricted user: This is what I use most often. A Restricted user can view everything in the property, but they can’t make changes behind the scenes. For most collaborators who just need the data, this is the right fit.
If your goal is visibility without risk, Restricted user is the safest default.
Send the Invite and Make Sure They Confirm It
Once I’ve entered the email and selected the permission level, I click Add user to send the invitation in Google Search Console.
Google emails them an invite, and they need to confirm from their inbox. You can track the invitation status under Users and permissions. After they click to accept, they’ll have access.
After acceptance, when they log into their own Google Search Console account, they’ll see your site in their list of properties, associated as a property owner or with the exact access you set, such as the ability to submit sitemaps.
This grants them access without requiring them to handle site verification themselves, whether through an HTML file upload, an HTML tag addition, or a verification token.
If you want Google’s official documentation on these roles, see Google’s guide to managing owners, users, and permissions.
Frequently Asked Questions About Google Search Console (FAQs)
Here are a few of the most frequently asked questions I get related to GSC and adding users.
Why can’t my teammate see the Search Console property after I invite them?
Most of the time, it’s because I invited them while logged into the wrong Google account, or I added them to a different property than the one they’re checking. I fix it by confirming the account and property, then reviewing the Users and permissions list again.
Which permission level should I use for most collaborators?
I usually choose Restricted because it allows viewing all the data without allowing changes behind the scenes.
What’s the risk of giving someone Owner access?
Owner access gives someone the ability to change settings and invite new users. That’s why I rarely use it unless the person truly needs that level of control.
What can someone do with Full access in Google Search Console?
With Full access, a user can take actions inside GSC. In practice, that can include sensitive actions like setting up redirects and uploading disavow files, so I only grant it when it’s clearly needed.
Where do I remove a user or change their permission level?
I go to Settings, then Users and permissions, then click the three dots next to the user I want to manage. That’s where I can remove them or adjust access.
Final Thoughts: Add Users Once, Maintain Current Access Permissions
Adding a user in Google Search Console is quick, but picking the wrong permission from the users and permissions menu can turn into a long afternoon of cleanup.
I stick to Restricted user for most invites, only bumping up to access levels like Full user, Verified owner, or Delegated owner when there’s a clear reason, such as onboarding an SEO agency. To manage users effectively, I keep property settings tight and verify ownership verification upfront.
If you’re also using Google Search Console alongside Google Analytics to guide your content decisions, my GSC keyword workflow guide and SEO for bloggers guide pair well with this setup.
If you run into the classic “they can’t see the property” issue as a property owner, check the Google account and property settings first. Those two details cause most of the confusion.
Use My 50+ Powerful Free Blogging Tools Today
When I first started blogging, I couldn’t afford fancy tools. That sucked. And that’s why I’ve built a stable of powerful free blogging tools ranging from keyword research to an AI article writer, blog idea generator and more. Forever free for all to use—no strings attached.
