Dozens of Google Merchant Center accounts woke up to mass product disapprovals on June 4, with the error message “Product page unavailable” applied to listings whose landing pages were working normally. The pattern, reported across more than ten separate accounts, points to a likely bug in Merchant Center’s automated landing-page validation system. Google has not confirmed the cause or issued a formal acknowledgment as of publication.
The disapproval notice instructs merchants to “ensure your product page can be accessed from desktop and mobile devices and is not restricted from Google crawling.” In a genuine crawl-block scenario, that guidance is actionable. When the pages are demonstrably live and indexed, the message is a false signal, and the standard remediation steps will do nothing to resolve it.
One working hypothesis circulating among practitioners is that a Shopify platform outage the previous day temporarily blocked Google’s crawler from reaching product pages, and that Merchant Center’s validation logic recorded those crawl failures as permanent disapprovals rather than transient errors. This is unconfirmed. Whether the root cause is a validation logic flaw, a stale crawl cache, or a dependency on a third-party platform’s uptime, the practical effect for affected merchants is the same: products are pulled from Google Shopping until the status resolves.
The revenue risk is real and front-loaded. A mass disapproval event does not unfold gradually. Shopping campaigns drawing on disapproved products lose impression share immediately, and recovery depends on how quickly Merchant Center re-crawls and re-validates the affected listings after the underlying issue clears. For merchants running time-sensitive promotions or carrying thin profit margins on Shopping traffic, every hour of suppressed visibility has a direct cost.
Automated validation false positives are not new to Merchant Center. Similar waves have hit the platform before, typically following infrastructure changes or crawler anomalies, and have resolved without merchant intervention once Google’s systems recalibrate. The consistent lesson from those episodes: bulk feed edits made in response to a suspected bug often create secondary problems, including new disapproval triggers, feed policy flags, or data mismatches that outlast the original incident.
The right response to a suspected false-disapproval wave follows a short checklist. First, verify your landing pages are genuinely accessible from both desktop and mobile, and confirm Google can crawl them by checking for any robots.txt restrictions or Cloudflare bot-management rules that may have tightened recently. Second, document the disapproval count, the affected product IDs, and the timestamp of the first notice; this record matters if you need to file a Merchant Center support request or demonstrate good-faith compliance later. Third, do not submit bulk re-approval requests or make wholesale feed changes until you have confirmed whether the wave is platform-wide. A false positive that resolves automatically will not require re-submission; a bulk edit made in a panic may delay the return to active status.
If the issue persists beyond 24 to 48 hours without a Google acknowledgment, a targeted support ticket citing the disapproval timestamps and a screenshot of the live landing page is the appropriate escalation path. The Google Merchant Center Help Forum, which showed no widespread thread on this incident as of reporting, is a secondary signal worth monitoring.
Merchants running Shopping campaigns should check their Merchant Center diagnostics now, compare the disapproval timestamps against any recent crawler or CDN configuration changes on their own infrastructure, and hold their feed edits until the situation clarifies.
Search Engine Roundtable first reported the Merchant Center “Product page unavailable” disapproval wave on June 4, 2026, citing practitioner accounts across multiple affected Google Ads merchant profiles.
