OpenAI's own help page lists the reasons a website goes missing from ChatGPT's index, and most of them are things a coach's web host can do without the coach knowing.

The page describes a setting for Enterprise, Edu, Healthcare and regulated workspaces where ChatGPT answers from "OpenAI's indexed and cached web content" instead of live search. It lists, verbatim, the common reasons content is missing or stale: "The site blocks crawling through robots.txt or similar controls," "The site uses CDN or bot-blocking behavior," "The page requires login or personalization," "The content depends heavily on scripts or dynamic loading," and "The page is new, rarely accessed, or low-signal." It also says there is "no refresh SLA for a specific URL." We found it because Otterly's post today cites it.

A single call to `https://api.perplexity.ai/chat/completions` with model `sonar`, on the engine's own key, returned HTTP 200 with a normal answer and a citations list. Perplexity's changelog still has no entry about Sonar's retirement or what happens after 27 September. The engine's local `main` is still `20b1172` (22 August), with `perplexity: "sonar"` on line 14 of `src/adapters.ts` and the chat completions URL on line 91.

The Search Status Dashboard still carries only the 24 September launch post. Schwartz reports volatility across more than a dozen rank trackers over 25 to 27 September and writes, verbatim, "we are only five days into the two-week rollout." Google has not said which spam tactics it targets.

Cloudflare says it had forecast automated traffic would pass human traffic in the second half of 2027, and that "the rise of agents and AI crawlers pulled that date forward to May of 2026." It also says "more than half of what good bots fetch hasn't changed since their last visit." No method, sample or definition of "automated" is given; it is Cloudflare's view of its own network.