On this page
An AI visibility audit checks two things: whether AI assistants can read your website, and how they answer the questions your patients ask, including which practices they name and which pages they cite. Curve Compliance covers both in AI Visibility, which shows how often AI assistants name and cite your practice and checks whether AI search can read your site. AI Visibility is a feature in Curve Compliance, and Curve also offers it as a managed service.
Want this audit on your own practice? AI Visibility turns what it finds into a weekly roadmap sized to what your clinicians can publish, with medical topics flagged for clinical review. Book a call to see AI Visibility on your own questions, or to talk about the managed service.
The 12-point AI visibility audit checklist
Part 1 asks whether AI search crawlers can read your pages. Part 2 asks what the assistants then say. Rows link to published guidance where it exists, opened November 2, 2026.
| # | Check | What to look for | Source |
|---|---|---|---|
| 1 | AI search crawlers allowed | robots.txt lets in OAI-SearchBot, Claude-SearchBot, PerplexityBot, Googlebot and Bingbot | OpenAI; Anthropic; Perplexity |
| 2 | Training crawlers set on purpose | GPTBot, ClaudeBot and Google-Extended are allowed or blocked as a deliberate choice | OpenAI; Google |
| 3 | User-requested fetches | You know what ChatGPT-User, Claude-User and Perplexity-User do when a patient asks about you | OpenAI; Anthropic |
| 4 | Firewall and CDN | Your firewall or CDN does not block the crawlers your robots.txt allows | Google; Perplexity |
| 5 | Indexable, with snippets | Key pages have no noindex or nosnippet rule | Google; Google |
| 6 | Text in the HTML | Your main content is in text, not only in images or scripts | |
| 7 | Page basics | Each page has a title, meta description, one H1, a canonical and a recent update | Your page source |
| 8 | Structured data | Markup matches the visible text on the page | |
| 9 | Sitemap and llms.txt | A sitemap exists; llms.txt is optional and serves other tools | Google; llmstxt.org |
| 10 | The questions to test | A list of patient questions by intent, with a city where it matters | Your Search Console and front desk |
| 11 | Competitors and sources | Who the answers name, and which pages and sites they cite | The answers themselves |
| 12 | Accuracy | Services, locations and insurance stated correctly in the answers | The answers themselves |
Part 1: can AI search crawlers read your site?
Each assistant's owner publishes what its crawlers do. OpenAI says “Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though can still appear as navigational links,” (OpenAI). Anthropic says “Disabling Claude-SearchBot on your site prevents our system from indexing your content for search optimization, which may reduce your site's visibility and accuracy in user search results” (Anthropic). Perplexity says “PerplexityBot is designed to surface and link websites in search results on Perplexity. It is not used to crawl content for AI foundation models” (Perplexity).
Training crawlers are a separate decision. OpenAI says “Disallowing GPTBot indicates a site's content should not be used in training generative AI foundation models” (OpenAI). Anthropic says that when a site restricts ClaudeBot, “it signals that the site's future materials should be excluded from our AI model training datasets” (Anthropic). Google says Google-Extended lets publishers manage whether content Google crawls may be used to train future Gemini models and for grounding in Gemini Apps, and that “Google-Extended does not impact a site's inclusion in Google Search nor is it used as a ranking signal in Google Search” (Google).
Then check the layer in front of robots.txt. Google's list of SEO basics for AI features starts with “Ensuring that crawling is allowed in robots.txt, and by any CDN or hosting infrastructure” (Google). Perplexity adds: “If you're using a Web Application Firewall (WAF) to protect your site, you may need to explicitly allow Perplexity's bots to ensure they can access your content” (Perplexity). For a crawler-by-crawler policy, see which AI crawlers a healthcare website should allow.
Page checks AI search depends on
Google sets one technical bar for its AI features: “To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet” (Google). A nosnippet rule matters here, because Google says it “will also prevent the content from being used as a direct input for AI Overviews and AI Mode” (Google). Look for noindex or nosnippet left on service pages.
Google's other basics read like an audit list: “Making sure that important content is available in textual form” and “Making sure your structured data matches the visible text on the page” (Google). On llms.txt, the proposal describes itself as “A proposal to standardise on using an /llms.txt file to provide information to help agents use a website” (llmstxt.org), while Google says “You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities), as Google Search itself doesn't use them” (Google). Treat llms.txt as optional. See llms.txt for healthcare websites and schema markup for healthcare AI search.
Part 2: the questions to test
Part 2 starts with a question list, not a keyword list. Write down the questions patients ask before they book, and tag each with an intent: informational, commercial, local, brand or comparison. Where the answer depends on place, write the city or region into the question itself, such as “dental implants in Tampa”.
Good sources for the list are your front desk, your own search data and the comparison questions patients ask about you and the practices nearby. See query fan-out for healthcare for the longer searches AI assistants run before they answer.
Competitors and the sources AI cites
For each question, record which brands the answer names and which pages it cites. Note where you are named, where a rival is named instead, and where no practice is named at all, because each calls for different work.
Then look at the sources: forums, videos, directories, health publishers, news, reference sites and your own pages. Those are the sources shaping what patients hear about your field. See where AI gets healthcare answers and AI share of voice.
What AI gets wrong about you
Write down the facts an assistant should get right: the services you offer, your locations, the insurance you take. Add the wrong claims you have heard patients repeat. Then read each answer for those claims and note the assistant and question behind each wrong sentence. See what to do when AI gets your practice wrong.
Turning the audit into a plan
An audit should end in a short list of work. Each failing site check becomes a fix. Each gap question becomes a page to write or update. Each wrong fact becomes a correction stated plainly on the page the answers cite. Size the list to what your clinicians can review each week. See an AI visibility content roadmap clinicians can keep up with.
Doing it by hand, or every week
You can run Part 2 by hand: ask each assistant each question, copy the answers into a sheet and repeat. A one-off check is hard to trust. Google says “AI Overviews are only shown when our systems determine that it is additive to classic Search, and as such, often don't trigger” (Google), and the same question can get a different answer the next time you ask it. Google also says “No third-party tool has access to our internal ranking or AI systems” (Google). A sound audit asks the assistants your patients' questions, records the answers and repeats on a schedule.
What This Looks Like in Practice
In one AI Visibility program we've run, for a HIPAA-focused healthcare software brand, Curve's team tracked the questions buyers ask AI assistants, found where competitors were named and the brand wasn't, and published pages to close those gaps. About five weeks in:
- AI assistants named or cited the brand in 53% of their answers to its 40 core buyer questions (104 of 196), across ChatGPT, Google AI Overviews, Google AI Mode, Perplexity and Claude.
- Across 184 real buyer questions and 912 AI answers, its site was cited in 236 answers, more than any competitor's and more than 2.5 times as many as the nearest one (89).
- 47 of the new pages were already cited by AI assistants within six days of going live.
- One new page brought in more than half of the brand's unpaid ChatGPT visits in its first week.
How Curve Compliance helps
AI Visibility is a feature in Curve Compliance, and Curve also offers it as a managed service. AI Visibility shows how often AI assistants, including ChatGPT, Google AI Overviews, Google AI Mode, Perplexity, Claude and Gemini, name and cite your practice for the questions your patients ask. It shows your mention rate (how often AI answers name you), citation rate (how often they cite your site) and share of voice (your share of the mentions among the brands you compete with). It checks whether AI search can read your site, and what to fix. It catches what AI gets wrong about your practice, so you can correct it on the pages AI reads.
With the managed service, Curve's team sets up your questions, competitors and topics, writes the pages on your roadmap, and makes the technical fixes that help AI assistants read your site. Your clinicians review and approve anything medical before it goes live. If your developer manages your site, Curve's team hands them the exact fixes. Each month, Curve's team walks you through your results on a call and sends a one-page report.
AI Visibility is built for healthcare: only the marketing question you track is sent to AI assistants, screened for PHI first, and never anything about a patient. Curve is SOC 2 Type II and signs a BAA on every plan. AI Visibility is available on request: book a call to get started.
Sources, checked November 2, 2026: Google, AI features and your website; Google, Optimizing your website for generative AI features; Google, Robots meta tag and data-nosnippet; Google, common crawlers; OpenAI, Overview of OpenAI Crawlers; Perplexity, Perplexity Crawlers; Anthropic, Does Anthropic crawl data from the web; llmstxt.org, The /llms.txt file.
Frequently Asked Questions
What is an AI visibility audit?
An AI visibility audit checks whether AI assistants can read your website and how they answer the questions your patients ask, including who they name and which pages they cite. Curve Compliance's AI Visibility covers both.
How do I check if ChatGPT can read my site?
Open your robots.txt and confirm OAI-SearchBot is allowed, because OpenAI says sites opted out of it are not shown in ChatGPT search answers (OpenAI). Then check that your firewall or CDN lets it through.
Should a healthcare practice block GPTBot?
That is your call. OpenAI says GPTBot gathers content that may be used for training and that blocking it signals your content should not be used that way (OpenAI). Search in ChatGPT runs on OAI-SearchBot, a separate setting.
Does nosnippet stop my pages from appearing in AI Overviews?
It can. Google says nosnippet applies to AI Overviews and AI Mode and “will also prevent the content from being used as a direct input for AI Overviews and AI Mode” (Google). Check that key service pages carry no nosnippet rule.
Does llms.txt matter for AI search?
Not for Google: it says Google Search itself does not use machine readable files, AI text files or Markdown (Google). Other tools may read the file (llmstxt.org), so it is optional.
How often should a practice run an AI visibility audit?
Check the site after any redesign, migration, or change to robots.txt or your firewall. Check the answers regularly, because the same question can get a different answer the next time and a single check can mislead.
Does an AI visibility audit send patient data to AI assistants?
It should not. Curve Compliance's AI Visibility asks AI assistants only the marketing questions you track, screened for PHI first, never anything about a patient.
Can Curve run the audit for me?
Yes. Curve's team can run AI Visibility for you as a managed service. See the managed service page.
Talk to Curve Compliance
Ready to see your own audit? Book a call to see AI Visibility on your own questions, or to talk about the managed service.