The Publisher Traffic Collapse
Stack Overflow's question volume fell roughly 75% from its peak after ChatGPT launched. For a decade the open web ran on a simple loop: user has a question, Googles it, clicks a link, the site captures the visit. Stack Overflow was the definitive example in tech. ChatGPT broke the loop by answering directly, and Google's AI Overviews made it worse by summarizing answers inside search results, so being cited became nearly worthless: you get the credit, someone else gets the user. The company pivoted to licensing its archive to OpenAI, monetizing the very data that made its live product redundant.
For founders and operators, this case sharpens the question of how much of your business flows through a channel you do not control, and what happens when that channel starts answering questions itself. It reframes the danger not as sudden collapse but as a slow bleed that flips your unit economics before you react. When the window to build traffic independence actually closes is the uncomfortable timing the app makes you confront.
Frequently asked questions
What happened to Stack Overflow's traffic after ChatGPT?
Stack Overflow's question volume fell roughly 75% from its peak after ChatGPT launched. For a decade the web ran on a loop where users Googled questions and clicked links, and Stack Overflow was the definitive tech example. ChatGPT broke that loop by answering directly.
How did Google AI Overviews make the publisher traffic collapse worse?
Google's AI Overviews summarized answers inside search results, so being cited became nearly worthless: the site gets the credit but someone else gets the user. That broke the click-through loop publishers depended on. Stack Overflow pivoted to licensing its archive to OpenAI to monetize the data that made its live product redundant.
Why is the publisher traffic collapse described as a slow bleed?
Because the danger is not sudden collapse but a gradual erosion that flips your unit economics before you react. When a channel you depend on starts answering questions itself, traffic and revenue drain steadily. By the time it is obvious, the window to adapt may have closed.
What can founders learn from the publisher traffic collapse?
Ask how much of your business flows through a channel you do not control, and what happens when that channel starts answering questions itself. The lesson is to build traffic independence before the window closes. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.