An AI visibility agency needs access to the specific evidence and actions in its agreed scope. Reviewing public answers and pages can start with public information. Investigating private traffic or indexing evidence may require a report or a limited account role. Publishing a change needs separate authority for the site or profile that will receive it.
For each request, ask what the agency must do, which property is involved, what result you will receive and when the access will end. If an internal owner can perform a one-off action and return the result, include that handoff in the plan. Give repeated tasks an access route that the business can review and remove.
AI Visibility is published by Lunasol, which offers GEO and AEO services. The access examples below are illustrative. Tool roles were checked against public documentation on 5 November 2026. Lunasol service overview
Start with the evidence the task requires
An initial review can use the pages, listings and other materials a prospective customer could see. An agency can also ask the business for a current public URL list or an approved service description to guide that work. For example, 009 Agency’s public audit offer describes using the business’s website and priority geographies and collecting the rest from public sources. That is one provider’s published audit scope. A private traffic analysis or deployment would call for different inputs. 009 Agency audit offer
Write down the point where public evidence stops answering the question. A reviewer can see which address appears on a public listing. The reviewer would need information from the business to establish which address should be used and who can approve a change. A public page can show what is displayed today. An indexing report can show a different state and needs its own source.
Before granting a role, ask whether a narrow export or a screen share with the account owner would let the agency complete the task. A dated set of pages, queries and report totals may be enough for a one-off comparison. An ongoing investigation that repeatedly changes date ranges or filters may be easier with an appropriate named account. Record that reason so the business can review it later.
Ask which Search Console action the agency needs
Google’s hiring guidance recommends read access to Search Console at the SEO audit stage. Its permissions documentation distinguishes Owner, Full user and Restricted user. Full users can take some actions, while the restricted role can view reports and has fetch-only access for URL Inspection according to the permissions table. Specify which report or inspection operation the agency needs and check the current table before granting it. Google’s hiring guidance and Search Console permissions
For example, a team might want to compare query and page trends for one site, inspect a group of URLs and decide whether to investigate further. Ask the site owner whether a restricted role supports the planned checks. If a later action requires a capability beyond that role, the owner can perform it or arrange separately approved access for the person doing it. The scope should identify the handoff so a missing capability does not stall the review.
Check the property as well as the role. The agency may only need the property that covers the relevant site. Google documents that ownership of a containing property can convey implicit ownership of a child property. If the permissions screen shows more access than you expected, inspect the containing property before treating a new invitation as the explanation. Search Console permissions and inherited ownership
Match Analytics access to the report
Start with the question being asked. A team assessing how people arrive at a particular set of pages may only need the appropriate report dimensions, event counts and date range. If the internal analyst can provide a repeatable export with the filters documented, the agency can work from that file. If the agency will examine the property regularly, choose the role that fits the work.
Google Analytics documents that Viewer can see data and settings and create its own explorations. Analyst adds sharing capabilities for explorations. Marketer can change events and key events, among other settings. Reviewing a count and changing the way a count is recorded are distinct tasks. If changes to events are part of the engagement, specify who proposes them, who approves them and who checks them after release. Google Analytics access and data restrictions
Check effective permissions before signing off the grant. A lower role on a property does not override a higher role inherited from the account. Google also offers No Cost Metrics and No Revenue Metrics data restrictions. Use them where they fit the task and verify how they affect the report. For example, Google says reports can display restricted metric values as zero. A report reviewer should know when a displayed zero reflects a restriction. Google Analytics effective permissions and report behaviour
Keep private lead data on its own line. A business might answer a question about accepted enquiries with a count by period and service. If the agency needs an authorised sample to investigate a tracking issue, specify the fields it needs, who prepares the file and where it can be used. Agree how retained exports will be handled after the task ends.
Separate public location checks from profile editing
A business with several locations can ask an agency to compare public branch details with an approved list. For example, Books Kinokuniya UAE’s official Instagram announcement of a signing at its Dubai Mall store supplies a public venue reference. A reviewer can inspect that dated announcement as part of checking public information. Updating a Google Business Profile for a location is a separate action requiring the business’s approval and the appropriate account role. Books Kinokuniya UAE’s official 5 November 2026 announcement
Google documents that a Business Profile manager can edit profile information, manage posts and respond to reviews. The role also covers other functions such as editing URLs. Use it when the approved task involves profile management and check that the business retains its ownership. Google’s third-party policy requires the customer to retain ownership or co-ownership and addresses removing management permissions when the relationship ends. Business Profile roles and Business Profile third-party policies
If the task is a single approved hours correction, the internal location owner could publish it and send a dated confirmation. If ongoing location management is in scope, name the profiles, the actions the agency will perform and the reviewer who approves changes. The role describes what the tool permits. The work agreement describes which of those actions the agency is authorised to take.
Give the website team a separate release decision
An agency can draft an update with no website account. A reviewer can often check a staged page using an approved preview route. Publishing the update or changing a shared template is a separate step. Identify the exact environment and who can deploy changes to it.
A public case from 009 Agency describes delivering technical specifications while the client’s developers deployed changes to their own site. A similar model can work when the buyer has a release team and a scheduled slot. Confirm who checks the implementation after it goes live, and where the agency can see the result. 009 Agency’s public INC4 case
If the agency will publish directly, match its access to the work agreed for the site. Define whether it can edit selected content, deploy a change to a shared template or alter wider settings. Use the role names available in the actual platform. If the site cannot express the boundary you need, use an internal release owner or another approved workflow for the affected task.
Keep an access register the business can review
The following is a worked example for a fictional business commissioning a two-branch review. The particular role depends on what each account permits and what the agreed task requires.
| Task | First access route to consider | Evidence or action to close |
|---|---|---|
| Compare public branch facts | Public pages and a dated approved branch list | A record of discrepancies for the location owner |
| Review Search Console performance | Selected export or restricted property access if recurring inspection requires it | Findings with the source property, period and filters |
| Review Analytics traffic and key event totals | Agreed export or property Viewer with appropriate restrictions | Review with known coverage and visible metric definitions |
| Correct one public profile detail | Internal owner publishes the approved change | Dated check of the public profile |
| Deploy two page edits | Client website team releases approved changes | Live URLs and verification evidence |
For each granted row, record the named account, exact resource, approved role, authoriser and review date. Confirm who is responsible for removal. When a role is expected to expire but the platform lacks automatic expiry, assign the removal to someone on the buyer’s team and include it in their closeout tasks.
The register also makes it easier to handle scope changes. If a report review uncovers a configuration issue, add a new row for changing it, with its own approval and verification. Record whether the internal team will do the work or whether the agency needs a different role. A task can move from observation to implementation without turning the original invitation into a general grant.
A completed register entry might say that the agency analyst will review four weeks of traffic to two approved pages. The internal analyst will supply a dated export showing the page filter, session source and the chosen event totals. The agency will return a brief that names any gaps in the data and the filters it used. At the review date the business can decide whether that export answered the question or whether a named property role is needed for further investigation.
Add the identity of the person who will actually use a role before sending the invitation. If work moves to another agency team member, check the old invitation and the new task together. A team handoff can leave two people with access when the buyer expected one. The buyer should review the current account list against the register whenever responsibility changes.
Close both the accounts and the information handover
At the end of the work, ask the agency to return the agreed evidence, reports and change history to a destination the business controls. Then review the current access list for each system. Check both the direct grant and any inherited or group permissions that could still apply. If a Search Console ownership method was used, use Google’s instructions to verify what remains before changing a verification token. Other services or owners may depend on it. Search Console ownership verification and removal
Finish by checking that the people who will maintain the work can open the files, find the approved facts and use the accounts they own. Confirm how any retained data will be handled under the agreed terms. If another round of work begins later, review the tasks and access again against the new scope.
The existing agency-choice guide helps decide who should own the work. Use the access register to turn that decision into specific account actions and evidence. GEO in house or with an agency



