Skip to main content
SEO 9 min read

Who Should Own Your Analytics and Search Console Accounts

Who Should Own Your Analytics and Search Console Accounts

If a vendor set up your Google Analytics or Search Console, it is worth knowing whose account it is. If nobody checks until the vendor relationship ends, the business may discover that it cannot access its historical data.

This article is a practical guide to deciding who should own those accounts, which roles a vendor needs, and how to remove access later. It is not legal advice, and we are not saying any particular vendor does anything wrong. We have not measured how often ownership problems happen, so we make no claim about that. What follows is a way to check your own setup, using what Google’s help pages say about roles.

If your question is about removing access across everything, including logins and tools, our post on website access cleanup when an employee or vendor leaves covers it. This article stays on the two measurement accounts.

A simple principle

Decide that the business controls the accounts, and the vendor is a user in them. Tie that to the roles Google documents: if only the vendor has Administrator access in Analytics or Owner access in Search Console, the business may depend on that vendor to change access. Keep at least one business-controlled identity in the highest role. Everything below is a way to make that true and check that it stays true.

What Google Analytics roles look like

Google’s Analytics Help page on access management lists five roles: Administrator, Editor, Marketer, Analyst and Viewer, plus a “None” setting. It describes them this way:

  • Administrator has full control of Analytics and can manage users, including adding or deleting users and assigning any role. Google notes that an Administrator can grant full permissions to any user, including themselves, for any account or property where they hold that role.
  • Editor has full control of settings at the property level. Google says an Editor cannot manage users, but can view users across a property.
  • Marketer can create, edit and delete audiences, events and key events.
  • Analyst can share explorations created in the property with other users.
  • Viewer can see settings and data, and can change which data appears in reports.

The same page says you must be an Administrator, at the account level or the property level as the case may be, to assign roles and data restrictions.

For you, the practical point is that the Administrator role controls who else has access. The question to ask is: who holds it, and is at least one of those people on your side of the relationship?

What Search Console permissions look like

Google’s Search Console Help page on managing owners, users and permissions says each user of a property is assigned a permission. The ones it names are Owner, Full user and Restricted user, and it also describes Associates, who it says cannot open or view the account directly.

Several points from that page matter for ownership:

  • Owners can add and remove other users, configure settings, view all data and use all tools. Google says you can grant permissions to other users only if you are a property owner.
  • A property must have at least one verified owner, or no users will have access to it.
  • There are two kinds of owner with the same permissions. A verified owner proved ownership with a token, such as an HTML file uploaded to the website. A delegated owner was granted ownership by a verified owner without a token.
  • To add or remove a verified owner, Google says you add or remove a token on the site. To add or remove a delegated owner, an owner of any type uses the user management screen.

The page also says that if the only verified owner of your site leaves your team, you should verify ownership to maintain or regain access. It adds that if you are taking over a site, after you verify ownership you can unverify previous owners by removing their verification token.

That detail is worth noticing. A verified owner is tied to a token placed on the site, so removing someone’s access involves more than deleting a name from a list. Google’s page says that when an owner is removed, the person loses access to the property immediately, but their verification tokens are not deleted or revoked. As long as a token remains, Google says the removed owner can re-verify ownership and regain access, and that all current owners are notified if this happens.

Questions to answer about your accounts

Sit down with whoever manages your accounts and answer these in writing:

  1. Who is the Administrator of our Analytics account and property? Is at least one of them a person at our company, using an email address we control?
  2. Who are the owners of our Search Console property, and are they verified or delegated owners? Which verification token is on our site, and who placed it?
  3. What role does each vendor have, and what does that role let them do? If a vendor needs less than the highest role, change it.
  4. Are access and roles tied to named people, or to a shared login that several people use?
  5. Which named, business-managed Google identities have access? Confirm that the business controls those identities and can keep administrative access when an employee leaves, without anyone sharing login credentials.
  6. What would we do if the vendor left tomorrow? Who would remove them, and how long would it take?

If you cannot answer any of these, that is useful to know before a change in your team or vendor makes it urgent.

Give a vendor the role the work needs

You can decide how much access to give by looking at what the work requires, using only the descriptions Google publishes.

  • Search Console, basic viewing: Google describes a Restricted user as having simple view rights on most data. If a vendor only needs to look at the data, that may be enough.
  • Search Console, wider data and some actions: Google describes a Full user as having view rights to all data and being able to take some actions. Consider this when a vendor needs all the data and the actions a Full user can take.
  • Search Console, managing people and ownership: reserve Owner for work that requires adding or removing users or owners, because Google says only owners can do that.
  • Analytics, reading reports: Google says a Viewer can see settings and data and change what appears in reports.
  • Analytics, building audiences or key events: Google says a Marketer can create, edit and delete audiences, events and key events.
  • Analytics, managing people: reserve Administrator for work that requires managing users, because Google says only an Administrator can assign roles.

Google’s permission details change, so confirm the choice against the current Search Console permissions table and the Analytics role descriptions before you grant anything. We are not recommending a particular role for any particular task, because it depends on the work. The principle is to match the role to the task, and to revisit it when the work changes.

Be most careful about the roles that can manage users: Administrator in Analytics and Owner in Search Console. Those control who else has access, so it is reasonable to ask why a vendor needs them and to keep your own people in the same roles.

Removing access later

Plan the exit when you grant access, and write it down. For each vendor, record:

  • Which accounts and properties they can reach, and in which role.
  • Who on your side is responsible for removing them.
  • For Search Console, whether they are a verified owner whose token is on your site, a delegated owner, or a user, and which other Google services, if any, rely on the same token.
  • The date you last reviewed it.

When the relationship ends, work through each account in order.

Analytics: an Administrator removes the vendor’s access in access management, and you then check the user list to confirm it.

Search Console: the order matters.

  1. First confirm your business has its own verified owner. Google’s page says a property must have at least one verified owner, or no users will have access. If the vendor is the only verified owner, establish your own ownership before removing them.
  2. Remove the vendor as an owner or user on the Users and permissions page. For an owner, Google says access is lost immediately.
  3. Review the verification tokens that belong to that vendor. Google says that if you do not delete them, the removed owner can re-verify ownership. The page says you can see the remaining tokens in the Unused ownership tokens list, and that an owner who used several verification methods may have several tokens.
  4. Check what else depends on each token before you delete it. Google warns that the same verification token can be reused across services, such as Search Console, Merchant Center and Google Workspace, and that removing it could negatively affect other services relying on it. Ask whoever manages those services before removing a token.
  5. Remove the tokens you have confirmed are safe to remove, then check the user list and the Unused ownership tokens list again.

If you find an owner you do not recognize, Google’s page says you might have been hacked. Treat that as a security question and involve someone qualified, not as a routine cleanup.

What this article does not cover

This is a reading of two Google help pages, which may change, so check the current pages before you act. It does not cover how to configure tracking, key events or reports, and it does not advise on contracts, which belong with the person who reviews yours. We also do not claim any role arrangement is best for every business.

If you would like a second reader for how your accounts are set up, you can request a measurement-access review through our SEO service page, or contact us directly. For related reading on named accounts and sign-in security, see our post on website login security and named accounts.

Sources: Access and data-restriction management, Analytics Help and Managing owners, users, and permissions, Search Console Help.

Tags: google-analytics-ownership search-console-ownership analytics-access vendor-access measurement-accounts
JJ

Jeremy Johnson

Owner

Jeremy co-owns Robben Media and directs strategy for every client engagement. With a Computer Engineering degree from Missouri S&T, he brings deep technical expertise in web development, SEO, and automation. Before acquiring Robben Media in 2023, Jeremy led marketing and branch management in the mortgage industry. He believes marketing should be measured by revenue generated, not impressions reported.

What Our Clients Say

Real results from real businesses. No fluff, no fake reviews.

4.9/5.0 from 71 reviews
“Jeremy is an absolute wealth of knowledge. As a newer business owner he has helped me establish an online presence. I appreciate how thorough and how well he explains even the basics so I can always understand what is needed. Looking forward to continuing to build my relationship with Jeremey and Robben Media.”
Cara O
“Robben Media has done amazing work for us. From creation of a website, to maintenance, to SEO - you name it, they're a master at it. We switched from a company we "thought" was doing a good job - but once we went to Robben Media our online success exploded. They are super nice, knowledgeable, and attentive. I would highly suggest you hire this team if you want to grow your company!”
JB
Joe Burns
“Jeremy is extremely knowledgeable in his field. He is always prepared and armed with the knowledge and experience needed to grow your business online. If you want your business to be easily found in web searches, or if you need some help building or improving your website, Jeremy with Robben Media is the one to call!”
AK
Amber Klempke

Ready to Put These Strategies to Work?

Your competitors are already investing in digital marketing. Let's make sure you're not left behind.