Free tool
AI visibility checker
Convertica's free AI visibility checker tests the part of AI visibility you control: your own site. Enter a page and the audit app scores its AI visibility and agent readiness out of 100. Or paste your robots.txt below and see at once which AI crawlers it lets in. It reads your site only. It does not ask ChatGPT, Perplexity, Gemini or Google's AI Overviews whether they cite you.
Short answer
An AI visibility checker tests whether AI search engines and assistants can reach and read your website. Convertica's free AI visibility checker scores a page's AI visibility and agent readiness out of 100, and an instant check shows which AI crawlers your robots.txt allows. It reads your site only: it does not ask ChatGPT or Google whether they cite you.
- The live check runs Convertica's free audit app on one page and scores AI visibility and agent readiness alongside seven other checks, each out of 100.
- The instant robots.txt check needs no email: paste your file and it reports 20 AI crawlers from nine operators, at / and at a path you choose.
- A crawler that has its own group in robots.txt ignores the * group, so rules written for every crawler may not apply to it.
- Training, search and user-triggered crawlers are separate: blocking GPTBot does not block OAI-SearchBot.
- The free report has your overall score, all eight check scores and three fixes you can make now.
Robots.txt AI crawler check
Free, no email. Paste a robots.txt file and see which of 20 AI crawlers it allows or blocks. It runs in your browser: what you paste is not sent anywhere.
AI search and answer crawlers allowed at /
8 of 8
Allowed at /: search and answers 8 of 8, fetch for a user 5 of 5, model training 3 of 6, open crawl data 0 of 1.
Blocked at /: GPTBot, ClaudeBot, Google-Extended, CCBot.
Allowed at /pricing/: search and answers 7 of 8, fetch for a user 5 of 5, model training 3 of 6, open crawl data 0 of 1.
Blocked at /pricing/: PerplexityBot, GPTBot, ClaudeBot, Google-Extended, CCBot.
1 Sitemap line listed.
Example result, for the made-up file above
| Crawler | Used for | At / | At /pricing/ |
|---|---|---|---|
| OAI-SearchBotOpenAI | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| Claude-SearchBotAnthropic | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| PerplexityBotPerplexity | Search and answers | AllowedNo rule in the PerplexityBot group matches this path. | BlockedDisallow: /pricing/ on line 17, in the PerplexityBot group. |
| GooglebotGoogle | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| ApplebotApple | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| DuckAssistBotDuckDuckGo | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| MistralAI-IndexMistral AI | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| Amzn-SearchBotAmazon | Search and answers | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| ChatGPT-UserOpenAI | Fetch for a user | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| Claude-UserAnthropic | Fetch for a user | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| Perplexity-UserPerplexity | Fetch for a user | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| MistralAI-UserMistral AI | Fetch for a user | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| Amzn-UserAmazon | Fetch for a user | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| GPTBotOpenAI | Model training | BlockedDisallow: / on line 10, in the GPTBot group. | BlockedDisallow: / on line 10, in the GPTBot group. |
| ClaudeBotAnthropic | Model training | BlockedDisallow: / on line 10, in the ClaudeBot group. | BlockedDisallow: / on line 10, in the ClaudeBot group. |
| Google-ExtendedGoogle | Model training | BlockedDisallow: / on line 13, in the Google-Extended group. | BlockedDisallow: / on line 13, in the Google-Extended group. |
| Applebot-ExtendedApple | Model training | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| MistralAI-TrainingMistral AI | Model training | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| AmazonbotAmazon | Model training | AllowedNo rule in the * group matches this path. | AllowedNo rule in the * group matches this path. |
| CCBotCommon Crawl | Open crawl data | BlockedDisallow: / on line 10, in the CCBot group. | BlockedDisallow: / on line 10, in the CCBot group. |
Sitemap line in this file: https://www.example.com/sitemap.xml.
How the file was read
How does robots.txt decide which AI crawlers get in?
A robots.txt file decides access for each AI crawler in two stages. First the crawler picks its group: the groups that name it, or the * group if none does. Then, for each URL, the longest matching Allow or Disallow path in that group wins, and a tie goes to Allow. No matching rule means the URL is allowed.
group = every group that names the crawler, merged
otherwise the * group
otherwise no rules at all
rule = the matching Allow or Disallow with the longest path
(a tie goes to Allow)
verdict = Allow, or no matching rule: allowed
Disallow: blocked
* = any run of characters $ = the URL ends here
These are the rules of RFC 9309, the Robots Exclusion Protocol, and the check on this page applies them as written. Names such as User-agent are not case-sensitive; paths are. Blank lines and comments change nothing, and a Sitemap line never ends a group.
Worked example 1: a group of its own replaces the * group
In the made-up file above, PerplexityBot has its own group with one rule, Disallow: /pricing/. That group is all it reads, so the Disallow: /cart/ written for * does not apply to it: at /cart/ PerplexityBot is allowed, while OAI-SearchBot, which has no group and reads *, is blocked. If you give a crawler its own group, repeat in it every rule you still want it to follow.
The same file gives Google-Extended two rules. At /blog/ai-search-guide/ both match: the path in Disallow: / is 1 character long and the path in Allow: /blog/ is 6, so the longer one decides and the page is allowed. At / only the Disallow matches, so the homepage is blocked.
Worked example 2: wildcards
A second made-up file, with one group for every crawler:
User-agent: *
Disallow: /*.pdf$
Disallow: /search
Allow: /search/help
| URL path | Deciding rule | Result |
|---|---|---|
/files/guide.pdf | Disallow: /*.pdf$ | Blocked |
/files/guide.pdf?download=1 | No rule matches | Allowed |
/search?q=shoes | Disallow: /search | Blocked |
/search/help | Allow: /search/help | Allowed |
/about/ | No rule matches | Allowed |
The $ is why the same PDF is blocked on its plain URL and allowed with a query string: the second URL no longer ends in .pdf. And /search/help is allowed because its Allow rule is longer than Disallow: /search.
How to use the robots.txt AI crawler check
- Open your robots.txt. It lives at the root of each host: yourdomain.com/robots.txt. A subdomain such as shop.yourdomain.com has its own file.
- Paste all of it over the example. If there is no file at all, no rules apply and every crawler may fetch every page.
- Add a page you care about. A product, pricing or article URL: rules often differ by folder.
- Read the table from the top. Search and answer crawlers first, then fetches for a user, then model training. Each verdict names the line that decided it.
- Read the notes. Misspelled directives, rules that sit before any
User-agentline and paths without a leading slash are listed, because they do nothing. - Fix the file, then paste it again. OpenAI and Perplexity both say a robots.txt change can take around 24 hours to reach their systems.
The check tells you what the file says. It cannot see a firewall, CDN or bot protection rule that turns a crawler away before robots.txt is ever read, and it cannot make a crawler obey.
What does the AI visibility checker measure?
The AI visibility checker measures how easily machines can reach and read one page of your site. It reads your robots.txt rules for six AI search and assistant crawlers, your structured data, how much of the page is in the HTML before JavaScript runs, whether the business is clearly named, llms.txt, and whether questions on the page get direct answers.
It is check 7 of the 8 in Convertica's free CRO audit, named "AI visibility and agent readiness". The app loads your page in a real browser at phone and desktop size, fetches the page's raw HTML, your robots.txt and your llms.txt, and measures these parts:
| Part | What the check reads | What a gap looks like |
|---|---|---|
| AI crawler access | Your live robots.txt, for the path of the page you entered: whether OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot and Perplexity-User may fetch it | A rule that blocks one or more of them from the page |
| Structured data | Whether the page has JSON-LD, in the HTML or after scripts run, and whether every block parses | No JSON-LD at all, or a block with a syntax error |
| A clearly named business | Organization markup, its sameAs links to official profiles, and a business name in the markup or in an og:site_name tag | Nothing in the markup says who runs the site |
| Markup that fits the page | A type that matches what the page is: Product with an Offer and a price on a product page; types such as Service, SoftwareApplication, Article or FAQPage elsewhere | A product page with no Product markup, or Product markup with no price |
| Text in the HTML | How much of the text a visitor sees is already in the HTML before any JavaScript runs | Most of the page only appears after scripts run |
| Price without JavaScript | On store and software pages that show a price: whether that price is in the raw HTML | A price on screen that is missing from the HTML |
| Contact and policies | A phone, email or contact link in the raw HTML, plus shipping or returns wording on a store page or a privacy policy link on other pages | No way to contact the business, or no policy, readable in the HTML |
| llms.txt | Whether /llms.txt exists and returns plain text | No file at /llms.txt (a low impact finding) |
| Direct answers | Whether headings phrased as questions are followed by a short, direct answer | Question headings followed by long passages, or by nothing that answers them |
An AI review then reads the page text and screenshots and answers one question: could an AI agent state, from this page alone, what is sold, who it is for, the price or how to get it, the policies and the name of the business? The review is told never to claim that any AI assistant or search feature cites or shows the page, because the check has no data for that.
These parts are Convertica's own view of what makes a page easy for a machine to read. They are not a list of ranking factors. Google, for example, says there are no additional requirements to appear in AI Overviews or AI Mode beyond being indexed and eligible to be shown with a snippet, and that no special structured data or AI text file is needed.
The same run scores seven other checks on the same page: first impressions, calls to action, forms and friction, trust and credibility, mobile experience, page performance and SEO fundamentals. The landing page analyzer is the same engine pointed at a landing page.
How is the AI visibility score calculated?
The AI visibility and agent readiness score is a number out of 100 for the one page you entered. The measured parts in the table make up 70% of it and the AI review 30%. Convertica labels 80 or more good, 50 to 79 needs work, and below 50 a problem.
- Crawler access counts search and assistant crawlers only. The score uses the share of those six crawlers that may fetch the page.
- Blocked training crawlers do not lower the measured score. A rule that blocks a training crawler such as GPTBot or ClaudeBot is reported as a separate, low impact finding, because that is a business choice.
- It feeds one overall score. The overall score in your report is the plain average of the checks that could be scored, and every check weighs the same.
The parts, their weights and the pass marks are Convertica's choices, not taken from research or an industry benchmark. A high score means fewer known gaps on the page. It does not predict that any AI engine will mention, cite or recommend you.
What is free, and what is in the full report?
Both tools are free. The robots.txt AI crawler check asks for nothing. The live check asks for an email address, and its free report has your overall score, all eight check scores and three fixes you can make now. The optional full report costs $97 and has every finding, including the high impact ones, with how to implement each fix.
| Part | Cost | What you give | What you get |
|---|---|---|---|
| Robots.txt AI crawler check | Free | The text of a robots.txt file. No email. | Allowed or blocked for 20 AI crawlers, at / and at a path you choose, with the line that decided each |
| Free report | Free | A page URL and your email address | The free report has your overall score, all eight check scores and three fixes you can make now. The AI visibility and agent readiness score is one of the eight. |
| Full report | $97 | Paid and unlocked inside the audit app, after you have seen your free report | The full report has every finding, including the high impact ones, with how to implement each fix. |
One thing to know before you run it: the free report shows three fixes, chosen from across all eight checks. When the AI visibility and agent readiness check has a medium or low impact finding, one of the three comes from that check. Its high impact findings, like every finding beyond the three, are in the full report. Your AI visibility and agent readiness score is in the free report either way.
What this AI visibility checker does not do
This AI visibility checker reads your site and nothing else. It does not send a question to ChatGPT, Perplexity, Gemini, Claude or Google, so it cannot tell you whether those engines mention or cite you, how often, for which questions, or which competitors they name. Finding that out means asking the engines, by hand or with a citation tracking product.
| Compared on | Site-side readiness check (this page) | Citation or mention tracking |
|---|---|---|
| The question it answers | Can AI crawlers and agents reach this page and read its facts? | Do AI engines mention or cite the brand, and for which questions? |
| How it works | Fetches the page, robots.txt and llms.txt and measures them | Sends a set of questions to AI engines, or searches a store of recorded AI answers, and looks for the brand |
| What it needs from you | A page URL, or the text of your robots.txt | A brand name, usually competitors, and the questions buyers ask |
| How steady the result is | The same page gives the same measured facts until the page changes | AI answers vary between runs, people and places, so results are samples and trends |
| What it cannot tell you | Whether anyone cites you | What on your own site to fix |
The two answer different questions. Start with the readiness check: a page that AI crawlers cannot fetch or read gives an engine nothing to quote, whatever a tracker reports. Tracking is worth adding once nothing on your own site is in the way.
Other limits worth knowing:
- It cannot see blocks outside robots.txt. A firewall, CDN or bot protection rule can refuse an AI crawler that robots.txt allows. The audit fetches your pages as itself, not as GPTBot or ClaudeBot.
- It cannot confirm that crawlers visit. That is in your server or CDN logs.
- It reads one page per run. It is not a crawl of the whole site, and a homepage and a product page can score differently, so check the page types that matter to you.
- It is not a ranking check. It says nothing about where you rank in Google or how much traffic AI search sends you.
Which AI crawlers should you allow in robots.txt?
Allow the AI crawlers that match what you want from each company. To be shown in an AI search product, allow its search crawler, such as OAI-SearchBot, Claude-SearchBot or PerplexityBot. For Google's AI Overviews the crawler is Googlebot itself. Training crawlers such as GPTBot and ClaudeBot are a separate choice about how your content is used.
The table lists the 20 crawlers and control tokens the check on this page reports on, from nine operators. Each is grouped by what its operator's own documentation says it is for, and no further.
| robots.txt token | Group | What the operator says it is for | What else the operator says |
|---|---|---|---|
| OAI-SearchBotOpenAI | Search and answers | Surfaces websites in ChatGPT's search features. | OpenAI says a site that opts out will not be shown in ChatGPT search answers, though it can still appear as a navigational link. |
| Claude-SearchBotAnthropic | Search and answers | Crawls the web to improve the quality of search results for Claude users. | Anthropic says blocking it may reduce your site's visibility and accuracy in user search results. |
| PerplexityBotPerplexity | Search and answers | Surfaces and links websites in Perplexity's search results. | Perplexity says it is not used to crawl content for AI foundation models. |
| GooglebotGoogle | Search and answers | Crawls for Google Search, which includes AI Overviews and AI Mode. | Google says robots.txt rules for Googlebot are the control for how a site is crawled for Search, its AI features included. |
| ApplebotApple | Search and answers | Powers search in Spotlight, Siri and Safari. | Apple says Applebot follows Googlebot's rules when a file names Googlebot and not Applebot, and that what it crawls may also be used to train Apple's models unless Applebot-Extended is disallowed. |
| DuckAssistBotDuckDuckGo | Search and answers | Crawls pages in real time for DuckDuckGo's AI-assisted answers. | DuckDuckGo says the data is not used to train AI models, and that opting out does not affect its organic search results. |
| MistralAI-IndexMistral AI | Search and answers | Indexes content for Mistral search, which helps answer questions in Mistral's assistant. | Mistral says content it crawls is not used for generative AI training. |
| Amzn-SearchBotAmazon | Search and answers | Improves search experiences in Amazon products and services, such as Alexa. | Amazon says that when a file does not mention it but allows other search bots, it follows the rules given to those bots. This check applies only the rules for its own name or for *. |
| ChatGPT-UserOpenAI | Fetch for a user | Visits a page when a ChatGPT user's question or a custom GPT calls for it. | OpenAI says robots.txt rules may not apply, because a user starts these requests. |
| Claude-UserAnthropic | Fetch for a user | Fetches a page when a Claude user's question calls for it. | Anthropic says blocking it stops Claude from retrieving your content in response to a user's query. |
| Perplexity-UserPerplexity | Fetch for a user | Visits a page when a Perplexity user's question calls for it. | Perplexity says this fetcher generally ignores robots.txt rules, because a user requested the fetch. |
| MistralAI-UserMistral AI | Fetch for a user | Visits a page when a user of Mistral's assistant asks a question. | Mistral says it is not used for automatic crawling or for generative AI training. |
| Amzn-UserAmazon | Fetch for a user | Fetches live information for user requests, such as Alexa questions. | Amazon says it may not follow all robots.txt directives, because a user can start its requests. |
| GPTBotOpenAI | Model training | Crawls content that may be used to train OpenAI's generative AI foundation models. | OpenAI says disallowing it indicates that a site's content should not be used for that training. |
| ClaudeBotAnthropic | Model training | Collects web content that could contribute to training Anthropic's models. | Anthropic says restricting it signals that the site's future material should be left out of its training datasets. |
| Google-ExtendedGoogle | Model training | Controls whether content Google crawls may be used to train Gemini models and to ground Gemini answers. | A control token, not a crawler: Google says it has no user agent string of its own and does not affect inclusion or ranking in Google Search. |
| Applebot-ExtendedApple | Model training | Controls whether content Applebot crawls may be used to train Apple's foundation models. | A control token: Apple says it does not crawl pages, and that pages which disallow it can still be included in search results. |
| MistralAI-TrainingMistral AI | Model training | Crawls content to help build datasets for training Mistral's generative AI models. | Mistral says it is not used for search indexing or to answer live user questions. |
| AmazonbotAmazon | Model training | Used to improve Amazon's products and services, and may be used to train Amazon AI models. | Amazon also lists Amzn-SearchBot and Amzn-User, which it says do not crawl content for generative AI model training. |
| CCBotCommon Crawl | Open crawl data | Builds Common Crawl's open repository of web crawl data, which anyone can access and analyze. | Common Crawl's page names no single use for the data, so CCBot is not grouped under search or training here. |
Sources, each operator's own page:
- OpenAI: Overview of OpenAI Crawlers
- Anthropic: Does Anthropic crawl data from the web, and how can site owners block the crawler?
- Perplexity: Perplexity Crawlers
- Google: Google's common crawlers
- Google: AI features and your website
- Apple: About Applebot
- DuckDuckGo: Is DuckAssistBot related to DuckDuckGo?
- Mistral AI: Mistral crawlers
- Amazon: About Amazonbot
- Common Crawl: CCBot
Operators add, rename and retire crawlers, so read the linked page before you rely on a rule. Four things in the table are easy to get wrong:
- Google's AI Overviews are not a separate crawler. Google says robots.txt rules for Googlebot are the control for how a site is crawled for Search, AI features included. Google-Extended only governs Gemini training and grounding, and Google says it does not affect inclusion or ranking in Search.
- Training and search are separate settings. OpenAI, Anthropic and Mistral each document one crawler for training and another for search. Blocking the first does not block the second, unless one rule catches both.
- Some tokens are not crawlers. Google-Extended and Applebot-Extended never request a page. They are labels a robots.txt file uses to say how content fetched by Googlebot or Applebot may be used.
- User-triggered fetchers may not follow robots.txt. OpenAI says the rules may not apply to ChatGPT-User, Perplexity says Perplexity-User generally ignores them, and Amazon says Amzn-User may not follow all of them, because a person started the request.
One common setup, shown to illustrate the syntax and not as a recommendation, keeps AI search crawlers in and training crawlers out. Each named group repeats the rules from the * group, because a crawler with its own group does not read *:
User-agent: *
Disallow: /cart/
# AI search: same rules as everyone else
User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
Disallow: /cart/
# AI training: not wanted
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
Disallow: /
How to check your AI visibility, step by step
To check your AI visibility, work from your own site outward. Confirm that AI crawlers can fetch your pages, that the facts are in the HTML and in valid structured data, and only then ask the AI engines your buyers' questions and watch your analytics for visits they send. The first four steps use this page and free tools.
-
Check crawler access
Paste your robots.txt into the robots.txt AI crawler check above and add your most important page as the path. A blocked search crawler makes the later steps pointless for that engine.
-
Run the live check on a key page
Enter a product, pricing or service page in the form at the top. Your report scores AI visibility and agent readiness for that page, with the seven other checks from the same run.
-
Read the page as a machine does
Open the page source, not the inspector, and search for your price, product name and returns terms. If they are missing, they are added by JavaScript or sit in an image, and a crawler that does not run scripts will not read them.
-
Validate your structured data
Run the URL through Google's Rich Results Test or the Schema.org validator. Fix syntax errors first, then check that every value in the markup matches what the page shows.
-
Ask the AI engines yourself
Put the questions your buyers ask to ChatGPT, Perplexity, Gemini and Google, and note who is named and which pages are linked. This is the step no site-side tool can do for you. Answers change from run to run, so repeat it and look for patterns.
-
Look at Search Console and analytics
Google says appearances in AI Overviews and AI Mode are counted in Search Console's Performance report under the Web search type. In your analytics, look for visits referred by AI assistants and how they convert.
-
Check your logs
Server or CDN logs show which AI crawlers request your pages and what response they get. A user agent string can be faked, so confirm with the IP ranges that operators such as OpenAI, Perplexity and Amazon publish.
For the wider checklist, from readable facts to whether an agent can complete a form or a checkout, use the AI agent readiness checklist.
How to improve your AI visibility after the check
Improve AI visibility in the order the check exposes problems: remove what blocks AI crawlers, put the facts in the HTML, state who you are and what the page offers in valid markup, then answer the questions buyers ask in plain sentences. These steps make a page easier to read and quote. None of them guarantees a citation.
- Unblock the crawlers you want. Fix robots.txt, then ask whoever runs your CDN or firewall whether its bot rules treat AI crawlers the same way.
- Put the facts in the HTML. Price, availability, delivery, returns and contact details should be in the page source as text, not added by scripts or shown only in images.
- Name the business in markup. Add Organization markup with your name, logo and sameAs links to your official profiles.
- Use markup that fits the page. Product with an Offer and a price on product pages; Service, SoftwareApplication, Article or FAQPage where they describe the page. Keep it identical to what a visitor sees.
- Answer questions directly. Under a heading phrased as a question, start with a short answer that makes sense on its own, then add the detail.
- Add llms.txt if it is cheap for you. It is optional. The llms.txt guide covers what it is and what it does not do, and the llms.txt generator builds and validates the file.
What other sites say about you also shapes what AI engines repeat, and no check of your own site can measure that. Convertica's generative engine optimization services page explains how that work is done and measured.
Being read is half of it. When an AI answer sends a person, or an AI agent, to your page, the page still has to convert, which is why the same run scores your first screen, calls to action, forms, trust, mobile experience and speed. See AI conversion rate optimization for how the two fit together, and agentic commerce for what changes when the visitor is an agent that buys.
See all free tools and how they fit together.
AI visibility checker FAQ
What is an AI visibility checker?
An AI visibility checker is a tool that tests how visible a website is to AI search engines and assistants. There are two kinds. A site-side checker, like this one, reads your site: crawler access, structured data and what is in the HTML. A citation tracker sends questions to AI engines and records whether your brand appears in the answers.
Is this AI visibility checker free?
Yes. The robots.txt AI crawler check is free, needs no email and runs in your browser. The live check is free too: it asks for an email address because the report is sent to you, and the free report has your overall score, all eight check scores and three fixes you can make now. An optional full report, $97, has every finding, including the high impact ones, with how to implement each fix.
Does the checker ask ChatGPT, Perplexity or Gemini about my brand?
No. It reads your own site and sends no questions to any AI engine, so it cannot tell you whether or how often they mention or cite you. To see that, ask the engines the questions your buyers ask, or use a citation tracking product. This check tells you whether something on your own site stands in the way.
How is the AI visibility score calculated?
The AI visibility and agent readiness score is out of 100 for one page. 70% comes from measured facts: robots.txt rules for six AI search and assistant crawlers, structured data, what is in the HTML without JavaScript, a clearly named business, llms.txt and direct answers under question headings. The other 30% comes from an AI review of the page.
What is a good AI visibility score?
Convertica labels a score of 80 or more good, 50 to 79 needs work, and below 50 a problem. Those pass marks are Convertica's own, not an industry benchmark, and the score does not predict whether any AI engine will cite you. Use it to find gaps on the page and to compare the same page before and after a change.
Which AI crawlers should I allow in robots.txt?
Allow the crawlers that match what you want. To be shown in an AI search product, allow its search crawler: OAI-SearchBot for ChatGPT search, Claude-SearchBot for Claude and PerplexityBot for Perplexity. For Google's AI Overviews, the crawler is Googlebot. Training crawlers such as GPTBot and ClaudeBot, and the Google-Extended token, are a separate choice about how your content is used.
Does blocking GPTBot remove my site from ChatGPT search?
No, not by itself. OpenAI documents GPTBot and OAI-SearchBot as independent settings: GPTBot collects content that may be used for model training, and OAI-SearchBot is the one that surfaces sites in ChatGPT's search features. A site can disallow GPTBot and still allow OAI-SearchBot. Check that a rule meant for one does not catch the other.
How do I check whether my page appears in Google AI Overviews?
Search Google for the question and look at the links in the AI Overview: no tool that only reads your site can tell you. Google says a page must be indexed and eligible to be shown with a snippet to appear as a supporting link, that robots.txt rules for Googlebot control crawling for these features, and that appearances are counted in Search Console's Performance report under the Web search type.
Does robots.txt stop AI assistants from reading my page?
Not always. robots.txt is a set of instructions that crawlers choose to follow, not an access control. The operators listed on this page document it as the way to control their search and training crawlers. For fetches a user triggers, OpenAI says robots.txt rules may not apply to ChatGPT-User, and Perplexity says Perplexity-User generally ignores them. To enforce a block, use server or firewall rules.
Why do I have to paste my robots.txt instead of entering a URL?
Because the instant check runs entirely in your browser, and browsers do not let a page read files from another website. Open yourdomain.com/robots.txt, copy the text and paste it in. The live check is different: it runs on Convertica's servers and fetches your robots.txt and llms.txt itself.
Do I need an llms.txt file for AI visibility?
No. An llms.txt file is optional. Google says you do not need to create new machine-readable files or AI text files to appear in AI Overviews or AI Mode. The live check looks for /llms.txt and reports a missing one as a low impact finding. If you want one, Convertica's llms.txt generator builds and validates the file.
Can I check a competitor's site?
Yes. A robots.txt file is public, so you can open a competitor's at theirdomain.com/robots.txt and paste it into the instant check. The live check works on any public page too. It reads only what a new visitor could load without logging in.
Is this an AI SEO checker or an AI Overview checker?
It covers the site-side part of both. The AI visibility and agent readiness check tests whether AI crawlers can reach the page and read its facts, and the same run scores SEO fundamentals such as the title, headings, canonical and indexing. It does not look up whether a keyword triggers an AI Overview or who is cited in it.
How often should I run an AI visibility check?
Run it after anything that changes what crawlers can reach or read: an edit to robots.txt, a new CDN or bot protection rule, a redesign or platform move, or a change to how prices and content are rendered. Operators also add and rename crawlers, so check the robots.txt table again when one of them announces a new one.