Mobile-first indexing: what happens to content hidden on mobile
Short answer: Google crawls and indexes the mobile version of your pages, so content that exists only on desktop is effectively invisible to it. Tucking text into tabs or accordions on mobile is fine according to Google's own guidance, as long as it's in the page; removing it, or loading it only when someone taps, is not. Check that headings, structured data, titles, descriptions, images and robots tags match across versions, then confirm with URL Inspection.
Many sites were designed desktop-first and then trimmed for phones: shorter descriptions, fewer FAQs, a carousel replaced by one image. That made sense for small screens. Under mobile-first indexing, though, the trimmed version is the one Google reads.
How Google reads your site today
Google's mobile-first indexing best practices say plainly that it uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. The same page explains that the parity concerns apply mainly to two setups:
- Dynamic serving: same URL, different HTML depending on the device
- Separate URLs (often m.example.com): different HTML on different URLs
With responsive design, which Google recommends as the easiest to implement and maintain, the same HTML goes to every device, so content and metadata are identical by definition. Problems still creep in when a responsive theme hides or omits elements on small screens using JavaScript, or when a page builder lets you mark sections "desktop only".
Hidden, tucked away, or missing?
These three are different, and only one is a real problem.
- Tucked away (accordions, tabs, "read more" that expands content already in the HTML): Google's guide explicitly suggests moving content into accordions or tabs to save space instead of removing it.
- Hidden by CSS but present in the HTML: the text is in the page Google fetches, but Google's guide doesn't address this case directly. Prefer a visible toggle (an accordion) over permanently hidden text, and make sure it isn't a thinner version of the desktop content.
- Missing (not in the mobile HTML at all, or loaded only after a tap or swipe): Google can't index what isn't there. Its guide warns it won't load content that needs user interaction such as swiping, clicking or typing.
The page also notes that if your mobile page intentionally carries less content than desktop, you can expect some traffic loss.
Mismatch → effect → fix
| Mismatch between mobile and desktop | What Google ends up with | Fix |
|---|---|---|
| Product details or service text removed on mobile | Less content to rank on; the desktop text is ignored | Restore the text in accordions or tabs on mobile |
| Reviews or FAQs load only when "Show more" is tapped (fetched on click) | That content isn't indexed | Include it in the initial HTML and expand/collapse with CSS or JavaScript |
| Different headings on mobile (shortened or removed H2s) | Weaker understanding of the page structure | Use the same clear headings on both |
| Structured data only in desktop templates | No rich result eligibility from the mobile page | Add the same structured data to mobile; on m-dot sites, use mobile URLs inside it |
| Different title or meta description on mobile | Mobile versions shown and used | Make them equivalent |
noindex or nofollow on mobile pages only |
Pages may drop from the index | Use identical robots meta tags |
| Images missing, low-resolution or without alt text on mobile | Weaker image search presence | Same quality images and alt text on both versions |
| Image URLs differ between versions | Possible temporary image traffic dip | Use the same image URLs where you can |
| Lazy-loaded content that only appears on scroll events Google doesn't trigger | Content not seen | Load content when it enters the viewport, using browser lazy-loading or IntersectionObserver |
| Mobile resources blocked in robots.txt | Page can't be rendered properly | Allow crawling of CSS, JavaScript and images on the mobile site |
| m-dot pages redirect to the mobile home page | Those pages vanish from the index | Give every desktop page an equivalent mobile URL |
Lazy loading: the quiet one
Lazy loading is good for speed and usually fine for search. Google's lazy-loading guidance asks that relevant content load whenever it's visible in the viewport, using methods such as the browser's built-in lazy loading or the IntersectionObserver API. Where infinite scroll loads more items, it recommends paginated loading with distinct, linked URLs and updating the displayed URL with the History API.
The risky pattern is content that only loads in response to a scroll event or a click. If a "Load more reviews" button fetches the reviews, assume Google doesn't see them.
Separate mobile sites (m-dot): extra checks
If your site still runs on separate desktop and mobile URLs, Google's guide adds several requirements:
- Error status must match: a page that works on desktop but errors on mobile will be missing from the index
- No URL fragments (#) on mobile URLs, since fragment URLs usually aren't indexable
- Each desktop page needs an equivalent mobile page, not a redirect to the mobile home page
- Verify both versions in Search Console
For most small businesses, moving to a responsive design removes this whole category of problems.
A 30-minute audit
- Pick your ten most important pages: home, top services or products, top blog posts.
- Open each on a phone and on desktop side by side. Note any text, images, FAQs, reviews or tables missing on mobile.
- Check your page builder's visibility settings. Look for sections set to "hide on mobile" and decide whether each should be restored or collapsed instead.
- View source on mobile (or emulate a phone in browser developer tools) and search the HTML for a sentence from each hidden section. If it's not there, Google doesn't have it.
- Compare titles, meta descriptions and robots tags between versions if you use dynamic serving or m-dot.
- Run URL Inspection. Google's URL Inspection help describes testing a live URL and viewing a screenshot of how Google's inspection tool renders the page, plus the loaded resources and page code. Search the rendered HTML for your hidden sections. For the step-by-step on that tool, see using URL Inspection after a change.
- Fix, then re-test the same pages.
What not to worry about
- A different layout on mobile. Google's guide allows a different design to suit small screens, as long as the content is equivalent.
- Collapsed accordions. If the text is in the HTML, it counts.
- Fewer decorative images, as long as important images (products, team, work samples) are present.
FAQ
Does content in a collapsed accordion count for SEO?
Google's guide recommends accordions and tabs as the way to keep content on mobile without cluttering the screen, so content that is in the page but collapsed is the right approach.
My site is responsive. Do I need to worry?
Less, but check for sections your theme or builder hides on mobile and for content that only loads on tap.
Will Google index my desktop-only content at all?
Google indexes from the mobile version. Treat content missing on mobile as missing from the index.
Should I keep an m-dot site?
It can work if you follow every extra requirement, but responsive design is simpler to keep consistent.
Restoring the pieces your mobile pages quietly dropped is usually a short job, so send us the pages you rely on most and we'll compare both versions.