Before the Keys Change Hands: Mapping Search Console Ownership in a UK Agency Switch

Most UK businesses treat the end of an agency retainer as a commercial matter: notice periods are served, final invoices are settled, and a new supplier is appointed. What is often overlooked is that the outgoing agency may still hold the keys to assets the business will rely on for years. Search Console is rarely the only one, but it is the most consequential, because it holds the record of how Google has actually treated the site.

This article sets out a practical audit for the weeks either side of a change of supplier, or for firms bringing search work in-house. It is written for the person who has been handed the task of "sorting out the accounts" and has discovered that nobody is entirely sure who set them up.

Ownership Is Not the Same as Access

Google Search Console distinguishes between verified owners and users. A verified owner has confirmed control of the property through a DNS record, an HTML file on the server, a Google Analytics or Tag Manager association, or a Google Sites link. A user simply has been granted a permission level, from full to restricted.

The distinction matters at handover because a property can have several owners and an unlimited number of users. If the outgoing agency is an owner and the client is not, the client is a tenant in their own account. Removing the agency's access is straightforward; removing an owner who is the only verified owner is not, and in some configurations cannot be done without re-verification first.

Before any permissions are touched, confirm that the business holds at least one owner-level verification method that it controls independently of the agency. For most UK firms this means a DNS TXT record administered by whoever manages the domain, or a verification file placed on the server by the in-house developer.

Build an Asset Register Before You Build a To-Do List

A single spreadsheet, circulated to both parties and dated, is the most effective instrument in this process. List every property and account that could influence search performance, and record for each one: the property identifier, the verification method, the current owners, the current users and their permission levels, and who holds the billing relationship where money is involved.

The register should cover, at minimum:

• Search Console, including domain properties and any legacy URL-prefix properties
• Google Analytics 4, plus any retained Universal Analytics read-only access
• Google Tag Manager containers
• Google Ads accounts and their linked Search Console associations
• Bing Webmaster Tools
• Google Business Profile, particularly where multiple locations are managed
• Google Merchant Center, for retail and property firms running product listings
• Any third-party rank tracker, crawler or reporting platform holding an API connection

Firms with a franchised or multi-site estate should expect the register to be longer than they anticipate. A local SEO supplier may hold permissions on a dozen Business Profile locations that nobody in head office has ever logged into.

The Verification Layer Is the Real Prize

Permissions can be reissued in minutes. Verification is slower to rebuild, and rebuilding it is the step most often skipped.

Work through each verification method in turn and establish whether it will survive the agency's departure. A DNS TXT record is only useful if the business controls the DNS zone; if the agency manages DNS on the client's behalf, that arrangement needs to be unwound before the record is relied upon. An HTML verification file will persist on the server only until the next deployment, and a site migration or CMS rebuild will remove it silently.

Where a property is verified solely through a Google Analytics or Tag Manager association that the agency controls, the client's ownership is contingent on an account they do not administer. Add an independent method now, while both parties are still on speaking terms.

API Links and the Invisible Plumbing

Search Console data rarely stays inside Search Console. It is pulled into Looker Studio dashboards, bulk export tools, keyword platforms and internal reporting warehouses via OAuth grants and, increasingly, service accounts.

These connections are invisible in the user interface, which is precisely why they are missed. A departing agency's service account can continue to read performance data long after the retainer has ended, and a client-side dashboard can break the moment a grant is revoked.

Ask the outgoing supplier for a written list of every API integration, OAuth client and service account with access to the properties. Reconcile it against the register. Then decide, item by item, whether the connection should be transferred, rebuilt under client ownership, or retired.

The Order of Operations Matters

Closing access in the wrong sequence is how firms lose data. A workable order is:

1. Confirm client owner-level verification on every property, using a method the business controls.
2. Export a full historical data set from Search Console, Analytics and any reporting platform, and store it somewhere the business administers.
3. Transfer or rebuild dashboards under the client's own accounts.
4. Run both sets of access in parallel for a defined period, typically one full reporting cycle, so that the incoming team can ask questions while the outgoing team is still available.
5. Remove agency users and owners, and revoke API grants, in a single documented session.
6. Recheck the property list and permission screens a fortnight later to catch anything that was re-added by an automated process.

Step two is the one that clients regret skipping. Search Console retains a limited window of detailed data; once a property is deleted or a user loses access, some of that history becomes difficult or impossible to reconstruct. Treat the export as a deliverable of the handover, not an afterthought.

Put It in the Contract, Not Just the Spreadsheet

Procurement teams are used to specifying deliverables and notice periods. Access should be specified in the same way. A well-drafted agreement will state that all properties are created under client-owned accounts, that the client is named as a verified owner from day one, that a data export is provided at termination, and that access is removed within an agreed number of working days.

Where a supplier resists client ownership of Search Console, that is itself a useful signal during selection. There is no technical reason for an agency to hold sole ownership of a client's property, and the firms that insist on it are creating a dependency that will cost the client time at the least convenient moment.

A Final Check Before the New Team Starts

Once the handover is complete, ask the incoming agency or in-house lead to produce their own short confirmation: which properties they can see, which verification methods are live, which analytics and advertising accounts are linked, and whether any expected data is missing. A discrepancy at this stage is far cheaper to resolve than a discrepancy discovered three months into a new retainer, when the explanation has to be reconstructed from memory.

The account is an asset. Treat the handover as a transfer of property, with an inventory, a signature and a date, and the change of agency becomes a straightforward commercial event rather than an archaeological one.