What You Will Learn
- Assign individual logins with the lowest viable permission level instead of sharing a single Google account.
- Verified owners hold permanent administrative control and can only be removed by deleting their underlying verification token.
- Maintain a simple team access register to audit permissions and cleanly offboard team members or outside contractors.
Managing Search Console user permissions correctly protects your site data and keeps your configuration clean. When team members share a single login or everyone holds owner rights, you cannot tell who changed a setting, submitted a removal, or modified a sitemap. The solution is straightforward: give every team member their own Google account login, grant only the permission level needed for their daily tasks, and keep an access register that tracks who holds verified ownership tokens.
In this guide, we will walk through auditing your current property access, choosing between permission tiers, mapping roles for a small team, removing obsolete accounts, and checking verification tokens so old vendors cannot regain entry.
Prerequisites Before You Begin
Before you adjust user roles in Google Search Console, make sure you have the following ready:
- Verified Owner access: You must be logged in as an Owner (either verified or delegated) to view the full user list and modify permissions. If you only have Full or Restricted access, you cannot add or remove users.
- Individual Google accounts: Collect the work email address or Google account for each team member. Do not use generic accounts such as
marketing@yourdomain.comshared across multiple staff. - Access to your hosting, DNS, or CMS: To audit verified owners, you need access to your domain registrar, DNS records, or site root files.
- Your property list: Determine whether you are managing a Domain property or a URL-Prefix property. If you need help choosing or setting these up, review How to Choose the Right Search Console Property for a Report or How to Verify a Search Console Domain Property With DNS.
Step 1: Inventory Your Current Property Users
The first step is checking who currently has access to your Search Console property. Over time, past employees, freelance developers, and old SEO agencies often remain on the user list long after their contracts end.
Let us check the user list step by step:
- Sign in to Google Search Console and select your property from the top-left dropdown.
- In the left-hand navigation menu, scroll to the bottom and click Settings (gear icon).
- Look for the row labelled Users and permissions and click on it.
- Review the table of accounts. You will see columns listing the email address, permission level, and in some views, the verification status.
Write down every email address listed. Note which accounts belong to active team members, which belong to past agencies or contractors, and which are unknown.
Step 2: Understand the Search Console Permission Levels
Google Search Console provides distinct permission levels. Assigning everyone "Owner" rights is a severe security risk. Here is how the levels differ:
| Permission Level | What They Can Do | Recommended Role |
|---|---|---|
| Verified Owner | Full control. Can add/remove users, change settings, submit sitemaps, inspect URLs, and request indexing. Proven by a physical token (DNS, HTML file, meta tag). | Site founder, technical lead, or primary domain admin. |
| Delegated Owner | Can perform all owner actions, including adding and removing other users, but does not personally hold a verification token. Granted by a Verified Owner. | Senior marketing director or lead developer managing day-to-day settings. |
| Full User | Can view all performance and indexing data. Can use the URL Inspection tool to test pages and request indexing URL Inspection Tool. Cannot manage users or change property associations. | Internal SEO specialists, content managers, and active developers. |
| Restricted User | Read-only access to most performance reports, search queries, and impression charts How Are You Performing on Google?. Cannot request indexing or run administrative tests. | Copywriters, junior analysts, external consultants, and executives needing summary data. |
Note that submitting a sitemap directly in the Sitemaps report requires owner permissions Search Console Sitemaps Report. If non-owner team members need Google to discover sitemaps, ensure the sitemap URL is referenced in your robots.txt file .
Step 3: Map Roles to Team Responsibilities
A small team usually consists of a few distinct functions: leadership, content creation, technical maintenance, and outside reporting. Use the rule of least privilege: give each person the minimum level of access needed to finish their job.
Illustrative Example: Four-Person Publishing Team
Let us look at a hypothetical setup for a small content business:
- Arun (Founder & Domain Admin): Holds Verified Owner status via a DNS TXT record. Arun retains ultimate control over the domain and user roster.
- Pooja (Lead Developer): Holds Full User status. Pooja needs to inspect live URLs, review crawl errors, and test mobile usability, but does not need to add or delete other users.
- Rohan (Content Editor): Holds Full User status. Rohan monitors search queries, checks index status for newly published blog posts, and requests indexing through the URL Inspection tool .
- Meera (Freelance Copywriter): Holds Restricted User status. Meera only needs to see which queries bring impressions and clicks in the Search performance report to inform topic research .
Notice that in this example, only one person holds owner rights. If Pooja or Rohan need to step away or leave the team, the property settings remain secure.
Step 4: Add Authorized Individual Users
Once you decide on the proper level for each person, add them individually:
- Go to Settings > Users and permissions in your Search Console property.
- Click the blue Add user button at the top right.
- Enter the user's valid Google account email address.
- Select either Full or Restricted from the Permission dropdown menu.
- Click Add to save.
The user will immediately see the property in their Search Console dashboard when they sign in. They do not need to upload any verification files or add HTML meta tags to their templates.
Step 5: Remove Obsolete or Inactive Accounts
Whenever an employee leaves or an agency agreement finishes, remove their access right away:
- Open the Users and permissions screen.
- Find the user you want to remove.
- Click the three vertical dots (menu icon) on the right side of their row.
- Click Remove access and confirm your choice.
Removing access takes effect immediately for delegated owners, full users, and restricted users. However, if the person was a Verified Owner, a simple click in this menu is not enough.
Step 6: Check and Clean Up Verified Ownership Dependencies
This is where many website owners make a critical mistake. If a former developer or agency verified their own Google account using an HTML verification file, a meta tag, or a DNS record, they are a Verified Owner. If you try to remove them inside Search Console, Google will simply re-verify their account the next time Google checks the property token.
To permanently remove an unneeded verified owner, follow these steps:
- In Settings > Ownership verification, review which verification methods are currently active (HTML tag, HTML file upload, Google Analytics tracking code, Google Tag Manager container, or DNS record).
- Identify which method belongs to the person you need to remove. For instance, if an agency uploaded an HTML verification file named
google12345abc.htmlto your root server, find that file. - Log in to your hosting server or CMS and delete the physical verification file, or remove the HTML
<meta>verification tag from your theme header. If it is a DNS entry, remove the TXT record from your domain DNS management zone. - If verification was completed via a URL-prefix method, you can also review How to Verify a Search Console URL-Prefix Property to understand how prefix tokens interact with property ownership.
- Return to Search Console under Settings > Users and permissions. Locate the unused verified owner, click the options menu, and choose Unverify owner.
- Google will check if the verification token is still present. Because you deleted the underlying file or code in Step 3, the unverification will succeed, and they cannot regain access.
How to Build a Team Access Register
To avoid confusion in the future, create an internal spreadsheet called the Search Console Access Register. It does not need to be complicated. Include these columns:
- Name: Team member or contractor name.
- Google Account Email: The specific login used.
- Property Assigned: Domain property, URL-Prefix, or both.
- Permission Level: Verified Owner, Delegated Owner, Full, or Restricted.
- Verification Token Used: (If Owner) DNS record, HTML file name, or None.
- Date Granted: When access was added.
- Review Date: A calendar date every quarter to review whether this person still needs access.
Common Mistakes to Avoid
- Sharing one owner password: Never create a shared account (like
admin@site.com) that multiple staff share. You lose audit history, and changing the password locks everyone out simultaneously. - Leaving orphan verification files on the server: Deleting a user from the Search Console interface without removing their verification meta tag or HTML file allows them to re-verify themselves at any point.
- Granting Owner status for basic reporting: Junior analysts and freelance writers only need Restricted or Full status. Owner status exposes sitemap controls and allows accidental user deletions.
- Forgetting property variants: If your team uses both a Domain property and a URL-prefix property, updating users on the Domain property does not always mirror across separate prefix properties. Check permissions on all active properties.
How to Verify Your Result
Once you finish adjusting permissions and removing old users, confirm your work with this three-part verification:
- Check the user roster: Visit Settings > Users and permissions. Ensure that only active, authorized team members appear in the table with their assigned roles.
- Test the removed account: If possible, ask the offboarded contractor or check an old test account to ensure the property no longer appears on their Search Console property list.
- Check verification tokens: Go to Settings > Ownership verification. Confirm that only your primary administrative verification method shows as "Verified". No unknown HTML tags or unassigned DNS records should remain.
Limitations and When to Seek Technical Help
Search Console permissions apply at the property level. They do not allow you to restrict access to specific folders or subdirectories within a single Domain property. If you need a content writer to view data only for a /blog/ subdirectory, you must create a dedicated URL-Prefix property for that subfolder and grant them access to that specific property.
If you discover unfamiliar DNS TXT records or code snippets embedded in your theme that you cannot identify, do not delete them blindly. Consult your web hosting administrator or a qualified developer to avoid breaking third-party email authentication (such as SPF/DKIM) or live analytics scripts.
Next Steps
Open your Google Search Console property right now and navigate to Settings > Users and permissions. Run a quick five-minute audit of the email addresses listed. Remove any accounts you do not recognize, downgrade team members who do not need full administrative rights, and document your current setup in a team access register.
Frequently Asked Questions
What is the difference between a Verified Owner and a Delegated Owner?
A Verified Owner proved control over the website using a direct verification method, such as an HTML file upload or a DNS record. A Delegated Owner was granted owner rights by a Verified Owner inside the Search Console interface. Delegated owners can manage users and settings, but they do not hold an independent verification token.
Can a Full User submit a sitemap in Google Search Console?
No. Submitting a new sitemap through the Search Console Sitemaps report requires owner permissions. If a team member has Full or Restricted access, they can view submitted sitemaps, but they cannot add a new one through that report. Alternatively, sitemaps can be declared inside the website robots.txt file.
Why did a removed user reappear in Search Console after I deleted them?
This happens when the user was originally added as a Verified Owner. If their verification token—such as an HTML tag in the site header, an HTML file on the server, or a DNS record—remains active, Google automatically re-verifies them. You must remove the underlying token from your site before un-verifying the account.
Post a Comment