Google Merchant Center · Landing pages

    Unavailable Mobile Landing Page in Merchant Center: Fix It

    Shown in Google Merchant Center: Unable to view store on mobile

    How do I fix "Unable to view store on mobile" in Google Merchant Center?

    "Unable to view store on mobile" (formerly "Unavailable mobile landing page") means Google couldn't load your product page when crawling as a smartphone, even if it works on desktop, so the product is disabled on both mobile and desktop. The fix is to test the URL with a smartphone user agent, remove whatever breaks or blocks it on mobile (redirects, interstitials, bot rules, a bad mobile_link), then request a website check.

    What this issue means

    Google crawls landing pages with both desktop and mobile user agents. Most shopping traffic is mobile, so if the smartphone crawler fails, Google treats the product as unavailable. Google says ads and listings for affected products are disabled on desktop and mobile until it can access the page, so one mobile problem takes the whole product offline.

    If you submit a mobile_link attribute, Google crawls that URL for mobile. If you don't, it crawls your link URL with a mobile user agent.

    Why it happens

    Mobile-specific causes are different from a simple 404:

    • Mobile-only redirects. The site sends phones to an m. subdomain, a separate mobile path or the homepage, adding redirect hops (Google allows no more than two) or landing on a page without the product.
    • A broken or outdated mobile_link. The feed still points to an old mobile site that was retired.
    • App-install or "open in app" redirects that bounce mobile visitors away from the web page.
    • Full-page interstitials and popups (age gates, country selectors, email signups) that replace the content for mobile visitors.
    • Bot protection triggered by mobile user agents. Firewall or CDN rules challenge or block the smartphone crawler specifically.
    • Robots.txt rules that block Googlebot on mobile paths or the mobile subdomain. Google reports this as a separate robots.txt variant.
    • Mobile pages that time out because of heavy scripts, or that return 5xx under load.

    How to fix it

    1. Get the exact URL. In Products > Needs attention, filter by the issue and open a product. Check whether Google crawled your link or a mobile_link.
    2. Test as a smartphone. In Search Console, use the URL Inspection Tool and run a live test (Google's smartphone crawler is used by default). Check that the page renders the product, not a redirect, challenge or popup. In a desktop browser, use developer tools to emulate a phone and watch the redirect chain.
    3. Remove mobile redirects. Use responsive design so the same URL serves everyone. If you must keep a separate mobile site, make sure each product URL maps to the matching mobile product URL in one hop.
    4. Fix or remove mobile_link. If your site is responsive, you don't need mobile_link; remove the attribute so Google uses link. If you do need it, make sure every value is a live product page on your verified domain.
    5. Tame interstitials. Age gates, location pickers and signup popups shouldn't hide the product for crawlers. Use dismissible overlays or banners rather than full-page redirects.
    6. Check firewall and CDN rules. Make sure rules don't challenge Googlebot's smartphone user agent. Use your provider's verified-bot allowances rather than allowing by user agent string alone, since that can be spoofed.
    7. Platform specifics.
      • Shopify: Mobile problems are usually caused by apps: popups, geolocation redirects, age verification and "open in app" banners. Disable recently added ones and retest. The Google & YouTube app sends a single responsive URL, so mobile_link usually isn't needed.
      • WooCommerce: Check mobile-specific plugins, AMP setups and caching plugins that serve a different mobile cache. A stale or broken mobile cache is a common cause.
    8. Request a website check from the product's issue panel once the smartphone test passes.

    How long until it's fixed

    Google says a website check can take up to 12 hours, and you can't submit another request during that period. After a successful fix the issue should clear from Needs attention within a couple of days. If you don't request a check, Google will recheck automatically later.

    How to prevent it

    • Use one responsive URL per product instead of a separate mobile site.
    • Test new popups, apps and plugins on a phone before launch.
    • Keep bot protection configured to allow verified Googlebot.
    • Run a smartphone URL Inspection test on a few products after any theme or CDN change.
    • Track page speed on mobile; slow pages are more likely to time out during crawls.

    Mobile landing page issues often hide behind apps and CDN settings. Mercantads can find the blocker and get your products back into Shopping. Get help with Merchant Center or contact us.

    Fix it yourself or have us fix it

    Do it yourselfMercantads does it for you
    Find the causeFollow the steps on this pageWe audit your feed, store and account
    Make the fixEdit products, feed rules or site pages yourselfWe fix it, in bulk where possible
    ReviewsRequest the review and waitWe prepare and submit the review for you
    After it's fixedWatch for it to come backOngoing feed monitoring so it doesn't
    Talk to us
    FAQ

    Frequently Asked Questions

    Google disables the product everywhere when it can't access the mobile page. Fixing the mobile problem restores both.

    Only if mobile visitors use a different URL than desktop visitors. Responsive sites should leave it out.

    Yes, if it redirects to a separate page or hides the product content for crawlers. A dismissible overlay on the same URL is less likely to cause problems.

    Unavailable Mobile Landing Page in Merchant Center: Fix It

    Tell us what Google Merchant Center is showing. We'll find the cause and fix it, so your products and ads get back to selling.