Merchant Center Says Your Product Page Is Unavailable? Here Is What to Check

1. Open the Link Inside Merchant Centre

Go to Products → Needs attention, open the landing-page issue and select an affected product. Open the website link shown for that product.

This matters because it might be different from the link you get by browsing your shop. A product rename, an old mobile URL or an integration that has not synced can leave Google trying the wrong address.

If the link returns a missing-page error, correct it in the system that supplies your product feed. That might be your ecommerce platform, a feed app or a custom export. Editing it only in Merchant Centre can be undone by the next sync.

If the product has been permanently removed, remove it from the feed too. Redirecting every deleted product to the homepage does not give Google the product page it needs.

A successful feed upload does not mean the links work. It means Google received the data. It still has to visit the pages listed in it.

2. Check Whether the Failures Have Something in Common

Open a few affected products before changing anything across the site. Try an older product, a newer one and a product Google has approved.

If only old links fail, investigate the feed. If unrelated products started failing together, check for a recent hosting or Cloudflare change. If only mobile fails, look for a separate mobile address in the product data.

Google supports several product URL fields, including link and mobile_link. Shopping ads can also use an ads_redirect tracking address. You do not need to change all of them; check which ones the affected product actually uses.

Keep any size, colour or region information in the URL when you test it. For example:

1https://example.com/products/boots?variant=black-size-10

Opening /products/boots alone does not test the link above. The extra part selects the variant, and that might be where the request fails.

Also check where you end up after opening the link. If it sends you through several redirects or lands on a category page, update the feed to point directly to the correct product. Google's desktop landing-page guidance recommends no more than two redirects.

3. Read the Error Code

The issue details may include a more specific crawl error. Use that to decide who needs to fix it:

If you cannot find a code, give your developer a few affected item IDs and their links. Ask them to check what those pages return to Google's crawlers.

A page can also return 200 OK while showing a login screen or an empty template. Have them check the page content as well as the status code.

If Google names robots.txt, check that file first. Google lists an unreachable robots file as a cause of product-page failures. Open https://your-domain.com/robots.txt and have your host check Google's requests to it. Fixing the product URL alone will not resolve a block on that file.

4. Look for a Cloudflare Block

In Cloudflare, select the site and open Security Analytics → Events. Search around the time the problem started, using one of the affected product URLs.

Open any Block or Managed Challenge events and check the service and rule that caused them. Look at relevant Googlebot traffic and Storebot-Google, which Google uses for Shopping.

An exception for one Google crawler does not necessarily cover the others. If the rule is intended to allow Google, your developer should check that the failed request really came from Google using its crawler verification guidance.

Once you find the block, fix that rule. A country restriction needs different treatment from a rate limit or a managed security rule.

Watch for Bot Fight Mode. Ordinary Bot Fight Mode cannot be bypassed with a WAF Skip rule. If it is responsible, turn it off and review the bot protection you need. Super Bot Fight Mode supports exceptions.

Do not disable security for every visitor to every product page just to let Google in. An exception should be limited to the traffic and protection involved.

If there are no matching events, check the server logs as well. Cloudflare's logs can be sampled, and a request can also be refused by the host after Cloudflare lets it through.

If Everything Loads Now but Google Still Reports an Error

Check when the failure happened. A brief outage can be over by the time you investigate, while Merchant Centre still shows the result of its earlier visit.

You can also get different results when you are logged in to the shop. Open the affected URL in a private window and check that it works without a saved country, selected variant or administrator session.

If the page loads but shows the wrong size, price or availability, investigate that separately. Google's landing-page requirements require the advertised product to match what the customer sees.

For example, if black size 10 and tan size 9 both open the same default boot, check whether the site's cache is ignoring the variant parameter. I covered that distinction in my Statamic query-string article: tracking parameters and parameters that change the product need different treatment.

Once robots.txt is accessible, check that its rules permit the product pages. Search Console can help test access, but it does not reproduce every Shopping request.

Ask Google to Check Again

After the repair, reopen the affected links and confirm the correct products load. If you changed the feed, wait for the corrected URLs to appear in Merchant Centre.

Then use the website check or review option offered for the issue. Google can also check the pages automatically. Follow the waiting period shown in the account; repeatedly resubmitting the same unchanged data will not make the server more accessible.

Watch the affected product count over the next few days. If it starts climbing again, compare the new failures with your hosting and Cloudflare logs. That is a sign to investigate intermittent errors rather than keep requesting review.

Whoever manages your website maintenance should know when product-page failures appear. A shop can keep accepting orders while Google quietly loses access to its catalogue.