Inventory the property and current access
Open the property using a business-controlled Google account and record whether it is an owner or a user. Note whether the property covers the domain or only a URL prefix. A contractor sending screenshots is not equivalent to the business retaining its own access. List the domain provider and person who can manage verification records.
Source checks: Google Search Console: Verify site ownership · Google Search Console: Owners and verification tokens
Establish independent business verification first
Use the verification method appropriate to the property and platform. For a Domain property, follow the provided DNS verification instructions rather than copying an old contractor's token. Add the newly issued record exactly through the domain provider's supported interface. Confirm verification before removing anyone else's access. Record the method without placing account passwords in the handoff sheet.
Preserve the verification mechanism
DNS verification records must remain for ownership verification to continue. Do not delete them as launch clutter. If another method is used, identify the file, HTML tag, or integrated account that supports it. A theme replacement can remove a tag and a hosting migration can omit a verification file. Include the mechanism in future migration instructions.
Review former access and remaining tokens
Coordinate a narrow cleanup with the business owner.
- Confirm the business account can still open the intended property and reports.
- Change contractor access through the property permissions settings as appropriate.
- Review unused ownership tokens and their associated users.
- Remove only identified former-owner verification mechanisms that are no longer authorized.
- Keep business-owned verification intact and retest access afterward.
- Record the date, approver, and exact records changed.
Avoid broad DNS cleanup and shared identities
A DNS record may support email authentication or another service, so do not delete all TXT records. Removing an owner in Search Console does not automatically erase their verification token; an existing token can allow verification again. Conversely, a new contractor should not inherit the business owner's personal sign-in. Use individual access rather than shared passwords.
Keep the handoff verifiable
The useful outcome is the business retaining independent verified access and the intended team permissions. Save the property name, account role, verification method, and technical contact in the ownership inventory. Recheck after the next domain, hosting, or SEO-plugin change. Search performance data and owner permissions are separate checks.
For a departure involving disputed ownership or an account you cannot access, use the official provider recovery and permissions processes. Do not invent a DNS record or remove unrelated services to force access. A concise record of which account controls which verification method helps the domain administrator make a supported, targeted decision.
Illustrative replacement of a contractor's verification
An illustrative business has only user access to a Domain property while its contractor is a verified owner. The business account generates its own DNS verification record, the domain administrator adds it, and the business confirms owner status. Only then are former access and unused tokens reviewed. Email-related DNS records remain untouched.
The handoff inventory records the business account's successful verification date and which administrator maintains its DNS record. It does not copy that account's password into a shared spreadsheet or remove records merely because they contain Google in the value.
Verify the business before removing former access
Business account
Confirm property scope
New verification
Business-issued DNS token
Owner access
Verify before cleanup
Former tokens
Review only identified mechanisms
Illustrative handoff protects continuity through an independent ownership method.
Your practical checklist
- Record the exact property and business-account role.
- Identify the domain provider and authorized administrator.
- Complete independent business-owned verification first.
- Preserve the active verification mechanism.
- Review former-owner tokens separately from access removal.
- Retest access and save the approved change record.
Your next action
Check your business account's role and verification method for the property covering your active domain.
Questions about this task
Does removing a contractor delete their verification token?
No. Google documents token cleanup separately. Review the identified verification mechanism so a former authorized owner does not simply verify again through an overlooked token.
Should I delete every Google verification record?
No. Match each record to its purpose and authorized account. Preserve business verification and other active services; broad record deletion can create unrelated failures.
Sources and editorial notes
Prepared with AI-assisted research. Official sources are linked below; worked examples and checklists are Getting Found Local recommendations, not measured client outcomes.
Sources checked October 13, 2026. Platform interfaces and local resources may change; follow the current instructions on the linked official page.
- Google Search Console: Verify site ownership ↗
- Google Search Console: Owners and verification tokens ↗
How we research, illustrate, and update these guides · Suggest a correction