Your robots.txt can allow every OpenAI bot, and ChatGPT may still refuse to open your site. Search Engine Journal reported on October 29 that OpenAI runs a central safety check, known inside its systems as Aura, that decides whether its web-browsing tools are allowed to connect to a given website. If a site gets flagged, tools like Codex's Browser Use and ChatGPT's live search will refuse to open it at all, completely ignoring your local settings and robots.txt rules.
Aura is a site-safety check that sits apart from OpenAI's crawlers. The company publicly lists several different web crawlers, including GPTBot for training models, OAI-SearchBot for search features, and ChatGPT-User for direct requests made by users. Aura is a separate guard: it decides whether autonomous browsing tools are allowed to visit a specific link, before any request leaves OpenAI. The name appears in OpenAI's systems and codebase, and in network traffic making checks to an endpoint for site status. It is not to be confused with Aura, which was a codename for Atlas, OpenAI's browser.
OpenAI's public help pages state that agents might be blocked from visiting certain sites for security, safety and compliance reasons, using a global blocklist, and that browsing is blocked on sites linked to illegal activity. What OpenAI does not explain publicly is the technical setup behind the system, or the exact criteria that put a site on the list.
When Aura flags a site, the browsing tool refuses the visit outright. Tests described in the report showed Codex's Browser Use returning a message that the action was rejected due to browser security policy, with the site-safety policy named as the only reason. Because the block stops the connection before any request leaves OpenAI, the site's own server logs show no record of the failed visit at all. From the site owner's side, nothing arrives. There is simply silence where ChatGPT traffic should be.
A flagged decision is saved locally for 24 hours. OpenAI engineers have said network glitches during status checks default to allowing access, so a failed check does not block a site by accident. But once a site is explicitly flagged, the block holds. There is currently no public way to find out why a website was blocked, no self-service page to check a site's status, and no formal route to ask for a review.
The report centres on a real case: a major international publisher that had been blocked since May 2026. Since that month, ChatGPT repeatedly failed to load the publisher's pages, returning general error messages without ever trying to connect. Tests using the Codex command line tool and desktop apps confirmed that Browser Use explicitly refused to visit the site, and comparison tests showed the failure came from a mistaken safety label rather than any mistake in the website's setup.
The publisher's own traffic figures made the picture stranger. Its logs showed only around 5,000 successful connections served to OpenAI's training crawlers over 30 days, while other AI crawlers could still access the site normally. Support staff avoided naming the internal Aura system directly, but admitted in writing that a safety block was active. The publisher is unnamed, and OpenAI has not commented on the case, so the evidence rests on one outlet's account. Even so, it is a documented example of a normal, well-established site losing ChatGPT visibility for months without explanation.
The instinct of most SEOs is to reach for robots.txt, but this is a different layer of control. A crawl permission, a browser permission and a safety decision answer different questions, and changing one does not establish that the others will permit access. Allowing GPTBot and OAI-SearchBot in robots.txt controls crawling and training collection. It does not touch the site-safety check that governs whether a live browsing tool may open a page.
That distinction cuts both ways. A successful GPTBot request proves only that the request succeeded, not that a ChatGPT browsing session can open the same page. And a site that blocks OpenAI's crawlers in robots.txt may still be reachable by user-triggered browsing, since OpenAI says robots.txt rules may not apply to those user-initiated requests. Site owners who treat every OpenAI request as the same kind of interaction will misread both their logs and their visibility.
ChatGPT is becoming a discovery channel, and an Aura block removes a site from it silently. There is no Search Console warning, no crawl error and no log entry, which means the first sign of a problem is usually a drop in referral traffic that looks like nothing changed. For publishers and brands that depend on AI search referrals, the practical step is to test directly: ask ChatGPT to open your pages. If it cannot, while other AI crawlers reach the site fine, a platform-level block is a real possibility.
The wider lesson is that AI search visibility now depends on more than crawling and indexing. There is a safety layer above the crawler, controlled by the platform, with no public criteria and no appeal process. Link builders should treat AI-browser accessibility as a check of its own, alongside robots.txt and indexing. Until OpenAI publishes a way to check or challenge a classification, the only defence is noticing the silence early.
Sources: Search Engine Journal, October 29, 2026.
Related reading on this site: Brave Sells Its Search Index to AI — Your Site Is Probably In It, Cloudflare CEO: AI Agent Optimization Is the New SEO, Google: Technical SEO Remains Key for AI SEO, ChatGPT Sends Just 0.62% of Google's Organic Traffic, AI Assistants Hit 76 Billion Monthly Sessions, Graphite Estimates, and Google Rank Data Issues, Lighthouse Update and AI Opt-Out.
Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.
Start free trial