Analyze Your Website's AI Readiness
Find out how ChatGPT, Perplexity, and Google AI see your site, whether AI agents can actually use it, and what to fix so they cite you more.
How it works?
We crawl your site the way AI bots like Perplexity and ChatGPT do, then check it against the 8 agentic standards that decide whether AI agents can find and use it.
AI Readiness Score
Get a comprehensive score showing how well your website is optimized for AI search engines. Our analysis combines multiple factors into one actionable metric.
- 0-100 AI readiness score - benchmarked against what AI search engines look for
- Separate Content and Crawlability scores - know exactly which side needs work
- AI-written analysis - understand your results without reading every metric
Content
Crawlability
Agent Readiness
AI search reads your site. AI agents act on it. We check whether agents can discover, query, and transact with your site through eight emerging standards.
- Agent discovery - MCP Server Cards, A2A Agent Cards, and Agent Skills that make your site visible to the agent ecosystem
- Agent interfaces - webMCP tools, NLWeb natural-language endpoints, and Markdown responses agents can actually use
- Agentic commerce - UCP manifests and x402 micropayments that let agents buy from you
Agent Readiness
+3 bonus added to total score
and 3 more agent standards - bonus only, never subtracts
Content Analysis
and 8 more content checks
Content Analysis
We evaluate 13 content signals that determine whether AI search will cite your page - from how fact-rich your writing is to whether your headings make sense.
- Facts & Details - are there enough named entities, numbers, and data points for AI to reference?
- Unnecessary Words - filler and fluff that dilute your content's authority
- Heading Structure - clean, logical headings that AI trusts to understand your page
- Links to Sources, Author Info & Freshness - trust signals that make AI confident enough to cite you
Crawlability Analysis
Ensure AI crawlers can access and understand your site with comprehensive technical checks.
- AI Access Rules - is anything blocking AI crawlers? We check robots.txt, firewalls, meta tags, and paywall detection
- JavaScript Rendering Gap - content that bots can't see without a browser
- Loading Speed & Page Size - slow or bloated pages get skipped by crawlers
Crawlability Analysis
and 5 more crawlability checks
How AI Sees Your Site
Preview your page through the eyes of an AI crawler - stripped HTML, markdown conversion, and a side-by-side comparison of what's visible vs. hidden.
- Content visibility check - is there hidden text that AI can't see?
- Markdown conversion - what AI likes to read
- Fast vs. Deep crawlers - compare what different AI bots can see
# Welcome to Our Website ## About Our Services We provide comprehensive AI optimization services to help your website rank better in AI search results. ### Key Features - Technical SEO analysis - Content quality assessment - Content optimization > "AI search is the future of discovery" > - Industry Expert Contact us today to get started...
11
Crawlability checks
12
Content metrics
8
Agent standards
Our methodology is based on research from
Your app looks fine. The crawlers got an empty page.
AI coding tools ship React by default, and a React app with no server rendering serves crawlers one empty <div> and a bundle. GPTBot, ClaudeBot and PerplexityBot do not run that bundle, so whatever is on screen for a human is not what reaches them.
We load your page twice, once as raw HTML and once in a real headless browser, and report the difference as a number. Then we name the framework behind it so the fix is specific rather than general advice.
What GPTBot got
41
words
What a browser got
1,284
words
Detected: Next.js. Render this route on the server or pre-build it so the HTML arrives complete.
Illustrative reading from a client-rendered page
248 pages across 4 sections
+6 since last run
and 1 more section
Illustrative report for a monitored domain
Answer “why doesn’t ChatGPT mention us” with a number
One URL settles an argument about one page. The Site Health Report covers the whole domain and gives you something to hand over.
- The whole domain, not one page - every URL classified by type, each section graded on its own
- Checks a single page cannot answer - AI crawler access, llms.txt coverage, schema gaps by template
- Rerun weekly, with a diff - run it once a week per site and each run is compared to the last, so you can show what moved
- Your name on the PDF - white-label export, 10 domains, up to 5,000 pages a run
What you get the moment you scan
The same full analysis on every scan - crawlability, content intelligence, and prioritized fixes.
The exact percentage AI crawlers never see
We load your page twice, once as raw HTML and once in a real headless browser, and report the difference. GPTBot, ClaudeBot and PerplexityBot only ever get the first version. We name the framework too, so the fix matches whether you shipped Next.js, Vue, Angular or a plain Vite app.
30+ checks that take hours to run by hand
Information density, source citations, bot access, structured data, heading hierarchy, freshness signals, and eight agent standards - everything that decides whether an AI cites your page or skips it.
Or grade the whole domain, not one page
The Site Health Report crawls your site, groups it into sections, and adds checks a single page cannot answer: which AI crawlers robots.txt admits, whether llms.txt covers your key pages, and which templates lost their structured data. Rerun it each week and every run is diffed against the last.
Drop it into any pipeline
Full REST API with the same analysis you get in the dashboard. Wire it into your CI/CD, your monitoring stack, or your client reporting tools.
Give your AI agent the keys
Use Model Context Protocol to let your AI agent analyze pages, read scores, and act on results without human involvement. This is how AI-native teams operate.
Frequently Asked Questions
Everything you need to know about optimizing your website for AI search engines and getting cited in AI-generated results.
How do I get cited as a source in Perplexity or ChatGPT?
To increase your chances of being cited by AI search engines like Perplexity or ChatGPT, you need to focus on three key areas. But first, understand that traditional SEO practices serve as the foundation - if your site isn't well-optimized for search engines, AI crawlers will struggle to find and understand your content too.
- Build on strong SEO fundamentals - Solid technical SEO (page speed, mobile-friendliness, clean URLs, proper heading structure) is the foundation that makes everything else work. AI search builds on top of these same principles.
- Create authoritative, well-researched content - AI models prioritize sources that demonstrate expertise, include citations, statistics, and quotes from credible experts.
- Ensure your site is technically accessible - Make sure AI crawlers can access your content by checking your robots.txt settings and having a proper sitemap.
- Use structured data - Implement Schema.org markup so AI can easily understand the context, authorship, and topic of your content.
Our analysis tool evaluates all these factors and gives you specific recommendations to improve your citation potential.
Does Schema Markup actually help AI understand my site?
Yes, Schema Markup (structured data) significantly helps AI systems understand your content. Here's why it matters:
- It provides explicit context - Schema tells AI exactly what your content is about, whether it's an article, product, recipe, FAQ, or other content type.
- It identifies key entities - Author information, organization details, and publication dates help AI assess your content's credibility and freshness.
- It structures relationships - AI can better understand how different pieces of information on your page relate to each other.
Our tool checks whether you have Schema Markup implemented and validates that it's correctly formatted. We'll tell you exactly which Schema types are most valuable for your content.
Should I block AI bots in my robots.txt or allow them?
This depends on your goals. If you want your content to appear in AI search results and be cited by tools like ChatGPT and Perplexity, you should allow AI crawlers.
Common AI crawler user-agents include:
- GPTBot (OpenAI/ChatGPT)
- PerplexityBot (Perplexity AI)
- ClaudeBot (Anthropic)
- Google-Extended (Google AI)
Our analysis checks your robots.txt file and tells you exactly which AI crawlers are currently allowed or blocked. If you're blocking bots unintentionally, we'll flag it and show you how to fix it.
How are the results analyzed?
Our analysis combines automated technical checks with AI content evaluation:
- Content signals - We score 12 metrics: Facts & Details, Filler Words, Heading Structure, Topic Focus, Links to Sources, Schema Markup, Freshness, Originality, AI Text, Writing Style Match, Author Info, and Tables and Lists.
- Crawlability checks - We test JavaScript Rendering Gap, AI Access Rules, Site Map, HTTPS Security, Firewall detection, Loading Speed, Page Size, Meta Tags Restrictions, Paywall Block, and Internal Links.
- AI summary - An AI model reads your full report and writes a plain-language explanation of your biggest opportunities.
Each factor is scored individually. You get an overall AI Readiness Score plus separate breakdowns for Content and Crawlability.
Will I get actionable insights from the analysis?
Absolutely. Our reports are designed to be practical, not just informational. For every issue we identify, you'll receive:
- Clear explanations - We tell you exactly what's working and what needs improvement in plain language.
- Priority rankings - Issues are organized by impact so you know what to fix first.
- Specific recommendations - Not just "add Schema Markup" but which types of Schema would benefit your specific content.
- Before/after guidance - Understand what a good implementation looks like compared to your current state.
Whether you're making changes yourself or working with a developer, the report gives you everything you need to improve your AI visibility.
Which AI search engines are supported?
Our analysis helps you optimize for all major AI search platforms, including:
- ChatGPT Search - OpenAI's browsing and search capabilities
- Perplexity AI - Real-time AI-powered search with citations
- Google AI Overviews - AI-generated summaries in Google Search
- Claude - Anthropic's AI assistant with web browsing
- Microsoft Copilot - Bing-powered AI search
While each platform has slight differences, the core principles of good content, technical accessibility, and authority signals apply across all of them. Optimizing for one generally improves your visibility across all AI search tools.
Can AI bots index websites that rely mostly on JavaScript rendering?
This is a critical consideration. Most AI crawlers don't have JavaScript rendering capabilities. Only Google, which means:
- Server-side rendered content is typically indexed well
- Client-side only content (React, Vue, Angular SPAs without SSR) may be partially or completely invisible to AI crawlers
- Dynamic content loaded after page load might not be captured
While Google and Bing have the resources to render JavaScript, many AI-specific crawlers (like those from OpenAI and Anthropic) prefer "Raw HTML." If your site relies on JS to display text, you risk being invisible to the LLMs that power AI search results. We recommend using Server-Side Rendering (SSR) or Static Site Generation (SSG) to ensure your content is "AI-readable" from the millisecond a bot lands on your page.
Can your tool detect if my page uses JavaScript rendering?
Yes! Our analysis includes JavaScript rendering detection. We compare:
- Raw HTML response - What a basic crawler (or AI bot) sees without executing JavaScript
- Fully rendered page - What a browser sees after JavaScript executes
If there's a significant difference, we'll flag it and explain what content might be invisible to AI crawlers. This helps you understand if you need to implement SSR or make other changes to improve AI visibility.
Can AI agents use my website - and what is Agent Readiness?
AI search engines read your site to cite it. AI agents go further - they query it, book through it, and buy from it. Agent Readiness measures whether your site supports the standards that make that possible.
- Discovery: MCP Server Cards, A2A Agent Cards, and Agent Skills tell agents what your site can do.
- Interfaces: webMCP and NLWeb let agents call your site directly instead of scraping it; Markdown responses cut their reading cost.
- Commerce: UCP manifests and x402 micropayments let agents transact with you.
Almost no sites implement these yet, so we grade it as a pure bonus: each detected standard adds a point to your total score (up to four), and missing them never costs you anything. Every scan includes the check, free.
I built my site with Lovable, v0, Bolt or Cursor. Is it AI-ready?
Often not, and the reason is the rendering mode rather than anything you wrote. These tools default to React, and a React app without server rendering serves crawlers an empty container plus a bundle. GPTBot, ClaudeBot and PerplexityBot do not run that bundle.
The catch is that Googlebot does render, so the site can rank normally in Google while the AI crawlers receive nothing. Your analytics will not show this.
A scan reports the gap as a percentage and names the framework it detected, so you know whether it is worth fixing before you touch the build.
Can you analyze my whole site, not just one page?
Yes, that is the Site Health Report. Add a domain and we discover its pages from the sitemap, its feeds, and a bounded crawl, classify each one by type, and grade the site section by section.
A domain run also answers questions a single page cannot: which of eight AI crawlers your robots.txt admits, whether llms.txt lists the pages worth quoting, and which page templates are missing their structured data.
On paid plans you can rerun it once a week per site, and each run is diffed against the last, so you see what moved rather than just where you stand.
Fix your pages and increase your AI visibility
Scan any page. See exactly what to fix.