Your search rankings can look healthy while an AI answer ignores your brand, describes it incorrectly, or recommends a competitor. That does not mean SEO stopped mattering. It means the outcome you need to measure has changed.
A useful AI brand visibility audit shows where your brand appears, what the system claims about it, which evidence supports the answer, and why another brand may be selected instead. Traditional search visibility and AI visibility can diverge, so you cannot use rankings or local-pack presence as a substitute for this work.
Key takeaways
- Measure mentions, recommendations, citations, and factual accuracy separately. They are different outcomes with different fixes.
- Test the questions customers ask while choosing, comparing, and validating options. A branded lookup alone cannot reveal whether AI systems discover your brand.
- Check crawler access, entity consistency, factual specificity, claim support, unique information, and JSON-LD before treating missing visibility as a content-volume problem.
- Treat one generated answer as an observation. Prioritize patterns that recur across relevant prompts, sessions, or AI surfaces.
- Fix access barriers and incorrect facts before chasing more mentions. Being visible with the wrong information is not a win.
Build a prompt set around customer decisions
Start with the decision your customer is trying to make. A prompt such as What is [brand]? tests recognition and basic factual recall. It does not show whether your brand would be found when the customer has not named it.
Create prompts for each commercially important audience, need, location, and constraint. Keep the wording neutral. If you tell the system that your brand is the leading option or ask why it was excluded, you have already biased the test.
- Discovery: Which [category] providers serve [audience or location] and meet [specific need]?
- Fit: Which option is suitable for someone who needs [feature, policy, use case, or constraint]?
- Comparison: How do [brand] and [competitor] differ for [specific decision]?
- Fact retrieval: What does [brand] offer, where is it available, and what policies apply?
- Validation: Is [brand] a credible option for [use case], and what evidence supports that assessment?
Reuse the same wording when you want comparable observations. Begin a fresh conversation where possible, preserve the complete response, and record any visible citations. Do not reduce the result to a yes-or-no mention check.
| Dimension | What to record | What it reveals |
|---|---|---|
| Presence | Absent, named, or described without a clear name | Whether the system associates your entity with the prompt |
| Prominence | Primary recommendation, alternative, comparison subject, or passing mention | Whether visibility is commercially meaningful |
| Citation | Your site, another site, or no visible citation | Which evidence is available for inspection |
| Accuracy | Correct, outdated, contradictory, unsupported, or unclear | Whether visibility helps or harms the customer decision |
| Competitive displacement | Which alternative appears and the stated reason | Where another brand supplies stronger relevance or evidence |
Paid monitoring platforms can automate structured prompts across multiple AI surfaces and track mentions, citations, competitors, and inconsistencies over time. That automation is difficult to reproduce at scale, but the initial diagnostic can still be performed manually if you preserve the evidence and apply consistent labels.
Inspect the signals behind each answer
Prompt results show the symptom. Your next job is to find the upstream reason. More content is not the default answer: an access restriction, contradictory business fact, vague claim, or missing entity relationship can undermine an otherwise substantial site.
Confirm that AI crawlers can reach meaningful content
Open yourdomain.com/robots.txt and inspect any rules for GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. A disallow rule may be an intentional policy choice, so document it before changing it. The audit question is whether access matches the organization’s actual policy, not whether every crawler should automatically be allowed.
Then visit the site as a new user. Check whether the homepage or important landing pages hide their substantive content behind a cookie wall, language selector, location picker, or another interstitial. These gates can leave less-established crawlers unable to reach the facts even when conventional search crawling appears healthy.
Map the entities the brand needs AI to understand
List each distinct thing an answer may need to describe: the business, products or service lines, relevant staff, policies, locations, and location context. For each entity, record its canonical name, defining attributes, public URL, supporting evidence, and the person responsible for keeping it current.
Do not treat a passing marketing mention as documentation. A location page that says conveniently located but gives no nearby landmarks, distances, transport details, or service area leaves the location entity underdefined. A service page that promises flexible options but never names those options creates the same problem.
Compare important facts across the website, Google Business Profile, and other public representations. Different names, addresses, policies, descriptions, or availability statements create entity drift. Consistency is a foundational trust signal; decide which location is canonical, correct it first, and then align the rest.
Test whether the facts are extractable and defensible
AI systems can reuse a direct factual statement more cleanly than a sentence built from vague adjectives and unclear pronouns. Paste a priority page into an AI assistant and ask it to identify every pronoun, adjective, or phrase whose referent or meaning is ambiguous. Require a fact-specific rewrite for each flagged sentence, then verify the rewrite yourself before publishing it.
Audit claims separately. Search your pages for best, most, only, award-winning, leading, and similar language. Record the evidence behind each claim, the entity that granted any award, and the page where a reader can verify it. If the evidence does not exist, narrow the statement to a supportable fact or remove it. An uncheckable superlative gives an AI system little reason to repeat the claim.
Look for information gain and meaningful structured data
Take several sentences from a priority page and search for them in quotation marks. If competitors could publish the same wording without changing a detail, the page contributes little unique evidence. Replace generic language with information your organization can substantiate: named processes, exact policy conditions, original measurements, specific product attributes, or first-party findings.
View the page source and search for application/ld+json. No match means that page has no JSON-LD block. A match is only the beginning of the check: inspect whether the markup represents the actual entities and relationships on the page or merely supplies a thin, flat label.
Verify that names, URLs, locations, and relationships agree with visible content. Inspect sameAs values carefully and use them only for records that genuinely identify the same entity, including applicable Wikidata or Knowledge Graph identifiers. Structured data can clarify identity and relationships, but its presence does not guarantee a recommendation.
Turn response patterns into a prioritized diagnosis
A single visibility percentage conceals the difference between absence, weak prominence, missing evidence, and factual error. Diagnose each repeated pattern before assigning work.
| Observed pattern | Investigate first | Action to take |
|---|---|---|
| Brand is absent from non-branded discovery prompts | Crawler access, category association, location facts, and incomplete entities | Resolve access barriers and add explicit, supportable facts connecting the brand to the relevant need |
| Brand appears only when named | Weak association with the use case, audience, category, or location | Strengthen the relevant entity pages with decision-ready facts rather than repeating the brand name |
| Brand is mentioned with incorrect facts | Contradictory or outdated public representations | Correct the canonical page, align external profiles, and document the changed fact for retesting |
| A competitor is recommended and cited | The cited page’s specificity, proof, entity coverage, and fit to the prompt | Identify the evidence your page lacks; do not copy the competitor’s wording |
| Your site is cited but the brand is not recommended | Evidence for customer fit, limitations, policies, and differentiators | Make the decision criteria explicit and support each material claim |
| A recommendation appears without a visible citation | Accuracy and reproducibility of the stated reasoning | Record the answer without guessing its origin, verify every claim, and look for the pattern in other tests |
Prioritize by consequence and dependency, not by whichever gap is easiest to edit.
- Remove access barriers that prevent important pages from being reached.
- Correct wrong or contradictory business facts, especially facts that could change a customer’s decision.
- Complete the commercially important entities and their location, product, service, staff, and policy attributes.
- Replace generic claims with verifiable evidence and information the brand uniquely possesses.
- Refine JSON-LD so it faithfully represents the corrected visible content and entity relationships.
- Rerun the unchanged prompts and compare the complete answers, not just the mention count.
Each resulting ticket should contain the prompt, the complete observed answer, the affected customer decision, the suspected cause, the page or profile to change, the evidence required, and the retest condition. This keeps an AI visibility problem from becoming a vague request to improve the content.
Make the audit repeatable without turning it into dashboard theater
Keep a durable audit log. At minimum, capture the prompt, audience, need, location or constraint, AI surface, conversation state, observation date, full answer, prominence label, cited URLs, factual errors, named competitors, suspected cause, owner, and fix status. Preserve raw outputs even if you later calculate summary metrics.
Repeat the audit with the same core prompt set after material changes to the website, business facts, policies, products, services, or locations. Add prompts when a genuinely new customer decision appears, but do not silently rewrite old prompts and compare the results as if the test stayed constant.
Automation becomes useful when the number of prompts, AI surfaces, locations, or competitors makes manual tracking unreliable. Some platforms let teams ask natural-language questions and receive answers grounded in their own visibility data. That can speed up investigation, but the interface should still lead you back to inspectable evidence.
Before adopting a paid visibility platform, verify that it can retain raw responses, expose citations, preserve prompt wording, distinguish mentions from recommendations, compare competitors, flag entity inconsistencies, and show change history. A polished composite score is not enough if you cannot trace it to the answer that created it.
Begin with the customer decision that matters most. Capture the current answers, label what happened, and fix the first upstream failure: access, identity, specificity, evidence, or structure. Then rerun the same prompt. The practical goal is fewer missing, unsupported, and incorrect brand answers when a customer is ready to choose.
References
- Conductor Blog — AI Has a Lot to Say About Your Brand. Ask Conductor.
- Search Engine Land — 9 checks to audit your AI visibility without a paid tool
Leave a Reply