AI Content Visibility Checker

An AI visibility checker tells you whether the assistants people now ask for answers, such as ChatGPT search, Google AI Overviews, Microsoft Copilot and Perplexity, can actually read and quote one of your pages. Paste a page address and this free AI Content Visibility Checker looks at it the way those systems do. It checks whether robots.txt lets their crawlers fetch that exact path, whether noindex or nosnippet rules stop the page being quoted, and how much of the text is in the HTML before any JavaScript runs. It then looks at how the page is written and marked up: one clear H1, a short opening answer, headings people would ask as questions, lists and tables, a named author, a visible date, structured data and links to sources. Every finding comes with a plain-English fix.

How to use the AI visibility checker

1. 1 Paste the page you want quotedEnter the full address of one page, such as a guide, a service page or a product page. The checker reads that exact URL, so test the pages you most want to appear in AI answers, not just your home page.
2. 2 Check crawler access firstThe access table shows whether Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot and PerplexityBot may fetch this path under your robots.txt. A block here outweighs everything else on the page.
3. 3 Read the opening passageThe checker shows the first real paragraph after your H1, the passage an answer engine is most likely to lift. If it does not answer the question on its own in two or three sentences, rewrite it.
4. 4 Work through the warningsEach warning explains what it affects and how to fix it: adding an author and dates, breaking long text into lists, adding Article or Service schema, or linking to the sources behind your facts.
5. 5 Re-check after you publish changesResults are cached for about ten minutes. Once your edits are live, run the check again to confirm, then ask Google and Bing to recrawl the page in Search Console and Bing Webmaster Tools.

How AI answers find and quote a page

When someone asks an AI assistant a question that needs current information, the assistant usually runs a search behind the scenes, fetches a handful of pages and writes an answer from them, often with links to the pages it used. Google AI Overviews and AI Mode build on Google's own index, Microsoft Copilot builds on Bing, and ChatGPT search, Claude and Perplexity run their own crawlers alongside licensed or partner search results.

That process has two separate gates. The first is technical: the system has to be allowed to fetch the page and has to find the text when it does. The second is editorial: out of everything it fetched, it has to judge your page relevant and trustworthy, and find a passage that answers the question cleanly enough to quote. A page can fail at either gate. This checker tests the technical gate thoroughly and gives you concrete signals for the editorial one.

Nothing here is a secret ranking formula. The same things that help a person skim a page and trust it, such as a direct answer, clear headings, an author and a date, are the things that make a passage easy for a machine to extract and attribute.

Crawler access, page by page

robots.txt rules apply to paths, not just to whole sites. A site can welcome AI crawlers on its home page and still block them from /blog/ or /guides/ with a single Disallow line added years ago. That is why this checker reads the rules for the exact path you enter.

It reports five crawlers. Googlebot and Bingbot matter most, because AI Overviews and Copilot draw on the normal Google and Bing indexes; if either is blocked, the page drops out of classic search as well. OAI-SearchBot, Claude-SearchBot and PerplexityBot fetch pages so their assistants can cite them. Training crawlers such as GPTBot or Google-Extended are deliberately left out of this page check: blocking them is a reasonable choice and does not stop you being cited. Use our AI Crawler Checker for the full site-wide picture, including training bots and llms.txt.

Some content delivery networks and security services block AI crawlers at the network level, whatever robots.txt says. If this checker shows the page as allowed but you still never see AI crawler visits in your server logs, check your CDN or firewall settings too.

Indexing and snippet controls

A noindex rule in a meta robots tag or an X-Robots-Tag header removes the page from search results, and with it from the AI features built on those results. It is common on staging copies, thank-you pages and filtered listings, and it occasionally leaks onto important pages after a site migration.

Snippet controls are subtler. nosnippet, or max-snippet set to zero, tells Google not to quote any text from the page in results or AI Overviews, and Bing applies the same directive to Copilot answers. The data-nosnippet attribute does the same for individual elements, which is useful for hiding a cookie notice from snippets but harmful if it wraps your main answer. The checker flags all three, along with a canonical tag that points to a different address, because search engines usually show and cite the canonical version instead of the one you tested.

Text that exists without JavaScript

Many modern sites send a nearly empty HTML shell and build the page in the browser with JavaScript. Google can render JavaScript, though it may do so later than its first crawl. Most AI crawlers fetch the raw HTML and do not run scripts at all, so to them a client-rendered page can look blank.

The checker counts the words in the main content of the HTML your server sends, ignoring navigation, headers, footers, forms and scripts. Several hundred words of real content is a healthy sign for a guide or service page. If the count is far lower than what you see in your browser, your content is being added by JavaScript. Server-side rendering, static generation or pre-rendering fixes this without changing how the page looks.

Writing a page that can be quoted

Answer engines prefer passages that make sense on their own. A paragraph that starts with "As mentioned above" or only reaches the point after three sentences of scene-setting is hard to quote without distorting it. The checker therefore shows you the opening paragraph after your H1 and its length.

• Lead with the answer: put the direct answer to the page's main question in the first two or three sentences, roughly 40 to 60 words, then expand.
• One topic per page, named in one H1: the title tag and the H1 should describe the same subject in the words people use.
• Headings people would ask: phrase some H2s as questions, such as "How much does it cost?", and answer immediately underneath.
• Lists and tables for steps, options, prices and comparisons: they are easier to extract accurately than long paragraphs.
• Specific facts with sources: dates, figures and rules are more useful when they link to the original source.

Authorship, freshness and structured data

People and machines both judge a source partly on who stands behind it and how current it is. The checker looks for an author in your Article schema, a meta author tag or a visible byline, and for the most recent date in your schema, Open Graph article tags or time elements. A page last dated more than two years ago is flagged, because for many topics an assistant will prefer a source it can tell is current. Only change the date when you have genuinely reviewed and updated the content.

Structured data in JSON-LD states plainly what the page is, who published it and when. The checker reports every schema type it finds and passes the page when at least one describes the content, such as Article, FAQPage, HowTo, Product, Service, LocalBusiness or Organization. Schema does not guarantee rich results or citations, but it removes guesswork. Validate your markup with our Schema Markup Validator after you add it.

What this checker cannot tell you

It cannot see inside any AI system, so it cannot tell you whether your page has already been cited or how often. For that, look for referral visits from chatgpt.com, perplexity.ai and copilot.microsoft.com in your analytics, check the performance reports in Google Search Console, which include AI Overviews and AI Mode traffic within web search, and search your topic in the assistants yourself.

It also reads one page at a time and only the HTML a crawler receives. It does not judge whether your content is accurate, original or better than the competing pages, which is ultimately what decides who gets quoted. Use it to remove the technical and structural obstacles, then put your effort into making the page the most useful answer to the question.

Examples you can copy

User-agent: *
Disallow: /account/

User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
Allow: /
Disallow: /account/

Sitemap: https://www.example.com/sitemap.xml

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How often should a boiler be serviced?",
  "author": { "@type": "Person", "name": "Jane Doe", "url": "https://www.example.com/team/jane-doe" },
  "publisher": { "@type": "Organization", "name": "Example Heating" },
  "datePublished": "2026-03-04",
  "dateModified": "2026-10-01"
}
</script>

<h1>How often should a boiler be serviced?</h1>
<p>Once a year. Most manufacturers require an annual service to keep
the warranty valid, and a yearly check catches gas leaks and
carbon monoxide risks before they become dangerous.</p>
<h2>What does a boiler service include?</h2>

Common mistakes to avoid

Frequently asked questions