How to Get Your Site Cited by ChatGPT and Perplexity

A practical checklist for becoming a source an AI answer engine quotes: crawlability, extractable answers, specificity, and the measurement that actually works.

Getting cited by an answer engine comes down to three gates, in order: can it fetch you, can it parse you, and is there anything worth quoting. Most sites fail at the second one and never find out.

Here's the checklist, roughly in order of how much difference each makes.

1. Check you aren't blocking the crawlers

Start here, because everything downstream is wasted if this is wrong. Open yoursite.com/robots.txt and look for disallow rules on GPTBot, OAI-SearchBot, ClaudeBot or PerplexityBot. Plenty of sites are blocking them without realising — the rules arrived in a copied robots.txt, a security plugin, or a CDN bot-fighting preset that treats every unfamiliar agent as hostile.

Blocking them is a legitimate choice. Doing it by accident isn't. Full detail in AI crawlers and robots.txt.

2. Make sure your content exists without JavaScript

This is the big one. Several AI crawlers don't execute JavaScript, or do it unreliably. If your content is client-rendered, they may fetch your page and receive an empty shell.

Test it in ten seconds: curl -s https://yoursite.com/page | grep "a distinctive sentence". If your own words aren't in the response, an answer engine may not see them either. Fix it with server-side rendering, static generation, or at minimum pre-rendering for bots.

3. Put a self-contained answer directly under a matching heading

Answer engines extract passages, not pages. The pattern that works:

• Heading = the question as asked. "How long does a passport renewal take?" beats "Processing times".
• First two sentences = the whole answer, standing alone, needing no earlier context. If lifted out of your page and dropped into a chat window, it should still make sense.
• Then elaborate with the caveats, the workings and the edge cases.

This is also just good writing, which is why it's the recommendation that ages best.

4. Be specific enough to be safe to quote

Models are conservative about attributing vague claims. "Most users see faster builds" is unquotable. "Build time fell from 40s to 6s on a 12k-file project (v3.2, March 2026)" is quotable, because it's checkable and it carries its own context. Numbers, dates, versions and named sources all raise the odds.

5. Give the page real structure

Headings in a sane order with no skipped levels. Lists marked up as lists. Tables as tables. Comparisons as actual tables rather than three columns of divs. A parser sees markup, not layout — and a page that looks beautifully organised can be structurally flat.

6. Make authorship and freshness legible

Publish and update dates that are visible and in your structured data. A named author with real credentials. An about page that establishes who you are. None of this is a ranking trick — it's the evidence a system uses to decide whether quoting you is a risk.

7. Add structured data, but keep expectations calibrated

FAQ, HowTo, Article and Organization schema help a machine work out what your entities are. Use the free schema generator if you're hand-writing JSON-LD. What schema does not do is create authority or force a citation, whatever anyone tells you.

How to tell whether any of it worked

There's no Search Console for answer engines. What you can do:

1. Ask the questions your page should win in ChatGPT, Perplexity and Google AI Overviews, and note who gets cited. Re-check monthly. Crude, but it's ground truth.
2. Watch AI referrers in analytics. Perplexity and ChatGPT pass referral traffic; it usually shows up as a small but unusually well-converting segment.
3. Audit the mechanics directly with the AI visibility checker, or the Chrome extension for page-by-page work. It scores extractability separately from SEO and names what's blocking you.

Nobody can promise you a citation, and the honest version of this advice is that you're removing obstacles rather than pulling a lever. The upside is that most of your competitors haven't removed theirs.