Google Doesn't Want to Send Traffic. It Wants to Finish the Task

Go into AI Mode and ask it to find something you'd actually buy. A laptop, a hotel for the weekend, an app your team needs.

Watch what happens before a single link shows up. It compares options. It filters on price, delivery, region.

By the time a URL appears, the decision is already made. The click used to start the research. Now it comes after it.

Zero-click took your informational traffic. This takes the part that was making you money.

This isn't a prediction

Here's Sundar Pichai in April: "If I fast-forward, a lot of what are just information-seeking queries will be agentic in Search. You'll be completing tasks. You'll have many threads running."

Not answers. Tasks.

And it's shipping. AI Mode already handles restaurant tables, event tickets and appointments in the US.

Ask for Me will even call a local business on your behalf to check pricing and availability.

Look at the pattern, not the feature list. The interface gathers availability, weighs the options, builds the shortlist, then hands off at the last step. For restaurants it doesn't even hand off. It books.

Everything upstream of the transaction is being absorbed. That's the part you were paid for.

Losing an answer costs attention. Losing a task step costs revenue

If you sell ads, an informational visit was the business. For everyone else it was never worth much on its own. It was attention, and attribution for a report.

This is different. If an interface can pull your price, check your stock and hand the user a recommendation, it has taken over the middle of your funnel. Not the top.

The click becomes optional at exactly the point where it used to convert.

Where it stops working

The strong version of this argument – nobody visits a website again – is wrong, and this year proved it.

OpenAI scaled back Instant Checkout in March. Purchases moved out of the chat. Discovery stayed. Shopify's president put the number of merchants that ever went live at about a dozen.

Walmart put a number on it. In-chat purchases converted at one-third the rate of customers who clicked through to Walmart.com. Their head of AI called it "a very temporary moment in time."

So nobody is buying your product inside a chat window at scale. The blocker isn't the plumbing. It's trust.

People will let a machine compare options all day. Handing it the card is a different decision.

Everything before payment has no such problem. That's where the work already moved.

What a task interface needs, and what it finds instead

A system trying to finish a job needs facts it can extract without interpretation. What it costs, whether it's in stock, how long delivery takes, what it actually does.

Here's what I find instead.

Price on request. Availability rendered client-side after a call to an inventory endpoint. Delivery terms in a footer PDF. Variant data in a JavaScript state blob that never reaches the HTML. The details as an image of a table.

Client-side rendering is the worst of it. Google renders JavaScript. Nobody else does.

For a human, none of this is a problem. Someone will fill in the form and wait a day for a reply, because that's how it has always worked.

A machine won't wait for your reply. It'll use the competitor who published the number.

I see this often on sites that are healthy by every other measure. Fast, crawlable, indexed, ranking. Completely unusable as a data source.

Friction was the business model

Let's go straight to the issue. Most of these decisions were deliberate.

Hiding pricing is a sales strategy. Gating the details is lead generation. Nobody built those by accident.

The assumption underneath was that the customer has no other route to the information. That assumption is expiring.

When an assistant compiles a shortlist, the business that requires a conversation doesn't get a placeholder. It gets left out, or described from a three-year-old review.

Keep the gate if you want. Just know what it costs now. Not fewer leads. Not being in the comparison at all.

The advice didn't change. The consequence did.

Google's guidance on AI features says no new schema is required. No AI text files, no special markup. Same index, same rules.

So the list hasn't changed.

Structured data describing what's actually on the page. Product, Offer and availability on commercial pages, not only the Organization block that handles your entity. Commercial facts server-rendered rather than hydrated in. Feeds that match the site instead of drifting three weeks after a price change.

That last one is enforced. Merchant Center documents it plainly: a price passed dynamically after page load triggers an error, and a mismatch can get the item disapproved.

Keep doing it and the whole account is at risk.

Boring work, all of it. The kind that gets deprioritised because it doesn't look like growth.

The site is no longer a set of ranking assets. It's the data layer other systems read to make decisions about you.

Your reports will get worse before your business does

Search Console started breaking out generative AI features in June. Impressions only. No clicks, no CTR, no queries.

You can prove you appeared. You can't see what happened next.

And the traffic doesn't come back either. Cloudflare Radar splits AI crawler traffic by purpose, and requests tied to a live user action sit around 2.6%.

The rest is training and indexing. Nobody arrives.

So stop treating sessions as the health metric. Watch branded search, the ratio of direct to organic, and which bots hit your pricing pages and what status codes they get.

The measurement problem is real. The data layer is the bigger one.

The click was a workaround

Search sent people to websites because it couldn't do the job itself. Everything after matching a query to a document was your responsibility, so you got the visit.

That limitation is what your traffic was built on. It's being removed, unevenly, but in one direction.

This doesn't make websites irrelevant. Something still has to hold the facts, and it'll be your site or someone else's summary of it. It just makes vague, gated, half-rendered sites easy to route around.

Google was never in the business of sending you traffic. It was in the business of finishing the user's task, and the click was the only way it knew how.