Merchant Center

How to Fix Product Landing Page Errors in Merchant Center

What “Product page unavailable” means, the specific crawl errors behind it, how to test pages the way Google does, and how to get products back once pages work.

Google routinely crawls the landing pages in your product data. If it can’t reach a page, the product is disabled until the page is accessible again. Unlike content issues, this is about whether Google can load the page at all.

The good news is that landing page errors are usually technical and testable. This guide walks through each error type Google lists, how to reproduce it, how to fix it on Shopify, WooCommerce or a custom site, and what to do after the fix.

Short answer: “Product page unavailable” means Google couldn’t access the URL in your link, link_template or mobile_link attribute, so the product is disabled. Common causes are 404s, more than two redirects, server (5xx) errors, blocked robots.txt, DNS failures, or URLs on the wrong domain or protocol. Fix the page, test it with the URL Inspection Tool, then request a website check.

Key Takeaways

  • Products stay disabled until Google can access the landing page again.
  • Keep redirects to two or fewer, and make sure robots.txt is reachable and allows Googlebot.
  • Product URLs must start with http:// or https:// and use your verified domain.
  • Test pages with the URL Inspection Tool using both desktop and smartphone fetches.
  • A website check takes up to 12 hours; errors should clear within a couple of days.

What “Product page unavailable” means

Google’s Product page unavailable fix article explains that the error appears when the landing page set in link, link_template or mobile_link can’t be accessed. Affected products are disabled until the page is accessible.

Google crawls landing pages routinely, not only when you submit data. A page that worked when you uploaded the feed can still trigger the error later if the site goes down, a product is deleted, or a security setting starts blocking crawlers.

Landing page errors are different from content mismatches. If Google can load the page but the price or availability doesn’t match your data, see the guides on price mismatches and availability mismatches instead.

The error types and what causes them

ErrorWhat it meansCommon causes in practice
Page not found (404)The URL returns a 404Product deleted or unpublished, URL handle changed, variant URL no longer valid
Too many redirectsThe URL goes through more than two redirectsHTTP to HTTPS to www to trailing-slash chains, old URL redirects stacked on top of each other
Couldn’t connect / HTTP 5xxThe server didn’t respond or returned a server errorDowntime, overloaded hosting, firewall or bot protection blocking Googlebot, maintenance mode
Can’t access robots.txtGoogle couldn’t fetch your robots.txt filerobots.txt returning a server error or timing out
Hostname not resolvableDNS lookup for the domain failedExpired domain, DNS misconfiguration, removed subdomain
URL protocol or domainThe URL doesn’t start with http:// or https://, or isn’t on the verified domainRelative URLs in the feed, product URLs on a different domain than the one claimed
Regional availability URLsURLs with region_id aren’t crawlableRegion parameters returning errors or blocked pages

Google also asks that symbols in URLs be URL-encoded; a comma, for example, should be %2C. Unencoded characters can produce URLs that resolve to the wrong page or fail entirely.

How to confirm the cause

  1. Open Products > Needs attention, select the landing page issue and note several sample products and their URLs.
  2. Open each sample URL exactly as it appears in your data (including parameters) in a private browser window.
  3. Use the URL Inspection Tool, which Google recommends for testing, with both desktop and smartphone fetches. This shows whether Googlebot gets the page, a redirect, an error or a block.
  4. Check the redirect chain with a header checker or your browser’s developer tools and count the hops.
  5. Fetch /robots.txt on the product domain and confirm it loads and doesn’t block product URLs.
  6. Compare the domain in the product URL with the website claimed in Merchant Center.
  7. Look for a pattern across samples: same collection, same URL format, same time window (an outage), or same variant parameter.

A page that loads for you can still fail for Googlebot. Bot protection, rate limits, geo-blocking and country redirects often treat crawlers differently from browsers, which is why the URL Inspection Tool matters more than a manual visit.

Fixing each error type

404 errors

  • If the product still exists, restore its URL or update the link in your data to the current URL.
  • If the product is discontinued, remove it from your data rather than leaving a dead link. If you only need to hide it temporarily, Google’s availability guidance points to the pause attribute (up to 14 days) or excluded_destination. See how to manage out-of-stock products.
  • If a URL handle changed, update the feed source so the new URL syncs, rather than relying on a redirect.

Too many redirects

Google asks you to keep redirects to two or fewer. The best fix is to put the final URL in your data: correct protocol, correct host (www or not), correct trailing slash. Then collapse any redirect chains on the server so old URLs go straight to the final page in one hop.

Server errors and connection failures

  • Check uptime and server logs for the time of the error.
  • Check firewall, CDN and bot protection settings for rules that block or challenge Googlebot.
  • Make sure maintenance mode isn’t left on for some pages or regions.
  • If many products fail at once after a large feed upload, check whether the server can handle the crawl load. Google notes crawling is subject to server capacity.

robots.txt and DNS

  • Make sure robots.txt returns successfully and doesn’t block Googlebot from product URLs.
  • Check DNS records for the product domain and any subdomains used in product URLs, and confirm the domain hasn’t expired.

Protocol and domain

Every product URL must start with http:// or https:// and use the domain you verified in Merchant Center. Relative URLs and URLs on a staging, vanity or old domain will fail. Read more in the guide to verifying and claiming your website.

Regional availability URLs

If you use the regional availability add-on, URLs that include region_id must be crawlable. Test a sample for each region, not only the default URL.

Shopify and WooCommerce notes

Shopify

Google’s Shopify app setup article warns that with multiple domains, redirects or vanity URLs, the Google & YouTube app claims a site automatically, and the claimed domain may not match the domain in product URLs. That leads to approval issues. Google’s fix:

  1. In Merchant Center, go to Settings > Business info and edit the online store.
  2. Enter the domain used in your product URLs (it must be listed in Shopify under Settings > Domains).
  3. Save, then select Change and Claim.
  4. Let products sync automatically or trigger a manual sync.

More Shopify-specific issues are covered in Shopify Merchant Center troubleshooting.

WooCommerce

On WooCommerce, check permalink changes, security plugins that block bots, and caching or maintenance plugins. If you changed permalinks or moved to HTTPS, resync the product data so the feed carries the new URLs. See WooCommerce product feed errors.

After the fix: website checks and timing

  1. Retest a few sample URLs with the URL Inspection Tool.
  2. Request a website check from the issue in Merchant Center. Google says this can take up to 12 hours, and you can’t submit a new request during that time.
  3. Give it time. Google says errors should disappear within a couple of days.
  4. If issues persist, they are shown on the product’s details under Needs attention. Check those products individually.

Website checks are different from policy review requests. The disapprovals guide explains when to use each.

Preventing landing page errors

  • Monitor uptime and alert on server errors, especially during sales and deployments.
  • Allowlist Googlebot in bot protection and firewall rules, and re-check after security changes.
  • Remove discontinued products from your data before deleting their pages.
  • Use final URLs in your data; don’t rely on redirects.
  • Keep the product URL domain and the claimed Merchant Center domain the same.
  • After a migration, theme change or URL structure change, spot-check product URLs and the Needs attention tab.

For an ongoing routine, see how to use Merchant Center diagnostics.

When to get help

If errors come from hosting, CDN or firewall rules you don’t control, or affect many products after a migration, it helps to have someone trace the crawl path end to end. Our disapproval service handles landing page errors, and our technical SEO service covers redirects, crawl access and server issues. Google makes the final decision on reapproval.

Frequently asked questions

What does “Product page unavailable” mean in Merchant Center?

Google couldn’t access the landing page in your link, link_template or mobile_link attribute. The product is disabled until the page is accessible.

How many redirects does Google allow for product URLs?

Google asks you to keep redirects to two or fewer.

How long does it take for landing page errors to clear?

A website check can take up to 12 hours. Google says errors should disappear within a couple of days after the fix.

My product page works in my browser. Why does Google say it’s unavailable?

Googlebot may be blocked by bot protection, robots.txt, geo-redirects or server limits that don’t affect you. Test the URL with the URL Inspection Tool using desktop and smartphone fetches.

Can my product URLs use a different domain than my website?

Product URLs must use the verified domain. On Shopify, make sure the domain claimed in Merchant Center matches the domain in your product URLs.

Products disabled by landing page errors?

We trace why Google can’t reach your product pages, fix the cause and request a website check once pages load.

Sources

Last reviewed October 10, 2026 against the official documentation listed above. Google changes Merchant Center features and policies regularly — always confirm details in your own account.

Similar Posts