Lorixen.
EN

Search Console Set Up by Your Old Agency: Taking Ownership

Short answer: You do not need the agency's permission to become an owner. Search Console data belongs to the property, not to whoever verified it, so if you verify the same property yourself you see the full history the moment you are in. The cleanest route is a Domain property, proven by placing Google's TXT entry in your DNS zone. Once you are a verified owner, remove the agency's verification tokens from your DNS, site files or tags, then unverify or remove their accounts in Users and permissions, and reconnect Search Console to your GA4 property.

Why this matters

When an agency set up Search Console under its own Google account, you might never have been given access, or you were added only as a restricted user. After the relationship ends, that leaves you unable to submit sitemaps, request indexing, see manual actions or receive security alerts. Worse, a former supplier still has full control over settings like removals.

Taking ownership does not reset anything. Performance data, coverage reports and history stay attached to the property itself.

Domain property or URL-prefix property?

Search Console has two property types:

Type Covers Verification
Domain property, e.g. example.com.au All subdomains and both http and https DNS record only
URL-prefix property, e.g. https://www.example.com.au/ Only that exact protocol and host HTML file, meta tag, Google Analytics, Tag Manager or DNS

Check which type the agency created. If they used a URL-prefix property, you can verify that same prefix to see its history. We also recommend adding a Domain property for yourself, because it captures everything, including the non-www version and any subdomain such as a shop or booking site.

Step 1: Verify with a DNS TXT record

  1. Sign in to Search Console with a Google account your business controls. A shared company account or your own work address is better than a staff member's personal Gmail.
  2. Choose Add property and pick Domain. Enter your domain without https or www.
  3. Google shows a TXT record that starts with google-site-verification=. Copy it.
  4. Log in to wherever your DNS is managed. That might be your registrar, such as a .com.au provider, or a service like Cloudflare if your nameservers point there.
  5. Add a new TXT record on the root of the domain (often shown as @) with the value Google gave you.
  6. Return to Search Console and press Verify. If it fails, wait a little and retry; DNS changes can take time.

Google's verification help page lists every method and common errors.

If you cannot access DNS because the agency also controls your domain, sort that first. Your domain registration should be in your business's name with an account you control.

Step 2: Verify the URL-prefix property too, if needed

If the old property is URL-prefix only and you want its separate history and settings, add the same URL-prefix property under your account. Use one of:

  • HTML file: place Google's small verification file in your site's root folder.
  • Meta tag: paste the tag into the homepage head section through your theme or SEO plugin settings.
  • GA tag or GTM container: works if your account already has edit rights on the tag that runs on the site.

Once verified, you see the same data the agency sees.

Step 3: Understand verified and delegated owners

Search Console has several roles, explained in Google's users and permissions guide:

  • Verified owner: proved ownership through a token. Has full control.
  • Delegated owner: added by a verified owner without their own token. Also has full control, but their status depends on someone else's verification.
  • Full user: can see all data and take some actions.
  • Restricted user: can see most data, but cannot change settings.

Open Settings and the people page there; it lists everyone and how each was added. Agencies often appear as verified owners with a token you need to find and remove.

Step 4: Remove the old verification tokens

A verified owner stays verified while their token exists. Removing them from the user list alone is not enough, because Search Console re-checks tokens and can restore their access. Find each token:

  1. DNS: look for TXT records starting with google-site-verification= that are not yours. Compare against the value shown in your own verification details.
  2. HTML files: check the site root for files named like google1234abcd.html.
  3. Meta tags: search the homepage source for name="google-site-verification".
  4. Tags: if they verified through GA or GTM, taking away their rights in those accounts breaks that route.

Delete only tokens that are not yours. Keep a note of your own value so you do not remove it by mistake.

Step 5: Unverify and remove old users

Back in Settings, Users and permissions:

  1. For each former agency verified owner, open the three-dot menu and choose to unverify or remove them. Search Console only lets you remove a verified owner after their token is gone.
  2. Delete any remaining delegated owners or users whose work with you has ended.
  3. Add anyone in your team who should keep access, at the lowest role that works.

Repeat for every property: Domain, each URL-prefix variant, and any subdomain properties the agency created.

Step 6: Reconnect Google Analytics and check settings

The link between GA4 and Search Console may have been made by the agency. In GA4, open Admin, then Product links, then Search Console links. If the existing link uses a property you control, keep it. If not, create a new link to your Domain or URL-prefix property.

While you are in Search Console, also check:

  • Sitemaps: resubmit your current sitemap URL.
  • Removals: confirm there are no active removal requests you did not intend.
  • Email notifications: make sure alerts reach an address the business monitors.

FAQ

Will we lose our historical data?

No. Data belongs to the property. Any newly verified owner sees the same history, up to the period Search Console normally keeps.

Do we need the agency to cooperate?

Not for verification, as long as you control your DNS or website. Cooperation helps only if they also hold your domain or hosting logins.

Why did the agency reappear after we removed them?

Their token remains somewhere in your DNS zone or site files. Remove the token first, then remove the user.

Should we use a personal Gmail account?

Better to use an account the business owns, so access does not leave with one staff member.

We regularly help owners recover accounts from former suppliers, and you can reach out to us to have every one handed back cleanly.

Sources

WhatsAppBook a call