Your Merchant Center Organic Traffic Drops on Aug 24

Google Merchant Center performance reporting changes on August 24, 2026 — and for most merchants the first visible symptom will be an organic-traffic line that steps down without any real change in demand. Google announced the update on August 11 in its Merchant Center help documentation: commission-eligible YouTube affiliate traffic moves out of the “Organic” reporting value into its own category, and YouTube organic click and impression definitions realign to standard YouTube reporting.

The stakes are not the traffic — that continues exactly as before. The stakes are the reporting layer built on top of it. Both organic-side changes restate historical data back to July 1, 2026, which means numbers already delivered in July client reports will no longer match what Merchant Center shows for the same dates. A third change pushes Ads-side product metrics up on the same day — and that one is explicitly not restated. Any dashboard, alert, or month-over-month comparison keyed to these metrics will register movement that has nothing to do with performance.

This guide walks through the four announced changes, why the organic line drops twice at once, the asymmetry in how history is restated, what to export before the 24th, which dashboards break silently, and the exact caption language that keeps a client from reading a definition change as lost traffic.

Google published the update on August 11, 2026 in its Merchant Center help documentation — thirteen days ahead of the effective date — and at the time of writing it sits at the top of the official Merchant Center announcements change log. Two independent trade outlets (Search Engine Roundtable and Search Engine Land, both publishing August 12) corroborate the announcement and its dates, so this is a confirmed, scheduled change — not a rumor.

Four changes are described. Three take effect on Monday, August 24, 2026. The fourth — a new “Network” segmentation dimension similar to the one in Google Ads — is explicitly labeled by Google as “(To be launched in the future for Merchant Center)” with no date given. Here is the full set at a glance:

The table’s most decision-relevant column is the last one, and it is the detail most coverage will get wrong: only the two organic-shrinking changes touch history. The Ads-side increase applies from August 24 forward only. Section 04 unpacks why that asymmetry matters for month-over-month reporting. This is also a different event from the Merchant Center AI-visibility reporting pilot we covered in July — that pilot adds a new report about AI surfaces, while this change redefines the metrics in the existing performance reports. Background on the pilot: Merchant Center AI Performance Insights pilot, explained.

Two separate mechanisms push the “Organic” value down on the same day, for the same July-1-forward window. They are easy to conflate, and worth keeping distinct — because Merchant Center reporting alone will not tell you how much of your drop came from which.

Note what Google does not publish: any magnitude. The primary documentation gives direction only — “significant drop” and “can lead to a drop” — with no percentage, no range, and no worked example. The size of your drop depends entirely on how much commission-eligible YouTube affiliate traffic your products carry and how far the old YouTube counting diverged from the new standard for your listings. A merchant with no YouTube affiliate exposure may barely move; a merchant leaning on creator content could see a visible step down. Treat any specific percentage you encounter elsewhere as someone’s estimate, not Google’s disclosure.

What “YouTube affiliate” traffic actually is

The traffic being split out comes from the YouTube Shopping affiliate program, which Google describes as enabling merchants to “put their products in the spotlight on YouTube” — eligible creators tag products in videos, Shorts, and live streams, and viewers shop while they watch. YouTube handles creator onboarding, affiliate link management, conversion tracking, and billing; merchants pay only when a creator drives a purchase, and checkout happens on the merchant’s own site. Commission rates are customizable by merchant category, though the program’s help page does not state specific rate figures or payout pending-period lengths. Inside Merchant Center, the program lives under Marketing in the left navigation, with a 28-day analytics snapshot covering sales, commissions, clicks, orders, and commission rate.

That is why the split arguably improves the report: affiliate traffic is commissioned, creator-driven demand, and folding it into “Organic” always overstated what standard free listings were doing on their own. From August 24 the Organic value becomes a cleaner read on free-listing performance — it just gets there by stepping down first.

While the organic line steps down, the third change moves Ads-side product metrics in the opposite direction. Merchant Center’s Ads product-level reporting expands to include performance from all ad channels and formats — data for all networks in Performance Max campaigns, plus metrics for Video, App, and Demand Gen campaigns. Google says this “may cause a one-time increase in metrics such as impressions, clicks, and more.” Two opposite-direction jumps landing on the same Monday is exactly the shape that breaks alert thresholds on both ends.

This expansion mirrors something the Google Ads side already did. Per Google’s own Ads help documentation, product reporting in the Google Ads “Products” tab expanded starting June 2026 to the same scope — all-network Performance Max plus Video, App, and Demand Gen. The August 24 change is Merchant Center’s own performance reports catching up to match what the Ads-side Products tab has shown since June; PPC Land’s independent write-up makes the same observation. Two different reports, two different effective dates, same underlying data scope.

One disambiguation worth being precise about: this is not the same story as the Product clicks and Non-product clicks column split that appeared in Google Ads product reporting in late July. That was a new pair of columns inside the Google Ads interface, already live; this is a scope expansion of Merchant Center’s own performance reports, effective August 24. Both touch product-level reporting, which is exactly why they get conflated. We covered the column split separately in Google Ads splits product clicks: new metrics explained.

The single most consequential sentence in Google’s announcement is its closing note: “Historical data will only be retroactively updated for the separation of YouTube affiliate results and updated Youtube organic traffic definitions.” That is changes 1 and 2 only. The Ads product-level expansion affects data from August 24 forward and leaves history untouched.

The asymmetry has two concrete consequences. First, the organic comparisons shift under you: from August 24, Merchant Center’s organic figures for July 1 onward will be recomputed under the new definitions, so a July number you quoted in a client report in early August will no longer match what the platform shows for the same dates. Month-over-month deltas that span the July boundary become apples-to-apples again only once both months are on restated definitions. Second, the Ads-side series does not get this treatment — its history stays as originally reported, and the expansion shows up as a forward-only step. Comparing Ads product metrics across the August 24 boundary means comparing two different scopes, with no restated history to normalize against.

That point, from PPC Land’s independent analysis of the change, is the practical takeaway for anyone who ships client reporting: it is not just future dashboards that move. Documents you have already sent become inconsistent with the live platform the moment the restatement lands — through no error on your part. Which is why the next section is about exporting first.

Neither the Merchant Center pages we reviewed nor the independent coverage of this change points to any official Google guidance on exporting historical data, recalibrating dashboards, or handling client reporting around the restatement — the documentation describes the change and stops there. The following checklist is our own operational inference from the documented facts, and it has a hard deadline: once August 24 arrives, the as-originally-reported organic numbers for July 1 onward will no longer be reproducible from Merchant Center’s own performance reports, and we found no documented way to retrieve the pre-restatement values.

If your feed and reporting stack is spread across several surfaces, this is also a sensible moment to confirm which downstream tools ingest Merchant Center reporting data at all — feed platforms, BI dashboards, agency reporting suites — because each one inherits the definition change on its own refresh schedule. Our ecommerce services team runs exactly this kind of reporting-continuity audit ahead of platform changes, and the same feed-hygiene thinking applies as in our product data guide for AI shopping surfaces.

A reporting-definition change does not throw errors. Every dashboard keeps rendering; every scheduled report keeps sending. What breaks is the meaning of the numbers — and PPC Land’s analysis names the failure mode precisely: alerting keyed to organic click volume should be expected to register the drop as an anomaly on or shortly after August 24, and ads-impression alerting to register the increase the same way, with neither movement reflecting a change in performance.

The deeper pattern here is worth internalizing beyond this one change: platform reporting definitions are an unversioned dependency of every marketing dashboard. When a metric is redefined upstream, nothing in the pipeline flags it — the numbers just move, and whoever reads the dashboard supplies their own (wrong) explanation. Teams that keep a change log of known platform reporting events next to their dashboards diagnose these steps in minutes; teams that do not can spend a week hunting a traffic loss that never happened. If your measurement stack does not have that habit yet, our analytics services team builds exactly this kind of annotation layer into client reporting.

The cleanest client caption is built from the three facts Google actually discloses: the effective date (August 24), the restatement start (July 1), and the closing note on which changes restate. It deliberately avoids inventing a magnitude Google has not published. Once the change lands, a footnote along these lines belongs on every affected chart:

Three delivery notes. First, send the caption before the client sees the drop — an explanation that arrives with the anomaly reads as competence, one that arrives after a worried email reads as an excuse. Second, resist the temptation to forecast the size of the drop; if a client asks how big it will be, the honest answer is that Google discloses direction only and the magnitude depends on their YouTube affiliate exposure. Third, keep the affiliate reframe handy: the traffic is not gone, and the portion moving to the new “Youtube affiliate” value is arguably the more interesting number — it is commissioned, creator-driven demand that was previously invisible inside the organic total. For what a Merchant Center rebrand looks like when it genuinely changes nothing, compare the July rename we covered in Merchant Center drops “Next” — this one, by contrast, changes your numbers.