Google Shopping sales dropped? How to find the change behind it

Why did my Google Shopping sales drop?

Google Shopping sales drop when fewer of your products are eligible to show, when your campaigns win fewer auctions, or when shoppers who click stop buying. Each of those has a different owner and a different log, which is why Shopping drops are hard to explain.

Product eligibility lives in Google Merchant Center: a disapproved product stops showing across Google, so a feed problem can remove your bestsellers overnight. Auction share lives in Google Ads: budgets, bid strategy targets, paused campaigns and listing group edits decide how often eligible products appear. Buying behaviour lives on your site: price, stock, shipping and checkout.

The fastest way to the cause is to check them in that order, after you have confirmed the drop is real and limited to Shopping. If sales fell across every channel, start with why ecommerce sales drop instead, because the cause is more likely on the site or in demand.

Is the drop limited to Shopping, or did tracking change?

Compare orders in your store backend with Shopping conversions in Google Ads for the same days. If the backend is stable and only Google Ads reports fewer sales, the problem is measurement, not sales.

• Check the backend first. Count orders and revenue for the days after the drop against the same weekdays of the previous weeks. A drop that does not exist in the backend is a conversion tag, consent or attribution issue.
• Split by channel. If organic search, email and other paid channels held while Shopping fell, the cause sits in Merchant Center or in your Shopping and Performance Max campaigns.
• Split by product. A drop concentrated in one brand, category or price band points to a feed or product change. A drop spread evenly across the catalogue points to a campaign setting or a site-wide change.
• Mind the most recent days. Conversions can be reported days after the click, so the last few days often look worse than they will end up. Compare like with like before you act.

Write down the first day that looks wrong. Every later step compares changes against that date.

What Merchant Center problems stop Shopping sales?

Disapprovals and warnings in Merchant Center are the most common cause of a sudden Shopping drop. Google says disapproved products stop showing across Google, while products with warnings keep showing but their performance may be limited, and unresolved warnings can turn into disapprovals (Merchant Center Help).

To check, open Products under Products & store and select the Needs attention tab. Two details matter for diagnosis:

• Prioritized fixes hides small issues. When the Prioritized fixes toggle is on, issues with little or no impact may not be displayed. Turn it off to see every issue.
• View history shows when status changed. The View history button at the top of Needs attention opens the latest product status and its history, which you can filter by period, country and status (Merchant Center Help). Use it to date the moment products went from approved to disapproved.

Price mismatches

Google compares the price in your product data with the price on your landing page or in its structured data, and a mismatch can get the product disapproved; Google adds that it may lead to an account suspension. Common causes include site prices changing more often than the feed, wrong sale price dates or time zones, and prices loaded only with JavaScript. After you fix the data, Googlebot re-crawls disapproved products over the next few hours or days (Merchant Center Help).

Automatic updates

Merchant Center automations are on by default and can update price, sale price, availability and condition from your landing pages. Google notes they may not work well for products whose price or availability changes more than once a day, and that such products may be disapproved instead of updated (Merchant Center Help). A flash sale or a stock sync that runs every hour is a typical trigger.

Which Google Ads changes cut Shopping traffic?

If Merchant Center shows no new issues, look at Google Ads. Budget cuts, paused campaigns, listing group edits and bid strategy targets all decide how often your eligible products appear.

• Target ROAS raised. Google says a target set too high may limit the traffic your ads get, while lowering it gradually lets the bid strategy enter more auctions. The bidder reacts immediately but needs time, about 1 to 2 conversion cycles, to reach a new target (Google Ads Help).
• Budget or campaign status. A lower daily budget or a paused Shopping or Performance Max campaign removes impressions straight away. If most of your Shopping traffic runs through PMax, see which Performance Max edits move results.
• Listing groups and product filters. Excluding a brand or category, or a feed label that no longer matches the campaign filter, quietly removes products from serving.
• Bid strategy or goal switch. Moving to a different Smart Bidding strategy, or changing the conversion goal, can start a learning period in which results swing.

To find these edits, open Change history from the Campaigns menu. It covers the past 2 years and can be filtered by date range, type of change, campaign or ad group. The User column shows who made each edit in the interface, or a system or tool name for automated, API and third-party changes (Google Ads Help). The Google Ads change history guide shows how to filter it quickly.

How do I isolate which change caused the Shopping sales drop?

Put every change from the 7 to 14 days before the drop on one timeline, rule out tracking first, then test one suspect at a time. The change that lines up with the start date, and with the products or campaigns that fell, is your lead suspect.

1. Confirm the drop in the backend
2. Check Merchant Center history
3. Read Google Ads change history
4. Test one hypothesis

The hard part is that the evidence is split: Merchant Center knows product status, Google Ads knows campaign edits, and only your team knows about the price update, the new shipping rule or the feed tool change. With every change on one timeline, the pattern is usually plain: a target ROAS increase on Thursday, impressions down from Friday, no new disapprovals in between. In Changeline, Google Ads edits are imported automatically and the team logs feed, price and site changes next to them.

To prove it, reverse or test the suspect: restore the old target on one campaign, fix the disapproved items, or roll back the feed rule. If Shopping sales recover where you changed something and not elsewhere, you have the cause.

Example: on Monday, the manager of an online sports retailer asks why Shopping sales fell 35% since Friday. The backend confirms it, and only Shopping fell. Needs attention shows no new disapprovals and View history is flat. Change history shows that the target ROAS of the main Performance Max campaign was raised from 400% to 550% on Thursday. A feed rule that shortened titles on Friday touched only one category, while sales fell in all of them. The team sets the target back to 450% and sales recover over the following week.

How do I keep the next Shopping drop easy to explain?

Record Shopping-related changes when they happen, in one place, with a date, an owner and a reason. When the next drop comes, the first question, what changed, already has an answer.

Review Shopping sales weekly by product group against that record, so a disapproval or a target change is caught within days rather than at the end of the month. A shared marketing change log keeps feed, site and ad changes together, which neither Merchant Center nor Google Ads does on its own. When a client asks about the drop, the guide to explaining a conversion drop to a client covers how to present the answer.