AI search, SEO & online discovery
Practical coverage from Dubai

Saved
Guides

What to Ask an Agency Before Buying a GEO Audit

Summarize with AI
Business paperwork being reviewed; illustrative photograph.
Photo by Pavel Danilyuk / PexelsIllustrative photography
In this article 8 sections

Before signing, ask the agency to walk your team through one sample finding. Start with the observation, follow it to the underlying evidence and have the person who would implement the recommendation explain how they would verify it. Then ask what happens if your audit arrives with a broken evidence link, an unfinished check or a finding your team cannot reproduce.

This is a practical test of whether you can accept and use the work you are buying. It applies to a paid diagnostic and to a complimentary audit that could lead to a separate implementation proposal. The existing AI Visibility guide covers what the audit should contain. Use this guide when a proposal is on the table and you need to decide what would count as delivery. What an AI search audit should include

AI Visibility is published by Lunasol, which offers related services and advertises a free manual AI visibility audit. Apply the same acceptance checks to its offer. The examples below draw on public agency material and a fictional buyer rehearsal. Lunasol GEO service

Ask for a finding you can follow in both directions

Start with a recommendation in the sample. Ask which observation led to it and where you can inspect that observation. Then start from the evidence and see whether your team reaches the same conclusion. The agency should be able to explain the reasoning when more than one interpretation is plausible.

A sample may include a page address, the public fact recorded there, a dated observation and a recommendation for the person who owns that fact. A summary slide might say a service area is unclear. The supporting record should show which page or answer caused the concern and what the reviewer would need to confirm with the business.

Ask who produced the sample and what you may keep. A public case can show how a provider describes completed work. A demonstration can show how it would structure a file. A permitted excerpt from an actual audit can show the level of detail it delivered. Give each sample the weight its provenance supports. If confidentiality limits sharing, agree on a synthetic example with the same fields and level of detail.

Have your editor or developer perform part of the walkthrough. If the recommendation says to correct a service area, can they find the approved coverage, identify the page and tell which change they would check? The sales presenter may understand the proposal perfectly while the person responsible for acting on it still lacks essential information.

Read public examples for the delivery boundary

009 Agency links to a public INC4 case from its audit offer and says the published examples had client approval. The case separates dated measurements from work it reports shipping and says INC4’s developers deployed site changes from agency specifications. Some prompts and internal items are marked as undisclosed. These details let a buyer ask which equivalent records would be delivered privately and who would make the changes. The case documents the agency’s account of its work. Its reported results belong to that engagement. 009 Agency audit offer and INC4 public case

NotHuman publishes an example GEO proposal with separate rows for an initial diagnosis and recurring deliverables, and includes a column describing evidence of delivery. When comparing a one-off audit with an ongoing programme, use that distinction to identify what the initial fee includes. Ask the agency to specify which items you would receive at handover and which would begin only under a later engagement. NotHuman public proposal example

Read an agency’s public example as evidence about the format it shows. If the sales team offers to provide a comparable deliverable, ask it to describe that deliverable in your proposal. Your comparison should rest on what each agency commits to provide for your scope, including how the materials can be reviewed and retained.

Rehearse a disputed finding before kickoff

Imagine a Dubai office maintenance company commissioning an audit for one service. During a sample walkthrough, the agency presents a hypothetical finding that a customer answer describes the service as covering an area outside the company’s current remit. The buyer wants to know whether there is an error to correct and which evidence should drive the work.

Ask the agency to show the observation and the approved coverage source. If the public site and internal service owner disagree, put the source conflict in the finding and assign somebody to resolve it. If the only evidence is one generated answer, label it as an observation. It can justify further investigation while the source of the wording remains uncertain.

Then rehearse acceptance. The buyer should be able to open the saved record, locate the coverage statement and see who will confirm it. If the observation has no evidence reference, send it back for completion. If the observation is documented but the agency cannot determine where the assistant got the claim, the report can still be usable with that uncertainty clearly recorded.

This scenario is fictional. Its purpose is to agree how the agency and buyer will handle a finding they read differently. A delivery standard that only works when everyone agrees on the first call will leave important decisions unresolved when the report arrives.

Agree how to handle partial coverage

Ask the agency how it records a check that could not be completed. A platform might show a sign-in screen, a site tool might require access, or an approved branch list might arrive after the agreed review date. Each circumstance has a different remedy. Record the missing item, why it matters, who can resolve it and whether it affects the remaining work.

A replacement test can be valid if both sides agree it answers the original buyer question. If the agency proposed a consumer experience and used an API instead, ask how the scope describes that change and what the resulting observation supports. Google’s October 2026 model announcement names different product and subscription contexts in one caption. It is a concrete example of why a model name alone is too broad for a test record. The announcement supplies product context. Test conditions should come from the agency’s own record. Google’s official 13 October announcement

Decide how the agency will report those exceptions before collection. A practical handover lists each agreed check with a status such as completed, inaccessible or awaiting input. Agree whether the agency will retry it, deliver with an explicit gap or seek approval for a change of scope. That gives the buyer something concrete to accept even when access conditions change.

Match each permission to an audit task

Ask what the agency will do with every requested account permission, which property it needs, who will use the access and when the work requiring it ends. For example, someone checking Search Console may need to read information for the relevant website. A person deploying changes would need a different authorisation tied to implementation.

Google’s hiring guidance recommends read access to Search Console at the SEO audit stage and advises checking third-party recommendations against official documentation before major changes. Its AI features guide explains that Google Search’s usual SEO foundations remain relevant to AI Overviews and AI Mode. If a proposal calls for a special configuration, ask which documented behaviour it addresses and what the agency will inspect to verify the recommendation. Google’s guidance on hiring an SEO and AI features and your website

Agree what the agency can deliver from public evidence if some account access arrives late. A public page review and an account-based finding can coexist in one audit if their evidence is identified. A missing input should appear beside the affected conclusion so the business knows which decision still needs work.

Agree what will pass the handover

Delivery question What the buyer can inspect What to resolve if it is missing
Can we verify a finding? A dated observation, evidence reference and explanation of the recommendation Supply the reference or label the conclusion as unverified
Can we see what was covered? A scope record matching agreed services, markets and surfaces to check status Retry, approve a scope change or record the gap
Can our team act on the work? An action with a destination, owner, dependency and verification step Assign ownership and settle the blocking decision
Can we reopen the evidence later? Files the receiving team can open and trace from summary to underlying record Agree export format and permitted reuse before accepting
Can we close the review? A named reviewer, due date and a record of corrections Agree who decides and how outstanding points are closed

Use the acceptance table with a real sample. Have someone on your side open the proposed file format and locate a finding without the agency driving the screen. If the output relies on a dashboard, ask for a demonstration of the export you will receive. Check which fields carry across and whether the links will still open after the engagement.

Ask the agency to distinguish a correction to the agreed audit from a request for extra work. A missing reference for an in-scope finding is different from adding another market after the audit begins. Agree who will review the first delivery, how long the team has to raise issues and how the agency will respond. Put the agreed process in the proposal or accompanying scope so the review can use it.

Compare proposals against the same buyer decision

Suppose one fictional bidder offers a broader prompt panel and a presentation. Another offers fewer observations, a walkthrough and an export that links each finding to evidence. The right choice depends on the decision. A team choosing what to correct this month may need a narrower, more actionable diagnostic. A team comparing several markets may need wider coverage plus a usable record.

Give both providers the same example task. Ask how they would establish whether an incorrect service-area answer warrants a site update, what they would hand over, and which work would be priced separately. Compare the response with what your people can maintain. If your developer is only available next month, the immediate value might be a well-specified brief that can wait for the right person.

An agency can commit to a dated delivery and a documented method. A future platform answer belongs in the observation plan. Keep those items in separate proposal rows so the reviewer can assess the work even if a repeated answer changes or the platform cannot be accessed that day.

Write the acceptance decision before you sign

For the fictional maintenance audit, the buyer’s note might say that the agency will deliver the agreed service and market checks, a dated evidence file and a short handover with the service owner. Every incomplete check will have a reason and next action. The buyer will verify a sample of findings against their references, record disagreements and confirm which items can be taken forward. Implementation and any subsequent measurement have their own scope and owner.

Before signing, ask your reviewer to explain what they would accept, return for correction or defer pending evidence. Ask the agency to do the same with the sample. If the two accounts differ, turn that disagreement into a specific change in the proposal. The walkthrough is finished when both sides can identify the evidence and the person who will make the handover decision.

Research checked 5 November 2026. Public agency offers and examples can change. The rehearsal and competing bids are editorial illustrations.

You’ve reached the end of this article. Read as plain text

Search the blog

Summarize with AI

Choose your assistant. Copy the article and summary request, then paste it into a new chat.

The full article is included, so your assistant can read it without opening this website. Nothing is submitted automatically.

View or copy the summary requestOpen assistant

Summaries are generated by your chosen service and may miss details. Its account requirements and terms apply.