SEO Agency Access and Permissions: What to Grant, What to Withhold, and What to Own
Give a new SEO agency the lowest access level that still lets them do the job, and make sure every account stays registered to your company, never theirs. For most ecommerce and SaaS teams that means a Full user role in Search Console, an Analyst or Editor role in GA4, and a staff account with limited permissions in the CMS. The rest of this post explains why, because the access you hand over in week one decides how much leverage you have in month twelve. At OnyxRank, we ask for read access first and request write access only against a specific task, and you can apply the same rule to any agency you hire.
Why access is a buying decision, not an admin task
Most founders treat access as paperwork that happens after the contract is signed. It is actually the point where ownership of your search data gets decided. If the agency verifies your site in Search Console under their own Google account, creates the GA4 property on their own login, or registers your Google Business Profile with their email, you do not own the history. Leaving the agency then means starting your data over.
There is also a risk side. An agency account with broad CMS rights can publish, edit templates, or change redirects. That is useful when it is deliberate and reviewed. It is damaging when a junior contractor pushes a bulk change on a Friday and nobody on your team knows it happened.
Treat access the way you treat a financial control: least privilege, named individuals, and a record of who can do what. If you are still comparing providers, our [guide to comparing SEO agency proposals](/blog/how-to-compare-seo-agency-proposals-scorecard-2026) covers what to score before you reach this stage, and [what happens to your data when you leave an agency](/blog/seo-agency-offboarding-data-ownership-2026) covers the other end of the relationship.
Google Search Console: the roles that matter
Search Console is where the agency sees your queries, indexing status, and manual actions. Google documents the permission model in its [Search Console help page on owners, users, and permissions](https://support.google.com/webmasters/answer/7687615). The key distinctions:
- **Verified owner:** someone who proved ownership with a token, such as an uploaded HTML file or a tag. Google notes that if a verified owner loses their verification, no one else may have access to the property.
- **Delegated owner:** granted ownership by a verified owner without a token.
- **Full user:** can view all data and take some actions.
- **Restricted user:** can view most data but cannot take actions.
What to grant
Your company should hold the verified ownership, ideally with at least two named people from your side so one departure does not lock you out. Give the agency Full user access. That covers reporting, URL inspection, and sitemap work for nearly every engagement. Restricted user is enough for a reporting only relationship, such as an advisor reviewing monthly numbers.
What to withhold
Do not give an agency owner status unless there is a specific reason, because owners can add and remove other users, including you. If an agency insists on being the verified owner, treat that as a red flag. Ownership also controls sensitive actions like removal requests and settings changes, which should not sit with a vendor by default.
Domain properties verified through DNS are the sturdiest setup, because verification survives template changes and does not depend on a file or tag that a developer might delete during a redesign.
Google Analytics 4: Analyst first, Editor if needed
GA4 uses a role system documented in Google's [Analytics Help page on access and data restriction management](https://support.google.com/analytics/answer/9305587). Roles are assigned at the account level or the property level, and the main ones are Administrator, Editor, Marketer, Analyst, and Viewer.
For an SEO engagement, Analyst is usually the right starting point. It lets the agency build reports and explorations and pull the organic data they need without changing your configuration. Move to Editor only when the agency is responsible for tracking work, such as setting up conversion events for organic landing pages, and downgrade it when that project ends.
Keep Administrator on your side. Administrators can add and remove users and change data retention settings, which is control you should not delegate casually. Also ask who created each property and data stream. If the agency created it under their own login, request a transfer to a company owned account before any real history accumulates.
A practical check: open the access management screen yourself in week one and confirm that every user listed is a named person you recognize. Shared logins like a generic "seo@agency" address make audits impossible.
CMS and hosting: where the real risk sits
Search Console and GA4 are read mostly. Your CMS is where an agency can break things. How much access to give depends on what the agency is actually contracted to do.
Shopify and other ecommerce platforms
Shopify lets you create staff accounts with specific permissions, described in its [staff permissions documentation](https://help.shopify.com/en/manual/your-account/users/roles/permissions). Use that. Grant only the areas the work needs, such as products, collections, and online store content for an agency that edits titles and descriptions, and leave out areas like payments, customer data, and account settings. An agency optimizing collection pages does not need to see customer records.
If an agency needs theme or template changes, consider requiring a development theme or staging copy, with changes reviewed before publishing. Our post on [ecommerce category page SEO](/blog/ecommerce-category-page-seo-collection-pages-rank-2026) shows the kind of template level changes that justify this.
SaaS and custom stacks
For a headless or custom site, agencies rarely need production access at all. A better arrangement is that the agency writes tickets with exact specifications, and your engineers ship them. If you want the agency to commit content directly, give them access to a content repository or a CMS role limited to the blog and docs sections, with publishing behind an approval step.
Hosting, DNS, and registrar
Do not give an agency access to your registrar, DNS provider, or hosting account in a normal engagement. These control whether your site exists. When a migration or redirect project requires DNS changes, have your team make them while the agency watches, or grant temporary scoped access with a defined end date.
A least privilege checklist you can paste into your onboarding
Use this list in your kickoff call. Each item is something you can verify, not a promise.
1. **Ownership stays with you.** Search Console, GA4, Tag Manager, and Google Business Profile are all registered to company controlled accounts.
2. **Named users only.** Every agency login belongs to one identifiable person, with no shared accounts.
3. **Lowest role first.** Full user in Search Console, Analyst in GA4, a limited staff role in the CMS.
4. **Time boxed elevations.** Any higher permission is tied to a task and a date, then removed.
5. **Two factor authentication.** Ask that every agency user with access to your systems has it enabled on their Google account.
6. **A change log.** The agency records what they changed on your site, when, and why, in a shared document or ticket system.
7. **A quarterly access review.** Someone on your side exports the user lists and removes people who have left the engagement.
The contract clause that backs it up
Access settings can be changed in a minute, so the contract needs to say what the settings imply. Look for language covering these points:
- All accounts, properties, and data created for the engagement are owned by you.
- The agency returns or deletes any credentials on termination, within a stated number of days.
- The agency discloses any contractors or subcontractors who will touch your systems.
- Content the agency publishes on your site is yours, including drafts and source files.
The last point matters more now that search engines scrutinize low quality output. Google's [spam policies](https://developers.google.com/search/docs/essentials/spam-policies) describe scaled content abuse as many pages generated primarily to manipulate rankings, regardless of whether a person or automation produced them. If an agency has publishing rights on your site, you want a review gate, because you carry the consequences of what they publish. Our write up on [what to ask about AI SEO agency staffing](/blog/ai-seo-agency-staffing-whos-working-on-your-account-2026) pairs well with this, since it covers who is actually behind the logins.
What good agencies say when you ask
Reasonable agencies do not push back on any of this. Expect answers like "we only need Full user and Analyst to start" and "send us the staging link and we will attach the change list." Be cautious if you hear:
- "We need to be the owner so we can set it up properly."
- "It is easier if you just share your login."
- "We will handle the DNS and hosting for you."
- "Our team uses one shared account for all clients."
None of these is automatically fatal, but each one means you should slow down and ask why the standard setup will not work. A vendor who cannot explain their access needs in terms of specific tasks usually has not planned the work.
FAQ
What access does an SEO agency need on day one?
A Full user role in Search Console, an Analyst role in GA4, and read access to your CMS or a staging environment. Request write access later, tied to a specific deliverable.
Should an SEO agency be the owner of my Search Console property?
No. Your company should hold verified ownership so the data history stays with you if you switch providers. Google lets owners add and remove other users, so ownership is real control.
Is it safe to share my CMS login with an SEO agency?
Sharing a login is the weakest option, because you cannot tell who did what. Create a named staff account with limited permissions instead, which platforms like Shopify support directly.
How do I take access back when I leave an agency?
Open the user management screen in Search Console, GA4, Tag Manager, and your CMS, and remove every agency user. Then confirm that no property, container, or profile is registered under an agency owned account.
Key takeaways
- Access decides who owns your search history. Register every property to your company before the agency starts.
- Start with Full user in Search Console, Analyst in GA4, and a limited CMS role, and raise permissions only for defined tasks.
- Keep registrar, DNS, and hosting out of a normal engagement.
- Put ownership, credential return, and subcontractor disclosure in the contract.
- Review user lists every quarter, and remove anyone who no longer needs access.
If you want a second opinion on your current setup, request our [free SEO audit](/free-audit) and we will flag ownership and access gaps alongside the technical findings. You can also see how our engagements are structured on the [pricing page](/pricing).
Pro Intel subscribers get the full picture - proprietary analysis, keyword opportunities, tactical playbooks, and template downloads every week. $49/mo.
One email per week. Actionable, no fluff.