AI visibility audit: what it measures and how to run one

Record how AI search tools describe your business, check their sources and turn findings into a scoped plan. A practical audit method with separate measures for citations, visits and enquiries.

Short answer

An AI visibility audit records what selected search assistants say about your business for a defined set of buyer questions. It checks mentions, factual accuracy and cited sources. Keep the evidence and test conditions with every result. This is a sample of answers, not a ranking across the entire market, proof of traffic or a count of qualified leads.

What the audit can measure

Start with the decision the audit should support: correcting an inaccurate company description, assessing a priority service or deciding which existing page needs work. Define the market and language before selecting prompts.

Keep four observations separate: whether the business is mentioned, whether its description is accurate, whether a source links to its website and whether the answer presents it as one possible choice. A mention without a link differs from a citation. Neither proves that a reader clicked or contacted you.

OpenAI's documentation for ChatGPT web search describes search responses with links to sources and the use of search partners. Record the actual product and search mode you tested rather than assuming every chat uses the same retrieval process.

Choose questions tied to a buying decision

Take questions from real sales and support conversations, removing personal or confidential information. Cover the offer, the problem it solves, comparisons, implementation constraints and the countries you serve. Keep branded questions separate from questions that do not name your company.

For example, a hypothetical business buying an internal workflow tool might ask how to compare existing software with a custom build. A question about the definition of artificial intelligence serves a different purpose. Do not count them as equally qualified simply because both include AI.

Use a manageable panel your team can repeat. There is no universal number of prompts that makes a sample representative. List its coverage and omissions so a later reader can understand the limits.

Capture the same information for every observation

  • Question: exact wording and whether it names your brand.
  • Test context: engine or product, date, language, test country and any explicit location in the prompt.
  • Response: the answer, its citations and the relevant excerpt, with confidential information excluded.
  • Verdict: mention, citation, factual error or absence in this response, with a written rule for each.
  • Repetition: distinguish repeated tests from a unique buyer question and preserve unsuccessful or unavailable tests too.

Record whether search was used and any account or product conditions that affect comparability, without copying credentials. If a product cannot be accessed under the planned conditions, mark that test unavailable rather than replacing it silently.

Interpret the sample without turning it into a market claim

If your company is absent, report that it was absent from the observed response. Do not conclude that no buyer can discover it. If a description is wrong, identify the exact statement and compare it with an authorised business source.

When reporting a proportion, show its denominator and counting rule: unique questions, answers or test runs are different units. A second run can differ. Preserve the individual observations so another reviewer can reproduce the calculation and inspect exceptions.

Compare results only when markets, question panels and test conditions are documented. A study of another audience cannot establish your company’s visibility.

Check sources and technical eligibility separately

Open the cited pages and check whether they support the answer. A correct business fact on your own site, an outdated directory entry and a competitor comparison are different types of evidence. Do not infer that buying a directory listing will cause the assistant to recommend you.

For Google, the official AI features guidance explains relevant Search eligibility, including indexing and snippet eligibility, and says no special schema or AI-specific file is required. Meeting requirements does not guarantee inclusion. Keep that Google-specific rule distinct from other platforms.

Perplexity's description of its search crawlers distinguishes search crawling from foundation-model training. An observed citation does not establish that your site is stored in a model's training data.

For the technical part of the audit, use our website readability checklist to separate access and indexing checks from observed citations.

Compare audit scopes before comparing prices

A proposal should name the markets, languages, engines, question panel, repetitions, deliverables and review process. Specify whether it includes technical inspection, factual corrections, content work or only observations. Ask who receives the underlying evidence and how confidential data is handled.

Separate the first project conversation from a detailed diagnosis. For LYVIA, the 30-minute conversation establishes business needs and fit. The audit, implementation and ongoing review are then scoped in a proposal. No universal price or guaranteed recovery period is assumed here.

Turn findings into a page-level plan

Connect each finding to a proposed action and a check: correct a false statement on a controlled page, clarify an offer, fix a broken internal link or investigate an indexing issue. Record which changes you control and which external corrections depend on another publisher.

Use the content strategy method to group questions into useful pages rather than creating one page per prompt. The SEO and AI search visibility service explains how diagnosis, implementation and monitoring can be scoped.

Maintain separate records for search data from Google and Bing, measurable website visits and enquiries received by the business. A citation does not prove a visit; a contact-button click does not prove a received request. Apply the agreed qualification criteria to real enquiries before describing them as leads.

Frequently asked questions

What is an AI visibility audit?

It is a documented sample of how selected AI search tools describe a business and which sources they cite for agreed buyer questions. It records mentions, accuracy, sources and limits, then distinguishes observations from proposed fixes.

Can I start with a manual audit?

Yes. Choose a small set of realistic buyer questions and record the test conditions and answers. Repeat the same panel under documented conditions. The time required depends on the number of engines, questions and repetitions; a short check is not a complete market assessment.

How is an audit priced?

Define the markets, languages, engines, questions, repetitions and evidence to retain. Separate diagnosis, implementation and ongoing monitoring in the proposal. LYVIA scopes this work after a project-fit conversation; this guide does not claim a universal market price.

Does an AI citation mean the content trained the model?

No. An assistant may cite a page retrieved for a web search. A citation establishes a reference in that particular answer, not that the page was used to train a model, brought a visitor or generated an enquiry.

How often should the audit be repeated?

Agree a cadence that fits the decisions you need to make and the effort of reviewing the evidence. Keep the question panel and test conditions comparable, and record changes. Repeat after a relevant site change as well as on the agreed schedule, without treating every difference as a causal effect.

Bring your priority offer, target markets and available search data to a 30-minute project conversation. We can then decide whether a scoped audit is the right next step.

LYVIA

LYVIA Team

AI automation and SEO/GEO visibility

LYVIA builds custom tools and works on SEO and AI search visibility for established small and mid-sized businesses.