AI AI Tools Guidebook
Troubleshooting

Indexing Dropped After Google Switched Site to Mobile-First Indexing

You got the Search Console email confirming mobile-first indexing. Two weeks later, pages and impressions drop. The desktop version had content the mobile version doesn't.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

Search Console sends the notification: “Your site is now indexed mobile-first.” A week or two later, Pages report shows a drop in valid pages and impressions decline 15-40%. Mobile-first means Google uses the mobile rendering of your page as the canonical version for ranking. Anything the desktop version has and the mobile version doesn’t — content, structured data, internal links, alt text — effectively disappears from Google’s view.

This article focuses on what desktop-only signals get lost, not on mobile usability (covered separately). The fix is to bring the mobile version to parity with desktop, content-wise.

Common causes

1. Mobile version hides content behind tabs / accordions without rendering it

Desktop shows the full article. Mobile, to fit small screens, uses accordions that lazy-load section content via JS. Googlebot renders the mobile version but the accordion JS doesn’t fire for crawlers. Hidden content stays hidden.

How to spot it: View source on the mobile URL (or DevTools mobile emulation, “View source” not “Inspect”). If section bodies are missing from raw HTML, they’re missing from the index.

2. Mobile site is a separate m.example.com subdomain with thinner content

Legacy m-dot setup. Mobile site was built years ago, has shorter intros, no FAQ, no related links. Google now considers m.example.com the canonical and ignores the desktop’s richer content.

How to spot it: Compare m.example.com/article/x against www.example.com/article/x side by side. Count words. Count internal links. If mobile is significantly shorter, that’s the problem.

3. Structured data only on desktop template

Desktop emits Article, FAQPage, Breadcrumb JSON-LD. The responsive template skips JSON-LD on small viewports to “reduce payload.” Rich results disappear.

How to spot it: Mobile URL → view source → grep application/ld+json. Compare count and types against desktop view source.

Desktop has a sidebar with 20 related articles, an author bio, archive links. Mobile collapses everything into a hamburger menu loaded by JS. Googlebot loses those internal link signals.

How to spot it: curl -A "Mozilla/5.0 (iPhone; CPU iPhone OS 17_0)" https://yoursite.com/article/x and count <a href= tags. Compare to a desktop UA fetch.

5. Images missing alt text or smaller srcset on mobile

Desktop has <img alt="detailed alt text">; mobile uses a different <picture> element without alt, or a thumbnail-only version. Image Search rankings collapse.

How to spot it: Mobile view source → grep <img. Look for missing alt= attributes or different image URLs than desktop.

6. Robots meta or canonical differs across viewports

A buggy template emits <meta name="robots" content="noindex"> only on mobile viewport (or vice versa). Or canonical points to a different URL based on user-agent.

How to spot it: Fetch the same URL with desktop UA and mobile UA. Compare the <meta name="robots"> and <link rel="canonical"> tags. Any difference is a bug.

7. AMP page set as canonical but rendering breaks

If you used AMP pages and they’re now the mobile canonical, AMP validation errors or missing content there directly hurt indexing of the non-AMP page.

How to spot it: Search Console → AMP report. Any errors there are now ranking-affecting.

Shortest path to fix

Step 1: Audit content parity

Pick 20 representative pages. For each, capture desktop HTML and mobile HTML. Compare word count, link count, structured data blocks, image count, alt text.

for url in /article/a /article/b /category/c; do
  echo "=== $url ==="
  curl -s -A "Mozilla/5.0 (X11; Linux)" "https://yoursite.com$url" | wc -w
  curl -s -A "Mozilla/5.0 (iPhone)" "https://yoursite.com$url" | wc -w
done

Any gap > 10% needs to be closed.

Step 2: Move accordion / tab content into raw HTML

Even if a section is hidden by CSS or behind a tab UI, it must be in the rendered HTML, not lazy-loaded by JS on user interaction.

<!-- Bad: only renders on click -->
<button onclick="loadSection()">Show details</button>
<div id="details"></div>

<!-- Good: content in HTML, hidden by CSS, JS toggles visibility -->
<details>
  <summary>Show details</summary>
  <div>The actual content lives here in the raw HTML.</div>
</details>

Step 3: Consolidate m-dot into responsive

If you still have m.example.com, the long-term fix is one responsive site at www.example.com. Short-term: ensure m-dot has the same content, structured data, and internal links as desktop, with bidirectional rel=alternate and rel=canonical.

Step 4: Emit structured data on every viewport

JSON-LD must be in the HTML regardless of screen size. Never inject it conditionally based on viewport width or user-agent.

The hamburger menu should be HTML links hidden by CSS, not links injected by JS on click:

<nav class="mobile-nav">
  <a href="/categories/">Categories</a>
  <a href="/authors/">Authors</a>
  <a href="/archive/">Archive</a>
</nav>

Then a CSS class shows/hides on toggle.

Step 6: Unify meta tags

Verify <meta name="robots">, <link rel="canonical">, and <meta name="description"> are identical across desktop and mobile viewports. Render them server-side, not from JS.

Step 7: Resubmit affected URLs

After parity is restored, URL Inspection → “Request indexing” on the 20-50 most impacted pages. Full recovery typically takes 4-8 weeks.

When this is not on you

Some impression drop after mobile-first switch is normal even with perfect parity — the SERP simply changes. Drops > 25% are usually a content gap, not a normal fluctuation.

Easy to misdiagnose as

A Core Web Vitals or page experience update. Page experience matters, but it’s a tiebreaker. A 30% impression drop right after mobile-first switch is almost always a content-parity issue, not CWV.

Prevention

  • Single responsive codebase; avoid m-dot subdomains.
  • Never gate content behind JS-required interactions on mobile.
  • All structured data lives in the server-rendered HTML.
  • Run a desktop-vs-mobile diff in CI for a sample of pages.
  • Audit alt text on every image regardless of viewport.

FAQ

  • Can I opt out of mobile-first indexing? No — all sites are now mobile-first by default since 2023.
  • Does Google still look at desktop content at all? Very rarely, only for sites without a mobile version. Don’t rely on it.

Tags: #SEO #Troubleshooting #Indexing #Search Console #mobile-first #responsive

Related Articles