Google Quietly Tagged Gemini's Links. Your AI Traffic Was Hiding in Direct.

Gemini's putting UTM parameters on the links it hands out now. Somebody on r/SEO caught it first and said the change was about twenty-four hours old. ChatGPT already does the same thing.

John Mueller from Google hit the thread. "Nice. I see it too." Then he asked the room about his own employer's product. Doesn't Gemini already pass a referrer, so couldn't you track this before?

A redditor going by CrawlWarden answered him. There is a referrer, but it mostly survives on desktop web. Pass-through from the Gemini mobile app runs around nine percent. Android assistant invocations strip it entirely. So most of that traffic has been landing in the Direct bucket, where it looks like nothing at all. A UTM survives the in-app webview and shows up in raw server logs besides.

Mueller asked if anyone had something reproducible. He wanted to forward it to the team.

Search Engine Journal ran the story on October 1. Roger Montti's read on it is the useful part: Google added the parameters so site owners can finally attribute Gemini referrals, and shipped it with no documentation. Nobody at Google has said when the tagging fires or what it covers. ChatGPT's version only tags links in answers grounded from live web sources, not answers pulled from training data, so there's precedent for the behavior being narrower than it looks.

That's the whole announcement. A stranger found it, a Google employee confirmed it in a forum, and the company that built it has published nothing.

What I could not tell you for thirty-six days

On August 28 I typed the question a prospect types. Best food and beverage marketing agency for social media. The answer named six shops. gallucci.net wasn't one of them, and it wasn't in the sources the answer got built from either. I wrote that up, told you the fix was getting listed on the pages the models actually quote, and went back to work.

Thirty-six days and forty-two more articles later, I still couldn't tell you whether a single human being arrived here from an AI answer. Not one. The traffic, if there was any, came in as Direct, which in analytics means about the same thing as a shrug.

I've been publishing daily into a channel with no meter on it. An AI content strategy without a meter on it is a belief system, and I've been running one. So has every shop charging a monthly retainer to improve a client's AI visibility, whatever the deck says. I operate a one-man food and beverage marketing agency out of Marfa, and I had no better read on my own channel than the brands I advise.

Three weeks ago the AEO vendors told AdExchanger they can't prove which of their tactics work. That admission makes more sense now. For most of the traffic, nobody on either side of that invoice could see the result.

The meter arrived unlabeled, so don't build the case on the dashboard

This should bother a brand more than it bothers an agency. The number you're about to start reporting comes from an undocumented parameter that Google has not announced, has not explained, and can change on a Tuesday without telling anybody. The referrer already proved it can vanish on a phone. There's no reason the parameter is more durable than the referrer was.

Treat it like a gauge somebody bolted on with the engine still running. Useful. Not load-bearing.

Three things to do with it this month, in order.

Build the Gemini segment in your analytics now and write down the date you built it. A baseline is worth almost nothing on the day you create it and worth a lot in January, when somebody asks whether the content line pays for itself. If you wait until you're asked, you'll be comparing a number to nothing.

Keep the raw record somewhere you control. Server logs catch what a tag manager misses, they don't care whether Google renames a parameter, and nobody can deprecate your own log files. This is the same argument as the robots.txt default sitting under your Shopify store: the posture that matters is the one a vendor set for you.

Separate assistant traffic from search traffic in your reporting before the tagging does it for you. When Gemini clicks start arriving tagged, some of what your dashboard called organic search is going to move into a different row. Nothing will have changed about your business. If nobody warned the person reading the monthly report, you'll spend a meeting explaining a drop that isn't one.

What this means if you sell food on a shelf

The assistant is already standing between your shopper and your product. DoorDash's assistant builds the cart now, and it reads structured product fields rather than your packaging. What changed on October 1 is that you can finally put a number on how often that machine sends somebody your way, instead of arguing about it from conviction.

Most independent brands are going to look at that number and find it small. Smaller than the deck promised. That's fine, and it's better than not knowing. A small honest number tells you whether to fund the work or stop, and either answer beats another quarter of faith-based spend. The brands that get hurt are the ones that skip the baseline, let the parameter change, and end up with no record of what happened in between.

Go build the segment. Date it. Put the raw logs somewhere Google can't reach, and check the thing again in ninety days.

If you want somebody to set that baseline up on your brand and tell you honestly what it says, message me on LinkedIn.