Google has confirmed it is investigating a Merchant Center outage, without disclosing the root cause, the affected features, or an expected resolution time. For advertisers whose revenue depends on a product feed, the hardest part is not the downtime itself — it is operating without knowing what exactly is broken.
Google posted an incident notice saying it was investigating reports of a problem affecting Merchant Center. The incident began on August 6 at 13:06 UTC, and Google published its first public update at 17:46 UTC, confirming the investigation and promising more detail as it became available.
As of that update, Google had shared nothing about the root cause, the affected features, or a resolution timeline. Advertisers know only that something is wrong — determining the scope inside their own accounts is on them.
Merchant Center is not just a product upload tool. Google Shopping, Performance Max, and free product listings all serve from that feed. When feed processing or product approval flows wobble, what disappears is not creative performance but serving eligibility. No bid increase fixes that.
The most common mistake is hunting for the cause inside your own account. Raising bids because impressions dropped, re-uploading the entire product data set, or restructuring campaigns will leave your performance data contaminated long after the incident closes. Once a platform outage and your own changes overlap in the same window, no later analysis has a clean baseline. That risk grows when structural changes are already in flight, as with Google's recent Performance Max lead-billing guidance.
Annotate the timeline. Mark August 6, 13:06 UTC in your reporting. That single note is your defense when explaining weekly and monthly numbers later.
Capture the current state. Screenshot product approval status and feed processing timestamps so you have a before-and-after reference once service is restored.
Pause experiments. Do not launch new campaigns or run A/B tests while an uncontrolled external variable is active — the results will not be interpretable.
Communicate early. Telling a stakeholder before performance drops carries very different weight than explaining after. If you are reviewing how your paid media operations are structured, see our services overview.
Google has not yet said what broke. Until it does, the best move is to wait out the recovery without polluting your data, and to document everything you can.
According to Google's incident notice, it began on August 6, 2026 at 13:06 UTC, with the first public update posted the same day at 17:46 UTC.
No. If the impression drop is caused by a platform incident, bid changes will not help and will make post-recovery analysis harder.
Google has not confirmed scope, but anything dependent on the Merchant Center feed — Shopping campaigns, Performance Max, and free product listings — is potentially affected.
Compare product approval status, feed processing timestamps, and impression/click trends against your pre-incident baseline, and keep the outage annotation in your reports.
To apply what you just read to your own site, start with a free audit of where things are now.
A strategist replies within 24 hours on business days.
A new Enhanced matching option is appearing in Customer Match settings, extending first-party audience reach by matching consented users with consented publisher users.
Google is adding multi-campaign A/B testing, experiments that keep brand and location controls on, and expanded Performance Planner forecasting to AI Max for Search campaigns.
Demand Gen starts where there is no keyword and no existing interest. As that protection disappears, PPC specialists need creative strategy, audience research and full-journey measurement.