"Unavailable desktop landing page" and "Unavailable mobile landing page" are two Google Merchant Center issues with one cause: Google tried to open a product's page and could not. This guide explains what each one means, the crawl errors behind them, and how to get the products back.
What the two issues mean
Google's help pages describe both the same way. A landing page you submitted for a product cannot be accessed by Google, so it may not be accessible to shoppers either. Affected products stop showing in Shopping ads and free listings until Google can reach the page.
| Issue | What failed |
|---|---|
| Unavailable desktop landing page | Google's crawl of the desktop landing page |
| Unavailable mobile landing page | Google's crawl with a mobile user agent |
Google notes that the mobile issue stops the product on desktop too.
Find the crawl error
In Merchant Center, go to Products and open the Needs attention tab, then use the filter to find the affected products. Google's steps say to check each product's landing page by its item ID, and that a Crawl error column shows why Google could not reach it.
The crawl errors and their fixes
Google lists the same crawl errors on both help pages. Each one points to a different kind of problem.
| Crawl error | What Google says to do |
|---|---|
| Page not found (404) | Submit a working landing page URL |
| Too many redirects | Use a URL with no more than 2 redirects |
| Could not connect, or HTTP 5xx response | Keep the website consistently available |
| Hostname not resolvable | Check that your DNS configuration is correct |
Google also sets rules for the URL itself: it has to start with http:// or https://, use your verified domain, and have symbols URL-encoded, for example a comma written as %2C.
Common causes on a store
These are typical situations behind each error, not a list from Google. Check them against the crawl error you see.
- 404: The product was deleted, unpublished or had its URL changed after the product data was sent
- Redirects: An old URL passes through a chain of redirects before reaching the page
- 5xx or no connection: The site was down or in maintenance when Google crawled it
- Hostname: A domain or DNS change has not finished
Test the page and request a check
Google recommends the URL Inspection Tool to test a page the way its crawler sees it. Select Desktop as the type of fetch for the desktop issue, and Smartphone for the mobile issue.
- After fixing: You can request a website check to speed up reapproval. Your account needs a verified and claimed website
- Review time: Google says it may take up to 12 hours, and you cannot submit another request during that time
- Without a request: An automatic review happens later
- After new product data: Google says the errors should disappear within a couple of days
For other issues, see the common reasons products are disapproved.
Doing this at scale
FeedFix checks every product against Google Merchant Center and Meta Catalog rules and scores each one from 0 to 100 per channel. It drafts compliant title and description rewrites that you review as before/after diffs and apply in bulk, and every change is audit-logged. It does not repair broken URLs or server errors, so those stay with you or your developer. See FeedFix.