Web Development
Strategy & Industry
GPTBot Is Knocking: Decide Who Gets Your Content, and Why
OpenAI published documentation on August 7 for a crawler named GPTBot. Its user-agent string, its IP ranges, and the sentence that converts a technical note into a governance event: GPTBot respects robots.txt. That means that as of this month, AI training access to your content is an explicit choice that every publisher owns, whether they know it or not. For twenty years robots.txt was plumbing. As of this month it is policy. Somebody in your building should own it.
The early returns sorted fast. Major news outlets (the Times, the wire services, the big publishers) blocked within weeks. Their math is easy to read from their lawsuits. The long tail of the web, the institutional sites this readership runs included, has largely not noticed the choice exists. Which means their answer is currently the default, and the default is yes.
This post’s job is the one the census-and-governance genre always performs when a new decision surface appears. Make the choice visible. Install the precision the discourse is already blurring. And give a frame for deciding by interest rather than reflex. Our client calls this month confirm both reflexes are circulating. The block-everything outrage and the ignore-it-entirely shrug. Neither survives contact with any one institution’s actual interests. Robots.txt went twenty years without needing strategy input. That era ended August 7.
What blocking actually governs: the precision that matters
The mechanics, stated exactly. Every policy talk we have joined this month needed these fixes in the first ten minutes. A robots.txt disallow for GPTBot governs future training crawls by this one crawler. Content OpenAI’s systems would gather going forward for model training.
It does not govern several things. Existing corpora: whatever was ingested before the block was placed is in the models that were trained on it. There is no retroactive un-ingestion, and policies premised on removal are premised on a capability that does not exist. Search indexing: GPTBot is not Googlebot. Blocking it costs no search visibility, and conflating the two is this month’s most common and most expensive confusion. What users paste into chat windows: your content, copied by a human into a prompt, travels regardless of any crawler directive. And other companies’ crawlers: the roster is already growing. The Common Crawl question, Google’s training practices, the research corpora, each with its own mechanisms or lack of them.
And the split that will shape this entire era, visible in embryo now and worth installing early: training access and answer-time fetching are different questions. A model trained on your content carries its patterns. A system that fetches and cites your pages at answer time (the browsing modes, the search hookups) touches your content in a different way, with different economics. A cite, a referral, a nod. The tooling to say different answers to those two questions (yes to fetch-with-credit, no to silent training, or any other mix) barely exists yet. The standards conversation is embryonic. The robots.txt vocabulary was never designed for it. We expect the next several years of content-access governance to be substantially about building that missing vocabulary.
Position by incentive, not reflex
The content-is-the-business camp: publishers whose business is the content itself (the news outlets, the subscription shops, the licensors) face plain logic. Training access transfers value without payment. Blocking keeps their seat at the table for the licensing market visibly forming. Their early blocks are rational strategy, not gesture.
The reach-and-trust position: institutions whose content exists to be found and trusted (the universities, the health systems, the mission publishers of this audience) face different math. Being in the systems people increasingly ask may serve the mission. The be-the-source advice, extended to training data. Absence cedes the answer space to whoever remains. We have argued for years that being what the machines cite is the emerging visibility currency.
The mixed sites, which is most sites: the answer often differs by content tier. The research and expertise tier argues for presence. The premium or licensable tier argues for protection. Current tooling barely supports tiered answers, so the practical near-term position is the site-level call plus written reasoning, revisited as the tooling matures.
The process, which matters more than the position: decide on purpose, in the meeting most teams have not scheduled. Comms, counsel, and content leads, one hour. Document the reasoning, the future-proofing against both staff turnover and policy drift. And calendar a quarterly revisit, because the crawler roster, the tooling, and the licensing market are all moving.
The access-governance era opens
August 7 is a threshold worth marking. The web’s original deal (crawl freely, index openly, send traffic back) funded twenty years of open publishing. It is being renegotiated in public. Crawler by crawler, lawsuit by lawsuit, license by license. The GPTBot documentation is the first formal instrument of the renegotiation. A named party, a declared mechanism, a choice offered.
What follows, per the direction-of-travel method we trust. More named crawlers: Google’s equivalent toggle is visibly coming, and the roster will grow. Finer-grained standards: the training-versus-fetch wording above, and the sourcing plumbing our Firefly coverage described, arriving from the supply side. A licensing market, already forming at the top of the publisher tier. And, for the institutional web, a standing new line in the governance portfolio. Content-access policy, owned, written, and reviewed. It sits next to the privacy, security, and accessibility rules the last decade installed.
The organizations that treat it that way, a policy, not a panic, will make their choices calmly as the instruments mature. The ones that don’t will discover their defaults were decisions, made silently, on the day the discovery costs something. We have written that sentence about every governance surface it has ever covered. It has never once been wrong, and the era it now applies to is the biggest content-value renegotiation since search itself.
The assignment
Compressed. This quarter, convene the meeting: communications, counsel, and content leadership. One hour. Decide the site-level position by the incentive analysis above. Place or withhold the robots.txt entries accordingly. Document the reasoning with a date on it. Calendar the quarterly revisit, with the crawler roster and tooling maturity as recurring agenda items.
The mechanical work is minutes. The thinking is the deliverable. The written reasoning turns this month’s call from a reflex into a position your successors can update rather than dig up.
To end where we started. The knock at the door is not hostile, but it is not neutral either. It is the sound of your content’s value being repriced by systems that will shape how the next decade finds, cites, and answers with institutional knowledge. The only wrong response we recognize is the one most of the web is currently giving: not hearing it at all. Decide who gets your content, and why, on purpose, in writing. The door has a lock now. That is new, it matters, and somebody in your building should own the key.