AI Visibility Audit
SEO & WebCheck how well your website is set up to be found, understood and referenced by AI search and assistants — which AI crawlers can reach it, and what they can read.
Sends the address you enter to FreePanda so we can crawl it — nothing else about you
What people do next
Features
- Shows which AI crawlers your robots.txt lets in and keeps out — search and citation bots, on-demand fetchers, training crawlers and control tokens — from OpenAI, Anthropic, Perplexity, Google, Microsoft, Apple and others.
- Tells apart blocking the crawlers that power AI search, which removes you from AI answers, from blocking model-training crawlers, which is a legitimate choice.
- Finds pages that are an empty shell until JavaScript runs — what most AI crawlers actually see.
- Checks how clearly your brand and organisation are described: schema, sameAs profiles, consistent naming, about and contact pages.
- Reviews structured data for articles, FAQs, breadcrumbs and products.
- Looks at how machine-readable your content is: semantic structure, headings, lists and tables, alt text, and long unbroken walls of text.
- Checks answerability and citation readiness: concise openings, question-style headings, dates, authorship, sources and trust pages.
- Gives an overall readiness score, a score for each area, and for every issue why it matters and how to fix it.
- Reuses the crawl from an SEO audit of the same site if you ran one moments ago, so it is instant.
How to use the AI Visibility Audit
- 1Type your website address — example.com is enough.
- 2Press Audit site and wait for the crawl. If you just ran the SEO Audit on the same site, this is instant.
- 3Check the AI crawler table first: are the crawlers you want reaching your site?
- 4Work through the issues from Critical down, using the “How to fix” note on each.
- 5Download the report or copy the link to share it with whoever will make the changes.
Frequently asked questions
What is an AI visibility audit?
A check of how well a website is set up to be discovered, understood and potentially referenced by AI search and assistants. It looks at whether AI crawlers can reach your pages, whether the content is in the HTML they receive, how clearly your brand and organisation are described, and whether your pages are structured so that an answer can be lifted from them and attributed to you.
Will fixing these issues get me cited by ChatGPT, Perplexity or Google’s AI features?
Nobody can promise that, and no tool outside those companies can measure it. What this audit measures is readiness: how many well-established barriers a site has between it and being included at all. Fixing them removes reasons you might be missed; it does not guarantee you will be chosen. Treat the score as a to-do list, not a prediction.
Which AI crawlers does it check?
It reads your robots.txt against the crawlers the vendors publish: OpenAI’s GPTBot, OAI-SearchBot and ChatGPT-User; Anthropic’s ClaudeBot, Claude-SearchBot and Claude-User; Perplexity’s PerplexityBot and Perplexity-User; Googlebot and the Google-Extended control token; Bingbot; Applebot and Applebot-Extended; Common Crawl’s CCBot; and others. The list changes as vendors add and rename bots, so it is a snapshot of what is documented today.
Should I block GPTBot and other AI training crawlers?
That is your decision, and the audit does not mark it as a fault. Training crawlers collect content to train models; blocking them does not remove your site from AI search, which uses different crawlers. What the audit does flag is blocking the search and on-demand crawlers, because that keeps your pages out of AI answers entirely — and blanket rules that block every bot without meaning to.
Why does JavaScript matter for AI visibility?
Most AI crawlers fetch the HTML your server sends and do not run scripts. If a page is an empty shell that JavaScript fills in, they see nothing to read. The audit flags those pages as one of its most serious findings. Server-side rendering or static generation fixes it.
What is llms.txt, and do I need one?
llms.txt is a proposal for a plain-text file that summarises a site for language models. It is not a standard, and no major AI provider has confirmed that it uses the file, so the audit treats a missing one as a low-priority note and never as something that costs you score. Adding one is cheap and harmless; do not expect it to change anything by itself.
What can this audit not tell me?
Whether an AI has actually cited you, or what it says about your brand — that needs live queries against the AI platforms, which this does not run. It also cannot see blocking that happens outside robots.txt, such as a firewall or CDN rule that turns AI crawlers away by their user-agent. If you use a service like that, check its settings.
How is this different from the SEO Audit?
Both read the same crawl. The SEO Audit asks whether search engines can find, index and rank your pages; this one asks whether AI systems can reach, read and reference them. Many fixes help both. If you run one and then the other on the same site within a few minutes, the second reuses the first’s crawl and is instant.
What is stored, and who can see my report?
We store the address you entered and the report, so you can come back to it and share it. Anyone with the report’s link can read it — the link is long and random, and the report contains only what a crawler could see on your public pages. We store nothing about you beyond a one-way hash of your network address, used to limit how many audits one person can start.