How to get your site cited by ChatGPT and Perplexity (AEO in practice)
Short answer: to get cited in AI answers you need three things working together — content an engine can extract (clear Q&A, schema, summaries), a technically healthy and indexable site, and brand mentions on the external sources those engines trust. Then you measure your citation share and improve it. There's no single tag to add; it's a loop.
This is the practical companion to our AEO overview. Below is what actually moves the needle, in priority order.
1. Make your content extractable
Answer engines lift sentences, not pages. Help them:
- Lead with the answer. Put a one- or two-sentence direct answer at the top of each page (the "short answer" pattern this post uses). Engines quote these.
- Phrase headings as questions your buyers actually type, and answer them immediately underneath.
- Add FAQPage schema mirroring a visible FAQ. It gives the engine a clean question→answer pair to lift.
- Keep paragraphs tight. A 60-word answer is more quotable than a 300-word essay.
2. Be technically eligible
Engines source candidates from search indexes. If you're not indexable or you're slow, you never enter the pool:
- Ship server-rendered HTML, a
sitemap.xml, and arobots.txtthat explicitly allows the AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, and friends). Being absent from robots is a silent reason sites never get cited. - Fix Core Web Vitals — poor mobile LCP keeps you out of Google's AI Overviews.
- Add a machine-readable
llms.txtdescribing your product so crawler agents understand you with low effort.
3. Earn external mentions
This is the slowest but highest-leverage lever. Engines cite the brands that appear on sources they already trust — review sites, comparison articles, community threads, reputable directories. Concretely:
- Publish honest comparison pages ("X vs Y") so there's a structured answer to "alternatives to X" that includes you.
- Get listed where your category is discussed (Product Hunt, dev communities, industry roundups).
- Encourage genuine reviews and mentions; engines weight third-party corroboration heavily.
4. Measure, then iterate
You can't improve what you don't measure. The honest method is probing: ask each engine the buyer-intent questions your customers ask — with web search enabled — and count how often you're cited. Track the rate per engine over time and re-check after each change.
OctopusLab automates this for every project: five generated buyer-intent prompts across ChatGPT, Perplexity, Claude and Gemini, scored on a schedule, with an AI advisor that reads the answers (including who gets cited instead of you) and returns a prioritized plan. That last part matters — the fastest path to being cited is often "write the comparison page the engine is currently quoting from a competitor."
What to expect
AEO is weeks, not days. New content has to be indexed and your brand has to accumulate on trusted sources before citations appear. A score of 0% at launch is normal and not a failure — it's the baseline you grow from. The teams that win treat it like SEO in 2010: unglamorous, compounding, measured.
FAQ
How do I get cited by ChatGPT? Make your content extractable (lead with the answer, FAQ schema), be technically indexable and fast, earn mentions on sources ChatGPT's search trusts, then measure your citation rate on real buyer prompts and iterate.
Is AEO different from SEO?
They overlap — fast, indexable, well-structured pages help both — but AEO additionally rewards explicit Q&A structure, extractable summaries, llms.txt, and third-party brand mentions, because the goal is being quoted in an answer, not ranked in a list.
How long until I see citations? Usually weeks. Engines must index new content and encounter your brand on trusted external sources first. Continuous measurement is how you see the trend before the wins land.
Can I track whether AI engines cite my site? Yes — probe each engine with your target prompts and parse the answers for your domain. OctopusLab does this automatically per project and reports citation share per engine.
Want updates? Watch github.com/jarwiscode/OctopusLab or write to hello@octopus-lab.app.