How to Fix “Unavailable desktop landing page [link]” (404) in Google Merchant Center
Google could not load the landing page: a 404, a redirect chain, a soft 404, a geo-block or a robots rule stopped the crawler.
Scan your feed for this error for free
Paste your product feed URL (XML, CSV or JSON). The audit checks Unavailable desktop landing page [link] along with 25+ other pre-channel rules.
Why this happens
Technical root cause
Feed URLs are generated from handles or IDs that change when products are renamed, archived or moved between categories, and stale exports keep pointing at the old path.
Google Merchant Center reports it as Unavailable desktop landing page [link] and applies: Immediate product disapproval — the destination cannot be verified.
Native CMS friction
Shopify
Renaming a product changes its handle and the old URL 404s; collection-scoped URLs break when the product leaves the collection.
VTEX
Product URLs include the category path, so recategorising an item invalidates every previously exported link.
WooCommerce
Permalink structure changes rewrite every product URL at once without updating cached feed exports.
Fixing it manually
- 1
Export the disapproved item URLs and request each one to see the real status code.
- 2
Fix the source of the URL so the export builds the current canonical path, not a cached one.
- 3
Remove redirect chains — point the feed at the final URL directly.
- 4
Confirm the page is not blocked by robots.txt, a geo-redirect or an age gate for Google's crawler.
- 5
Exclude archived and unpublished products from the feed instead of leaving dead links.
The IRONFEED automated solution
One rule, applied to every product on every export. No spreadsheets, no re-uploads.
IF http_status(link) != 200 OR redirect_count > 1
SET link = canonical_url(product_handle)
IF still failing THEN EXCLUDE item from feedRun automatic linter checks before Google Merchant Center crawls your feed. IRONFEED validates every export against the channel spec, so this error is caught in Feed Review instead of in your channel dashboard.
Attribute requirements
| Attribute | Google Merchant Center requirement | Accepted format | IRONFEED transformation |
|---|---|---|---|
link | Required; must return HTTP 200 for Google's crawler | Absolute HTTPS URL, no redirect chain | Pre-export status validation with automatic exclusion of dead links |
canonical_link | Recommended when the feed URL carries tracking parameters | Absolute HTTPS URL | Derived from the clean product URL |
Frequently asked questions
Related Feed Issues & Fixes
Other critical errors affecting catalog performance on Google, Meta, TikTok, and Mercado Libre.
Image too small [image_link]
Feeds frequently export the thumbnail rendition instead of the master asset, because the thumbnail is the URL the storefront exposes first in its product payload.
View Fix & RuleInvalid URL in link or mobile_link
Tracking parameters are appended by string concatenation, which produces double question marks, unencoded spaces or duplicate UTM keys. Some exports also emit a path without the domain.
View Fix & RulePromotional overlay on image [image_link]
Marketing teams bake sale badges into the primary asset for the storefront, and the feed inherits whichever image is flagged as primary in the catalog.
View Fix & RuleLooking for a different error?