Guide

How to Get Cited by ChatGPT and Perplexity

Being cited in an AI answer is the new front page. It isn't luck — it's a set of structural choices that make your page the easiest thing for an engine to quote.

By Kloovy · Updated June 18, 2026 · 8 min read

Why do AI engines cite some pages and not others?

An AI engine cites a page when it can do three things easily: reach the page, understand it, and lift a clean, quotable answer from it. Pages that hide their content behind JavaScript, bury the answer halfway down, ship no schema, or block AI crawlers get skipped — even when the writing is excellent. Everything below removes a reason for the engine to pass you over.

Step 1: Let AI crawlers in

Crawler access is binary. If your robots.txt blocks GPTBot, PerplexityBot, ClaudeBot, or Google-Extended, you earn zero citations from that engine regardless of content quality. Explicitly allow the AI crawlers you want citing you, then add an llms.txt file at your root that maps your key pages so engines can find the content that matters.

Step 2: Put the answer in the HTML source

Many AI crawlers don't execute JavaScript. If your answer is rendered client-side, they see an empty shell. Serve static HTML or server-rendered pages (SSG/SSR) so every meaningful sentence exists in the source the crawler receives. This single choice decides whether a client-only site is citable at all.

Step 3: Lead with a quotable answer block

Open each page with a 40–60 word block that answers its core question in plain, declarative prose, directly under the H1. Around 44% of AI citations come from the first ~30% of a page, so front-load the value. Write it so a single paragraph can be lifted verbatim and still make sense out of context — that is exactly what an engine does.

Step 4: Add schema

Schema gives engines a machine-readable map of your page. Add Article schema to content and FAQPage schema to question-and-answer sections. FAQ schema alone makes a page about 3.2× more likely to appear in Google AI Overviews. Keep the visible FAQ text and the schema in sync — mismatches undermine trust in both.

Step 5: Use question-shaped headings

Phrase H2s and H3s as the real questions people ask, then answer each immediately below. This mirrors how users prompt AI engines and lets a model match a query to your heading and extract the paragraph beneath it. It also makes the page scannable for humans, which is never wasted.

Step 6: Cite statistics and sources

Concrete numbers and citations raise citation odds 30–40% each, per the Princeton GEO study, because they lower a model's uncertainty about whether your claim is reliable. Use real figures where they're truthful, attribute them, and prefer specific data over adjectives. Declarative, encyclopedic tone beats hype every time.

Step 7: Build entity authority

Engines cite brands they recognize and describe consistently. Make sure your name, category, and key facts are stated the same way across your own site and the third-party sources engines trust — directories, profiles, reviews, and listicles. Consistent representation across the web is what turns a page that's quotable into a brand that's recommended.

How long until you get cited?

Set expectations honestly. Structural fixes don't surface everywhere at once — each engine re-crawls and re-indexes on its own clock. Branded and long-tail queries respond first; competitive head terms take the longest.

Key takeaways

• Let AI crawlers in — a blocked crawler means zero citations from that engine.
• Keep the answer in the HTML source; client-only rendering is invisible to many crawlers.
• Lead with a 40–60 word quotable answer under the H1.
• Add Article and FAQ schema, and keep schema in sync with visible text.
• Use question-shaped headings and back claims with cited statistics.
• Build consistent entity authority across the web, then give changes 1–6 weeks to surface.

Frequently asked questions