How to Show Up in ChatGPT
Allow OAI-SearchBot, ship a page the fetch can quote, then verify with crawler logs and a prompt list. Content without a 200 is not a ChatGPT strategy.
Showing up in ChatGPT is a pipeline. Allow the search crawler. Publish a URL that states the claim. Confirm the bot hit it. Confirm the answer cited it. Most "GEO content" skips the fetch and the log, then blames the model.
OpenAI's publisher FAQ and bot documentation are the spec. We will not outrank them with adjectives. Any public site can appear in ChatGPT search. Summaries and snippets need OAI-SearchBot unblocked. Referrals carry utm_source=chatgpt.com.
Fetch layer
Allow OAI-SearchBot. That is search surfacing. Allow the published IP ranges too. Robots.txt can take about 24 hours.
GPTBot is training. You can split them. If both are allowed, OpenAI may reuse one crawl. That is their note, not a content tactic.
ChatGPT-User is a person-triggered GET (a question in ChatGPT, Custom GPTs). It does not replace SearchBot in robots.txt. OpenAI says robots.txt may not apply because a user asked. It is not used to decide Search appearance. Do not use User as your Search opt-in.
If security "blocks AI bots," check whether they bundled SearchBot with scrapers. OpenAI publishes IP ranges for a reason. User-agent matching without IPs is theater. A 403 on the money URL is an infra ticket. Stop the writer.
If a disallowed URL still arrives via a third party, ChatGPT Atlas may show only title plus link. The FAQ: use noindex if you want that gone, and the crawler must be allowed to read the tag. Disallow plus hope is how tags never apply.
Page layer
HTML the bot can see. Answer in the first sentences under the heading a buyer would ask. Original detail beats another "best X in 2026" clone. Google's guide calls that non-commodity content. Same instinct, different engine. Google also says it does not use llms.txt for Search. OpenAI's FAQ does not make one a prerequisite either. Do not stall a publish on a special file.
Stable URLs. Internal links. A sitemap. There is no ChatGPT submit console.
Promptwatch Content Agents can open a gap from tracked prompts and push to Webflow or Framer after a human accepts. WordPress is not live. Essential includes 5 AEO articles at $95/mo, but it does not include Agent Analytics. On Essential, check your own server or CDN logs before drafting. Professional first adds 25M Promptwatch crawler logs. If that view shows a 403, skip the agent because the problem is not the draft.
Proof layer
Explore: 10 ChatGPT prompts, free. Enough to see a hole. Essential is the first tier for a larger list, citation analytics, and visitor analytics, with country targeting only. Compare your URL with Reddit or a roundup, then put the visitor script or GTM data for utm_source=chatgpt.com next to the mention, not instead of it. A referral without a stored citation can happen. A citation without a session can happen. Report both.
Work in this order: fetch errors, offsite citations, then a draft. Professional can bring the fetch evidence into Agent Analytics and Unified Actions. Paid checks are daily, not a pager.
Relixir will talk autonomous CMS publish. Live price is Custom. Jasper GEO sits on Business, custom. Neither replaces SearchBot access.
Otterly from $29/mo will not close this loop. It counts mentions. Peec AI we leave last.
Do this Monday
Allow SearchBot. Inspect one money URL in logs against published IPs. Write or update one page that answers one purchase question in visible text. Track that question for two weeks. If the answer never moves, you did not fail "ChatGPT SEO." You failed a fetch or you are not the source. Fix that before you generate twenty articles.
Show up, here, means a stored answer that cites a URL you control after a 200 you can point at. Allow the bot. Ship the page. Keep the log. Product: promptwatch.com.