FeedArmy's Emmanuel Flossie published guidance on March 21, 2026, detailing how to resolve a recurring Google Merchant Center error that stops Shopping ads from running - despite having nothing to do with the merchant's own website.

The error, labelled "Product Page Unavailable" inside Merchant Center's interface, appears in the "Needs Attention" tab and flags individual product listings as inaccessible. According to Flossie, a Google Ads Diamond Product Expert and founder of FeedArmy, the name itself is misleading. "Despite the name," according to the FeedArmy article published on March 21, 2026, "this error usually isn't about your product pages being down or broken." The actual cause is Google's own crawler failing to reach the merchant's website - the product pages themselves remain functional.

What the error actually means

The technical root of the problem lies in Google's crawling infrastructure. According to Flossie, the error occurs when Google's bot times out attempting to connect to a merchant's site, or when DNS resolution fails on Google's end. It is not a reflection of website performance or uptime on the merchant's side. Crawl interruptions of this nature have been documented across Google's infrastructure in 2025, when multiple hosting platforms including Vercel, WP Engine, and Fastly experienced near-zero crawl rates due to a Google-side technical fault confirmed by Search Advocate John Mueller in August 2025.

The scale of the flag provides the clearest signal of origin. According to Flossie, if approximately 10% of a merchant's products are affected, the cause is almost certainly on Google's side. "If for example it's all your products then that will be of course an issue with your website," Flossie explained in the YouTube video published the same day on the FeedArmy channel, which counts 4,480 subscribers. The 10% threshold is not a formal benchmark published by Google - it is an empirical pattern drawn from Flossie's observations across multiple client accounts at FeedArmy.

The direct impact on Google Ads

The error carries immediate commercial consequences. According to the FeedArmy article, "this error will cause your Google Ads to stop running for those affected products." The flagged products do not serve in Shopping ads until the issue is resolved. For merchants running campaigns with tight margins or during high-demand periods, even a short pause on a subset of products translates into lost revenue and degraded campaign performance metrics.

This matters within the broader context of Merchant Center reliability. Google Merchant Center's automatic import feature was documented in January 2026 to be failing its own stated 24-hour update cycle, with products in some accounts showing data nine to ten days out of date. The two issues - stale data and sudden product page flags - represent distinct failure modes, but both share a common consequence: Shopping ads stop reflecting accurate inventory, and the merchant bears the operational burden of identifying and resolving a platform-side failure.

The connection between Merchant Center reliability and campaign performance is well-established. A March 2026 incident documented by Flossie showed how a complete Merchant Center account closure - triggered by a third-party agency that had retained super admin access for six years - wiped all product feeds, feed rules, supplemental feeds, and account linkages including Google Ads, Google Analytics, and PayPal connections. In that case, all Shopping ads stopped serving immediately. The "product page unavailable" error operates on a narrower scale but through the same mechanism: Merchant Center withdraws product approval, and ad delivery stops.

The resolution process, step by step

According to Flossie, the fix requires four steps inside Merchant Center and takes only a few minutes to complete.

The first step is navigating to the "Needs Attention" tab inside Google Merchant Center. This tab surfaces all flagged products. Merchants select the "Product page unavailable" issue and click the "View Products" button to see the full list of affected listings.

The second step involves clicking on a single affected product - not every product individually. Opening any one product details page is sufficient. According to the FeedArmy guidance, "You don't need to go through each product individually, just pick one."

The third step is clicking "Review and Fix" in the upper right corner of the product details page. This takes the merchant to the needs attention tab for that specific product, where the crawl-related issue is surfaced with resolution options.

The fourth and final step is scrolling down to "Request Website Check" and confirming the request. According to Flossie, "within 24 hours, the flagged products should be approved and your ads should be back up and running." The check triggers Google to re-attempt a crawl of the merchant's website. If the DNS resolution or bot timeout that originally caused the flag has since cleared - which it typically has, given the Google-side origin - the products pass review and return to active status.

The entire resolution workflow requires no changes to the merchant's website, product feed, or campaign settings. It is an administrative request sent directly to Google's crawl systems.

A problem that keeps coming back

The more difficult dimension of this error is its recurrence. According to the FeedArmy article, "this issue tends to come back. Sometimes it reappears the very next day." Flossie does not frame this as a fixable merchant-side issue. The root cause sits within Google's infrastructure, and there is no permanent resolution available at the merchant level.

This recurrence pattern places the operational burden on the merchant. Each recurrence requires a manual "Request Website Check" submission. Without a dedicated monitoring process, a merchant may not notice that 10% of their products have been paused for days, particularly if overall campaign performance fluctuations are attributed to other causes such as seasonality, bidding changes, or market competition.

The absence of automated alerts for this error type compounds the problem. Merchant Center's diagnostics interface surfaces the issue in the "Needs Attention" tab, but merchants must actively log in and check the tab to detect it. Merchant Center for Agencies, which Google made generally available in the US and Canada on March 11, 2026, does provide a diagnostics page that surfaces item-level issues across all client accounts. For agencies managing multiple merchants, that consolidated view reduces the likelihood of missing recurring crawl failures. Individual merchants operating their own accounts have no equivalent early warning system beyond manual monitoring.

According to Flossie, merchants who experience this error repeatedly should contact Google Support and submit feedback. "The more merchants flag it, the more pressure there is for Google to address it properly," according to the FeedArmy article. This recommendation reflects a practical reality: fixing the error instance takes minutes, but changing the underlying crawl behaviour requires Google's own infrastructure team to act, and that only happens when enough feedback reaches them through formal support channels.

Context within a pattern of Merchant Center errors

The "product page unavailable" error is one of several recurring operational challenges that Merchant Center users have faced over the past twelve months. The broader pattern is worth understanding.

In January 2026, Flossie documented that Google Merchant Center's automatic import feature was updating product data nine to ten days behind schedule, despite claiming a 24-hour update cycle. That delay caused ads to run on stale pricing and availability data - another platform-side failure with direct commercial impact on merchants. That same month, Google announced that merchants would be required to use separate product IDs for online versus in-store versions of the same product when attributes differ, a change that took effect in March 2026.

In March 2026, Merchant Center activity intensified further. On March 6, the third-party agency closure incident wiped a client account entirely. On March 11, Google launched Merchant Center for Agencies in the US and Canada, providing agencies with a consolidated interface for managing product data across multiple client accounts. March 21 then brought Flossie's guidance on the "product page unavailable" error. The month has seen structural platform developments running alongside documented operational failures within the same system.

FeedArmy's September 2025 launch of local inventory tracking for Shopify, which added automated submission of store-specific product data through Google Tag Manager, was itself delayed by incomplete Google documentation. The pattern of Google platform changes arriving ahead of clear documentation - and of Google-side infrastructure issues affecting merchant operations - runs through multiple FeedArmy observations across 2025 and 2026.

The inaccurate availability policy, which Google introduced to replace the "Delivery Issues" violation, has been documented on PPC Land since 2021 and represents a different but related category of Merchant Center error - one where the product page is reachable but the content on it is inconsistent with the feed data. The "product page unavailable" error sits at the opposite end of the spectrum: the feed data may be fine, but Google cannot reach the page to verify it.

Why this matters for marketers

For marketing professionals managing Shopping campaigns, this error is notable because it isolates a class of campaign failure that is entirely outside advertiser control. A merchant can have correctly formatted product data, a functioning website, compliant pricing, and accurate availability information - and still find a portion of their products paused because of a transient DNS or crawling fault on Google's systems.

Budget management becomes less predictable when product eligibility can drop without warning and without any merchant-side change. Performance Max campaigns, which use product feed data to generate ads across Search, YouTube, Display, Discover, Gmail, and Maps, are particularly sensitive to product availability fluctuations. A sudden reduction in the number of approved products narrows the inventory available for automated campaign optimisation.

The practical implication is straightforward: merchants running Shopping campaigns should check the "Needs Attention" tab in Merchant Center on a regular basis - daily for high-volume accounts - and treat the "Request Website Check" workflow as a standard maintenance task rather than an exceptional fix. Monitoring cadence, not technical expertise, is the determining factor in minimising the revenue impact of this error.

Timeline

Summary

Who: Emmanuel Flossie, founder of FeedArmy and Google Ads Diamond Product Expert, published the guidance. The affected parties are merchants using Google Merchant Center to run Shopping ads.

What: The "Product Page Unavailable" error in Google Merchant Center flags products as inaccessible and pauses their associated Shopping ads. The error is caused by Google's crawler failing to connect to merchant websites due to DNS errors or bot timeouts - not by any fault in the merchant's website or product feed. The resolution involves submitting a "Request Website Check" through the Merchant Center interface, which restores product approval within 24 hours. The error recurs persistently, requiring repeated manual intervention.

When: FeedArmy published the article and accompanying YouTube video on March 21, 2026.

Where: The issue occurs inside Google Merchant Center's "Needs Attention" tab. The fix is applied through the product details page within the same platform. The documentation was published on the FeedArmy website at feedarmy.com and on the FeedArmy YouTube channel.

Why: The error matters to marketers because it causes Shopping ads to stop serving on affected products without any merchant-side action or warning - a direct revenue impact on campaigns where product eligibility directly determines ad delivery and campaign optimisation.

Share this article
The link has been copied!