Content AI can read
Whether your main content and H1 are in the HTML or only loaded with JavaScript. AI crawlers do not run JavaScript, so JS-rendered content is invisible to them.
Paste your address and get two scores in seconds: one for Google SEO, one for how visible you are to AI search. Most sites are invisible to ChatGPT and never know it.
We read your home page only. No login, nothing to install.
Paste your address, read your two scores, unlock the fixes when you are ready.
Type your domain and run the check. No account, no install. The scanner reads your public home page the way Google and AI crawlers do.
You get an SEO score (how well you rank on Google) and an AEO score (how visible you are to AI search like ChatGPT, Claude and Perplexity), with the count of issues holding each one back.
Your two scores and issue counts are free. To read every issue in full and get a copy-paste prompt that fixes each, plus a check of every page, you unlock the full report for $99 once, with no subscription.
Google renders JavaScript, so it reads your site. AI crawlers do not, so a JS-built site can rank on Google and still be invisible in ChatGPT. The scanner checks both layers.
Whether your main content and H1 are in the HTML or only loaded with JavaScript. AI crawlers do not run JavaScript, so JS-rendered content is invisible to them.
Your title tags, meta descriptions and headings, the signals Google and readers use to understand the page.
JSON-LD schema (Article, FAQ, Organization) that lets AI engines lift facts from your page cleanly instead of guessing.
robots.txt, sitemap, canonical tags and whether AI crawlers like GPTBot and ClaudeBot are allowed in.
Whether ChatGPT, Claude, Perplexity and Gemini can actually read and cite your pages, the new layer most tools ignore.
An llms.txt map that tells AI engines where your content lives, plus a clear heading structure they can pull answers from. Learn how llms.txt works in the full guide.
Google renders JavaScript before it indexes a page. AI crawlers don't. A site built with React, Next.js, or any JS framework can rank on page one of Google and still be completely invisible when someone asks ChatGPT, Claude, or Perplexity a question your content answers.
More people get answers from AI search every month. When an AI engine answers a question your page could answer, it pulls from pages it can actually read and cite. If your content is locked behind client-side rendering, missing structured data, or blocked by your robots.txt, you're excluded from that answer and from the referral traffic that comes with it.
Brand mention trackers tell you whether AI names your brand. That matters, but it skips the root cause: if AI crawlers cannot read your pages, they cannot cite them no matter how strong your brand is. This checker scans your page the way GPTBot and ClaudeBot do and gives you both scores: one for traditional Google SEO, one for AI visibility (AEO). You see the exact gap between the two and which issues to fix first.
Not sure what the difference between SEO and AEO actually is? Read the full breakdown of SEO vs AEO for the technical details. If you want to go deeper on getting your site cited by AI engines, the guide on how to get cited by ChatGPT covers it step by step. For a broader look at how AI search is reshaping discovery, see how to rank in AI Overviews.
The scanner flags these in order of impact. Fix the top ones and your AEO score moves. For ongoing monitoring, the full SEO and AEO scan checks every page on a schedule.
AI crawlers don't run JavaScript. If your main content, H1, or product descriptions load only through client-side JS, they see an empty shell. Enable server-side rendering (SSR) or static site generation (SSG) for every content page. The scanner flags this under "Content AI can read".
Schema markup (Article, FAQ, Organization, HowTo) gives AI engines clean, machine-readable facts to quote instead of guessing from paragraphs. A page with valid JSON-LD is easier for AI to parse and cite accurately. The scanner checks this under "Structured data".
An llms.txt file is a plain-text sitemap built for language models. It tells AI crawlers where your important content lives, what your site does, and which pages to read first. Most sites don't have one yet, so adding it gives you an early advantage. Read how llms.txt works and how to build one.
Many sites block GPTBot, ClaudeBot, or PerplexityBot without realizing it, often inherited from a default config or a security plugin. If these crawlers can't access your pages, you're invisible to the AI engines they power. The scanner checks every major AI crawler under "Crawlability".
AI engines extract answers from structured content. Pages with descriptive H2 headings, concise paragraphs, and a direct answer at the top of each section are much easier for them to quote. For a deeper look at what makes content quotable, read about llms.txt and how AI engines discover content.
An AI visibility checker tells you whether AI search engines like ChatGPT, Claude, Perplexity and Gemini can read and cite your website. Paste your URL above and you get an AI visibility (AEO) score plus the count of issues hiding you from AI, alongside your Google SEO score. The free check shows your scores and issue counts; the full list and the copy-paste fixes are in the full report, $99 once.
Paste your URL into the scanner above. It reads your home page the way an AI crawler does and gives you an AEO score plus the count of issues hiding you from AI search. AI crawlers do not run JavaScript, so if your content loads with JavaScript they see only your navigation. The free scan tells you your score and how many issues you have; the full list and the fixes are in the full report, $99 once.
SEO is how well you rank on Google and Bing. AEO (Answer Engine Optimization) is how visible and citable you are to AI search like ChatGPT, Claude, Perplexity and Gemini. A site can rank fine on Google, which renders JavaScript, yet be invisible to AI engines, which do not. The scanner gives you a separate score for each.
Yes. You get your SEO and AEO scores and your issue counts with no signup. To read every issue in full and get the copy-paste fix for each, plus a check of every page, you unlock the full report for $99 once, with no subscription.
The free scan is a real diagnosis: your scores and your issue counts are accurate. The detailed findings and the fixes are the part that takes work to build, so they live in the paid report, $99 once. Nothing is faked, and the locked issues are never sent to your browser, so they are real.
The free scan checks your home page, which is enough to surface most issues since they are usually site-wide. Inside Amabrik you scan every page and re-scan whenever you ship, with a score history over time.
Yes. The scanner only reads your public home page. It never logs in, never changes anything, and is safe to run on your own site.
Fix the issues the checker finds, starting with the highest severity. The most common problems are JavaScript-rendered content that AI crawlers can't read, missing structured data (JSON-LD), blocked AI crawlers in robots.txt, and no llms.txt file. Enabling server-side rendering, adding valid schema markup, and unblocking GPTBot and ClaudeBot are the three changes that move the score the most.
Brand mention trackers (like Semrush or Ahrefs AI visibility tools) tell you whether your brand name appears in AI answers. This checker tells you whether AI crawlers can technically read and cite your pages at all. If GPTBot cannot parse your content because it is rendered in JavaScript, or if your robots.txt blocks it, no brand tracker will help because the AI engine cannot use what it cannot read. This is the root-cause check that comes first.
The scanner checks whether your site is readable by GPTBot (ChatGPT and Copilot), ClaudeBot (Claude), PerplexityBot (Perplexity), and Googlebot (Gemini and AI Overviews). It verifies each crawler's access in your robots.txt and tests whether your content is available without JavaScript, which is how all AI crawlers fetch pages.
Google renders JavaScript before indexing, so it can read a React or Next.js site. AI crawlers like GPTBot do not render JavaScript. They fetch raw HTML only. If your main content loads through client-side JavaScript, Google indexes it fine but ChatGPT, Claude and Perplexity see an empty page. The scanner catches this specific gap and tells you exactly which content is hidden.