Technical

Google Merchant Center Went Down on November 6 — and Google Confirmed It

Google Merchant Center went down on November 6, 2026 — and this time Google said so plainly. At 5:26am ET, or 10:26 UTC, Google posted on the Merchant Center status page: "We're investigating reports of an issue with Merchant API, Merchant Center, and Feeds." Retailers had already noticed. Feeds were failing with an "Internal error (9, 0)" message, and Merchant Center itself was running slow. Google cleared the error later on November 6, and feeds were processing normally again by November 7, according to Sayu's update. The outage was brief, but its timing — days before Black Friday — is why it matters.

What broke on November 6

The problem touched the whole Merchant Center stack. Google's status post named three parts of it at once: the Merchant API, Merchant Center itself, and Feeds. That breadth is what made the morning confusing for retailers. It was not one feed failing or one account glitching; it was the system merchants use to tell Google what they sell, at the moment they needed it most. Merchant Center itself was also slow, so even merchants who could get in found the experience degraded.

The error retailers saw was cryptic in the way platform errors usually are: "Internal error (9, 0)" against their feeds. A code like that tells a merchant nothing about the cause and nothing about the fix; it only says the platform is not doing its job. When the message appears across accounts at once, the diagnosis is at least easy — the problem is upstream, not in your feed file — but the remedy is to wait, and waiting is expensive in the week before Black Friday.

How big the disruption was

The scale varied by account, but at least one retailer saw the error against 1,004 products — a whole catalogue's worth of listings failing to process at once. That number is a single account's experience, not a platform-wide total, and Google has not published one. But it shows how an outage like this lands: not as a headline number, but as a thousand products that should be showing in Shopping results and are not, on the days when shoppers are starting to buy.

The good news is that the outage was short. Google cleared the error later on November 6, and by November 7 feeds were processing normally again, according to Sayu's update. A disruption measured in hours rather than days is the best outcome a merchant can hope for from a platform failure — but only if the hours did not fall across a moment when listings needed to update. A price change, a stock correction, or a new product that failed to push through during the window may have spent the busiest shopping days of the year out of date.

Why the timing stings for retailers

The calendar is the real story here. November 6 sits days before Black Friday, the point in the year when merchants are finalising prices, pushing new stock into feeds, and checking that every product is live in Google Shopping. A feed outage in that window does not just delay a listing; it delays the listing at the exact moment its visibility is worth the most. Even a few hours of failed processing can mean a product that misses the first wave of deal-hunting shoppers.

There is a practical lesson to take from it. Feeds should be checked early and checked often in the run-up to a big sales event, and the Merchant Center status page is worth a look before assuming a failed feed is your own fault. If the platform is the problem, the fix is Google's to make — but the merchant who spots it first is the merchant who can resubmit first once the error clears. In the week before Black Friday, that head start is worth having.

Sources

Sources: Search Engine Roundtable, November 6, 2026; Sayu, November 7, 2026.

Turn this playbook into links

Linkbaits helps you create content that earns citations and backlinks. Start with the free tools and build your first linkable asset this week.

Start free trial