Blog

How to Remove a Former Agency's Access to Your WordPress Site and Google Accounts

How to Remove a Former Agency's Access to Your WordPress Site and Google Accounts

Deleting your former agency’s WordPress login does not necessarily remove its access to your website or Google accounts. Hosting credentials, Google ownership verification, connected apps, and agency management tools can all provide separate ways back in.

A clean handover means putting your business in control first, then removing access without breaking your website, email, analytics, or advertising. Here is how to handle that in a sensible order.

Start with ownership, not password changes

Before removing anyone, confirm that you can sign in using accounts your business controls. Being able to view a report is not the same as being able to manage users, transfer ownership, or recover an account.

Make an access inventory covering:

  • WordPress, including any separate staging sites or multisite network.
  • Hosting, domain registration, DNS, and content delivery services.
  • Business email and the recovery email addresses attached to important accounts.
  • Google Search Console, Google Analytics, Google Tag Manager, Google Business Profile, and Google Ads.
  • Google Workspace and Google Cloud projects, if your business uses them.
  • Backup storage, remote maintenance tools, plugin licences, and connected services.

For each service, record the account or property identifier, business-controlled administrator, agency users, billing owner, and recovery method. Keep this inventory in a secure location, not a publicly shared spreadsheet containing passwords.

The safe order: establish your own access, confirm recovery options, preserve backups and settings, transfer dependencies, then remove the agency’s access.

If you cannot access the hosting account or your own WordPress dashboard, start with How to Recover Access to a WordPress Website When Your Developer Disappears. Removing accounts before resolving ownership can leave you locked out.

Agree on a handover date and preserve what you need

For an ordinary agency change, send a written handover request with a clear access-removal date. Ask for an inventory of services, custom code, scheduled tasks, licence dependencies, and integrations that use agency-owned accounts.

Take a fresh backup of the WordPress files and database, and confirm that you can retrieve it without the agency. Export relevant DNS records and save important tracking identifiers, account settings, and recent reports.

Do not cancel the old hosting or agency subscription just because the website appears in your new account. Confirm that backups, email delivery, DNS, and other dependencies have actually moved first.

If there is suspected unauthorized activity, prioritize securing business-controlled accounts and preserving logs rather than waiting for a routine handover. Do not assume an unfamiliar account proves misconduct, but document what you find before changing it.

Remove WordPress access without deleting your content

Confirm your own administrator account works

Use a named administrator account tied to an email address your business controls. Test signing in through a separate browser session before removing the former agency’s account.

Check both the administrator email in WordPress settings and the email on your user profile. They serve different purposes, and either may still point to the agency.

Review every user, not just the obvious agency account

In the WordPress user list, review administrators and other accounts with meaningful permissions. Agency access might use a developer’s name, a generic support address, or a role created by a membership or permissions plugin.

  • Remove users who no longer need access.
  • When deleting a user, reassign their posts and other supported content to an appropriate business user rather than choosing to delete that content.
  • Check plugin-specific ownership and assignments separately, since not every plugin handles user deletion the same way.
  • On WordPress multisite, review network-level super administrators as well as individual site users.

Downgrading an account is appropriate if the person still has an agreed editorial role. It is not complete offboarding, because the account can still sign in and access whatever its remaining permissions allow.

Revoke access that does not depend on a normal login

Review WordPress Application Passwords on retained accounts and revoke credentials the agency used. Check remote management plugins, hosting-based single sign-on, connected publishing tools, and external backup services too.

If an administrator account was shared, replace it with individual accounts and rotate its credentials. Have a developer invalidate relevant active sessions, and consider rotating WordPress authentication salts if broader session invalidation is needed, knowing this will log users out.

Enable two-factor authentication on retained administrator accounts. The guide How to Set Up Two-Factor Authentication for WordPress Admin Access explains the practical considerations.

Close the hosting, domain, and email routes too

Someone with hosting or file access may be able to regain WordPress access even after their WordPress user is removed. Review hosting account delegates, control-panel users, SFTP accounts, SSH keys, deployment tools, and backup destinations.

Remove obsolete access and rotate any shared credentials. If changing database credentials, coordinate the matching WordPress configuration change so the website does not lose its database connection.

Your domain registrar and DNS provider deserve the same attention. Confirm business-controlled contact details, recovery options, renewal billing, and two-factor authentication, then remove agency delegates and revoke their API tokens.

Do not delete DNS records merely because the agency added them. Those records may support business email, website routing, certificate validation, or third-party services.

Also review mailbox delegation, forwarding rules, and recovery addresses. Securing every other account does little good if password-reset emails still reach a mailbox the former agency can access.

Remove former agency access from Google Search Console

Search Console access needs special care because ownership can be verified through your website or DNS. Removing someone from a permissions list may not be enough if their verification method remains available.

  1. Confirm that a business-controlled Google account is a verified owner of the correct property.
  2. Review users and permissions for agency accounts, including owners and delegated users.
  3. Remove access that is no longer authorized.
  4. Review ownership verification methods and unused ownership tokens using Google’s current documentation.
  5. Remove agency-specific verification tokens only after identifying them and confirming your own verification will remain valid.

Verification might involve a DNS record, an HTML file, a website meta tag, or eligible Analytics or Tag Manager permissions. Check relevant Domain and URL-prefix properties, since access to one does not tell you everything about the others.

Do not remove an Analytics tag or DNS entry blindly to revoke ownership. First establish an independent business-controlled verification method and check what else depends on the existing setup.

Review Google Analytics access at both levels

In Google Analytics 4, review access management at both the account and property levels. Access inherited from the account cannot be fully removed by changing only the property’s permissions.

Confirm that your business has administrator access, then remove former agency users and any agency-controlled groups. Review linked products, reporting connections, and scheduled reports as separate handover items.

Removing a user normally does not require deleting the property or replacing the tracking code. Keeping the existing business property helps preserve reporting continuity and historical data.

If your property sits inside an agency-owned Analytics account, ask about moving it to a business-controlled account where eligible. Do not accept a new empty property as an equivalent replacement without discussing the loss of continuity and Google’s current transfer restrictions.

Check Google Tag Manager before touching tracking code

Google Tag Manager can publish changes to website tracking and other scripts. Treat publishing permission as meaningful website access, not simply permission to read marketing reports.

Review both account-level and container-level permissions. Ensure your business has the necessary administration and publishing access before removing agency users, and retain a container export as a reference.

Review live tags, custom HTML, templates, and outstanding workspace changes. Remove obsolete agency-specific tracking deliberately, but do not delete the whole container just to remove a user.

A container may support Analytics, advertising conversions, and consent controls simultaneously. If you replace it, each dependency needs testing.

Transfer Google Business Profile ownership properly

Your business should control the primary owner role for its Google Business Profile. If the agency is the primary owner, arrange the ownership transfer before removing its remaining access.

Google can apply waiting periods and restrictions to newly added owners and managers. Consult the current official documentation rather than assuming the transfer can be completed immediately.

  • Confirm that your business account has accepted its invitation.
  • Complete the primary ownership transfer where needed.
  • Review the people and access settings for former agency owners and managers.
  • Check whether access is managed through a business group or agency organization.
  • Verify your website link, booking links, business details, and any tracking phone numbers.

Do not create a duplicate profile to escape an ownership problem. Use Google’s ownership request or recovery process if the agency cannot or will not transfer access.

Unlink Google Ads management without disrupting campaigns

Google Ads may give an agency access through individual users, a linked manager account, or both. Check direct users and manager relationships rather than stopping after removing one email address.

Before unlinking a manager account, confirm that your business has administrative access and a workable billing arrangement. Agency-managed payment setups may need separate attention.

Ask whether campaigns rely on manager-owned conversion tracking, audience sharing, scripts, automated rules, or reporting integrations. Removing the management relationship can affect dependencies even when the campaigns remain in your account.

Do not delete campaigns to remove an agency. Decide separately whether advertising should continue, pause, or move to another provider, then verify billing and conversion measurement after the change.

Review Google account security and connected applications

Permissions inside Google products are only part of the picture. If anyone shared your business Google login, review its security settings, signed-in devices, recovery details, passkeys, two-step verification methods, app passwords, and third-party connections.

Change shared passwords and revoke unfamiliar or obsolete access. A password change alone should not be treated as a complete review of connected applications or delegated access.

If you use Google Workspace, check administrator roles, groups, mailbox delegation, and domain-wide delegation where applicable. Google Cloud projects may also contain agency users, service accounts, or credentials supporting Maps, reCAPTCHA, or other website integrations.

Do not disable a service account or API key without identifying its purpose. Replace credentials and update the dependent integration first when service continuity matters.

Handle licences, backups, and personal information separately

A website can be yours while some plugin subscriptions belong to the agency. Ask which licences transfer, which require your own subscription, and whether custom integrations depend on agency-owned services.

Removing a licence does not always stop a plugin immediately, but it may affect updates, support, or hosted features. Check the vendor’s current terms rather than assuming continued use will be problem-free.

Ask the former provider to confirm how it will handle retained website backups, form submissions, customer exports, and other business data. Revoking access does not erase copies already downloaded.

For Canadian businesses subject to PIPEDA or provincial privacy legislation, that retention question is part of responsible offboarding. Some records may legitimately need to be retained, so request an explanation of retention and deletion arrangements rather than demanding that every record disappear immediately.

Test the handover before calling it finished

Use a private browser window to test public-facing features, then check administrative access from your business accounts. A working homepage is not enough to confirm a successful handover.

  • Submit a contact form using test information and confirm delivery.
  • Check booking tools and, where applicable, the store’s checkout using an appropriate test method.
  • Confirm Analytics receives expected activity, allowing for consent settings and processing delays.
  • Verify Tag Manager publishing access and any essential conversion tracking.
  • Confirm Search Console ownership and Google Business Profile control.
  • Check backups, scheduled tasks, licence status, and account recovery methods.
  • Record removed users, revoked credentials, outstanding dependencies, and the completion date.

Avoid changing hosts, replacing tracking, and updating every plugin at the same time unless necessary. Smaller, documented changes make problems easier to trace.

For a reusable inventory, see the WordPress Website Handover Checklist for Agencies.

Keep future access easy to grant and easy to remove

Keep core accounts under business control and invite providers through their own named accounts. Grant only the permissions needed, and record who manages each service.

Ambrite’s WordPress maintenance plans work with any hosting provider and include updates, backups, and security monitoring. That ongoing website care is separate from ownership of your Google accounts, which should remain under your business’s control.

If you need help with the WordPress side of a handover, contact Ambrite by email with your website address and a list of the access you currently have. Do not include passwords in the initial message.

This article was written with the help of AI and reviewed by Ambrite. Pricing, features, and technical details may change, so always verify with official sources before making decisions.

Was this article useful?

Related Articles

Local SEO for Plumbers, Electricians, and HVAC
If you're a plumber, electrician, or HVAC contractor, you've probably noticed something...
Practice Area Page SEO for Law Firms
Your law firm's practice area pages are goldmines waiting to be discovered, or expensive...
Google Business Profile and Your Restaurant Website
If you're running a restaurant in 2026, you've probably claimed your Google Business Profile....
WordPress SEO for Home Service Companies
Your phone rings at 8 AM. Another customer found you through Google search, ready to book your...
SEO Basics: How to Get Found on Google
Getting found on Google isn't about gaming the system or knowing secret tricks. It's about...