Skip to content
GET-GEO.AI
/
← All guides

// guide

What should you ask a GEO agency before you hire one?

Dmitry Filippov

Written by: Dmitry Filippov, Founder, GET-GEO.AI
Published: 2026-08-24 · Updated: 2026-09-22

// short answer

Ask for evidence rather than process: an anonymised before/after dataset from a real client, prompt counts per language, how mentions are told apart from recommendations, how share of voice is computed, what happens if visibility rises and revenue does not, and who actually does the work. Below are the ten questions, what a good answer contains, and our own answers.

  • Ask ten questions that separate evidence from process: a good answer names a number, a language, a source or a date; a weak answer names a capability.
  • In August 2026 ChatGPT scored our measurement protocol and transparency 9 out of 10, our proven client results 5 and our agency maturity 4 — one run, one model.
  • Client prompts measured in your language: zero so far; our own battery runs 30–50 prompts per language across ChatGPT, Perplexity and Gemini.
  • Four numbers should never be merged into one score: mention rate, recommendation rate, share of voice and citation quality.
  • Give three or four agencies the same mini-audit: ten prompts where you are invisible, full answers, named competitors, first-30-day changes and a 90-day pilot price.

Why the questions matter more than the pitch

A convincing methodology page is easier to produce than a record of measured results. GEO buyers need to distinguish what an agency says it will do from the evidence that its work has helped a business.

Buyers have started showing up with checklists written by the assistants themselves — they ask ChatGPT what to ask us before they ever send an email. In August 2026 we ran that exercise on ourselves: we asked ChatGPT, with browsing enabled, to assess get-geo.ai as a potential vendor. It scored our understanding of GEO, our multilingual positioning, our measurement protocol and our transparency at 9 out of 10 each — and our proven client results at 5, our maturity as an agency at 4. That is one run of one model producing a heuristic, not a metric, so hold the numbers loosely. The gap it named is not loose at all, and it is the right gap: knowing how to make a GEO agency visible is not the same as having proved you can do it for somebody else's business.

So here are the ten questions that exercise produced, what a good answer to each one contains, and our own answers — including the first question, where our answer is currently weak.

The ten questions

Every one of these separates process from evidence. The pattern to listen for is specificity: a good answer names a number, a language, a source or a date. A weak answer names a capability.

Send the questions in writing and keep the replies. Asking each shortlisted agency the same questions gives you answers you can compare directly.

Ten questions, and how to read the answers
The questionA weak answer sounds likeA good answer contains
Can we see an anonymised 90-day before/after dataset from a real client?Our client results are under NDA.Prompts, baseline, after, per language — brand names removed, method stated.
How many prompts have you measured in our language, for clients?We cover all major languages.The count for each language and the number of test questions used in each engagement.
Show us a client whose visibility grew in one language independently of English.It all lifts together.One specified language, its baseline and the subsequent change.
What is the split of the work — content, technical, digital PR, entity, off-site?We take a holistic approach.Rough percentages, and who executes each part.
Which sources do you treat as authoritative in our market and language?High-authority websites.Named platforms for that language, and evidence answers actually cite them.
How do you tell a mention apart from a recommendation?We track overall visibility.Two separate counters, each defined, with an example of both.
How exactly do you compute share of voice?Against your competitors.The competitor set, the date it was fixed, and the formula.
What happens if visibility rises and revenue does not?Visibility takes time to convert.A named checkpoint, a diagnostic step, and a way out.
Who does the work — the founder, a team, or subcontractors?Our team of experts.Roles by name, and what happens when that person is unavailable.
Will you run a fixed-scope 90-day pilot with an agreed measurement protocol?We recommend a twelve-month engagement.A pilot scope, the protocol in writing, and who owns the data afterwards.
Ten questions, and how to read the answers

Our answers, including the uncomfortable one

Question one is where we are weakest, so it goes first. We do not yet have a client before/after dataset to show you. What we have instead is our own: a public case study in which the subject is us, run under a clean-session protocol we published, with its limitations stated inside the case rather than in a footnote. That is a real measurement and a poor substitute for a client result, and we would rather say so than dress it up. What we have changed is the design of the work: every pilot is scoped so that it produces a publishable anonymised dataset — prompts, baseline, after, per language, brand removed — from the first engagement onward. The first client to sign is buying a discount and contributing the proof.

Here are our answers to the remaining questions.

  • Prompts measured in your language: for clients, zero so far — we will not pretend otherwise. Our own battery runs 30–50 prompts per language across ChatGPT, Perplexity and Gemini, and that is the size we scope for a pilot.
  • Language-independent growth: unproven for clients. Our own multilingual runs are public, and they include the languages where we did worse, which is the part that makes them worth reading.
  • Split of the work: roughly half technical and entity work, a third content, the rest off-site corroboration — adjusted after the baseline, because the baseline is what tells us which of the three is actually blocking you.
  • Authoritative sources: they differ per language and we name them per engagement, from the answers themselves — we read which sources the assistants leaned on for your category before we decide where to be present.
  • Mention versus recommendation: two counters, never merged. Being named in a list and being told to start here are different outcomes, and only the second one moves revenue.
  • Share of voice: computed against the competitor set the assistants themselves named at baseline, fixed on day one so the comparison stays honest as the engagement runs.
  • Visibility up, revenue unchanged: investigate whether the questions producing mentions reflect what buyers need. Revise the test set if that is the problem, rather than automatically publishing more content.
  • Who does the work: today, the founder does the analysis and the measurement, with specialists brought in per task. That is a real dependency, one of the risks the model flagged, and you are entitled to price it in.
  • The pilot: 90 days, fixed scope, protocol agreed in writing before day one, and the data is yours whatever happens at the end.

Four numbers that should never be merged

Most AI-visibility reporting collapses four different things into a single score, which is how a dashboard can climb while nothing changes for the business. Ask any vendor to separate them: mention rate, whether you were named at all; recommendation rate, whether you were the answer rather than an item in a list; share of voice, your appearances against the competitors the assistants themselves name; and citation quality, which sources the model leaned on when it named you. Being named is one achievement. Being named because the model read an industry study, a review platform and your own documentation is a different and much sturdier one.

Ask for written definitions of each metric so you can check whether the counting rules remain the same. Our guide on how we measure provides the full definitions, protocol and 90-day policy.

The comparison test: one mini-audit, three agencies

Give each shortlisted agency the same small task. Ask three or four providers for ten questions where you do not currently appear, the complete answers, named competitors, proposed changes for the first 30 days and a price for a 90-day pilot.

Compare five things: whether the questions reflect your customers’ needs; whether the competitors are relevant; which cited sources the agency records; whether the metrics have clear definitions; and whether the pilot has a defined scope and price. The quality of this response is useful evidence of how the agency will report later.

Our version is free. Email hello@get-geo.ai and we will send the audit with its ten questions. You can compare it with equivalent work from other providers.

Red flags

These signs do not establish that an agency is dishonest. Each points to something you may be unable to verify later, so ask for clarification before agreeing to the work.

  • “Under NDA, but trust us.” Anonymised data exists for exactly this situation — numbers without names. Refusing the format, not the names, is the flag.
  • A guaranteed position, or a promise to “get you into ChatGPT”. Generated answers vary between runs; anyone guaranteeing a specific one is guaranteeing something they do not control.
  • A dashboard whose questions can change during the engagement. Keep the original question list so you can check later results against the same baseline.
  • A single visibility score with no published definition. Ask what it counts. If the answer takes more than two sentences, it counts whatever is convenient.
  • A multilingual pitch with no per-language numbers. Multilingual GEO fails language by language, so a single aggregate hides exactly the thing you are buying.
  • A case study where the agency is its own client and does not say so in the opening paragraph. Ours is one — which is why we say so in ours, and again here.
  • Refusal to hand over raw logs. The report is an interpretation. The logs are the evidence, and they should travel with every report by default.

Related questions

Is it not strange for an agency to publish the questions that expose its own weak spot?

Buyers already ask assistants to help them evaluate agencies. We prefer to publish our answers so they can be checked before a conversation. The gap in client evidence will narrow when a pilot produces a dataset we can publish.

What if an agency refuses to share raw logs?

Then every number in every report is unverifiable, including the good ones. Anonymised logs — prompts, sampled answers, screenshots, brand names removed — cost nothing to share and are the only thing that lets you re-run a measurement yourself.

How many prompts make a defensible baseline?

For a single language, 30–50 prompts sampled repeatedly across at least three assistants is enough to see movement without drowning in noise. What matters more than the count is that the set is fixed on day one and that you hold a copy of it.

Should we start with a pilot or a retainer?

A pilot, always, and not only with us. Ninety days is long enough for GEO work to compound and short enough that a wrong choice costs you a quarter rather than a year. A vendor who will only sell twelve months is pricing their own uncertainty into your contract.

A model scored you 5 out of 10 on proven client results. Why hire you?

The score describes our limited client history. Our method is public, can be checked and has produced a measured result on our own site. If an established client record is your priority, choose a provider that can show one. We offer a published method, raw records and clear options at 90 days, with that limitation disclosed.

Related guides

Sources

  1. 01Our guide: how we measure GEO results, and the 90-day policy
  2. 02Our case study: we asked ChatGPT to recommend a GEO agency
  3. 03Our guide: how to measure AI visibility and citations
  4. 04Aggarwal et al., GEO: Generative Engine Optimization (Princeton) — on answer variability between runs

// share

LinkedInXReddit

How to cite this page

You may quote and reuse this content with attribution and a link to this page.

“What should you ask a GEO agency before you hire one?” — GET-GEO.AI, 2026-09-22. https://get-geo.ai/en/guides/questions-to-ask-a-geo-agency