Less content on mobile: a mobile-first indexing risk

What it means

This warning means the mobile version of your page has significantly fewer elements than the desktop version — either content is actually missing, or it's hidden behind accordions, tabs, or lazy-loaded components that aren't visible to crawlers.

Why it matters

Google indexes and ranks using the mobile version, and only content present on mobile is used. If content is deleted rather than merely hidden, it won't appear in search results or AI-agent responses. Googlebot does not scroll or click, so hidden content that requires interaction is invisible to it.

How to fix it

1. Ensure content parity between mobile and desktop — same primary content, headings, structured data, image/video URLs with alt text, titles, descriptions, and the same robots meta tag.
2. Replace content deletion with accordions or tabs to save space without losing indexed content.
3. Verify that lazy-loaded images and components use native loading="lazy" or IntersectionObserver, not interaction-triggered loading.
4. Check that the mobile version is not blocking JS/CSS in robots.txt — if disallowed, Google cannot render and content vanishes.

Example

<!-- desktop: full article, 1,400 words -->
<article>...full body copy, specs, FAQ...</article>

<!-- mobile: collapsed to a summary, 320 words -->
<article>...intro paragraph only, rest behind an app prompt...</article>

<!-- mobile: same primary content as desktop -->
<article>...full body copy, specs, FAQ (collapsible, but in the DOM)...</article>

Mobile-first indexing means Google ranks what's on mobile. Ship the same primary content to both; using accordions/tabs is fine as long as the text is in the HTML.

When it's not a problem

This is fine when the mobile version uses responsive design with content hidden in accordions or tabs — Google accepts this as long as the same content is present. It's also acceptable when above-the-fold content is identical and below-the-fold content loads via approved lazy-loading methods.

How Crawlinx detects it

We fetch the page with a mobile user-agent and compare word counts. Mobile is flagged when it carries under 70% of the desktop word count AND the gap exceeds 200 words, so trivial header/footer differences don't trip it.

How common is it?

Not yet observed in our audit sample. We publish this explainer because the check runs on every crawl; once an audited site trips it, this page will break the issue down by platform, gatekeeper, vertical and country.

FAQ

Does hidden-behind-a-tab content count on mobile?

Yes. Content inside accordions or tabs still counts as long as it's present in the HTML the crawler receives. What hurts you is content that's simply absent from the mobile page.

Why does mobile content parity matter?

Google indexes the mobile version. If your mobile page strips out body copy, specs or reviews, those never get indexed — you rank on the thinner mobile version, not the rich desktop one.

What causes a mobile content gap?

Separate m. templates, app-install interstitials replacing content, or a responsive design that server-side omits sections on small screens. Serve the full content and let CSS handle layout.

Related guides

• Mobile-First Indexing: How to Pass Parity Checks