SEO gets you listed
GEO gets you quoted

SEO tooling audits the path to a ranking. willaicite audits the path to a citation. Five places the two roads split.

1. The block robots.txt won’t admit to

   willaicite fetches your page twice, once as an ordinary browser and once wearing an AI crawler’s user agent, then compares what comes back. A CDN firewall rule like Cloudflare’s one-click “block AI bots” toggle returns 403 to the real crawler while robots.txt keeps saying allowed. SEO crawlers never walk the AI-bot path, so they report clean while the engine silently drops your page.

   check	result	meaning
   robots.txt, GPTBot	allowed	what every SEO tool reads
   fetch, browser UA	200 OK	what your monitoring sees
   fetch, GPTBot UA	403 Forbidden	what the engine actually gets

2. The single-page app nobody’s reading

   Googlebot renders JavaScript; so does Lighthouse. GPTBot, ClaudeBot and PerplexityBot do not; they see whatever the server sends and nothing more. A client-rendered page audits perfectly and arrives at the answer engine as an empty shell. willaicite scores how much of your content survives in the raw HTML, from the exact no-JavaScript vantage those crawlers have.

   browser · JS executed

   AI crawler · raw HTML

   <div id="root"></div>

3. The outbound-citation inversion

   Classic SEO folklore says external links leak PageRank, so pages hoard authority and cite no one. The GEO study (Aggarwal et al., KDD 2024) measured the opposite effect on AI visibility: citing sources lifted it 24.9 percent, statistics 25.9 percent, and quotations 27.8 percent. One benchmark, directional rather than guaranteed. But it means optimizing for the ranking can quietly cost you the quote.

   citing sources+24.9%

   statistics+25.9%

   quotations+27.8%

4. A verdict per engine, weighed by what it costs you

   “Is Googlebot allowed” is one question. willaicite asks it for a roster of AI crawler tokens and separates retrieval crawlers, where a block means that engine can never cite you, from training-only tokens, where blocking is a legitimate policy choice rather than a citation problem. The full registry documents every token willaicite checks.

   crawler token	tier	consequence when blocked
   OAI-SearchBot	retrieval	blocked → ChatGPT can never cite you
   Claude-SearchBot	retrieval	blocked → Claude can never cite you
   PerplexityBot	retrieval	blocked → Perplexity can never cite you
   GPTBot · ClaudeBot · CCBot	training	blocking is a policy choice, not a citation bug

5. Is there a liftable answer?

   Engines quote a chunk, verbatim. willaicite checks whether one exists: a self-contained answer near the top of the page, headings phrased as the questions people actually ask, an FAQ ready to be lifted whole. A page that opens with a sentence like willaicite is a free audit that scores citation readiness hands the engine its quote; a page that opens with a hero animation hands it nothing. You can rank first for a query and still contain nothing an engine can use.

   • ✓self-contained definition in the first screenful: “X is …”
   • ✓headings phrased as questions users ask
   • ✗no FAQ: nothing an engine can lift whole

Every audit scores the same seven dimensions, weighted by how often each one decides whether a citation happens.

1. 01 AI crawler access wt high Can the engines that cite pages fetch this one at all: per crawler token, robots.txt and firewall both.
2. 02 Renderability wt high How much of the content survives in raw HTML, with no JavaScript executed.
3. 03 Answer-readiness wt high Is there a self-contained, liftable answer near the top, under question-shaped headings.
4. 04 Evidence density wt high The material engines prefer to quote: statistics, quotations and cited sources.
5. 05 Structured data wt medium Schema.org markup that helps Google AI Overviews and entity trust.
6. 06 Freshness wt medium Visible and machine-readable dates; engines discount the undatable.
7. 07 Entity & E-E-A-T wt medium A nameable author, organization and provenance an engine can attribute.