How to cited by ChatGPT.
Being cited by ChatGPT is not a single-feature fix — it's a cluster of signals working together. This is the minimum-viable setup that, in our data, produces a measurable citation rate bump within 14 days.
The short answer
Getting cited by ChatGPT means being easy to quote through Bing's grounding layer. Ship a well-formed llms.txt at your root, put FAQPage JSON-LD on your three highest-intent pages, earn one organic mention on a forum the model already trusts, push the changed URLs through IndexNow, then run a fixed query panel on a schedule so the change is visible.
Before you start
Four kinds of access decide whether this is a twenty-minute job or a sprint ticket. You need write access to the domain root, the ability to put a JSON-LD block into server-rendered HTML, ownership of a Bing Webmaster Tools property for the domain, and a forum account with enough history that its posts are not auto-filtered. None of these are hard. All of them are owned by different people in most companies, which is the actual obstacle.
- Root path control — /llms.txt has to be served from the apex, not from a CMS page or a redirect.
- Server-side head injection — schema written by client-side JavaScript is invisible to the Bingbot-class fetchers that feed the grounding layer.
- Bing Webmaster Tools ownership — without it you cannot mint an IndexNow key or read a crawl date.
- A query panel of 20–50 buyer questions written before you change anything, so a baseline exists to compare against.
Twenty minutes is the working time for someone holding all four. For a real team, budget a week of calendar time: the root file needs a deploy, the schema block needs review, and the forum mention needs a human who genuinely uses the product. Headless storefronts and locked-down DNS are the two setups that reliably blow the estimate, because in both cases the root path belongs to infrastructure rather than to marketing.
Why this works
ChatGPT with browsing does not rank your page. It reconstructs an answer out of chunks, and Bing's grounding layer supplies them — which is why every artefact here is aimed at that layer rather than at the model. llms.txt collapses the disambiguation cost of your site from four hundred similar titles down to ten described URLs plus a prose intro. FAQPage markup hands the retriever a question-and-answer pair already cut to the size of a citation, with the boundaries declared instead of inferred by a chunker.
The forum mention works on a different axis entirely. Structured markup makes you quotable; third-party corroboration is what lets a model attach a claim to a brand without hedging it into uselessness. One credible thread does something your own copy structurally cannot, because it puts the claim somewhere you do not control. That is also why paid placements underperform organic ones by more than their removal rate would suggest.
Aggarwal et al. measured up to roughly a 40% improvement in source visibility inside generative-engine responses from methods of exactly this shape: structure plus corroboration, not keyword density.
The steps
- 01
Publish llms.txt at your root
Create a Markdown file at /llms.txt with a one-sentence site description in a blockquote, a short paragraph of context, and a curated list of 10–30 URLs that best explain your product. ChatGPT browses through Bing's grounding layer, and that layer uses llms.txt as a disambiguation signal when it decides which of your pages is the canonical explanation of a concept. The file must be served from the apex path — not a CMS page at /pages/llms-txt, and not a redirect. Keep it to the URLs that actually explain the product; this is not a second sitemap. See our dedicated post on the spec.
Check
You'll know it worked when curl -I https://yoursite.com/llms.txt returns 200 with a text/plain or text/markdown content type and no redirect hop in between.
- 02
Add FAQ schema to your top three pages
Pick the three pages that best represent your category — the ones that answer a buying question rather than describe a feature. Add FAQPage JSON-LD with 5–8 questions answered in 40–120 words each, and render the same text visibly on the page. Use your buyers' actual phrasing: scrape support tickets and r/yourvertical for the wordings that recur, then use them verbatim. What the markup buys you is an explicit question-to-answer boundary, so the retriever quotes a whole answer instead of a span it guessed at. This is the single largest delta we see in ChatGPT citation rate.
Check
You'll know it worked when validator.schema.org parses each URL and reports one FAQPage node with exactly the number of Question children you wrote, and zero errors.
- 03
Get one organic Reddit mention
Not a paid placement. A real post by a customer, or a founder-level contribution to a thread where your product is genuinely relevant and disclosed as yours. In our citation data Reddit accounts for roughly 23% of ChatGPT's third-party citations, more than any other single domain. The mechanism is corroboration: the model can attach a claim to your brand without hedging because somebody who is not you said it, somewhere you do not control. Promotional posts get removed or filtered, and a removed comment is invisible to crawlers regardless of what your screenshot shows.
Check
You'll know it worked when the thread URL loads in a logged-out browser session with your comment still visible — a shadow-filtered comment renders for you and for nobody else.
- 04
Submit to Bing IndexNow
Bing operates the grounding layer for ChatGPT's browsing mode, so getting your changed URLs into Bing fast is the whole point of this step. The IndexNow endpoint accepts a key file and a list of URLs and pushes them to participating engines — Bing and Yandex — in seconds rather than waiting on a crawl cycle. Use your CMS's IndexNow plugin or call the endpoint directly; see indexnow.org/documentation. Google does not participate in IndexNow, and its Indexing API is documented only for JobPosting and BroadcastEvent, so use a sitemap there instead.
Check
You'll know it worked when the IndexNow endpoint returns a 200 or 202 and Bing Webmaster Tools' URL inspection shows a crawl date later than your submission.
- 05
Measure — don't guess
ChatGPT will not tell you when it cites you. You have to run your own query panel against it on a schedule and log every response. Build a list of 20–50 buyer-intent questions — never your brand name, which always returns you and therefore measures nothing — and issue each one in a clean session with no memory and no chat history, so what you capture is the model's baseline prior rather than a personalization artefact. AIRank does this automatically on a six-hour cadence; alternatively, script it against the OpenAI API and a small cron job.
Check
You'll know it worked when your log holds at least two complete runs of the full panel, so the second run gives you a variance baseline instead of a single unrepeatable data point.
How to verify it worked
Verification is a panel-level measurement, never a single query. Run all 20–50 queries before you ship anything and store the raw responses — that is your baseline, and you cannot reconstruct it afterwards. Re-run the identical panel weekly with a clean session per query, no memory and no chat history, so week two is comparable to week one rather than to whatever you happened to ask in between.
A 10–15% week-over-week swing on any single query is normal, so the number that matters is how many distinct queries in the panel cite you at all, smoothed over a 7-day trailing window. A real improvement looks like new queries entering the cited set and staying there for two consecutive weeks. One query flipping on and back off is variance, and chasing it will burn a month.
Timing
Week one is usually flat while Bing re-scores the changed URLs, and the curve steepens in week two. Judging this work before day ten tells you nothing at all.
Three ways this goes wrong
- The brand-query mirage. Symptom: your panel reports a healthy citation rate that never moves no matter what you ship. Cause: most probes contain your brand name, and a branded query almost always returns your own site, so it measures nothing but your existence. Fix: delete every branded probe and replace it with buyer-intent phrasing — best X for Y under a price, how do I do Z, is A a good alternative to B. Your number will drop hard. That lower number is the real one, and it is the only one that can improve.
- The single-session illusion. Symptom: you ran the query once, saw no citation, and concluded the change failed. Cause: retrieval layers are non-deterministic even at temperature zero, so one sample is an anecdote rather than a measurement. Fix: issue every query at least three times per cycle on the same platform and record the citation rate rather than the citation. Treat anything shorter than three consecutive weeks of trend as noise, and never compare a single Tuesday against a single Sunday.
- The invisible-head deploy. Symptom: your FAQPage JSON-LD validates perfectly in a browser devtools panel, but crawlers behave as though the markup does not exist. Cause: the block is injected by client-side JavaScript after hydration, and the fetchers feeding the grounding layer do not reliably execute it. Fix: request the page with curl and search the raw response body for the string FAQPage. If it is not in the bytes the server sent, move the block into server-rendered HTML and stop trusting the rendered DOM as evidence.
What to expect
Expect the first citation bump within 10–14 days of shipping all five steps. Week 1 is usually flat — the Bing index needs time to re-score — and the curve steepens in week 2. The biggest variable is whether step 3 lands; organic Reddit is the amplifier.
Does ChatGPT actually read llms.txt?
Not directly — OpenAI's GPTBot does not consume it. Ship it anyway, because Bing's grounding layer, which ChatGPT browses through, uses it as a disambiguation signal, and Claude and Perplexity read it more literally. llms.txt is a proposal rather than a ratified standard, so support varies by crawler. Treat it as cheap insurance across four platforms rather than a lever on one.
How many pages need FAQ schema before it matters?
Three is the working minimum, and they should be your highest-intent pages. AIRank's rubric awards the FAQPage points once, for having it on at least one high-intent page, so pages two and three are not about the score at all. They exist so the retriever has more than one pre-cut chunk to reach for when a query lands slightly off your main page's topic.
Will a paid Reddit placement work as well as an organic one?
No, and it is more likely to hurt. Promotional posts get removed or shadow-filtered, and a removed comment is invisible to crawlers no matter what your screenshot shows. What the model is corroborating is that somebody other than you said the thing. A founder answering a real question in a thread where the product is relevant clears that bar. A bought placement does not.
Do I need to submit to Google too, or is IndexNow enough?
IndexNow reaches Bing and Yandex, which covers the layer ChatGPT browses through. Google does not participate. Google's Indexing API is documented only for JobPosting and BroadcastEvent, so it is the wrong tool for general content — use a sitemap plus Search Console URL inspection there, and accept that Google's ingest is slower than the seconds IndexNow buys you on Bing.
How long before the first citation shows up?
Ten to fourteen days after all five steps ship, with week one typically flat. The Bing index has to re-score the changed URLs before anything can propagate, and a forum thread needs time to accumulate its own inbound signals. If nothing has moved by day twenty-one, the failure is almost always step three: the corroboration never actually landed.
Written by
The AIRank Editorial Team
Research & editorial, AIRank
The AIRank editorial team runs the 47-point scanner, the Observer pings, and the GEO research programme every week. Writing is reviewed by the core engineers who build the Injector, Blaster, and Surgeon agents.
Last reviewed
About the team →