ChatGPT can now open websites in its own browser in the cloud and act for the person using it: read a pricing page, fill in a form, prepare a booking or, with ChatGPT Wallet, pay. On November 13, 2026, OpenAI published guidance for site owners whose security settings turn those visits away. If your site sits behind Cloudflare, Vercel or another firewall, someone who asks ChatGPT to sign them up for your product may be stopped before they reach you. This guide is for a founder or small team: how to tell the cloud browser apart from OpenAI's crawlers, where to check each provider's setting, how to allow only verified visits, a 20-minute test of the task that matters to you and a log check. It is useful without a Soloop account and is not a statement from OpenAI or any provider.
The short answer
You do not need to add ChatGPT's cloud browser to an allowlist unless something blocks it. Its requests are signed with Web Bot Auth and carry a Signature-Agent header set to "https://chatgpt.com", so Cloudflare, Vercel, Akamai and HUMAN can verify them. If your bot protection blocks them, allow the verified agent by name in your provider's settings, never by turning protection off.
Then test the one task you care about, such as reading your pricing or starting a trial, from ChatGPT itself, and check what your provider or server recorded. The cloud browser is separate from ChatGPT-User, OAI-SearchBot and GPTBot, which robots.txt and IP lists control.
What OpenAI published on November 13, 2026
Alongside ChatGPT Wallet, OpenAI published a Commerce Partner Playbook for businesses. One of its pages, "Help ensure cloud browser access", says the cloud browser can already use your site and that the usual problem is a CDN or firewall blocking it by accident. OpenAI's help center has matching allowlisting steps. The same playbook covers product feeds, Wallet payments, plugins and Sign in with ChatGPT; this guide covers only access and testing.
"ChatGPT's cloud browser can already use your site. You don't need to add it to an allowlist." Security settings may block it unintentionally.
OpenAI: Help ensure cloud browser access to your siteEach request includes Signature, Signature-Input and a Signature-Agent header set to "https://chatgpt.com"; public keys are published at chatgpt.com/.well-known/http-message-signatures-directory.
OpenAI Help: ChatGPT Work's Cloud browser allowlisting (read Nov 17, 2026)OpenAI's help says some sites block automated browser agents even when they work in a person's own browser, and "each website ultimately decides whether to allow cloud browser traffic".
OpenAI Help: Using cloud browser in ChatGPTThe cloud browser is available in ChatGPT Work on paid plans in supported regions, excluding Free and Go; ChatGPT Wallet launched to a limited group of US Pro subscribers on November 13, 2026.
OpenAI Help: Using cloud browser in ChatGPT; TechCrunch, Nov 13, 2026Which OpenAI visitor is it?
OpenAI sends several kinds of traffic, and each has its own control. Blocking or allowing one does not change the others.
| Dimension | How to recognize it | What controls it |
|---|---|---|
| Cloud browser (ChatGPT Work, dots) | A normal-looking browser with a Signature-Agent header of "https://chatgpt.com"; Cloudflare shows it as dots, OpenAI, and Akamai, HUMAN and Vercel as ChatGPT Agent. | Your CDN or firewall's verified-bot or agent setting. It acts for one person, page by page. |
| ChatGPT-User | User agent containing ChatGPT-User/1.0; fetches a page when someone asks ChatGPT about it. | OpenAI says robots.txt may not apply because a user started it; it publishes IP ranges in chatgpt-user.json. |
| OAI-SearchBot | User agent containing OAI-SearchBot. | robots.txt. Blocking it keeps your pages out of ChatGPT search answers. |
| GPTBot | User agent containing GPTBot. | robots.txt. Blocking it means your content should not be used to train OpenAI's models. |
| OAI-AdsBot | User agent containing OAI-AdsBot; visits only pages submitted as ChatGPT ads. | Only relevant if you run ChatGPT ads. |
Check your provider's setting
Start with whoever answers requests before your server does. If you are not sure, your DNS provider or hosting dashboard will show whether Cloudflare, Vercel or another network sits in front of your site.
| Dimension | Where to look | What to set |
|---|---|---|
| Cloudflare | Security > Settings, filter by Bot traffic, then AI Crawler and Agent access policies. Under Personal Agents, find dots, OpenAI. | Allow (do not block). Or a WAF custom rule that allows or skips Bot Detection ID 129220581, listed as ChatGPT Operator. Cloudflare verifies the signature. |
| Vercel | The project's Firewall settings, including custom rules. | OpenAI says nothing is needed unless your own rules block it; Vercel verifies the signature on its ChatGPT Agent entry (chatgpt-operator). Check any custom rule that denies or challenges traffic. |
| Akamai | Shared Resources > Custom Bot Categories, then the Security Policy's Bot & Agent Control. | A custom category holding the verified bot ChatGPT Agent, with the action Allow. |
| HUMAN | Sightline: Policies > Traffic Policy Settings > Known bots & Crawlers. AgenticTrust: Policies > AI Agents Permissions. | ChatGPT Agent set to ON and Allow, or its permissions reviewed. |
| Another CDN, a firewall plugin or your own server | Rules that block by user agent, data-center IP, country or request rate, and challenges on sign-up or checkout. | Allow a request only after verifying its signature (RFC 9421) against OpenAI's published keys. Never allow on the header alone: anyone can send it. |
Allow it without opening the door to everything
- Allow the agent by its verified name or detection ID. A rule that matches the user agent or the Signature-Agent header alone lets anyone in who copies it.
- Keep rate limits, login protection and page-level access rules. OpenAI notes that an exception applies site-wide, so private pages must stay protected by your own access controls.
- Do not hard-code OpenAI's public key. On November 17, 2026 the key directory held one key that expires on November 24, 2026; keys rotate, so fetch them as your provider does.
- If a proxy or load balancer sits between your CDN and your server, make sure it passes the Signature, Signature-Input and Signature-Agent headers through.
- Leave crawler choices where they are. Allowing the cloud browser does not allow GPTBot, and blocking GPTBot does not block the cloud browser.
- Expect the person to approve important steps. OpenAI says ChatGPT asks for confirmation in chat before bookings, payments and other commitments, and you cannot yet set those rules for your site.
Test the one task that matters, in 20 minutes
Settings tell you what should happen; a test tells you what does. You need a paid ChatGPT plan with ChatGPT Work. Pick the single task a new customer would most likely hand to ChatGPT.
- Write the task as a customer would: "Go to example.com, find the cheapest plan that includes team accounts and start a free trial for me." Use your real domain and a test email address you control.
- Start it in ChatGPT Work and approve access to your site when asked. Note where it stops: a block page, a challenge, an empty page, a sign-in request, a confirmation or the finished task.
- At the same time, watch your provider's dashboard (in Cloudflare, Security Analytics shows a Personal Assistants category) or your server log for the same minutes.
- If it was blocked, change one setting from the provider table and run the same task again. Change nothing else at the same time.
- Record the result for each step of the task: reached, blocked by which rule, or handed back to the person. Repeat after you change your bot protection, sign-up flow or checkout.
Check your own logs for signed visits
If you run your own server, add the Signature-Agent header to your access log for a week. It is not proof on its own, since anyone can send the header, but it shows which pages the cloud browser reached and which status each got. Requests your CDN blocked never reach your server, so check the CDN's dashboard for those.
For nginx, define a format and use it: log_format agent_check '$remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$http_signature_agent"'; then access_log /var/log/nginx/access.log agent_check;. For Apache: LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" \"%{Signature-Agent}i\"" agent_check, then CustomLog with agent_check. Reload the server after the change.
Copy the script, paste it into a new file named chatgpt_browser_visits.py, read it, then run python3 chatgpt_browser_visits.py access.log access.log.1 > chatgpt-visits.csv. It needs only Python 3, reads the files on your computer and sends nothing anywhere. Pages with blocked cloud browser requests come first.
What a blocked result usually means
| Dimension | Likely cause | What to check |
|---|---|---|
| ChatGPT reports the site blocked it on the first page | An agent or AI bot policy, a country or data-center IP rule, or a challenge on every page. | The provider setting above, then any rule that challenges all traffic. |
| Pages load but sign-up or checkout fails | A CAPTCHA or bot check on the form, a rate limit on POST requests or a payment risk rule. | Rules on those paths. For payments, OpenAI is adding user signals in a Forwarded header; ask your risk or payment provider whether it reads them. |
| Your log shows 429 on several pages | Rate limiting tuned for people, not a browser that loads pages quickly. | Raise the limit for the verified agent only, not for everyone. |
| Nothing appears in your log | The CDN blocked or cached the requests, or a proxy dropped the header. | The CDN's analytics, and whether the Signature-Agent header reaches your server. |
Worked example: a booking page behind Cloudflare
This example is invented to show the workflow. A founder runs a small booking product behind Cloudflare, with the Agents policy set to Block and a WAF rule that challenges every visit to /signup.
- Test 1: the task "book a demo for next Tuesday" stops on the first page. Cloudflare's Personal Assistants widget shows 3 requests from dots, OpenAI, all blocked.
- The founder sets dots, OpenAI to Allow (do not block) and runs the same task. ChatGPT reads the pricing and booking pages, then stops at the /signup challenge.
- The founder adds a WAF custom rule, placed before the challenge rule, that skips it only for Bot Detection ID 129220581, and keeps the rate limit. Test 3 reaches the booking confirmation, where ChatGPT asks the person to confirm in chat.
- Over the next week the founder's log shows 14 cloud browser requests to pages: 12 answered 200 and 2 answered 429 on /book/slots. 12 + 2 = 14. The founder raises the rate limit for the verified agent on that path only.
Where Soloop fits
Soloop does not change your CDN, firewall or bot rules and does not read your logs. Use your provider's settings and the checks above.
Soloop helps with the work that brings people to your site in the first place: according to the Soloop manual, it can research a market with sources, write and publish X posts and replies through a connected account, send outreach through a connected Gmail account and prepare Google Ads search campaigns after setup and payment, with actions waiting for your approval by default.
Sources, limitations and refresh
OpenAI's commerce pages, crawler page and key directory were read on November 17, 2026. Its help center blocks automated reading, so its two help articles were read in a browser the same day. Cloudflare's own pages disagree on defaults for new domains: a July 2026 changelog says domains added from September 15, 2026 block agents on pages with ads, while its bots documentation, updated November 2, 2026, lists Allow as the default, so check your own setting. The Apache log format was tested on a local Apache server and the script on sample logs covering nginx and Apache quoting, blocked and redirected requests, assets, query strings, lookalike Signature-Agent values, OpenAI bots, lines without the extra field, malformed lines and .gz files; the nginx format was not run on a live nginx server here. The tables and worked example are editorial guidance, and the example is invented.
This guide will be reviewed by February 17, 2027, or sooner if OpenAI changes the cloud browser's identifiers, keys or sign-in and payment support, or Cloudflare changes its Personal Agent defaults.
Provider-by-provider steps, signature verification for other CDNs and FAQs on site-wide exceptions, other bots, feeds and plugins.
OpenAI: Help ensure cloud browser access to your siteWallet works with existing checkout pages; risk systems may block the cloud browser; user signals are being relayed in a Forwarded header.
OpenAI: Accept paymentsUser agents and controls for OAI-SearchBot, OAI-AdsBot, GPTBot and ChatGPT-User.
OpenAI: Overview of OpenAI crawlersAI Crawler and Agent access policies let you set an action for each top Personal Agent; Personal Agents inherit the Agents policy by default.
Cloudflare changelog, Nov 4, 2026Vercel's bot verification supports Web Bot Auth, so signed bots can pass Bot Protection and Challenge Mode.
Vercel changelog, Aug 12, 2025The Soloop manual describes research with sources, X posting through a connected account, Gmail outreach and Google Ads search campaigns after setup and payment; approval comes first by default. It does not configure CDNs or read logs.
Soloop product manual