Merchant Center disapproves a product with “Unavailable desktop landing page” or “Unavailable mobile landing page” when Google’s crawler could not load the URL in the link attribute: a 404 for a deleted product, a 5xx from the server, a timeout, a bot block or a redirect somewhere else. Make the URL return the product page with a 200 status for any visitor, then re-fetch the feed; Search Console’s URL Inspection tool shows you what Google sees.
| Shown in Merchant Center as | Unavailable desktop landing page |
|---|---|
| Attribute | link |
| Effect | Product disapproved |
| Where to find it | Products → Needs attention, then filter by this issue |
| Free check | Reported by the free feed check |
What Merchant Center means by “Unavailable desktop landing page”
Google’s crawler tried to open the product’s landing page and did not get a working product page back. Google’s product issues reference lists the issues as landing_page_error, “Unavailable desktop landing page”, and mobile_landing_page_error, “Unavailable mobile landing page”. Google’s help pages for the desktop and the mobile issue describe them for a landing page submitted through link_template or mobile_link_template, the attributes for merchant-hosted local storefronts, and give the same steps: make the page accessible from any device, location or browser, and test it with Search Console’s URL Inspection tool, choosing “Desktop” or “Smartphone” as the fetch type. Until Google can reach the page, the products stop showing in Shopping ads and free listings. The link specification has the requirements the page must meet.
The product is disapproved until a crawl succeeds. Google’s “Landing page not working” page covers landing pages that fail to load: an account or product disapproved under it can be fixed and sent for review, or the decision appealed.
Why it happens
- Deleted or unpublished products whose URL now returns 404, while the feed still lists them.
- Server errors (5xx) during a deployment, a plugin failure or an overloaded host at the moment of the crawl.
- Bot protection and geo-blocking. Cloudflare challenges, firewall rules, or a country block, such as one on US IP addresses, that keeps Google’s crawlers out.
- Password-protected or coming-soon storefronts, and staging URLs in the feed.
- Redirects to somewhere else. A URL that lands on the homepage or a category page, an interstitial, or a redirect loop.
- Mobile-only failures. A separate mobile address — a
mobile_link_templateURL — that returns a 404, redirects too many times or fails to connect when fetched as a smartphone, while the desktop page works. - http:// links on a store that has moved to https, where the old scheme no longer answers or redirects badly.
How to fix it
In Shopify
On Shopify, check for a storefront password, products unpublished from the Online Store channel but still in the feed, and apps that insert interstitials. Remove the storefront password, make sure every product in the feed is published to Online Store, and test one affected URL in Search Console’s URL Inspection tool with both the “Desktop” and the “Smartphone” fetch type.
In WooCommerce
Check the affected URLs’ status codes in your server log or with a quick fetch. For 403s, allow Googlebot through your security plugin, firewall or CDN without a JavaScript challenge; for 5xx, look at the error log around the crawl time; for 404s, remove the product from the feed. Our free connector only includes published, visible products and writes their current permalinks, so a deleted product leaves the feed on the next fetch.
In a CSV or XML feed
Filter Needs attention to this issue, download the CSV, and fetch each link with a plain HTTP client from outside your network: anything other than a 200 with the product page is the cause. Fix the URLs (current https address, the product page itself, no redirect), remove rows for products that no longer exist, and re-fetch the feed. Then, if Merchant Center lists “Landing page not working” under View setup and policy issues, request a review there.
How long until Merchant Center clears it
Google’s help page for the issue says that once the items are updated through a new data source upload or the Merchant API, the errors should disappear within a couple of days, after which the items start showing in Shopping ads and free listings again. An account with a verified and claimed website can ask for a website check to speed up the review; without one, an automatic review is still performed later. For “Landing page not working”, Google says a small ad edit or an appeal starts a fresh crawl, which usually finishes within 24 to 48 hours.
What FeedRobin does about it
The free check opens a sample of the product pages in your feed to compare prices, so a page that cannot be fetched shows up in that sample as unreachable, and the check separately reports product links still on http://, with the https:// address shown as a suggestion; FeedRobin does not switch product links to https. It does not crawl every URL, and the report says how many it looked at. For connected stores the links are the platform’s current product URLs, regenerated on every sync, so a renamed or deleted product cannot leave a dead link behind in the feed.
Questions merchants ask
The page loads for me. Why not for Google?
Google says firewalls, especially US-based IP blocks, and server-side restrictions can keep its crawlers out, and that a page that loads for you might not load for its automated systems. Geo-blocking, bot protection, a maintenance page shown to unknown visitors, or a store password all pass your test and fail Google’s. The URL Inspection tool in Search Console shows what Google received.
Why is only the mobile version unavailable?
Google crawls the mobile landing page with a mobile user agent. When you submit a separate mobile URL through mobile_link_template, that URL is checked on its own and can fail — a 404, too many redirects, a DNS or connection error — while the desktop page works. Test it in URL Inspection with “Smartphone” as the fetch type.
I deleted the product. Should I leave it in the feed until it clears?
No. Remove it from the feed. A deleted product’s URL keeps failing the crawl.
Sources
- How to fix: Unavailable desktop landing page — Google Merchant Center Help
- How to fix: Unavailable mobile landing page — Google Merchant Center Help
- Link template [link_template] — Google Merchant Center Help
- How to fix: Landing page not working — Google Merchant Center Help
- Link [link] — Google Merchant Center Help
- Product issues (Content API for Shopping, sunset on 18 August 2026): common item-level issue codes with their description and detail