Landing page errors: what Merchant Center expects

Every product link you send to Google has to open a live, working page: not a 404, not a 500, not a maintenance screen or an empty “not found” page. Google’s help pages say so in plain words. Test your product and policy links after every change and fix errors where they start.

Critical5 min read

By Edvinas Ivanauskas How the guides are reviewed

Why this matters

Google's “How to fix: Landing page not working” page is blunt: “Your item shouldn’t lead to a website that's under construction, or a site that links to an error page that displays a status code beginning with a 4 or a 5 (for example, a 404 or 500 error).” It asks you to “Verify that your landing page loads correctly and that the link (final URL) is free of typos or broken redirects.”

Its companion, “How to fix: Product page unavailable”, describes what happens when a page cannot be opened: “we disable products that have an unavailable landing page”. It lists the usual suspects one by one. For a 404: “The landing page was not found on the server.” For a server error: “When we tried to access the landing page, the server couldn't process the request due to an unknown reason.” For a domain that does not answer, it asks you to “make sure that your DNS configuration is set up properly”. And it ends with a rule worth pinning above the desk: “Ensure that every time you upload a new product, you include a landing page that can be accessed by anyone.”

There is a quieter version of the same problem. A discontinued product page that answers “200 OK” but shows “this item no longer exists” is not a working page just because the server said so. Google's documentation on HTTP status codes says of success responses: “If the content suggests an error for Google Search, an empty page or an error message, Search Console will show a soft 404 error.” Of real errors it says “Google doesn't use the content from URLs that return 4xx status codes.” Either way, the shopper who clicked your ad finds nothing to buy.

Product Experts on Google's Merchant Center Community list broken links among the basics to put right in a “Website needs improvement” case. Errors rarely arrive one at a time: they come in batches with clear-outs, migrations and app updates, which is why the test belongs in every one of those jobs.

The free scan reports a store that answers with an HTTP error as a failure, flags a store where it cannot retrieve a single product page, and reports a broken link to your returns, shipping, privacy or contact page as a failure. The product links you submit to Merchant Center are yours to test in bulk; the scan does not see them. See every page check on the misrepresentation checker, and for links inside the store read broken links on your store.

Typical evidence

Read the status line, not your good intentions

Every submitted URL is a promise that something loads there. Test the response and rendered page. The nastiest case is a soft 404: a healthy 200 status wrapped around a page that says 'product not found'. The header lies; the body gives it away.

GET · feed landing URLs3 / 6 unreachable

/products/oak-desk-lampok200

/products/walnut-shelfdeleted, no redirect404

/products/brass-pullbody: 'not found'200 · soft

/policies/returnsserver error500

/products/linen-runnerok200

/products/clay-vaseok200

Redirect a removed product only to a genuinely relevant live equivalent. Otherwise return an honest 404 and remove it from submitted product data. A dead landing page is a poor shopper experience and needs correction.

The public signals this check looks for:

Products were deleted or unpublished on the site but are still in the product data you sen…
Products were deleted or unpublished on the site but are still in the product data you send Google, so their ads land on a 404.
A returns, shipping or privacy page was renamed, the old address now errors, and the foote…
A returns, shipping or privacy page was renamed, the old address now errors, and the footer still links to it.
A discontinued product page answers “200 OK” but says the item no longer exists…
A discontinued product page answers “200 OK” but says the item no longer exists: a soft 404 in Search Console’s terms.
The server throws 500 or 503 errors under load, during an app update, or while a plugin mi…
The server throws 500 or 503 errors under load, during an app update, or while a plugin misbehaves.
The store sits behind a maintenance page or a password while its products are still live i…
The store sits behind a maintenance page or a password while its products are still live in Merchant Center.
A typo in the product link, or a link to a staging or old domain, points at a host that do…
A typo in the product link, or a link to a staging or old domain, points at a host that does not answer.

What it looks like once it is right

The same clear-out removes the products from the product data the same day, 301-redirects each old URL to its collection, and a bulk check of every product link and footer link comes back 200.

Common mistakes

Common mistake

A seasonal clear-out deletes 40 products on the site but leaves them in the Merchant Center feed. Their links now return 404 while the ads keep running, and the footer’s returns link points at a page renamed in spring.

Fix checklist

Download your product list from Merchant Center or your platform and test every product link with a bulk URL checker. Anything that does not answer 200 on the first request goes on a list.
Open the Needs attention tab in Merchant Center and filter for landing page issues such as “Product page unavailable”. Fix those items first; they are the ones already affected.
For a product you no longer sell, remove it from your product data, as Google’s maintenance page advises for discontinued products, and 301-redirect its old URL to the closest live product or its collection.
Fix soft 404s at the source. A product that is gone for good should return a real 404 or 410 and leave your product data; a product coming back should keep its page live with an honest out-of-stock message.
Click the returns, shipping, privacy, terms and contact links in your footer and checkout, and repair any that land on an error page.
Chase 5xx errors with your host or platform: a recent app or plugin change, a traffic spike or a failing server are the usual places to look. Google’s page asks you to “make sure that your website is always available”.
Before planned downtime, pause the affected products or campaigns, and bring them back once the pages load again.
Re-test after every theme change, app install or migration, and use Search Console’s URL Inspection tool on a few product URLs to see the response Google gets.

The 200 that's lying

A soft 404 returns a healthy status while the page itself says the product is gone. The header claims success; the body confesses. Test both the response and rendered page, including redirects for dead products.

discontinued product URL

/products/walnut-shelf200

FlagHTTP 200, but the body says 'not found' — soft 404

Sorry — this product is no longer available.

(empty template · no product · status still 200)

301 to the nearest live sibling, or its parent collection

or return an honest 404 and drop it from the feed

Never redirect a dead product to the homepage. It is an unrelated destination and can be handled as a soft 404. Match the redirect to a genuine replacement, or let the URL return a clear not-found response.

Questions merchants ask

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

It means Google could not open the landing page you submitted for a product. Google's help page lists causes such as a 404, too many redirects, a 5xx server error, an unreachable robots.txt file and a hostname that does not resolve, and says products with an unavailable landing page are disabled until the page can be accessed.

What is a soft 404, and why does it matter for Shopping?

A soft 404 is a page that answers “200 OK” but shows an error or an empty page; Search Console reports it by that name. For a product link it is a dead end dressed as a live page. Remove the product from your data and return a real 404, or keep the page live with honest stock status.

How do I test all my product links at once?

Download the product list, with its links, from Merchant Center or your platform and run the links through a bulk URL status checker. Anything that is not a 200 is a job. Then check the Needs attention tab for landing page issues, and re-run the test after every clear-out or migration.

Remediation

Risk signal

A dead landing page is money spent on a click that goes nowhere, and Google’s help pages are clear that products need a page that works. Test your links after every change: errors turn up with clear-outs, migrations and app updates, rarely on their own.

PriorityTreat this and any other highest-severity findings as first-priority work, then document each fix.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

Community guidance

Written by Product Experts, the users Google recognises for their answers on its Merchant Center Community forum. Often stricter than Google’s help pages, and not Google policy.

How to fix Google Merchant Center suspensions (plain-language walkthrough)Merchant Center Community · Product Expert guide — support.google.com

Last reviewed 23 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.