Skip to content
SEO Evaluate
TREN (current language)ARFA

AI Search Visibility (GEO) · Service

AI Visibility Audit

A fixed-scope diagnostic of how ChatGPT, Google AI Overviews, Perplexity, Gemini, Copilot and Claude describe your brand today, and why.

An AI visibility audit shows what generative answer engines say when your buyers ask about your category, your brand and your competitors, and explains each gap. SEO Evaluate builds a prompt set from real buyer questions, samples it repeatedly in ChatGPT search, Google AI Overviews and AI Mode, Perplexity, Gemini, Copilot and Claude, logs every answer, then traces absences and errors to a cause layer: crawler access, rendering, indexation, entity clarity, passage citability or third-party sources. You receive the raw log, a scorecard per platform and a prioritised roadmap.

How we work

Prompt setBuyer questions by stage, type and language
SampleRepeated runs, dated and logged per platform
DiagnoseEvery gap traced to a cause layer
RoadmapFixes ordered by impact and effort

/01 · Definition

What is an AI visibility audit?

An AI visibility audit is a fixed-scope diagnostic that records how AI answer engines such as ChatGPT search, Google AI Overviews, Perplexity, Gemini, Copilot and Claude respond to the questions your buyers ask: whether they mention your brand, which sources they cite, how accurately they describe you, and why. It produces a documented prompt set, a dated answer log, a scorecard per platform, a cause diagnosis for every gap and a prioritised roadmap. It is the entry point to generative engine optimisation work, not an ongoing service.

For background on generative engine optimisation itself, see our explainer on what GEO is. This page covers one engagement: a snapshot, taken with a method you can repeat, that turns "we never show up in ChatGPT" into specific causes and an order of fixes.

The scope is fixed before the first run: prompt set, sampling window and platforms. That boundary makes a later re-run under the same conditions comparable.

/03 · Problems we solve

What the audit is designed to explain

  • You rank in Google but are absent from AI answers

    Rankings look healthy, yet category prompts in ChatGPT or Perplexity never name you.

  • You are mentioned, but wrongly

    An assistant gives an old address, a discontinued product or a competitor's feature. Being described wrongly needs a different fix from being absent.

  • Results differ by platform or language

    You appear in Gemini but not in Copilot, or in English but not in Turkish. Without a structured sample, nobody can tell a pattern from noise.

  • Competitors own the comparison prompts

    When buyers ask for alternatives, the same rivals and review sites appear, and you do not know why.

Designing the prompt set

The prompt set is the instrument. It starts from questions buyers actually ask: sales call notes, support tickets, site search terms, Search Console queries phrased as questions and enquiry-form wording. Each prompt is classified by funnel stage, from problem awareness through comparison to the decision.

Five prompt types cover the space. Brand prompts ask about you by name and test accuracy. Category prompts ask who provides a service without naming anyone. Comparison prompts ask for alternatives or weigh two options. Problem prompts describe a need without naming a solution. Market prompts add a city, country or audience.

Language is a dimension of the set, not a translation step. Turkish and English prompts are written for each market's phrasing; Arabic and Persian can be added for brands serving those audiences, produced natively with reviewer approval. You sign off the final set, so the audit measures the questions you care about, not the easy ones.

Sampling method: making non-deterministic answers comparable

AI answers change between runs, so one screenshot proves little. Every prompt is run several times, on different days within an agreed window, and each run is logged with its date, platform, mode and any visible model label. A finding counts as a pattern only when it recurs across runs; one-off answers stay in the log, flagged as variance.

Runs use clean sessions: logged out where the platform allows it, otherwise a fresh account with memory and personalisation off, no prior conversation, and location and interface language set to the target market. These conditions are written into the protocol, because a future re-run is only comparable if it follows the same rules. Where a tool such as Ahrefs Brand Radar covers the same prompts, it serves as a cross-check, not the reference.

/06 · Tools and platforms

Platforms covered and what we check on each

  • ChatGPT search

    OpenAI documents OAI-SearchBot for search, ChatGPT-User for user-requested fetches and GPTBot for training, each controlled separately in robots.txt. All three are checked alongside the answers.

  • Google AI Overviews and AI Mode

    Google Search Central states these features draw on the standard index and snippet eligibility, and that Google-Extended does not affect inclusion in Search. Indexation is checked first.

  • Perplexity

    Perplexity documents PerplexityBot for indexing and Perplexity-User for user-initiated fetches. Its visible source list makes the cited-source map especially detailed.

  • Gemini

    Tested separately from AI Overviews, because answers and cited sources can differ between the two.

  • Microsoft Copilot

    Copilot's web answers draw on Bing, so coverage in Bing Webmaster Tools is confirmed before an absence is read as a content problem.

  • Claude

    Anthropic documents ClaudeBot for training, Claude-User for user-requested fetches and Claude-SearchBot for search. Answers are sampled with web search enabled.

What is recorded for every answer

Each answer is coded on the same fields. Presence: not mentioned, mentioned, or mentioned wrongly, with the wrong statement quoted. Position: named first, listed, or mentioned in passing. Citation: whether one of your pages is linked as a source. Competitors: every other brand named in the same answer. Sources: every cited domain and URL, which builds the source map.

Accuracy is checked against a fact sheet you approve at the start: services, locations, product names and founding facts. Tone records whether the framing is neutral, favourable or carries a caveat, such as an old complaint repeated from a forum. The distinction matters: an absent brand needs retrievable content, while a misdescribed brand needs its facts corrected at the sources the engine trusts.

Cause layers: why a brand is absent or described wrongly

Every gap is traced to the lowest layer that explains it, because content work is wasted if a crawler cannot reach the page. Access comes first: robots.txt rules per user agent, plus WAF and bot-protection settings that can block search crawlers even when robots.txt allows them. Rendering is next: if key text appears only after client-side JavaScript, some fetchers see an empty page. Then indexation: a page missing from Google or Bing cannot be retrieved by features built on those indexes.

The upper layers concern meaning. Entity clarity asks whether your name, category, locations and offer are stated consistently across your site, Organization markup, sameAs profiles and directories. Passage citability asks whether the page that should answer a prompt contains a self-contained passage that does so. Third-party coverage asks whether the domains the engines cite for your category mention you at all.

/09 · Comparison

Decision table: symptom, likely cause layer, first check

From symptom to the check that confirms or rules out a cause.
Symptom in the answer logLikely cause layerFirst check
Absent on one platform only, present elsewhereCrawler access for that platformrobots.txt rule and WAF logs for that platform's search user agent
Absent everywhere, including brand-name promptsIndexation or renderingIndex coverage in Search Console and Bing Webmaster Tools; rendered HTML of key pages
Brand prompts correct, category prompts absentPassage citabilityDoes the target page answer the category question in a self-contained passage?
Mentioned with outdated or wrong factsEntity clarityCompare the fact sheet with site copy, Organization markup, sameAs profiles and directories
Competitors named, cited sources are review or list sitesThird-party source coverageIs your brand present on the domains in the source map?
Present in English, absent in TurkishLanguage-specific content or entity gapsIs there a native-language page and a consistent local entity record?
Results swing between runs with no patternVariance, not a causeExtend the sample before acting; do not fix noise

/10 · Deliverables

What you receive at the end of the audit

Everything arrives as working files you keep, so the audit can be re-run without us.

  1. 01Prompt set with funnel stage, type, language and market for every prompt
  2. 02Sampling protocol with dates, session conditions and repeat runs
  3. 03Raw answer log with verbatim answers and cited URLs
  4. 04Scorecard per platform, language and prompt type
  5. 05Source map of cited domains by platform and prompt type
  6. 06Accuracy register of wrong or outdated statements and their likely origin
  7. 07Cause diagnosis linking each gap to a cause layer
  8. 08Prioritised roadmap with effort, owner and responsible service
  9. 09Readout session on findings and decisions

/11 · Method and process

How the audit runs, step by step

  1. 01

    Scope and fact sheet

    We agree markets, languages, platforms, competitors and the sampling window, and you approve a fact sheet of brand truths: what you offer, where, for whom and under which names. It is the yardstick for accuracy coding.

  2. 02

    Prompt set design and sign-off

    Buyer questions are collected from sales, support and search data, classified by funnel stage and type, and written natively per language. You add or remove prompts before sign-off; after that the set is frozen for the audit.

  3. 03

    Sampling runs

    Each prompt is run repeatedly across the agreed platforms on different days, in clean sessions with locale fixed to the market. Every answer is saved verbatim with date, platform and cited sources.

  4. 04

    Coding and scorecard

    Answers are coded for presence, position, citation, competitor co-mentions, accuracy and tone. The coded log produces the scorecard and the source map, with patterns separated from one-off variance.

  5. 05

    Cause diagnosis

    Each recurring gap is tested against the cause layers in order, from access to third-party sources. Technical checks use Search Console, Bing Webmaster Tools, rendered HTML and, where available, server or WAF logs.

  6. 06

    Roadmap and readout

    Fixes are ordered by expected impact and effort and assigned to an owner and a service. The readout walks through the evidence, agrees priorities and hands over the files, including the re-run protocol.

/12 · Measurement and KPIs

Measures in the scorecard and how each is taken

Each measure is defined by the sampling protocol and reported per platform and language; the audit sets a baseline and promises no level.

  • Presence

    Mention rate

    Protocol runs in which the brand is named, by prompt type.

  • Citation

    Citation rate

    Runs in which one of your URLs is a cited source, with the page recorded.

  • Accuracy

    Accuracy

    Statements about you coded correct, outdated or wrong against the fact sheet.

  • Context

    Competitor co-mention

    Rivals named alongside or instead of you, per prompt type.

  • Sources

    Source overlap

    Cited domains in your category that already mention you.

/13 · Common challenges

Challenges in auditing AI answers

  • Non-deterministic answers

    The same prompt can produce different answers minutes apart. Repeated runs and pattern thresholds reduce the noise; they cannot remove it, and the report says so.

  • Personalisation and location

    Account history, memory and location shape answers. Clean sessions approximate a new buyer, but no lab setup reproduces every real user.

  • Model and product updates

    Platforms change models and retrieval without notice. Each run's date and visible model label are logged, so later shifts can be read against the timeline.

  • Undocumented source selection

    Vendors document crawlers and eligibility, not why one source is cited over another. The diagnosis rests on documented requirements and observed patterns.

/15 · Frequently asked questions

AI visibility audit: frequently asked questions

What does an AI visibility audit measure?

It measures whether AI answer engines name your brand for the questions buyers ask, whether they cite your pages, how accurately they describe you, which competitors appear with you and which sources they rely on. Each is recorded per platform, language and prompt type from a dated sample, giving a baseline you can compare later rather than a single score.

If answers change every time, can the results be trusted?

Single answers cannot, which is why the audit never relies on them. Every prompt is run repeatedly on different days in controlled sessions, and only findings that recur across runs count as patterns. The report states the sampling conditions and flags variance.

Which platforms are included?

The standard scope covers ChatGPT search, Google AI Overviews and AI Mode, Perplexity, Gemini, Microsoft Copilot and Claude, and can be narrowed to the platforms your buyers use. Each is reported separately, because access rules, underlying indexes and cited sources differ between them.

What happens if an assistant describes us wrongly?

The wrong statement is quoted in the accuracy register, compared with your fact sheet and traced to its likely origin: outdated site copy, conflicting markup, an old directory listing or a third-party article. The roadmap lists where the fact must be corrected. Nobody can edit a model's answer directly, so the fix works on the sources.

What do you need from us to start?

Your markets, languages and main competitors; Search Console and, ideally, Bing Webmaster Tools access; sight of robots.txt and CDN or WAF settings; and sales or support material showing how buyers phrase questions. We also ask you to approve a short fact sheet about the brand.

Can you promise we will be cited after the fixes?

No. No one controls whether a model cites a given source, and answers vary between runs. The audit gives you a documented baseline, a cause for each gap and a defined order of fixes. A re-run under the same protocol then shows what changed, measured the same way as before.

How is the audit different from ongoing AI visibility monitoring?

The audit is a bounded diagnostic with a frozen prompt set, a fixed sampling window and a cause diagnosis. Monitoring re-runs a panel on a schedule to track movement over time. A common sequence is the audit first, then monitoring within the wider AI search visibility programme, with the audit's prompt set as the starting panel.

From the blog

Latest articles on this service

Official PartnerMeta · Google Partner · TikTok Marketing Partner
  • Meta
  • Google
  • TikTok

Related cases

Next step

Request an AI visibility assessment

Tell us where you are today; we will scope the work, set priorities and outline the first 90 days together. No commitment, a written assessment.