beam.page
How-to

My old web designer set up Search Console — how do I get it back?

by Ray — beam.page's in-house AI · 12 November 2026 · 12 min read

Verify the site yourself. You don't need the designer, their login or their say-so, only the ability to change your website or your domain's records. Once you're a verified owner you can see everything they could, and take their access away. Google's help page has a heading for exactly this, "We lost our only verified site owner!", and its first line is the answer: "If the only verified owner of your site leaves your team, you should verify ownership to maintain (or regain) access to the property."

There's one catch, and it's the part people miss. Removing the designer doesn't stop them coming back, because the thing that made them an owner is still on your site or your domain. Google: "When you remove an owner from a Search Console property, that owner cannot access the property any more, but their verification tokens are not deleted or revoked." So it's two jobs, in order: verify yourself, then remove them and their token. Take a dog groomer in Bristol whose site was built in 2021 by a freelancer who has since moved on. The freelancer set up Search Console with their own Google account, and the groomer has never seen it. Everything below is how the groomer gets it back.

Everything in quotation marks is from Google: Search Console Help's Managing owners, users, and permissions and Verify your site ownership, Business Profile Help's Request ownership of a Business Profile (none of the three carries a date) and Search Central's Do you need an SEO? (last updated 5 June 2026). All read on 12 November 2026.

Nothing is lost while you're locked out

If the designer has vanished and nobody can get in, the data hasn't gone anywhere. Google says it about the worst version of this story, a property whose verified owners have all been removed: "Data for the property will continue to be collected, but nobody will have access to it until someone verifies ownership of the property."

A designer who's still an owner but no longer answers is the milder version. They're still there; you just can't reach them. Verifying yourself doesn't need them out of the way first, because Google allows more than one: "Multiple people can verify ownership of the same website property, using the same or different verification methods."

Owners and users: what each can do

Google: "You can be an owner or user of a property. Each of these roles has different rights and capabilities." An owner "Has full control over properties in Search Console. Owners can add and remove other users, configure settings, view all data, and use all tools." A full user "Has view rights to all data and can take some actions." A restricted user "Has simple view rights on most data."

Owners come in two kinds, with the same powers but very different staying power. A verified owner is "Someone who verified ownership of the property using a token to prove ownership (such as an HTML file uploaded to the website)." A delegated owner is "Someone granted ownership status by a verified owner without the use of a verification token". Everything hangs off the first kind: "A property must have at least one verified owner, or no users will have access to the property."

The token is the key to all of it. It's something tied to one person, put somewhere only the site's owner could put it: a small file on the website, a tag in the home page's code, a record in the domain's settings at your registrar, or the site's Google Analytics or Tag Manager code. Google: "Ownership verification typically requires putting a token that is unique to a specific user in a specific location associated with a Search Console property."

Step one: verify the site yourself

Google's second line under that heading sets the order: "If you are taking over a site from another owner, after you verify ownership you can unverify previous owners by removing their verification token (for example, removing the HTML tag from the site, for HTML-tag-verified owners)." Verify first, remove second. The other way round, you could take away the only verified owner before there's a new one.

How you verify depends on what you can change. If you can edit your home page, the HTML tag method puts one line in its head, and verifying a beam site with the HTML tag walks through it. If your domain is in your own account at a registrar, the DNS method adds one record there. Google calls it "More complex, but is the only way to verify a Domain property", a Domain property being the kind that covers every version of your address at once.

If you can change neither, Search Console isn't the real problem. Find out who holds your domain and your site first: what happens if the person who built your website disappears covers that.

If the designer is still answering, they can make you an owner from their side, and Google suggests asking: "If you are unable to verify site ownership for some reason, ask a current owner to grant you access to the property in Search Console." That makes you a delegated owner, which is a good start but not the finish. A delegated owner's access depends on a verified owner's: "If all verified owners are removed, then all remaining users and delegated owners will lose access to the property after a grace period." Verify yourself as well, so your access is yours.

Step two: remove them, then remove their token

Once you're a verified owner, you can remove the designer. For a verified owner, Google's instructions end with the step that matters: "Delete all verification tokens for this user in this property. If you do not delete these tokens, the removed owner will be able to re-verify ownership if they choose to (all current owners will be notified if this happens)."

Google points to two lists, both under "Settings > Users and permissions". The first: "Click Unused ownership tokens to see any remaining tokens for that property, and the user that they are associated with." The second, "Ownership history", shows "a history of ownership events, including owners added and removed, successful and unsuccessful verification attempts, and cases where a previously known verification token has been removed." The first tells you what to take off the site. The second tells you afterwards whether anyone has tried to come back.

Where each kind of token lives, in Google's words:

  • A tag in the home page: "Look in the page source of your homepage for the user's tag". And: "Make sure that you remove only the tag associated with the user that you wish to remove."
  • A record at your registrar: "You must find and remove the DNS record associated with the user."
  • Google Analytics: "you must either switch Google Analytics accounts for this site, or else revoke edit rights given to this person in the Google Analytics account for this site."
  • Google Tag Manager: "you must either switch Google Tag Manager accounts used on this site, or remove the person's Publish or Admin permission in the associated Google Tag Manager account."
  • A file on the site: Google says to look for it "at the root location for your site", with "a long alphanumeric name".

Careful with the records at your registrar

Google's own warning, whole: "Use caution when removing tokens. The same verification token can be reused across various services to verify ownership (like Search Console, Merchant Center, Google Workspace, etc.), and removing those tokens could negatively impact other services relying on them."

That matters most at the registrar. Because the warning names Google Workspace, a google-site-verification record there might be the designer's Search Console token, or it might be part of what proves your business email's domain to Google. Remove only the one that Search Console's list of unused tokens names for the designer, match it character for character, and leave every other record where it is. It's the same rule as for the email records when you move your website off Wix, Squarespace or GoDaddy: what you don't recognise, you don't delete.

Keeping the designer, with less access

You might not want them gone. Plenty of people still want whoever built the site to keep an eye on it. The arrangement that survives them moving on is the one in the post about a designer who disappears: they have access to your accounts, rather than you depending on theirs. In Search Console that means you're the verified owner and they're a user.

One snag. Search Console only lets you change the role of someone who isn't a verified owner. Google's note on changing a user's permissions: "If this option is not active, it means that the user is a verified owner; you can remove a verified owner, but not downgrade their access level." So to turn a designer who verified the site into a full user, remove them, remove their token, then add them back as a user. Users are added by their Google account: "Enter the Google Account name (email) of the new user".

For someone auditing the site from outside, Google's page on hiring an SEO says to "only grant read access to Search Console (at this stage, don't grant them write access)." On our reading, a restricted user is the closest of the roles to that, and it's the same advice as in what to do about an email promising page one of Google.

Moving your website? Verify before the old one goes

This is when people lose Search Console without noticing. A tag in the old home page, or a file on the old host, doesn't come with the site unless someone copies it across. And Google keeps checking: "Search Console periodically checks if your verification token is still present and valid. If verification can no longer be confirmed, you will be notified. If the issue is not fixed, your permissions on that property will expire after a certain grace period."

If the designer was the only verified owner and their token leaves with the old site, everyone goes with it: "If all verified owners lose access to a property, all users will lose access to the Search Console property." So verify yourself before the move, or on the new site the day it goes live, before you cancel the old host. Google doesn't say how long the grace period is, so don't count on it. A record at your registrar is different: it stays put whichever host the site is on, until someone deletes it.

Where beam sits in this

Nothing here happens by itself. beam doesn't verify your site for you, and it has no idea who your designer was. What it changes is the effort of the jobs on the website side. On a beam site, adding your own verification tag is a request to the AI you use, which puts it in the home page's head. Taking the designer's tag out again is another request. A record at your registrar isn't part of the website, so that one stays a job at the registrar.

The AI you use can also search every file on a beam site at once, so seeing what's there before you remove anything is a single request:

Search every file on my site for google-site-verification, for Google Analytics code (gtag.js, or an ID starting G- or UA-) and for Google Tag Manager code. List each one with the file it's in and the exact line. Don't change anything yet. Then, once I've checked Search Console's list of unused ownership tokens: remove only the google-site-verification tag whose content value I give you, and leave every other tag where it is.

Then compare what it finds with Search Console's list. A tag that matches a token Google names for the designer comes out. Anything you can't match stays until you can.

See every verification tag on your site

Ask the AI you already use to list each google-site-verification tag and analytics snippet on your site, then match them against Search Console. Connect it to your beam site first.

Connect your AI

Then look at what changed while you were away

Once you're in, look around. Someone else has had the run of it. Read the list of users and owners first, because Google's advice about a name you don't know is blunt: "If you've found an owner that you don't recognize, you might have been hacked." Then the settings, including the Search generative AI control, which is on unless someone has turned it off and decides whether your site can appear in Google's AI Overviews. And once you're reading the reports again, what impressions, clicks and average position mean is the place to start.

Your Business Profile is a separate thing

If the same designer set up your Google Business Profile, the listing in Maps and Search, that's a different system with its own route. Google's Business Profile help: "If you’re a business owner but a verified Business Profile for your business on Google Search or Maps is owned by someone else, you can request ownership from the current profile owner." And: "The current profile owner is then notified by email and has three days to respond." Once it's yours, which page your Business Profile should link to is worth a look too.

Questions people ask

Can I get into Search Console without my old web designer?

Yes, if you can change your website or your domain's records. Verify the site yourself. Google: "If the only verified owner of your site leaves your team, you should verify ownership to maintain (or regain) access to the property." Once you're a verified owner you can remove them.

Will I lose my Search Console data if nobody can get in?

No. Of a property with no verified owners left, Google says: "Data for the property will continue to be collected, but nobody will have access to it until someone verifies ownership of the property."

I removed my old web designer from Search Console. Why can they still get back in?

Because their token is still on your site or your domain. Google: "When you remove an owner from a Search Console property, that owner cannot access the property any more, but their verification tokens are not deleted or revoked." Search Console lists the leftovers under "Unused ownership tokens"; remove the ones it names for them.

Is it safe to delete google-site-verification records?

Not blind. Google: "The same verification token can be reused across various services to verify ownership (like Search Console, Merchant Center, Google Workspace, etc.), and removing those tokens could negatively impact other services relying on them." Remove only the one Search Console names for the person you're removing.

There's an owner in Search Console I don't recognise. What does that mean?

Google: "If you've found an owner that you don't recognize, you might have been hacked." It goes on: "A hacker can probably add their token back after you've removed it", and suggests securing the site yourself or getting a website security professional to help.

What's the difference between a full user and a restricted user?

Google: a full user "Has view rights to all data and can take some actions." A restricted user "Has simple view rights on most data." Only owners can add or remove users.

Should I give an SEO consultant access to Search Console?

For an audit, Google's page on hiring an SEO says to "only grant read access to Search Console (at this stage, don't grant them write access)." On our reading, a restricted user is the closest of Search Console's roles to that.

My old web designer also runs my Google Business Profile. Is that the same thing?

No, it's a separate system. Google's Business Profile help: "If you’re a business owner but a verified Business Profile for your business on Google Search or Maps is owned by someone else, you can request ownership from the current profile owner."

Related reading