Your SEO agency has finished its contract, but can it still regain ownership of your Search Console property? Removing a name from a permissions list is only part of the review when verification tokens remain on the website or in supporting systems.

For a UAE business changing suppliers, the goal is continued access to search-performance evidence while retiring permissions that no longer have a business purpose. Search Console access is separate from Google Business Profile ownership and from control of your hosting account.

The illustration is a conceptual ownership handover, not an authentic Google screen or a client project.

Establish company-controlled ownership first

List the properties your team actually uses, including their scope, and identify an accountable company owner. Confirm that an authorised company account can open the correct property and perform the required administrative tasks before removing another person's access.

Keep at least one appropriate continuity route under company control. Do not share an agency's password as a substitute for assigning access to the right named accounts. Record who can administer the company identity if the usual contact is unavailable.

Identify users, owners and verification routes

Google's users and permissions documentation distinguishes ownership and user access. Review the current list and the unused ownership tokens associated with previous owners. A record of “agency removed” should state which account, role and property were checked.

Ask how each verified owner established ownership. The supporting proof might sit in DNS, an HTML file, a page tag or another supported verification route. Changing an account's role does not transfer ownership of the website infrastructure where that proof lives.

A focused SEO service review covering Search Console ownership and reporting continuity can help prepare the handover. Review Your Search Console Ownership with the website address, property scope and supplier transition date, without sending account passwords or verification secrets.

Review tokens before removing them

Google's ownership-token guidance explains why unused verification tokens matter: a removed owner may be able to regain access using proof that remains in place. Review all verification methods belonging to the departing owner rather than removing only the most obvious file.

Coordinate changes with the person responsible for DNS and site deployments. Google's permissions guidance warns that a token can support verification in more than one Google service. Identify those dependencies before deleting anything. A broad cleanup of unfamiliar DNS entries is not a safe ownership-review method.

The site-verification documentation describes supported methods and maintaining the proof needed for ongoing verification. Preserve the company's own valid verification route. Document the exact approved change and a way to check its result.

Test the handover against business tasks

  • Confirm the company owner still sees the intended property and relevant reports.
  • Check that current staff or suppliers have only the roles needed for their work.
  • Confirm the departing owner's access and associated unused tokens have been reviewed.
  • Check that a deployment or restored backup will not reintroduce retired verification files or tags.
  • Record who owns future access reviews and supplier offboarding.

Do not infer successful revocation merely because the former supplier stopped sending reports. Likewise, retaining ownership does not guarantee indexing, rankings or traffic. The page-indexing diagnosis guide covers a different operational question.

Include the rest of the supplier handover

Inventory hosting, domain, analytics and other marketing accounts separately, with named owners and verified access. Use the Business Profile agency-handover guide for local listing ownership. Avoid assuming that one Google permission screen covers all these systems.

Review Your Search Console Ownership to discuss property access, verification dependencies and the checks needed for a controlled supplier transition. Use the enquiry form below to describe the situation; it does not require access credentials.

Official Google documentation reviewed 25 October 2026. The handover checklist is proposed guidance, not a finding about your accounts or a promise of search performance.