Merchant Center landing page not working or unavailable: causes and fixes
UPDATED 4 MIN READBY THE SCENOX COMMERCE TEAM
SHORT ANSWER
Landing page errors mean Google could not load the product URL in your data: a 404, a 5xx error, too many redirects, a page under construction, a robots.txt block or a bot-protection wall. Test the URL in a private window and with the URL Inspection Tool, fix the cause and request a review. Recrawls usually take 24 to 48 hours.

ON THIS PAGE
When Google cannot load your product page, the item cannot be shown. This is also the issue most often caused by something outside the feed, such as a migration, a security setting or a slow server. This guide covers the variants, how to diagnose them and the fixes. For other disapprovals, see the Merchant Center disapprovals guide.
How the issue appears
In Products, then Needs attention, you may see "Landing page not working", "Page not found (404)", "Unavailable desktop landing page" or "Unavailable mobile landing page". Google's help pages on the landing page not working policy and the unavailable desktop landing page issue describe each. The desktop variant relates to the [link_template] attribute, the mobile variant to [mobile_link_template], and each can be tested with the URL Inspection Tool in Search Console using the matching fetch type.
What triggers it
- 404 or other 4xx or 5xx status. Deleted, renamed or unpublished products, or server errors.
- Redirect problems. Google's guidance is no more than two redirects. Chains left by a migration cause failures.
- Robots.txt blocks. Googlebot and Googlebot-Image must be able to crawl the site.
- Bot protection. A firewall or CDN that challenges crawlers.
- Page under construction or password protected.
- Slow loads. Timeouts during the crawl.
- Checkout unreachable. Google expects customers to be able to get from the landing page to checkout.
- Variant URLs that do not resolve.
How to find affected items
- Filter Needs attention by the landing page issue and download the CSV.
- Open the URLs in a private window, on desktop and mobile. Use a tool that shows status codes and redirect chains.
- Run important ones through the URL Inspection Tool and check what Google sees.
- Check your server logs for Googlebot requests that returned errors.
- Look for a date pattern. A sudden cluster usually follows a migration, theme change or security update.
Fix steps for Shopify
- Check deleted or archived products. A product removed from the store but still in the feed returns 404. Either restore it or remove it from the feed.
- If you changed handles, Shopify normally keeps redirects from old URLs, but confirm they exist for the affected products. A feed that still points at an old URL passes through a redirect, so update the feed to the final URL.
- Remove password protection from the storefront if it is still on.
- Check apps that add geo-redirects or age gates, which can bounce crawlers.
- Resync the sales channel and check Needs attention.
Fix steps for other platforms and feeds
- Regenerate the feed after any URL change and point links directly at final HTTPS URLs.
- Allow Googlebot and Googlebot-Image in robots.txt and in the firewall or CDN. Verify with the URL Inspection Tool.
- Cut redirect chains to two or fewer, ideally zero.
- Improve server response times and avoid heavy scripts that delay rendering.
- Check the mobile template link separately if you use one.
- After a platform change, map old URLs with 301 redirects. See our 301 redirect guide and the store migration service.
Re-review and recrawl expectations
Google says that once technical fixes are live, a small edit to the item or a review request can trigger a fresh crawl, which usually resolves within 24 to 48 hours. It also says products may take up to 48 hours to reappear after the page is accessible. If a review limit applies, Merchant Center states it, so fix everything before requesting.
Prevention
- Rebuild the feed after every URL, theme or platform change.
- Monitor for 404s on product URLs and remove or redirect them.
- Review firewall rules after security changes.
- Keep redirects direct and documented.
When to do it yourself and when to hand it off
If one broken URL or a single redirect is behind the issue, fixing the link and requesting a recrawl is a quick, do-it-yourself job.
Hand it off when a migration or URL change left many product pages broken and you need redirects and the feed fixed together. Our feed management service covers setup and clean-up: the AI engine does the volume, a person reviews every output, and you approve before anything goes live. We work through a staff or collaborator account you can remove, never your passwords. Feeds start from ₹7,999 / $299 / £239 / A$449 per channel, with a fixed quote after we inspect your files, and turnaround is from 48 hours for eligible projects; turnaround depends on scope, catalog complexity and the quality of the data and access we receive. You can ask for the free 10-product sample if the project is a fit.

