Google Merchant Center says a product page is unavailable when its crawler cannot reliably access the landing-page URL submitted in your product data. The cause may be a 404, server error, redirect chain, blocked crawler, unreachable robots.txt, DNS failure, regional restriction or invalid feed URL. A technical ecommerce SEO diagnosis starts with the affected link value, not the URL copied from your browser history. For stores selling into Dubai and the wider Emirates, our UAE ecommerce SEO service also checks market URLs, crawler access and regional feed behavior.
Download the affected-item list, test each final URL on mobile and desktop without login or cookies, and match the result to Merchant Center’s specific crawl error. Fix the underlying access problem before requesting another website check.
Quick diagnosis: what does the error mean?
| Merchant Center detail | What it means | First action |
|---|---|---|
| Page not found (404) | The submitted URL does not resolve to a live product | Correct the feed URL or restore the page |
| Too many redirects | Google cannot reach a stable final landing page | Submit the final canonical URL and shorten the chain |
| HTTP 5xx or timeout | The server failed or responded too slowly | Review uptime, logs, capacity and caching |
| Robots.txt unreachable | Google cannot confirm crawl permission | Restore a reliable robots response |
| Blocked by robots | Googlebot or AdsBot-Google is disallowed | Update crawl rules |
| Hostname not resolvable | DNS lookup failed | Check DNS records and propagation |
| Invalid URL or protocol | The link is malformed or uses the wrong domain | Correct and encode the submitted value |
| Regional page inaccessible | Geo, firewall or region parameter blocks Google | Allow required crawler access from the US |
Step 1: open the exact submitted link
In Merchant Center, open an affected product and copy the value submitted through link, link_template or mobile_link. Do not assume it matches the visible product URL in your CMS.
Test that URL in a private browser on mobile and desktop. Record every redirect, the final URL, status code and visible product. Tracking templates and market parameters can create a different path from the clean storefront URL.
Step 2: fix 404 and deleted-product URLs
If the submitted URL returns 404, update the feed to a live page for the same product. Do not redirect it to a category or home page solely to pass the crawl. The landing page must represent the product submitted.
Remove permanently unavailable items from active product data or use the correct availability workflow. If a product moved to an equivalent canonical URL, create a direct permanent redirect and submit the final URL in future feed updates.
The HTTP standard defines 404 Not Found as the server not finding a current representation of the target resource. A custom error design does not change that status. Test the response code, not only the words visible in the browser.
Step 3: remove redirect chains and loops
Common chains include HTTP to HTTPS, non-www to www, old domain to new domain, country selection, language routing and then the product URL. Merchant Center’s official issue page says landing pages with more than two redirects can trigger the unavailable error.
Submit the final canonical HTTPS product URL wherever possible. Test both desktop and mobile values and remove app or campaign redirects that create loops for clean sessions.
Step 4: investigate server errors and timeouts
A page that loads for you can still fail intermittently for Google. Check server and CDN logs around the diagnostic timestamp for 500, 502, 503, 504, connection reset or timeout responses. Compare normal users, Googlebot and AdsBot-Google.
Review hosting capacity, database performance, uncached variant requests, application errors and rate limiting. Do not whitelist only one crawler IP because Google crawler addresses can change; follow Google’s verification and access guidance.
Step 5: make robots.txt reliable
Merchant Center can disable products when it cannot access the site’s robots.txt file, even if the product page itself appears live. Test /robots.txt repeatedly and confirm a stable response.
Allow both Googlebot for organic crawling and AdsBot-Google for ad landing-page checks where required. Google Merchant Center’s product crawl issue guidance notes that allowing one crawler while blocking the other may still cause problems.
Step 6: check firewall, bot protection and geo rules
Web application firewalls can challenge or block automated requests based on user agent, IP reputation, request rate, country or missing cookies. Review security events for Google crawlers and product URL patterns.
Google states that product pages should be accessible from required locations and notes that it often crawls from the United States. A store can still limit where it sells, but its submitted landing pages must be crawlable under Merchant Center requirements.
Step 7: fix DNS and hostname failures
Check A, AAAA and CNAME records, nameserver health, DNSSEC, certificate coverage and recent domain changes. Test resolution from multiple networks. A bad IPv6 record can fail some requests even when IPv4 works.
Make sure the submitted hostname is the domain verified or claimed in Merchant Center. Remove old staging, platform and regional hosts from product data after migration.
Step 8: verify URL format and encoding
The URL must begin with HTTP or HTTPS, use the verified domain and encode special characters correctly. Look for spaces, unescaped commas, double question marks, broken entity encoding and accidental spreadsheet truncation.
For feeds built from templates, generate a sample URL for every market and product type. A template can look valid while producing malformed values only when optional parameters are blank.
Step 9: test mobile and desktop independently
If either the mobile or desktop landing page fails, Merchant Center can disapprove the item for both device types. Remove a separate mobile_link when the responsive canonical page is the correct destination, or fix the mobile URL and redirects.
Test on a fresh device profile without saved region, age or language cookies. Pop-ups must be dismissible and must not prevent Google from reading product information.
Step 10: verify regional pricing URLs
Stores using regional availability and pricing may submit URLs with a region identifier. Each generated URL must load the same product and remain crawlable. Confirm the region ID is valid, the page does not redirect endlessly and a default region is not required from a cookie.
Compare feed price and availability with what appears on initial page load for that region. Landing-page access can be fixed while a separate mismatch issue remains.
Step 11: align the page with landing-page requirements
A technically live page can still fail policy checks if the product is unavailable to purchase, hidden behind a blocking overlay or different from the feed item. Google’s landing-page requirements say price, availability and product identity should remain consistent regardless of device, browser, location, cookies or user agent.
Make the advertised product, price and buy action visible. Do not show a category, internal-search result or “select your country” dead end as the final landing page.
Step 12: request a review only after the fix is live
Google’s official product page unavailable guide recommends correcting the product links, uploading updated data and requesting a website check where available. An automatic review may also occur later.
Before requesting, test several affected URLs and one unaffected control. If the problem was intermittent, monitor for at least one stable period appropriate to the store’s traffic and infrastructure.
A practical investigation workflow
- Download all products affected by this exact issue.
- Group them by host, URL pattern, platform and error detail.
- Test one representative URL from each group.
- Capture status, redirects, robots response and final page.
- Check server, CDN and firewall logs at crawl time.
- Correct feed links or infrastructure.
- Refresh the product data source.
- Retest mobile, desktop and regional variants.
- Request a website check once.
- Monitor Needs attention and item eligibility.
How does the diagnosis differ by platform?
On Shopify, review the Google and YouTube sales channel, product publication, Markets domain, password protection and app redirects. A Shopify SEO audit should compare the submitted feed link with the canonical storefront URL.
On WooCommerce, review the feed plugin, cache, security extension, permalink status, product visibility and hosting logs. The feed may store an old URL after a slug or domain change.
What not to do
- Do not repeatedly request review while the page still fails.
- Do not redirect deleted products to an unrelated category.
- Do not block AdsBot-Google while allowing only Googlebot.
- Do not test only from your logged-in office browser.
- Do not assume a 200 status means the correct product loaded.
- Do not leave stale mobile or regional links in the feed.
FAQs
Why does Merchant Center say unavailable when the page works for me?
Google may receive a different response because of user agent, location, cookies, firewall rules, intermittent errors or the exact feed URL. Test a clean session and inspect logs.
How many redirects can a Merchant Center landing page have?
Google’s product-page-unavailable guidance warns about more than two redirects. Submit the final canonical URL and keep the path as direct as possible.
Which crawlers need access?
Merchant Center guidance references Googlebot for organic search and AdsBot-Google for ads. Check current documentation and allow the required crawlers to access product pages and robots.txt.
How long does reapproval take?
Timing varies by issue and review. Google notes that crawl-issue fixes may take up to 48 hours to reappear in listings, but do not promise that as a universal deadline.
Should I request a review for every affected product?
Fix the shared cause and refresh the data source first. Use the website-check or review workflow shown for the issue, then monitor all affected items.
Leave a Reply