The discussion about "mobile-first" has been going on for more than a decade. In 2015, it was an anticipation. In 2018, it was a warning. In 2023, Google switched its index completely to mobile-first. In 2026, talking about it as a "trend" is anachronistic.
And yet, the numbers show that the problem persists. According to an analysis by Ryte (2025) on 30,000 European sites, 23% still have significant differences between their desktop and mobile versions — hidden content, missing features, different schema markup. These sites are indexed based on their incomplete mobile version, and their performance suffers as a result.
Mobile-first in 2026: where do we stand?
"Mobile-first indexing" means that Google uses the mobile version of your site as the primary version for indexing and ranking. It is not an additional ranking factor — it is the foundation on which everything else is evaluated.
Concretely, if your mobile version has less content than your desktop version, it is the mobile version (with less content) that Google indexes. If your mobile version has no schema markup while your desktop version does, Google does not see your schema markup. If your mobile version is slow while your desktop version is fast, your Core Web Vitals are those of mobile.
European traffic figures according to Statcounter (January 2026):
| Region | Mobile | Desktop | Tablet |
|---|---|---|---|
| Europe (average) | 68% | 28% | 4% |
| Belgium | 62% | 34% | 4% |
| France | 65% | 31% | 4% |
| B2B (average) | 45% | 50% | 5% |
Important note for B2B: desktop remains the majority in some sectors (SaaS, finance, legal). But that does not mean you can ignore mobile — Google indexes the mobile version regardless of your traffic distribution.
Real impact on rankings
Mobile-first impacts rankings in three ways:
1. Indexed content = mobile content. If content is hidden on mobile (closed accordions, tabs not visible by default), Google considers it less important than visible content. Since 2020, Google has nuanced this position by declaring that content in mobile accordions is treated normally — but in practice, tests show that directly visible content performs better.
2. Core Web Vitals = mobile metrics. Your Core Web Vitals are measured on mobile. An LCP of 1.8s on desktop and 4.5s on mobile means Google sees an LCP of 4.5s. The shift from "good" to "poor" often happens on mobile.
3. User experience = mobile experience. User experience signals (bounce rate, time spent, interaction) are measured across all devices. But if 68% of your users are on mobile and your mobile UX is mediocre, your overall engagement metrics will suffer.
According to Cindy Krum, CEO of MobileMoxie (Berlin office): "The biggest misunderstanding about mobile-first is believing it is about having a responsive site. Responsive has been a prerequisite since 2015. Mobile-first in 2026 means thinking mobile first in every decision — architecture, content, performance, interaction."
Core Web Vitals on mobile: the benchmarks
Google's thresholds are the same for mobile and desktop, but reaching them on mobile is significantly more difficult:
| Metric | Good | Needs improvement | Poor | European mobile median |
|---|---|---|---|---|
| LCP | ≤ 2.5s | 2.5-4s | > 4s | 3.1s |
| INP | ≤ 200ms | 200-500ms | > 500ms | 280ms |
| CLS | ≤ 0.1 | 0.1-0.25 | > 0.25 | 0.12 |
The European median falls in the "needs improvement" range for all three metrics. This means the majority of sites do not meet Google's thresholds on mobile. This is a competitive opportunity: if you reach the "good" thresholds, you are already above half the sites in your sector.
The most impactful mobile optimisation levers
- LCP: optimise the hero image (WebP format, adapted size, preload). It is often the LCP element on mobile.
- INP: reduce blocking JavaScript. Defer non-critical scripts. Use
requestIdleCallbackfor heavy tasks. - CLS: define explicit dimensions for images and iframes. Reserve space for ads. Avoid fonts that cause a flash of invisible text (FOIT).
Mobile UX and SEO: the interdependencies
Mobile UX impacts SEO indirectly but measurably. A mobile user who does not find what they are looking for within 3 seconds returns to the search results. This quick return (pogo-sticking) is a negative signal for Google.
Mobile UX elements that impact SEO:
- Tap target sizes: Google recommends a minimum of 48x48px for buttons and links. Targets that are too small frustrate users and increase the bounce rate.
- Text legibility: minimum font size of 16px without zooming. Text that is too small on mobile pushes the user to zoom in or leave.
- Intrusive interstitials: Google penalises pop-ups that cover the main content on mobile. Cookie banners are tolerated; full-screen marketing pop-ups are not.
- Navigation: a well-designed hamburger menu, visible breadcrumbs, and an accessible search field. Mobile navigation should allow reaching any page in no more than 3 taps.
Mobile and AI visibility
The connection between mobile and AI visibility is indirect but significant. LLMs that use RAG systems (Perplexity, Google AI Overview) rely on the Google index — which is mobile-first. If your content is degraded on mobile (hidden text, missing schema markup, degraded performance), it is indexed in its degraded version, which reduces its probability of being selected as an AI source.
In addition, an increasing proportion of LLM queries is made from mobile devices. Perplexity, ChatGPT, and Gemini all have mobile apps with hundreds of millions of users. LLMs that provide sources need to ensure those sources are accessible on mobile — a site that is inaccessible on mobile is a poor recommendation.
As Marie Haynes, an SEO consultant based in Ottawa (with major European clients) notes: "Mobile-first is no longer a device question, it is a question of the quality of indexed content. If your mobile version is inferior to your desktop version, it is your inferior version that Google and AI see. Full stop."
Complete mobile optimisation checklist
Performance (8 points)
- Mobile LCP below 2.5 seconds
- Mobile INP below 200ms
- Mobile CLS below 0.1
- Mobile TTFB below 800ms
- Images optimised for mobile (srcset, WebP format)
- Non-blocking JavaScript (defer, async)
- Critical CSS inline, non-critical CSS deferred
- Service worker for caching (PWA)
Content and structure (7 points)
- Same content on mobile and desktop (no hidden text)
- Same schema markup on mobile and desktop
- Same internal linking on mobile and desktop
- Same meta tags on mobile and desktop
- Same images and alt texts on mobile and desktop
- Viewport configured correctly
- No content wider than the screen (horizontal scroll)
UX and accessibility (6 points)
- Tap targets of at least 48x48px
- Minimum font size of 16px
- Sufficient spacing between clickable elements
- No intrusive interstitials
- Navigation accessible within 3 taps maximum
- Forms adapted for mobile (field types, autocomplete)
For a complete analysis of your site, see our technical SEO audit guide which includes a dedicated mobile-first section, and our article on site architecture optimised for SEO and AI.
FAQ
Responsive, adaptive or separate mobile site: which to choose in 2026?
Responsive design is Google's official recommendation and the standard in 2026. Separate mobile sites (m.example.com) are discouraged as they create duplicate content and maintenance issues. Adaptive design (serving different HTML depending on the device) is acceptable but more complex to maintain. Responsive with a single URL per page is the simplest and most effective solution.
Is content in mobile accordions indexed by Google?
Yes, Google has confirmed that it indexes content in accordions, tabs, and collapsible sections on mobile. However, some studies (including one by Sistrix in 2024) suggest that directly visible content carries slightly more weight in rankings. The recommendation: use accordions if the UX justifies it, but do not hide your most important content.
Does Google penalise sites that are not mobile-friendly?
There is no "penalty" as such, but the impact is equivalent. Google indexes only the mobile version. If your site is not mobile-friendly, Google indexes a degraded version of your content. In addition, poor user experience increases the bounce rate, which negatively impacts your ranking signals.
How do I test whether my site is mobile-friendly?
Google retired the Mobile-Friendly Test tool in 2023. Use PageSpeed Insights (which tests the mobile version), Google Search Console (Experience > Core Web Vitals report filtered by mobile), and Chrome DevTools (device toggle mode). Also test on real devices — emulators do not reproduce all real-world conditions (network, memory, CPU).
Do PWAs (Progressive Web Apps) have an SEO advantage?
Not directly, but the features associated with PWAs (service worker for caching, instant loading, offline functionality) significantly improve Core Web Vitals and user experience. The advantage is not the "PWA" label but the performance it implies. Google does not give a specific SEO bonus to PWAs.
Is AMP still relevant in 2026?
AMP lost its relevance since Google removed the AMP requirement for the Top Stories carousel (2021) and the AMP badge from search results (2024). In 2026, AMP offers no SEO advantage over a well-optimised site. Most publishers who used AMP have migrated to standard well-performing web pages. Focus your efforts on Core Web Vitals rather than AMP.
Is your site truly mobile-first?
Our experts audit your mobile experience and identify priority optimisations for your SEO and AI visibility.
Audit my mobile site
