Visibility in the answers ChatGPT, Gemini and Google write

Organic SEO competes for a position in a list of results. GEO, also called AEO, is about what happens when there is no list but a single written answer - in Google AI Overviews, in ChatGPT or in Gemini. There is no first or second place there; there is a source that was cited and a source that was not. A good deal of the technical groundwork is shared: a fast site, a clear structure and correct schema help both. The difference is emphasis - an engine composing an answer is looking for a discrete fact with a source behind it, not a page tuned to a keyword.

You cannot control the answer, and anyone claiming otherwise is overstating it. You can influence what the engine finds about you, and that part is genuinely in your hands: how clearly you are identified, whether your business details match everywhere, whether a page answers the question directly, and whether external sources corroborate what you claim. An engine composing an answer avoids a source it is not confident in. The practical leverage is therefore on the engine confidence in you rather than on its phrasing - and that is exactly where the difference between being named and being left out sits.

We build a fixed bank of real questions from your field and run it every month against the same engines. For each question we record whether you were mentioned, in what context, which competitors appeared alongside you, and whether you were linked. This is comparative rather than absolute measurement, because the same question can produce different phrasing on different runs - which is why the bank has to stay fixed and the run has to repeat. Alongside it we track what is measurable with certainty: traffic, enquiries, and what Google actually reports in Search Console.

No, and it is worth being wary of anyone selling it as a replacement. Most searches still end in a click on a result, and the AI engines themselves lean on the same underlying signals: a fast site, a sound structure, content someone is willing to quote, and genuine authority. GEO is not a separate channel but a layer on top of organic work that is already sound. For a business whose base is shaky - a slow site, thin content, business details that contradict each other - the right move is to repair the base rather than buy an additional service that assumes the base exists.

The technical part moves relatively quickly: fixing the entity, the schema and inconsistent business details is picked up within weeks, and sometimes that alone is enough for an engine to stop confusing you with a similarly named company. The content part is slower, because an engine quotes a source it already trusts, and trust is not built in a month. We measure from the first month so there is a baseline to compare against, but we read the trend across several months rather than a single run - a single run can differ without anything having changed.

It happens, and more often than people expect - particularly for businesses whose name resembles another company, or whose details appear in different forms in different places. An engine fills gaps with what seems plausible, so an inconsistent detail easily becomes a confidently worded error. The remedy is not a request for correction but the removal of ambiguity: unify the name and details across every asset, link the profiles to each other explicitly, and publish a clear page that settles the facts. The more consistent the sources, the less room the engine has to invent.

The work splits in two, and so does the pricing. There is a one-off opening stage - the baseline check, the entity and schema work, and rewriting the commercial pages - and then ongoing monthly work covering measurement, content and extension. The scope follows the number of commercial pages and the state of the base, which is why we do not publish a single figure for this service. The baseline check tells you where you stand today before you commit to anything ongoing, and if your organic foundations are still missing we will tell you to start there rather than here.