How ChatGPT search picks and cites sources

ChatGPT search mixes a partner index, Bing among them, with pages crawled by OAI-SearchBot. It decides when to search, or you can force it in the UI. It rolled out to paid users on 31 October 2024, to all users in December 2024, and without an account in February 2025.

When it answers, it shows inline citations and a Sources panel with links. Shopping questions may show product cards. It cannot execute JavaScript, so content rendered only after scripts run is invisible to it.

There is no submission form. Your route in is to let the right crawlers in, write pages that answer directly, and appear on pages that are already being cited for your topic.

ChatGPT places small inline links at the claim it attributes, and repeats sources in a panel. The label is the site or page title. Links go to the cited URL.

An example: you ask “how to set up billing in YourProduct”. ChatGPT quotes a step from yourproduct.com/guides/getting-started, adds a link after the sentence, and shows that URL in the Sources panel.

It prefers pages that answer in the first paragraphs. Clear headings, consistent product and person names, lists, comparisons, and figures it can quote make a page easier to cite. A visible date and an author help it choose a recent, credible source across assistants as of 2026.

• Allow OAI-SearchBot in robots.txt. Blocking it makes you invisible in ChatGPT search.
• Keep content in the HTML. Do not rely on client-side rendering for key text.
• State the answer early. Put the gist in the first 1 to 3 paragraphs.
• Use headings that match the questions buyers ask. Write one page per question.
• Show a date and an author on guides and comparisons.
• Name products and people consistently across pages.
• Add lists and simple tables for steps, options and figures.
• Use descriptive, permanent URLs like /pricing and /guides/getting-started.

A fixed page looks like this: /guides/getting-started opens with “Set up YourProduct: create a workspace, add a card, invite your team.” Then a bulleted list, dated August 2026, with an author line and no content hidden behind scripts or tabs.

Generative engine optimisation is about being named and cited by assistants: ChatGPT search, Perplexity, Google AI Overviews and AI Mode, Claude, Gemini, Microsoft Copilot. It is the same aim as answer engine optimisation from the featured-snippet years. The practice is the page work you control.

1. 1

   Match the question in the H1 and H2

   If buyers ask “How to export invoices from YourProduct”, use that as the H1, and repeat it in a scannable H2 near the answer.

2. 2

   Lead with the answer, not context

   First sentence: “Go to Billing, click Export, choose CSV.” Follow with steps and edge cases. Keep setup and rationale later.

3. 3

   Use numbered steps and lists

   Assistants quote bullet and number lists. Write steps 1 to 5. Keep each step one action.

4. 4

   Include a small comparison or figure

   Add a table like Basic vs Pro limits or a one-sentence price note if relevant. Assistants lift crisp facts.

5. 5

   Stamp a recent date

   Show a visible updated date. Assistants often prefer fresher pages when many are similar.

6. 6

   Keep naming consistent

   Use the same product and feature names on /pricing, /docs and /blog. Avoid nicknames the index will not match.

On /pricing, make the plan limits a clean table, not an image. On /integrations/slack, place a three-step setup at the top, dated. On /blog/compare-yourproduct-vs-the-legacy-tool, conclude with a clear winner and a table of differences. This is the copy that gets quoted.

1. 1

   List buyer questions

   Write the top 20 questions from support and sales. Example: “yourproduct pricing”, “yourproduct alternatives”, “how to connect yourproduct to QuickBooks”.

2. 2

   Ask ChatGPT in a clean session

   Open chatgpt.com. Ask each question as buyers phrase it. If it does not search, press the search button. Screenshot the answer with the Sources panel.

3. 3

   Log every named site

   Record the names and URLs ChatGPT cites. Tag them by question and by page type, like “docs”, “comparison”, “list of tools”.

4. 4

   Repeat on the other assistants

   Run the same list on Perplexity, Claude search, Gemini, and Copilot. Compare overlaps and gaps.

5. 5

   Segment by referrer in analytics

   In your analytics, build segments for chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com. Watch them weekly.

No assistant publishes a citations report as of 2026. Your methods are asking on a schedule, reading referrers, and using trackers that automate the asking. Tools in the market include Profound, Peec AI, Otterly, Scrunch, the AI toolkits of Semrush and Ahrefs, and DataForSEO’s LLM mentions data. Pick one if you have many questions to monitor.

Three tokens control how OpenAI uses your site as of 2026. Set them explicitly in robots.txt. Treat search, on-demand fetching, and training as separate decisions.

# keep in ChatGPT search, allow on-demand fetches, block training
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: GPTBot
Disallow: /

Robots is voluntary. Blocking a training crawler does not remove data already collected. If you block answering and search crawlers like OAI-SearchBot, Bingbot or Googlebot, assistants cannot retrieve and will not cite your pages.

• JavaScript-only content. Move critical copy into the HTML source. Server render or hydrate after content is present.
• Hidden answers. Avoid accordions and tabs for the core steps. Place a concise answer above them.
• No date. Add an updated date under the title of help and comparison pages.
• Ambiguous names. Use the same feature names across the site and title tags.
• Thin product pages. Give /pricing and /features plain-language bullets with figures assistants can cite.
• Robots rules. Confirm you allow OAI-SearchBot and your CDN does not block it by IP or rate limit.

Check a page by pasting its URL into your browser’s View Source. If the key sentence is not there, ChatGPT cannot read it. For /pricing, put plan limits such as “Projects: 3, Seats: 5” in text near the top. For /guides/export-invoices, list steps 1 to 5 before screenshots.

Assistants name the pages they retrieve. Being on the lists, roundups and comparisons that already get cited is the straightest line to being named. This matters if your own site is small and new.

1. 1

   Find the cited roundups

   When you ask “best invoice tools for freelancers”, list the roundup URLs ChatGPT cites. Repeat on Perplexity and Copilot. Rank by how often they appear.

2. 2

   Pitch for inclusion

   Contact the authors with a short note and a clear reason to add YourProduct. Offer a test account and the one feature that stands out.

3. 3

   Publish your own comparison

   Write /alternatives/legacy-tool and /compare/yourproduct-vs-legacy-tool. Use a table and a date. Assistants often cite both third-party lists and vendor comparisons.

4. 4

   Keep names aligned

   Make sure your product is named the same way on your site and in outreach. Consistency helps assistants and editors match mentions.

A fixed example: /alternatives/legacy-tool opens with “The 7 best Legacy Tool alternatives in 2026” and a numbered list. Editors can cite it. Assistants can quote it. Your brand name appears in the same form across the page, the title tag and headings.

You will not get a native report of where your site was cited. Build a loop. Ask, log, ship fixes, and ask again. Treat it like keyword tracking, but for names and links in answers.

1. 1

   Weekly checks

   Run your 20 buyer questions in ChatGPT and Perplexity every week. Log names, links and positions in the Sources panel. Flag new entrants.

2. 2

   Source-focused edits

   When a rival page is cited for “yourproduct pricing”, compare structures. Rework /pricing to lead with the figures and plan limits in text.

3. 3

   Analytics segment

   Report sessions with referrers chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com. Tag pages they land on. Compare trend lines.

4. 4

   Quarterly content refresh

   Update dates and figures on your key guides and comparisons. Keep the first paragraphs stable and precise so they stay quotable.

Clicks from Google’s AI Overviews and AI Mode arrive as google.com in Search Console and analytics. They are mixed with web search. Track rankings and clicks for your question pages to see if your changes help. Use your /search-console Performance report to monitor queries and pages together.

You still need crawlable pages, titles under about 60 characters, and content that matches intent. The difference is what you optimise for: being quoted, not just ranked. That shifts layout and wording choices on key pages.

• Front-load the answer, not a teaser paragraph.
• Write one page per buyer question, not a broad hub that buries answers.
• Prefer text and tables to images of text.
• Show dates and authors on all help and comparison content.
• Use headings that restate the question in the buyer’s words.
• Avoid JS-only content for anything you want cited.