How to get ChatGPT to recommend your brand

ChatGPT recommends brands it can verify. It builds answers from training data, live web retrieval, and its own browsing, pulling from a blend of sources: Microsoft's Bing index through the long-standing partnership, OpenAI's own crawlers, and licensed content feeds. It reaches your site through three different crawlers that most sites treat as one. If any of the three is blocked, if none of its retrieval sources hold a fresh copy of your pages, or if your brand facts conflict across the web, ChatGPT recommends a competitor it can verify instead.

Why ChatGPT skips your brand

ChatGPT fails on brands in ways the other engines do not:

1. It uses three crawlers, not one. GPTBot feeds training data, OAI-SearchBot feeds live search, and ChatGPT-User fetches pages while answering. Block one and you lose that channel. Most sites block all three without knowing.
2. Its live answers blend several retrieval sources, with Bing's index as the long-standing backbone. A site that is thin everywhere except Google is invisible to most of ChatGPT's retrieval paths.
3. It cross-checks brand facts. When your site, your LinkedIn, and a reseller disagree on the basics, ChatGPT trusts none of them and picks a brand with one consistent story.

Step 1: Allow all three crawlers

Check your robots.txt at [yourdomain.com]/robots.txt, replacing yourdomain.com with your actual domain. If nothing loads, create the file at the root of your site. Then add these rules near the top, before any broad disallow rules:

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

Know what each one does. GPTBot is the training crawler: slowest to pay off, hardest to win back once blocked. OAI-SearchBot feeds live answers and is the one that matters this week. ChatGPT-User is the browsing agent that fetches when someone asks; blocking it means ChatGPT can never check your current prices.

Step 2: Check the edge, not just the file

This is the finding our scans surface most often. The robots.txt file says allow, but Cloudflare Bot Fight Mode or an AWS WAF rule blocks GPTBot at the edge anyway. The file is what you declare; the edge is what enforces. In Cloudflare, open Security > Bots and confirm AI crawlers are not being challenged or blocked. Then verify in your own logs:

grep -i "gptbot\|oai-searchbot\|chatgpt-user" /var/log/nginx/access.log

No hits after a week means something upstream is still blocking, regardless of what the file says.

Step 3: Cover Bing, not just Google

Bing's index has fed ChatGPT since the Microsoft partnership began, and it remains one of the retrieval sources that matters. Register the site in Bing Webmaster Tools and confirm your key pages are indexed there. Brands that only watch Google Search Console miss a feed that no other engine duplicates. This step is specific to ChatGPT and Copilot.

Step 4: Reconcile your brand facts

Pick one canonical brand name, one location, one description, and make every property you control match: site, LinkedIn, resellers, directories. You cannot fix old press, but ChatGPT weights the sources you control most heavily, so fix those first.

What this guide does not cover

Getting recommended is the start. Models refresh on their own schedule, your catalog drifts, and crawler behavior changes, which is why monitoring exists. And being recommended is not being bought from: letting the agent complete the purchase is a separate job.