Why these tools exist
Search is splitting in two. Half your buyers still type into Google; the other half just ask an AI assistant "what's the best option?" and act on the short list of brands it names back. Your Google ranking does not predict whether you make that list — a page that ranks #1 can be completely absent from the AI answer above it, and a page that doesn't rank well can be the one the model cites. So AI visibility has to be checked on its own terms, directly.
Getting cited by AI comes down to three gates, in order. An engine has to be able to **read** your page (the crawler isn't blocked), **recognize** your brand as a real entity (it knows who you are), and find your content **citable** (answer-first, factual, easy to quote). Miss any one and you're invisible — and the first two are pure technical hygiene most sites get wrong by accident. These free tools check each gate so you fix the cheap problems before you spend a dollar on strategy. (Want the full method? See how it works.)
AI visibility is optimizable, not a lottery
The peer-reviewed GEO study (Aggarwal et al., KDD 2024) tested what actually moves a page's visibility in AI answers. The top methods — citing sources, adding quotations, and adding statistics — lifted visibility by up to ~40%, while keyword stuffing did effectively nothing. These tools point you straight at those levers.
The toolkit — what each free tool does
Each tool maps to one of the three gates. Run them in this order: check that AI can read you, confirm it recognizes you, then point it at your best content. The first one is the working, interactive check — the other two harden the technical foundation underneath it.
1. AI Visibility Checker — does AI actually recommend you?
The headline question. The AI Visibility Checker explains the difference between a **mention** (the AI names you in its answer) and a **citation** (it links to your domain as a source — the stronger signal, and the only one that sends a click), then hands you the working check behind it: SourceWatch's free AI SEO audit. Enter one URL and in about 15 seconds you get a 0–100 AI-readiness score, an A–F grade, whether Google's Knowledge Graph recognizes your brand, whether AI crawlers can reach the page, and your highest-impact fixes — written in plain English, not a 40-page PDF. No login to see your result.
2. llms.txt Generator — hand LLMs a clean map of your site
The llms.txt Generator builds a `/llms.txt` file in the official spec format — an H1 with your site name, a blockquote summary, then sections of curated links to your most important pages. Unlike robots.txt, which tells crawlers what *not* to touch, llms.txt points models at what matters, solving the small-context-window problem when an assistant has room for only a few of your pages. Honest framing: this is a *proposed* standard (published September 2024), not yet universally honored — Google has said it does not use it. Treat it as low-cost, forward-looking hygiene, especially for AI coding-assistant and dev-tool audiences — not a guaranteed ranking lever. (SourceWatch ships one itself.)
3. AI Crawler Checker — make sure AI can read you at all
The most expensive mistake in AI SEO is the cheapest to fix: blocking the bots by accident. The AI Crawler Checker reads your robots.txt and tells you whether GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and Google-Extended are allowed to fetch your pages. This isn't cosmetic: in the free audit, a blocked AI crawler caps your readiness score at 40, because you simply cannot be cited by an engine that can't read you. One line in a config file can erase you from AI answers — check it first.
Don't know where to start? Run the free AI SEO audit. One URL, about 15 seconds, and it checks all three gates — read, recognize, cite — at once. No card, no login to see your result.
Run the free AI SEO auditHow to use the toolkit (a 15-minute checkup)
You don't need a strategy deck to get value here — you need a baseline. Run this quick loop once and you'll know exactly which of the three gates is costing you AI visibility.
- 1
Audit one key page
Start with the free AI SEO audit on your homepage or a top landing page. The score, grade and prioritized fixes give you a single read on all three gates and tell you where the biggest problem is.
- 2
Unblock the crawlers if you're capped
If the audit (or the AI Crawler Checker) flags a blocked bot, fix robots.txt first. It's the highest-leverage change you can make — nothing else matters if AI can't read the page.
- 3
Earn entity recognition
If Google's Knowledge Graph doesn't recognize your brand, add Organization schema and keep your name, profiles and references consistent across the web so engines know who you are before they'll recommend you.
- 4
Point models at your best work
Generate an llms.txt file and publish it at your domain root as a clean, curated map of your most citable pages — a low-effort signal you can ship this week.
- 5
Then measure the trend
The free tools are a snapshot. Because AI answers drift run to run, the real signal is the trend across scheduled checks — that's the AI visibility tracker, on a 14-day trial (card optional).
Why a snapshot isn't enough on its own
Ask the same question twice and an AI engine can name different brands — the wording and the sources drift. A one-time check tells you where you stand today; tracking the same checks on a schedule turns that snapshot into a trend you can actually act on. Start free, move to tracking when you want the line, not the dot.
The gate everyone forgets: AI is crawling you far more than you think
The "can AI read you?" gate isn't academic — AI crawler traffic is exploding, and most of it never sends a visitor back. If your robots.txt blocks the wrong bot, you're opting out of a channel that's growing faster than any other, often without realizing it.
+305%
growth in GPTBot crawler traffic in a single year (May 2024 → May 2025); overall AI-crawler traffic rose ~18% (Cloudflare, July 2025)
By May 2025, Cloudflare measured GPTBot at roughly 30% of AI-crawler traffic, ClaudeBot at ~21% and Meta's crawler at ~19%. And there's a catch the AI Crawler Checker is built around: these bots take far more than they send. Cloudflare's crawl-to-click data found Anthropic crawled roughly 38,000 pages for every visitor it referred, and OpenAI about 1,000-to-1 — with training driving an estimated 80% of AI-bot activity. The practical lesson is blunt: being readable is the price of entry. Block the crawler and you get neither the citation nor the click.
Block the right bot, not every bot
The crawlers aren't interchangeable. GPTBot is OpenAI's *training* crawler; OAI-SearchBot is what surfaces you *inside* ChatGPT's answers. Block GPTBot if you don't want your content training models — but if you also block OAI-SearchBot, you've removed yourself from ChatGPT search entirely. The AI Crawler Checker and the AI crawlers glossary spell out which toggle does what.
Where the free tools stop and SourceWatch begins
We'd rather be clear than oversell. The free tools above are genuinely useful and genuinely free — but they're a point-in-time read of the *technical readiness* of your pages. They tell you whether you can be cited. They don't tell you whether you actually are, across every engine, over time. That's the job of the paid product, and the line between them is honest and bright.
| Free AI visibility tools | SourceWatch (trial / paid) | |
|---|---|---|
| Cost | Free — no card, no login to see your score | 14-day trial, card optional |
| Scope | One page, point-in-time | Your whole site, tracked on a schedule |
| AI-readiness score + fixes | Yes (the free audit) | Yes, ongoing |
| Crawler-access + Knowledge Graph check | Yes | Yes |
| Mentions, citations & sentiment across engines | No | Yes — ChatGPT, Perplexity, Gemini & Claude |
| Share of voice vs competitors | No | Yes — per engine, not a blurred average |
| The real queries the models ran | No | Yes |
| First-party AI-crawler + AI-referral capture (verified vs vendor IPs) | No | Yes — measured, not inferred |
| Works inside Claude Code (MCP server) | No | Yes — agent reads the data and acts |
| AI content generation | No | No — content *briefs* only (you write it) |
| Public REST API | No | MCP today; REST API on the roadmap |
Two things the measurement product does that a checker can't
**Moat 1 — first-party traffic, verified.** Almost every AI visibility tool *infers* your standing by firing synthetic prompts at the models and counting mentions. Useful, but it's a sample that drifts with which prompts you pick. SourceWatch adds the other half: it captures the real AI crawlers hitting your pages and the real visitors who clicked through from an AI answer — from your own first-party data, via a one-line snippet or Cloudflare Worker — and verifies each hit against published vendor IP ranges, so a spoofed user-agent can't pollute your numbers. That's ground truth, not a guess. (More on the data: AI traffic analytics.)
**Moat 2 — it works inside Claude Code.** SourceWatch ships an MCP server, so your assistant can read your visibility data and act on it — pulling your citation gaps and the real queries the models ran, in the same loop, instead of leaving you staring at a dashboard. Among self-serve tools this is effectively unique; the only comparable agent stack is enterprise-only and gated behind a separate subscription. See how it stacks up in the best AI SEO tools roundup.
What SourceWatch does NOT do (choose with eyes open)
It doesn't write your content — it produces briefs and tells you exactly what to fix, but you (or your team, or your assistant) write it. There's no public REST API yet; access today is via MCP, with REST on the roadmap. The free audit covers one page; full-site checks are on the trial. And no honest tool can promise a Google Knowledge Panel or guaranteed ROI — anyone who does is selling a coin flip.
Start free, then see the whole picture. Run the audit now, and when you want mentions, citations and share of voice tracked across every engine, start the trial — card optional.
Run the free AI SEO audit