Skip to content

Free tool

Can AI crawlers read your site?

Enter a page and we run five checks that affect whether ChatGPT, Claude and Perplexity can reach and understand it.

Free. No account needed. We check one page at a time.

Your homepage is a good start. We read robots.txt, structured data, the meta description, the H1 heading and the viewport tag.

Five checks on one page: crawler access, structured data, meta description, H1 heading and viewport tag.

What this check looks at

The check runs five tests on the page you enter. Each one maps to a real reason AI crawlers miss content.

  • Crawler access. Whether your robots.txt lets AI crawlers such as GPTBot, ClaudeBot and PerplexityBot fetch your pages. A blanket Disallow: / blocks all of them, even if you only meant to stop spam bots.
  • Structured data. Whether the page carries JSON-LD (or other schema markup) that says what it is about and who made it. Without it, crawlers infer everything from body text.
  • Meta description. The short summary crawlers read first.
  • H1 heading. The main heading that names what the page is about.
  • Viewport tag. The basic mobile setup search engines expect.

We also show two hints that are not counted as checks: a rough content signal and whether the HTML mentions responsive layout.

The readiness score combines these checks into a rough guide. It is not a ranking and does not predict whether an AI answer will cite you.

Why sites score low

Most founders do not know they are blocking AI crawlers, because those crawlers did not exist when the site was built. Three patterns explain most low results:

A robots.txt that blocks everything. A Disallow: / under User-agent: *, added to stop spam crawlers, also stops GPTBot and ClaudeBot.

No structured data anywhere. Without schema markup, crawlers have to guess what the product does and can file the page under the wrong topic.

A missing or generic meta description. "Welcome to our site" tells a crawler nothing about the page.

How to fix each one

Fixing robots.txt

Open yoursite.com/robots.txt and add a group for each AI crawler you want to allow, above any wildcard rules:

robots.txt allowing AI crawlers
User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

Adding structured data

Add a JSON-LD block to the page <head> with at least a WebSite or SoftwareApplication type. Google's Rich Results Test can validate it.

Minimal JSON-LD block
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Your product",
  "applicationCategory": "BusinessApplication",
  "url": "https://yoursite.com"
}
</script>

Writing a useful meta description

One sentence, under about 155 characters, that answers "what is this page about?" Skip openers like "Learn more about" and state the thing plainly.

Questions about this check

Does a high score mean ChatGPT will cite me?

No. Citations depend on content quality, authority and how many other sources cover the topic. A low score does mean crawlers may not see your content at all.

How often should I run this?

After a migration, a CMS update or a hosting change. Deploys often overwrite robots.txt.

Do I need different settings for each AI crawler?

Only in robots.txt, where each crawler has its own user-agent name. Structured data and page basics help all of them.

Does this show whether AI crawlers actually visited?

No. It checks configuration. To see real crawler visits you need server-side data, which is what Referscope collects.

Less guessing. Clearer growth.

Connect your site today and see your first verified AI crawler by tomorrow.