Hiring an agency

How to Give an SEO Agency Access to Your Website Safely

What access an SEO agency really needs to your website, Search Console, Analytics and Tag Manager, and how to grant it without handing over the keys.

FindSEO8 min read

A hotel key board with rows of numbered hooks and white numbered tags. A few hooks still hold brass room keys, while most keys are out with guests.

Photo: Jonathan Haeber / Wikimedia Commons (CC BY 2.0)

In this article
  1. Why does agency access matter so much?
  2. What access does an agency need for an audit?
  3. What access does an agency need for ongoing work?
  4. How should you handle website, hosting and DNS logins?
  5. How do you keep access safe while you work together?
  6. What should you do when the work ends?
  7. A safe agency access checklist
  8. The bottom line

Give an SEO agency the lowest level of access that lets it do the job, through named logins for each person, and keep the top role in every account for your own business. For an audit, that usually means view-only access: Google's advice on hiring an SEO says to grant only read access to Search Console at the audit stage, not write access. Raise access only when there's a specific task that needs it, switch on multifactor authentication, take a backup before anyone changes your site, and remove access properly when the work ends. Google also reminds site owners that they're responsible for the actions of any company they hire.

This guide covers what to give an agency in each common account, how to handle website, hosting and DNS logins, and what to do when the relationship ends.

Why does agency access matter so much?

Because whoever holds the top role in an account controls it. In Google Search Console, owners can add and remove users and change settings. In WordPress, an Administrator can install plugins and edit code. If an agency holds those roles and you don't, you depend on its goodwill to get your own data back, and a single compromised agency login can reach your whole site.

Security agencies frame the fix the same way. NIST defines least privilege as restricting each user's access "to the minimum necessary to accomplish assigned tasks." For an SEO engagement, that means three things:

  1. Your business owns every account. The agency is a user, not the owner.
  2. Each person gets their own login. No shared passwords, so you can see who did what and remove one person without locking everyone out.
  3. Access matches the task. An audit needs less than a site migration, and a migration needs more only while it's happening.

Agreeing this upfront is easier than untangling it later. Our guide to what an SEO contract should include covers putting account ownership in writing, and our SEO contract template includes a clause for it.

Dozens of room keys on brightly coloured plastic fobs hang from hooks on a grey board, each paired with its own paper label.
One key per person, clearly labelled, is the model to copy for agency logins. Photo: Dinkum, CC0, via Wikimedia Commons.

What access does an agency need for an audit?

Less than most people give. An SEO audit is mostly reading: crawling public pages and reviewing Search Console and analytics data. Google says that if an SEO offers an audit, you should "only grant read access to Search Console (at this stage, don't grant them write access)."

In practice, a pre-contract or one-off audit usually needs:

  1. Search Console: Restricted user. Google's permissions guide describes Restricted users as having simple view rights on most data.
  2. Google Analytics 4: Viewer or Analyst. In the GA4 access roles, Viewers can see settings and data, and Analysts can also create and share explorations.
  3. Google Tag Manager: Read. Tag Manager's user permissions let Read users browse tags, triggers and variables without making changes.
  4. Google Ads, if relevant: Read-only. Under Google Ads access levels, Read-only users can view campaigns and run reports but can't edit campaigns.
  5. Your website: usually nothing. A crawler sees what Google sees, and a staging copy is safer than a live login if they need to check templates.

If an agency wants owner access just to quote, ask why. Our guide to what a technical SEO audit includes shows how much can be done from the outside.

What access does an agency need for ongoing work?

Once hired, an agency usually needs to make changes as well as look. Match its access to the work in your brief and keep the top role yourself:

  1. Search Console: Full user. Full users can view all data and take actions such as submitting sitemaps and validating fixes. Keep the verified Owner role with your own business, using a verification method you control. Our guide to setting up Google Search Console walks through verification.
  2. Google Analytics 4: Marketer or Editor. Google says Marketers can create audiences, events and key events, and Editors have full control of property settings. Only Administrators can manage users, so keep that role in-house.
  3. Google Tag Manager: Edit, with your staff publishing. Google's Edit level allows changes in workspaces but not publishing. It also recommends at least two account administrators and that the account is "managed by someone in your organization, not an external agency." Our guide to setting up Google Tag Manager covers the account structure.
  4. Google Ads: Standard. Standard users can edit campaigns, but only Admins can grant access or unlink manager accounts.
Conceptual table of what access to give an SEO agency in each account. Search Console: Restricted user for an audit, Full user for ongoing work, and keep the verified Owner role. Google Analytics 4: Viewer or Analyst for an audit, Marketer or Editor for ongoing work, keep Administrator. Google Tag Manager: Read for an audit, Edit with your staff approving and publishing, and keep account Admin with two of your people. Google Ads: Read-only, then Standard, keep Admin. Website CMS, hosting and DNS: usually none for an audit, then a named login with the lowest role that does the job, such as Editor, with Administrator, SFTP or DNS access only for a specific task. Sources: Google Search Central, Search Console, Analytics, Tag Manager and Google Ads Help, and WordPress.org.
Start low and keep the top role in every account. Conceptual, not data.

The same rule applies to your Business Profile and any other platform: the agency can be a manager or user, but your business should be the owner. Our guide to switching SEO agencies explains how to check and fix ownership in each Google account.

How should you handle website, hosting and DNS logins?

These carry the most risk, because they can change or break the live site. WordPress's roles and capabilities page describes an Administrator as having access to all administration features of a site, while an Editor can publish and manage posts and pages, including other users' content. Installing or activating plugins and changing site options are Administrator capabilities.

So match the role to the job:

  1. Content and on-page changes: an Editor account is usually enough for editing titles, copy and internal links.
  2. Plugin settings, redirects or schema plugins: these often need Administrator rights. Grant them to a named person for the task, then lower the role again.
  3. Shopify stores: use staff roles, which bundle only the permissions a job needs. Shopify's predefined Merchandiser role, for example, covers products, catalogues and content rather than everything.
  4. Hosting, SFTP and DNS: only for specific technical work such as a migration, and only through the agency's own login if your host supports it.

WordPress's hardening guide explains why this matters: someone who gets into an administrator account can install malicious scripts that may compromise the whole server. The same guide recommends two-step authentication, SFTP rather than plain FTP, and turning off the dashboard's built-in file editor, which attackers often use once they're logged in.

A technician in a red checked shirt crouches on a raised data-centre floor, working on a laptop connected to an open rack of servers and cables.
Server and DNS access can take a site offline, so it should be granted for a task, not by default. Photo: Derrick Coetzee, CC0, via Wikimedia Commons.

Before anyone with write access touches the site, take a full backup of files and database. WordPress's backup guide says a proper backup of both lets you restore things quickly if something goes wrong. For bigger changes such as a redesign or domain move, follow a plan like our guide to migrating a website without losing SEO.

Safer way Riskier way
A named login for each agency staff member One shared "agency" login or your own password
The lowest role that does the job Administrator or Owner by default
Multifactor authentication on every login Password only
Admin, SFTP or DNS access for a set task, then removed Permanent server and DNS access
A backup before changes and a written change log Changes nobody can trace or undo

How do you keep access safe while you work together?

Treat access as something you manage, not something you set once. CISA's guidance on requiring multifactor authentication says strong passwords are no longer enough on their own, recommends starting with admin accounts, and ranks security keys and authenticator apps above text or email codes. Google accounts support this through 2-Step Verification, so ask agency staff to switch it on for the Google accounts they use with you.

Then keep a simple routine:

  1. Keep a register of who has access to what, at what level and why.
  2. Ask for a change log. Google says that if an SEO has FTP access to your server, they should be willing to explain all the changes they make.
  3. Review every quarter. Remove people who've left the agency and access no current task needs.
  4. Link reporting to the work. Your monthly SEO report should show what changed and why, which is easier to check when changes are logged.
Conceptual six-step access lifecycle for working with an SEO agency: list the tasks, because no task means no access; back up the site and confirm your business holds the top role in every account; invite named people at the lowest role, with no shared passwords and multifactor authentication on; raise access only for a specific job agreed in writing with a change log, then lower it; review access every quarter; and offboard completely by removing users, deleting Search Console verification tokens, revoking keys and app passwords and changing any shared credential. Sources: Google Search Central, Search Console Help, CISA, NIST and WordPress.org.
Every agency login should have a reason, an owner and an end date.

Our Academy lesson on working with your agency covers the rest of a healthy working relationship.

What should you do when the work ends?

Remove access the same week, and do it thoroughly. Removing a user isn't always enough. Search Console's permissions guide says a removed verified owner can re-verify while their verification token remains, such as an HTML file, meta tag or DNS record, so delete those tokens too. Also:

  1. Remove the agency from every account on your register, not just the ones you use daily.
  2. Revoke API keys, application passwords and plugin licences tied to agency accounts.
  3. Change any credential that was ever shared, including hosting, SFTP and DNS passwords.
  4. Collect the handover of reports, change logs and assets you paid for.

If you're moving to a new agency, add the new team before you remove the old one, as our agency switching guide explains.

A safe agency access checklist

  • Your business is the owner or administrator of every account.
  • Each agency person has a named login. No shared passwords.
  • Audit access is view-only.
  • Ongoing access matches the tasks in your brief.
  • Two of your own people hold Tag Manager account Admin.
  • Multifactor authentication is on for every login.
  • Administrator, SFTP and DNS access is granted only for a set task.
  • A full backup exists before any site changes.
  • The agency keeps a change log you can read.
  • Access is reviewed every quarter and fully removed at the end, including Search Console tokens.

The bottom line

A good SEO agency doesn't need the keys to everything. It needs the right access for the job in front of it, through its own named logins, with your business keeping ownership. Start with view-only access for an audit, raise it for specific tasks, protect every login with multifactor authentication and remove access cleanly when the work ends. Ask about access in your first conversation, along with our other questions to ask an SEO agency and the red flags in SEO proposals. Before you sign, estimate the payoff with the SEO ROI calculator and compare how strong competing pages are with the page authority checker. When you're ready, compare technical SEO agencies, browse technical SEO specialists in Melbourne or SEO agencies across Australia, or get matched with an agency that fits your brief.

FAQs

Should I give my SEO agency admin access to my website?

Only when a specific task needs it, such as changing plugin settings or setting up redirects, and only through a named login for the person doing the work. For content and on-page changes, a WordPress Editor account is usually enough. Lower the role again when the task is done.

What Search Console access does an SEO agency need?

For an audit, Restricted user, which gives view rights on most data. Google advises granting only read access at the audit stage. For ongoing work, Full user is usually enough. Keep the verified Owner role with your own business.

Is it OK to share my password with an SEO agency?

It's better not to. Invite each agency staff member with their own login at the lowest role that does the job, and ask them to use multifactor authentication. Named logins let you see who made changes and remove one person without changing your own password.

Who should own my Google Tag Manager account?

Your business. Google recommends at least two account administrators and says the account should be managed by someone in your organisation, not an external agency. Give the agency Edit access to the container and have your staff approve and publish changes.

How do I remove an SEO agency's access when we stop working together?

Remove every agency user from each account, delete any Search Console verification tokens they added, revoke API keys and application passwords, and change any credentials that were shared. Do it the same week the work ends.

Sources

Ready for help with SEO?

Compare SEO-only agencies near you, with client reviews checked by a person, or tell us what you need and get matched.