Short answer: ChatGPT SEO comes down to four things, in this order. Let OAI-SearchBot and ChatGPT-User reach your pages, and treat GPTBot as a separate decision about training. Serve the content as HTML that reads without JavaScript. Write passages that answer a buyer's question on their own. And make sure the facts about you are the same on the sites ChatGPT cites besides yours. Then measure on a fixed question set with brand-named questions excluded. Nobody outside OpenAI controls which brands an answer names, so the honest goal is to be eligible and to see the result clearly, not to chase a rank.

Most advice on the subject skips the first two steps because they look like plumbing. They are where the largest and most silent losses happen: a site that cannot be fetched or read is not in the running, however good its copy is. The order below is the order in which the failures stack.

Four levers, in the order to pull them01AccessOAI-SearchBot andChatGPT-User allowed;GPTBot decided apartTESTFetch as the agent02ReadableKey sentences are inthe raw HTML, with noJavaScript neededTESTcurl, then grep03LiftableFirst sentence undereach heading answerson its ownTESTRead it out of context04CorroboratedCited directories andreview sites carryyour current factsTESTAsk what you doMeasured on a fixed question set, brand-named questions excluded, ChatGPT reported on its own
Figure 1. The four things that move ChatGPT visibility, in the order to work on them, with the quickest test for each. Each step depends on the one before it: a page the agent cannot fetch cannot be lifted, and a liftable passage on an unreadable page is never seen. Source: OpenAI’s bot documentation and the checks described in this article.

Three agents, three decisions: the ChatGPT SEO step most sites get wrong

OpenAI documents separate agents with separate jobs, and each one is a separate decision for you:

AgentWhat it doesThe decision you are making
GPTBotCrawls content that may be used to train OpenAI's models.Whether your content may be used for training. Blocking it does not remove you from ChatGPT search results.
OAI-SearchBotBuilds the index that surfaces websites in ChatGPT's search features.Whether you can appear in ChatGPT search results at all.
ChatGPT-UserFetches a page because a person in ChatGPT or a Custom GPT asked for it.Whether a user who asks ChatGPT to read your page gets anything back.

There is also OAI-AdsBot, which only checks pages submitted as ChatGPT ads and has nothing to do with whether you appear in answers. The source for all four is OpenAI's bot documentation, which also publishes the IP ranges each agent uses, so a request claiming to be one of them can be checked against a list rather than trusted on its user agent.

The common mistake is to make one decision with one rule. A site decides, reasonably, that it does not want its content used for training, then writes a wildcard or flips a "block AI bots" toggle that also catches OAI-SearchBot. Nothing breaks and no error appears; the site simply stops being an option in ChatGPT search. Name each agent explicitly and write the reason next to the rule. The full file, with platform-by-platform placement, is in how to block GPTBot without disappearing from ChatGPT.

Then test what your server does rather than what the file says. A CDN or firewall rule that returns 403 to OAI-SearchBot is a block in practice, whatever robots.txt says. Fetch a key page with the agent's name as the user agent, run a normal browser request alongside it as a control, and compare. Without the control, a site that is simply down looks exactly like a site that blocks the agent.

Serve content ChatGPT's agents can actually read

Most AI crawlers do not execute JavaScript. A page whose product names, prices or answers appear only after client-side rendering is an empty shell to them, and your own analytics will never show it, because analytics run in a browser that does execute scripts. A 200 response with an empty body is a failure, not a pass.

The check takes a minute: fetch the page as the agent and look for a sentence you care about.

curl -s -A "OAI-SearchBot" https://example.com/returns/ | grep -i "days to return"

Where this bites depends on the platform. Normal Shopify storefront pages arrive as complete HTML, but anything a theme loads through the Ajax Section Rendering API, such as faceted filtering or search pagination, and content injected by apps such as reviews and Q&A blocks, is not in that HTML. On HubSpot, forms, CTAs and chat populate client-side, so offer text living inside a form is invisible to a crawler. On Webflow, site search results and anything an Embed builds at runtime are missing. Our guide to JavaScript rendering and AI crawlers covers the fixes.

Write passages that survive being lifted

An assistant lifts sentences that answer a constraint: a dimension, a material, a return window, a compatibility, a price for a stated plan. Copy written for brand tone gives it nothing to lift, however good it reads. Three habits make a page easier to quote from:

  • One question per heading, in the words a buyer would use. "How long do I have to return an order?" tells a retriever what the passage answers. "Our promise" tells it nothing.
  • The answer in the first sentence under the heading, with the subject named. "The Pro plan includes five seats" survives being cut out. "It includes five seats" does not, because "it" pointed at a heading the excerpt left behind.
  • Facts in sentences, not only in widgets. A specification table is fine, but put the facts buyers ask about into a sentence too, and keep anything important out of tabs or accordions that only render client-side.

There is some published evidence about which edits help. The GEO paper by Aggarwal and colleagues, accepted to KDD 2024, tested rewrites on generative engine responses and reports that GEO methods can boost visibility by up to 40%. Citing sources, adding quotations and adding statistics performed best, while keyword stuffing offered little to no improvement. It is a research setup rather than a test on ChatGPT itself, but it points the same way as the habits above: concrete, attributable statements beat repetition.

The quick test is to read the first two sentences under each heading out of context. If they stand on their own as a correct answer, the passage is liftable. Writing for extraction shows before-and-after rewrites.

Get the same facts confirmed off your own site

Your site is the source of truth about your product, but it is not independent evidence. A model needs the same fact from independent places before it will state it confidently, and a claim that exists only on your own domain is the weakest evidence you can offer, however well it is marked up.

Published citation data shows where that evidence tends to come from. In Profound's analysis of 680 million citations, the most-cited domain in ChatGPT was Wikipedia at 7.8% of all citations, with Reddit second at 1.8%. Neither is a brand site. In the product categories we measured in our own benchmark, likewise, a large share of citations went to marketplaces, review sites and publisher round-ups rather than to brand sites.

Where else a claim appears decides how confidently a model states itWEAKESTOnly on your own siteHowever well it is marked up,it is not independent evidence.BETTERYour site plus oneoutside pageHelps only if that page iscurrent and agrees with you.STRONGESTThe same fact in severalindependent placesMarketplaces, directories, reviewsites and round-ups all agree.The work that moves a claim up the ladderAsk ChatGPT what yourcompany does; read theanswer for wrong detailsTrace each wrong detailto the stale outsidesource it came fromCorrect the sources you can;one name and descriptioneverywhere you control
Figure 2. A claim is only as strong as the independent places that repeat it, and the work that moves it up is checking and correcting those places. Source: the corroboration method in this guide.

Your product page can be excellent and still lose the citation to a listing that carries the same facts in a third party's words. The useful work is unglamorous:

  1. Ask ChatGPT what your company does, and read the answer for wrong details, not just for whether you were named. A plausible wrong fact usually traces back to one stale outside source.
  2. Check that the marketplaces, directories and review sites cited in your category carry your current facts, prices and availability, and correct the ones you can.
  3. Use one name and one plain description everywhere you control, so spelling variants and product-line names do not split you into several entities.

Third-party corroboration covers how to find and prioritise those sources.

ChatGPT SEO tactics compared: what changes an answer and what does not

Much of the effort that goes into ChatGPT SEO lands on moves that feel productive and change nothing in the answer, while the moves that do matter look minor. Set side by side:

MoveEffect on ChatGPT answersWhy
Blocking GPTBotNone on today's answersIt is the training crawler; search runs on OAI-SearchBot.
A wildcard rule or "block AI" toggleCan remove you from ChatGPT searchIt catches OAI-SearchBot along with GPTBot.
Moving key copy out of client-side widgetsMakes the content readable at allMost AI crawlers do not run JavaScript.
Repeating the target keywordLittle to no improvementThe GEO paper found keyword stuffing among the weakest edits.
Adding sources, quotations and statisticsAmong the strongest edits testedMeasured on generative engines in research, not on ChatGPT directly.
Correcting a stale directory or review listingRemoves a source of wrong detailsModels repeat what independent pages agree on.
Tracking your "rank" in ChatGPTNone, and it misleadsAn answer is not a ranked results page; the order moves between runs.

The pattern is that access and evidence decide eligibility, and wording decides whether a passage is worth quoting once a page is eligible. Nothing on this list guarantees a mention, and anyone who promises one is describing a rank that does not exist.

Measure presence, not a rank

Measurement is where ChatGPT programmes quietly go wrong, because the easiest numbers to produce are the most flattering. These rules come from mistakes we made in our own product and then fixed:

  • Exclude questions that contain your brand name. Ask whether a named company is any good and the answer will name it. In one of our own runs 13 of 15 generated questions carried the brand name, and the score read 13% when the honest value was zero.
  • Keep mentioned, cited and recommended apart. Your page can be cited as a source while the answer recommends a competitor. Merging the two hides the gap.
  • Count only sources marked in the answer text. Counting everything that was retrieved overstated our citation figures by two to four times before we fixed it.
  • Report ChatGPT on its own before any average. In our benchmark one model named 3.5 providers per answer and another 2.1, so a blended number describes neither engine.
  • Believe a change only when it repeats. Answers vary between runs even when nothing changed. Treat a movement as real when it appears in two consecutive runs on the same question set and the same methodology.
A measurement sheet that cannot flatter youChatGPT only, reported before any average · same question set and methodology in both runs · illustrative rowsQuestionNamedCitedRecommendedRun 2Read asbest CRM for a five-person agencyyesnonosameCountsis Acme CRM any good?Excluded: the question names the brand, so the answer will tooCRM that bills clients by the hournoyesnosameCounts: citedsimple CRM for freelancersyesnoyesdiffersWait for a repeatCited means a source marked in the answer text, not every page retrieved while the answer was composed.Named, cited and recommended stay in separate columns: a page can be cited while a competitor is recommended.
Figure 3. The measurement rules above as one sheet. The rows are illustrative; the rules come from errors we made and fixed in our own product, such as a brand-named question set that read 13% when the honest value was zero. Source: InsightWonder first-party measurement rules, August 2026.

Why the order of names in one sampled answer is not a metric is argued in why rank is the wrong metric. For what ChatGPT actually did across our own measured categories, see the ChatGPT engine page.

Sources