ChatGPT Access Tied To 9% Drop In Traditional Search
Summary
A Bocconi University study using Comscore clickstream data finds that broader ChatGPT Search access correlated with a 9.4% drop in traditional search queries, with the sharpest declines in informational and academic categories.
Search Engine Journal covers a Bocconi University paper analyzing U.S. desktop clickstream data to measure how ChatGPT Search’s rollout — from paid subscribers to free and anonymous users — affected traditional search behavior. The findings paint a specific, numbers-backed picture of where AI chat is pulling attention away from conventional search engines.
What’s actually new
The headline number: broader ChatGPT Search access correlated with a 9.4% weekly reduction in traditional search queries, growing to 17% after 20 weeks. Among users who were already on ChatGPT before the expanded rollout, the drop was smaller — 4.9% on average, reaching 8.2% after 20 weeks. The decline concentrated heavily in informational queries: academic research referrals fell 32.8% and reference queries dropped 26.5%, while transactional and recreational searches stayed roughly flat. ChatGPT referred users to outside websites in 5.2% of sessions versus Google’s 31.1%, and the destinations skewed toward smaller, specialized sites — SaaS platforms, developer tools, academic resources, and non-profit or subscription-based services rather than ad-supported properties. The researchers are explicit about the limits of their claim: they measured traffic allocation changes, not consumer surplus or publisher revenue impact.
What it means for your config
This isn’t a tooling release, so there’s no config migration or breaking change to worry about. But if you maintain developer-facing documentation sites, API references, or SaaS landing pages, the data is worth noting: ChatGPT’s referral patterns appear to favor exactly these kinds of properties over mainstream ad-supported destinations. That has implications for how you think about discoverability. If your docs site or developer portal relies on organic search traffic for adoption metrics, a portion of that funnel may be quietly shifting to AI-mediated discovery — where your content gets consumed but generates fewer actual visits. There’s no config switch to flip for this; it’s a structural trend in how traffic arrives. Teams that instrument referral sources (via analytics configs, UTM parameters, or server log parsing) should make sure they’re tagging AI-originated traffic distinctly so they can actually measure the shift rather than guessing.
Recommended next step
If you run a developer docs site or SaaS platform, check whether your analytics setup distinguishes AI referrals from traditional search. Most default configurations lump them together or miss them entirely. Adding referrer-based segmentation now gives you a baseline before the trend deepens. For the full data and the researchers’ own caveats about scope, read the original coverage — the Bocconi team is deliberately narrow in their claims, and that restraint is worth understanding before you act on the numbers.
Read the full announcement on Search Engine Journal → ChatGPT Access Tied To 9% Drop In Traditional Search
More Search Engine Journal Updates
TikTok Targets AI-Generated Spam Accounts In High-Risk Topics
TikTok announced upcoming tests to improve detection of accounts posting AI-generated spam in politics, finance, and medical topics. The platform also joined the C2PA steering committee and claims to have tagged over 3 billion videos as AI-generated.
Google's Marvin Clarifies AI Search and Qualified Future Conversions
Google Ads Liaison Ginny Marvin answered advertiser questions about AI Search ad eligibility, Qualified Future Conversions, and YouTube Creator Partnerships. No new products were announced — the Q&A added context to features revealed at Google Marketing Live.
The WebMCP Tools You Expose To Agents Can Be Used To Hijack Them
Chrome's security guidance for WebMCP details how the tools websites expose to AI agents create prompt-injection attack surfaces, and places the mitigation burden squarely on tool authors, not agent builders.