Why ChatGPT Matters for Developer Relations
Developers ask ChatGPT how to do things before they open your docs, and it answers from ChatGPT search results, which only include pages OAI-SearchBot is allowed to crawl. If your documentation is not reachable or not quotable, ChatGPT explains a competitor's API instead. For DevRel, that makes docs access and structure part of adoption, not just support.
The ChatGPT Mistake to Avoid
Confusing GPTBot with OAI-SearchBot. GPTBot only collects training data, while OAI-SearchBot decides whether pages can appear in ChatGPT answers. Blocking the wrong one either removes you from answers or leaves training access open when you meant to close it.
Action Items for Developer Relations
Apply the same rule to your docs subdomain: Allow OAI-SearchBot in robots.txt
Ask ChatGPT how to do your top five tasks and check the code it returns
Give each task page a short, correct code example near the top
Keep versioned docs clear about which version is current
Report recurring wrong answers from ChatGPT to the docs team
What Developer Relations Should Track in ChatGPT
Accuracy of ChatGPT's answers for your top tasks
Docs pages ChatGPT cites or quotes
Outdated API versions ChatGPT still suggests
Developer sign-ups referred from ChatGPT
Frequently Asked Questions
How can DevRel get ChatGPT to reference our docs?
Make the docs reachable (allow OAI-SearchBot and ChatGPT-User, including on a docs subdomain), then make each task page answer one task with a correct example near the top. ChatGPT can only quote what it can fetch and parse.
Why does ChatGPT suggest an old version of our API?
Older docs, blog posts or forum answers are still public and compete with current pages. Label the current version clearly, redirect or mark retired pages, and put the current example first.
Start Optimizing ChatGPT Today
Get expert help optimizing ChatGPT and building a comprehensive AI visibility strategy for Developer Relations.