The Practical Guide To AI Search Visibility

The Mistake That Undoes Everything Markup is a claim, not evidence. Structured data asserting that you own a profile only helps when that profile exists and points back at you. Markup naming an author only helps when the author can be found elsewhere.

One caveat worth writing on the report: any figure produced by a third party visibility tool is a sample from that tool's own prompt set and infrastructure, not a census. Attribute it to the tool by name whenever you quote it, and never present it as a count of what happened. geo seo agency

Treat markup as something with a maintenance cost rather than a one off implementation. Prices change, people leave, products are discontinued, and structured data quietly keeps asserting the old version long after the visible page has been updated. Adding a schema review to whatever process already updates your pages costs minutes and prevents the most damaging failure mode, which is confidently stating something that is no longer true.

Then add the structural markup, then check the whole thing with a reader in mind rather than a crawler. If a page has become harder for a person to use, something has gone wrong and the change should be reversed.

Audit for contradiction before adding anything new. Run your key pages through a validator, then read the output against what the page actually says and against your main directory listings. Contradictions are more damaging than gaps, because they actively undermine confidence in the record.

Ask ChatGPT, Perplexity or Gemini to recommend a supplier in your category and you will get a short list. Three names, maybe five. Your customers are already asking those questions, and the answer they receive does not come from a page of ten blue links they can scroll past. It comes as a recommendation, delivered with confidence, and most people act on it without checking a second source.

Assertions with nothing behind them are weaker than silence, because they introduce a detail that fails verification. The pattern that works is reciprocal: your site names the profile, the profile links to your site, and some independent source associates the two without either of you being involved.

Test it rather than assuming. Load your key pages with JavaScript disabled and see what survives. If the product specifications, pricing, service areas and contact details vanish, that is what a machine reads.

The fix is not abandoning modern frameworks. Server side rendering or static generation produces the same interface with meaningful content in the initial response, and it is faster for humans too, which is the usual pattern in this area.

Record the conditions alongside the results: which assistant, which model version if visible, whether web access was on, the date and the run number. When a result changes sharply, the conditions log is usually what tells you whether the world changed or your setup did.

What We Genuinely Do Not Know Several things are worth admitting rather than papering over. We do not know how the systems weight their signals against each other. We do not know how much residual influence training data has once retrieval is involved. We cannot reliably distinguish a change in your visibility from a change in the model's behaviour.

Visibility in this channel is not a number you can look up. There is no console that reports how often an assistant named your company last month, and the tools that claim to supply one are sampling rather than counting. That does not make measurement impossible. It makes it manual, and manual is fine as long as you are honest about what you are measuring.

Fix the Access Problems You Find While the baseline runs, check the mechanical side in parallel. Confirm your robots.txt permits the crawlers that feed assistants. Look at server logs for those agents and see what status codes they receive, since a bot management product returning challenges will make you invisible without anyone noticing.

Corroboration Beats Assertion The single clearest pattern in observed behaviour is that independent agreement outweighs self description. A claim made only on your own site is treated as a claim. The same claim appearing on a review platform, in a trade publication and in a forum thread is treated as a fact about the world.

Control the Session Conditions Personalisation quietly corrupts this. Run from a signed out session, or a fresh session with memory and history disabled, and do not use an account that has been researching your own company all week.

So attribute it by name every time it appears in a report. A visibility figure presented without saying which tool produced it and how it was sampled will eventually be quoted back at you as fact by somebody who did not know it was an estimate, and that is a difficult correction to make in front of a board. geo seo agency

Tracking this is genuinely awkward, and pretending otherwise is how most reporting in this field goes wrong. There is no console. Answers vary between runs. Referral attribution is inconsistent between assistants. Anyone handing you a single confident number has hidden a great deal of variance behind it.