AI Ads, AEO and GEO for B2B SaaS and tech. Your buyers ask AI. Be the answer. See who AI recommends instead of you
  1. Home
  2. Resources
  3. Troubleshooting: fixes for common problems

Help Centre · Troubleshooting

OAI-AdsBot blocked: fixing 403 errors from Cloudflare or a WAF

By the Answerbid teamVerified 12 October 20262 min read

Short answer

If OAI-AdsBot can't reach your landing page, OpenAI can't review the ad. Allow OAI-AdsBot (required) and OAI-SearchBot (recommended) in robots.txt, allowlist them by user agent in your CDN or firewall, exempt them from CAPTCHAs and JavaScript challenges, then resubmit affected ads. Don't ask for a manual bypass.

Steps

  1. Add Allow rules for OAI-AdsBot and OAI-SearchBot in robots.txt
  2. In Cloudflare, check bot-fight and WAF rules (OAI-AdsBot is a verified bot there)
  3. Exempt the user agents from CAPTCHAs and JS challenges
  4. If you need IPs, use openai.com/adsbot.json and searchbot.json, combined with user-agent checks
  5. Check image hosts too
  6. Resubmit or re-upload ads if status doesn't update

robots.txt

User-agent: OAI-AdsBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

Questions

Does blocking GPTBot affect ads?

No. GPTBot relates to training. OAI-AdsBot only visits submitted ad pages and its data isn't used to train models.

Facts checked against the sources below on 12 October 2026. Platforms change quickly: if something here no longer matches what you see, tell us and we will update it.

Sources

Free AI Shortlist Check

See what AI tells your buyers.

Book a free 30-minute AI Shortlist Check. We run your buyers' questions through ChatGPT, Perplexity, Google AI Overviews and Copilot and walk you through the results.

  • What ChatGPT answers about your category today
  • Where your ad would appear and what it would say
  • A budget range and a 90-day plan
Get my free check
Free AI Shortlist Check30 minutes, no commitment Book it