OpenAI's GPT-6 rollout broke ChatGPT's link tracking for about a week. Starting October 8, 2026, inline answer links stopped carrying the utm_source=chatgpt.com tag and often dropped the referrer entirely. Analytics tools filed those visits as Direct, not ChatGPT. OpenAI confirmed the ChatGPT UTM tag bug to Adobe on October 14, and a fix rolled out the next morning. If your AI-referral numbers tanked that week, check your Direct bucket before you rebuild anything.
What Happened to ChatGPT's UTM Tags?#
GPT-6 reached paid plans on October 7 and Free and Go accounts on October 8, 2026. From that point, ChatGPT's inline answer links lost the parameter that tells Google Analytics a visit came from ChatGPT, and many opened without a referrer at all. No tag and no referrer leaves GA4 nowhere to put that session except Direct.
Graphite's Ethan Smith measured a 22% to 57% fall in ChatGPT-attributed GA4 sessions starting October 9, settling around a 45% drop on average. Adobe's Cedric Huesler tracked roughly 500 pages where ChatGPT normally drove at least 5% of visits, and over October 9–13 saw ChatGPT visits fall by about 31,000 a day while Direct rose by roughly 26,000 a day. Search Engine Journal covered the full breakdown, including matching data from LLM Pulse and Profound. Huesler says OpenAI confirmed it was a bug on October 14, and a fix started rolling out around 2am Pacific the next morning.
Does the ChatGPT UTM Tag Bug Affect Your Business?#
If ChatGPT sends you a handful of sessions a month, this changes nothing you'd notice. If you've built real visibility in AI answers, and especially if a meaningful share of your visitors are on mobile, this is the week your reporting lied to you.
At WebEpex, we track AI-referral visibility for client sites across the GCC, Europe, USA, Canada, and India, and this is exactly the kind of silent breakage AEO reporting has to catch before a client sees a bad number and panics. Huesler's data found mobile the most exposed: 95% of mobile ChatGPT visits in his dataset relied on the tag alone, with no referrer as a backup.
If you run AI Overview or AI Mode citation tracking as part of your SEO reporting, your October 8–15 numbers for ChatGPT specifically aren't reliable. Don't average them into a trend line. Don't tell a client "AI traffic is down" without that caveat. Full stop.
Should You Trust ChatGPT Referral Data Going Forward?#
Mostly, yes, with one standing caveat. Most ChatGPT clicks still arrive with no referrer at all, bug or no bug. That was true before October 8 and it's still true after the fix. The tag does nearly all the work, which means one parameter change on OpenAI's side can erase an entire channel from your dashboard without a single visitor actually leaving.
Here's the honest part: I'll admit we don't actually know yet whether the fix is uniform. Glenn Gabe, a well-known SEO consultant, said he still hadn't seen it land on his own accounts days after Huesler's report went up. OpenAI hasn't published anything about this, no help article, no release note. We're treating Adobe's account as the best read available right now, nothing more.
What We Changed in Our Own Tracking Setups#
We pulled GA4 and Search Console data for every client site with meaningful AI-citation visibility the morning Huesler's numbers went around, and flagged October 8–15 as a known-bad window in every dashboard before a single client asked. That's the unglamorous part of this job, and it's also the part that actually protects a client's reporting.
Longer term, we're routing more of what we control, email links, ad links, anything on our own pages, through UTM parameters we set ourselves rather than leaning on whatever an AI platform decides to pass along. We don't control what ChatGPT, Gemini, or Google's AI Mode does with a link on their end, and this week proved that's not theoretical. Google made its own changes to AI Mode's link behavior the same week, a separate story, but it shows where the volatility sits right now: inside the AI answer layer, not on your own site.
What I'd Tell a Client This Week#
Three things, in order:
- Pull your GA4 channel report and filter to October 8–15, 2026.
- Annotate that window as a known tracking gap, not a real traffic loss.
- Spot-check against Search Console impressions occasionally going forward, instead of trusting GA4 alone.
Don't cut budget or change strategy off that one window. One dropped parameter shouldn't be able to erase a channel from your reporting again, and now you know to check. If you're not sure whether this touched your numbers, that's a two-minute check, not a redesign.
If you want a second pair of eyes on whether this actually moved yours, send me your October GA4 export and I'll tell you straight, no pitch attached. cal.com/webepex/growth-review