How to Get Your Website Cited by ChatGPT and Other AI Engines
Updated — 10 min read
To get your website cited by ChatGPT and other AI engines, your pages must be three things: reachable (AI crawlers can actually fetch them), readable (the content renders as plain HTML without JavaScript), and quotable (the answers are clear, factual, and easy to lift out of the page). Miss any one of these and you become invisible to generative engines, no matter how good your traditional SEO is. This guide walks through exactly how to get cited by AI step by step, from robots.txt rules for GPTBot to llms.txt files, structured data, and answer-first writing that models love to quote.
Generative AI search is a different game from classic Google ranking. ChatGPT SEO (often called GEO, or Generative Engine Optimization) is about earning a place inside an AI-generated answer, not just a blue link on page one. The good news: the fundamentals are concrete and within your control. Below you'll learn how AI engines choose sources, the six technical and editorial steps that move the needle, engine-by-engine specifics for ChatGPT, Perplexity, Gemini, and Claude, and how to measure whether you're actually being cited.
How AI engines choose which sources to cite
Before you can rank on ChatGPT or show up in Perplexity, you need to understand the mechanics. When a modern AI engine answers a question, it usually runs a live search, retrieves a handful of candidate pages, reads them, and then synthesizes an answer that cites the sources it actually used. Three forces decide whether your page makes the cut: retrieval, trust, and extractability.
Retrieval: can the engine find and fetch your page?
AI engines don't cite pages they never saw. Retrieval depends on two things: whether your content surfaces for the query (through the engine's own index or an underlying search provider like Bing or Google), and whether the engine's crawler is allowed to fetch the URL. If your robots.txt blocks GPTBot or PerplexityBot, or your server returns errors to those user-agents, you're filtered out before the model ever reads a word.
Trust: does the model consider you a credible source?
AI engines weigh signals that look a lot like Google's E-E-A-T: established domains, named authors with real expertise, citations from other reputable sites, and content that matches what the model already learned during training. A page that agrees with the broader web and comes from a recognized brand is far more likely to be cited than an anonymous post making unusual claims.
Extractability: can the model pull a clean answer out of your page?
This is the most overlooked factor and where most sites lose AI citations. Even a trusted, reachable page won't be quoted if the answer is buried in marketing fluff, locked behind JavaScript, or scattered across ten paragraphs. Models prefer pages where the answer is stated plainly, early, and in a structure (a sentence, a list, a table) that's easy to lift verbatim. Extractable content is quotable content.
Step 1 — Let AI crawlers reach your pages
The single most common reason a site never gets cited is that its robots.txt blocks AI bots, often by accident via a security plugin or an overly aggressive CDN rule. If you want to get cited by AI, you have to explicitly let the right user-agents in. These are the real AI crawler user-agents in use as of 2026:
Major AI crawler user-agents and what they do
| User-agent | Operator | Purpose |
|---|---|---|
| GPTBot | OpenAI | Crawls pages for training and indexing |
| ChatGPT-User | OpenAI | Fetches pages live when a user's prompt triggers browsing |
| OAI-SearchBot | OpenAI | Powers ChatGPT search results and citations |
| ClaudeBot | Anthropic | Crawls pages for Claude's training and retrieval |
| anthropic-ai | Anthropic | Older Anthropic crawler identifier |
| PerplexityBot | Perplexity | Indexes pages so they can appear as Perplexity sources |
| Google-Extended | Controls use of your content for Gemini and AI Overviews training |
To appear in ChatGPT and show up in Perplexity, allow these agents. Here is a minimal robots.txt that welcomes the major AI crawlers while keeping your normal rules intact:
# Allow AI search and answer engines
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: anthropic-ai
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /
# Everyone else
User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xmlGoogle-Extended does not affect whether you rank in normal Google Search. It only governs whether Google may use your content for Gemini and AI Overviews. Blocking it removes you from those AI experiences without protecting your classic SEO.After editing robots.txt, confirm it's live at https://yourdomain.com/robots.txt and that it isn't being overridden at the server or CDN layer. Some firewalls challenge or block bot user-agents regardless of what robots.txt says, so check your CDN's bot-management settings too.
Step 2 — Make content readable without JavaScript
Here's the truth that trips up modern web apps: most AI crawlers do not run JavaScript. When GPTBot, PerplexityBot, or ClaudeBot fetch your URL, they typically receive the raw HTML your server sends and read that. If your page ships an empty <div id="root"></div> and renders everything client-side with React, Vue, or a similar framework, AI crawlers may see a blank page with no content to quote.
The fix is to deliver real HTML on the first response using server-side rendering (SSR) or static site generation (SSG). Whether you use Next.js, Nuxt, Astro, SvelteKit, or a traditional CMS, the goal is identical: the meaningful text, headings, and structured data must be present in the initial HTML, not assembled later in the browser.
- Test it the way a bot sees it. Use
curl https://yourpage.comor "View Source" (not the rendered DOM in DevTools) and confirm your headline, body copy, and answers are all there. - Prefer SSG for stable content. Articles, docs, and landing pages that don't change per-request render fastest and most reliably as static HTML.
- Avoid hiding content behind interactions. Text that only appears after a click, scroll, or tab switch is text an AI crawler often won't see.
- Keep critical content out of images. Models can't reliably quote text baked into a screenshot or infographic; mirror it in real HTML.
Step 3 — Add structured data
Structured data won't single-handedly get you cited, but it helps engines understand what your page is, who wrote it, when it was published, and which questions it answers. JSON-LD is the preferred format because it lives in a single script block and is trivial for machines to parse. For articles and FAQ-style pages, two schema types do most of the heavy lifting: Article and FAQPage.
Here's a compact FAQPage example you can adapt. It signals the exact question-and-answer pairs on your page, which maps neatly onto how AI engines retrieve and quote answers:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Which AI bots should I allow in robots.txt?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Allow GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, anthropic-ai, PerplexityBot, and Google-Extended."
}
}]
}
</script>Pair FAQPage with an Article block that names the author and includes datePublished and dateModified. Those author and freshness fields feed directly into the trust signals we covered earlier. Validate your markup with Google's Rich Results Test or the Schema.org validator before publishing.
Step 4 — Write answer-first, quotable content
This is where most of your AI citations are won or lost. AI engines reward content that leads with the answer and supports it with clean, liftable structure. The classic SEO habit of warming up with three paragraphs of context before answering the question actively hurts you here, because the model may grab a competitor's crisp one-sentence answer instead.
- Lead with the answer. State the direct answer in the first one or two sentences of the page and under each heading, then elaborate.
- Use descriptive, question-style headings. Headings like "How long until ChatGPT cites my site?" match real prompts and give models a clear anchor.
- Break answers into lists and tables. Steps, comparisons, and pros/cons in list or table form are extremely easy to extract and reuse.
- Include concrete specifics. Numbers, dates, definitions, and named tools make a passage quotable; vague claims do not.
- Write self-contained sentences. A sentence that makes sense on its own, without the paragraph around it, is far more likely to be quoted verbatim.
- Define terms plainly. A one-line definition ("GEO is the practice of optimizing content to be cited by AI answer engines") is prime citation bait.
A simple test: read any sentence on your page in isolation. If it stands alone as a clear, accurate, quotable fact, you've written for AI engines. If it only makes sense with surrounding context, tighten it.
Step 5 — Publish an llms.txt file
llms.txt is an emerging, proposed standard: a single Markdown file at the root of your domain (https://yourdomain.com/llms.txt) that gives AI systems a curated, machine-friendly map of your most important content. Think of it as a robots.txt for meaning rather than permissions, or a sitemap written for language models. Adoption is still growing and not every engine consumes it yet, but it's cheap to add and forward-looking.
A basic llms.txt uses an H1 for your site name, an optional blockquote summary, and Markdown link lists pointing to your key pages:
# Check GEO Score
> Free tool to check how well your website is optimized to be cited by ChatGPT, Perplexity, Gemini, and Claude.
## Core pages
- [GEO Score Checker](https://checkgeoscore.com/): Run a free AI-SEO audit
- [How to get cited by ChatGPT](https://checkgeoscore.com/guides/how-to-get-cited-by-chatgpt): Full guideStep 6 — Build citation authority (E-E-A-T)
Once your pages are reachable, readable, and quotable, trust becomes the deciding factor between you and a competitor with equally clean content. AI engines lean heavily on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals, much like Google does. You build that authority both on your own site and across the wider web where models learn.
- Use real, named authors. Add bylines, author bios, credentials, and links to author profiles. Anonymous content is weaker citation material.
- Keep content fresh. Show clear publish and update dates, and genuinely revise pages when facts change. Models often prefer current sources for time-sensitive questions.
- Earn mentions where models learn. Citations, links, and references from reputable sites, plus presence on platforms like Wikipedia, industry publications, and well-known communities, all increase the odds a model recognizes your brand.
- Be consistent across the web. Aligned facts about your company, products, and expertise across your site, social profiles, and third-party pages reinforce trust.
- Demonstrate first-hand experience. Original data, screenshots, case studies, and tests signal genuine expertise that models and their training data reward.
Engine-by-engine notes
The six steps above apply everywhere, but each engine has quirks worth knowing when you want to appear in ChatGPT, show up in Perplexity, or land in Google's AI Overviews.
ChatGPT
ChatGPT with search uses OpenAI's crawlers: GPTBot for indexing, OAI-SearchBot for search results, and ChatGPT-User for live fetches triggered by a prompt. Allow all three. Because ChatGPT often leans on an underlying web index, strong traditional SEO and clean, extractable answers both help you rank on ChatGPT and earn inline citations.
Perplexity
Perplexity is citation-first by design: nearly every answer lists sources prominently. To show up in Perplexity, make sure PerplexityBot can crawl you, and focus hard on answer-first structure, because Perplexity rewards pages that directly and concisely address the query. Fresh, specific, well-sourced pages tend to surface as Perplexity sources.
Gemini and Google AI Overviews
Google's AI experiences draw on Google's existing index plus content permitted via Google-Extended. Your classic Google SEO foundation matters most here, layered with structured data and answer-first formatting. Remember that allowing Google-Extended is what opts your content into Gemini and AI Overviews usage.
Claude
Anthropic's Claude uses ClaudeBot (and the older anthropic-ai identifier) to crawl the web, and Claude's web search surfaces and cites sources in answers. Allow ClaudeBot, ship server-rendered HTML, and keep your answers clean and self-contained so Claude can quote them accurately.
How to measure whether you're cited
You can't improve what you don't measure. Testing whether AI engines see and cite you is straightforward and mostly free.
- 01Confirm crawlers can fetch your page. Run
curl -A "GPTBot" https://yourpage.comand check that real content comes back, not an empty shell or a block page. - 02Run target prompts in each engine. Ask ChatGPT, Perplexity, Gemini, and Claude the exact questions your page answers, and see whether your domain appears in the citations.
- 03Test brand and topic queries. Try "What is [your brand]?" and "best tools for [your topic]" to gauge whether models already know you.
- 04Track changes over time. Re-run the same prompts monthly; citations shift as engines re-crawl and re-rank.
- 05Audit the fundamentals automatically. Run your URL through a free GEO score checker to flag missing AI-bot access, client-side-only rendering, absent structured data, or weak answer-first formatting before you go prompt-hunting.
A tool like Check GEO Score at checkgeoscore.com inspects exactly these signals and gives you a prioritized list of fixes, so you spend your time on the changes most likely to earn AI citations rather than guessing.
Frequently asked questions
Which AI bots should I allow in robots.txt?+
Allow the major AI search and answer crawlers: GPTBot, ChatGPT-User, and OAI-SearchBot (OpenAI), ClaudeBot and anthropic-ai (Anthropic), PerplexityBot (Perplexity), and Google-Extended (Google's Gemini and AI Overviews). If you want to be cited by AI, these should be allowed rather than blocked.
Can ChatGPT read JavaScript sites?+
Usually not. Most AI crawlers, including OpenAI's, fetch the raw HTML your server returns and do not execute JavaScript. If your content is rendered client-side and the initial HTML is essentially empty, the crawler may see a blank page. Use server-side rendering or static generation so your content exists in the first HTML response.
How long until ChatGPT cites my site?+
There's no fixed timeline. Live-browsing features can surface a newly published, well-structured page within days if it's reachable and relevant, while citations that depend on a crawler re-indexing your site can take weeks. Getting the fundamentals right (reachable, readable, quotable) is what shortens the wait.
Does structured data guarantee a citation?+
No. Structured data like JSON-LD helps engines understand your content and improves your odds, but it isn't a guarantee. Citations still depend on retrieval, trust, and how extractable your actual answers are. Treat structured data as one supporting signal, not a silver bullet.
How do I check if ChatGPT can see my website?+
Run curl -A "GPTBot" https://yourpage.com and confirm your real content appears in the response, then verify your robots.txt doesn't block GPTBot and that your CDN isn't challenging the bot. You can also run your URL through a free GEO score checker to confirm AI crawlers can reach and read the page.
Do I need an llms.txt file?+
It's optional today. llms.txt is a proposed standard that not every engine consumes yet, so it won't generate citations on its own. It's low effort to add and forward-looking, so it's a reasonable hedge once your robots.txt, rendering, structured data, and content are already in good shape.
What is the difference between SEO and GEO?+
Traditional SEO optimizes for ranking links in search results. GEO (Generative Engine Optimization), sometimes called ChatGPT SEO, optimizes for being cited inside AI-generated answers. They overlap heavily on fundamentals like crawlability and authority, but GEO puts extra weight on machine-readable HTML and answer-first, quotable content.
Will blocking Google-Extended hurt my Google rankings?+
No. Google-Extended only controls whether Google can use your content for Gemini and AI Overviews. It does not affect your ranking in classic Google Search. Blocking it removes you from those AI experiences without protecting your traditional SEO, so allow it if you want AI visibility.
Why isn't my high-ranking page being cited by AI?+
The most common causes are content that only renders with JavaScript, a robots.txt or CDN rule blocking AI bots, or answers buried too deep to extract cleanly. A page can rank well on Google yet still be unreachable or unquotable for AI engines, so audit reachability, rendering, and answer-first structure.
How do I make my content more quotable for AI?+
Lead with a direct answer in the first sentence under each heading, use question-style headings that match real prompts, put steps and comparisons in lists and tables, include concrete numbers and definitions, and write self-contained sentences that make sense on their own. Quotable sentences are what models lift into answers.