Is the mobile-friendly tag still a ranking factor you shouldn't overlook?

What exactly does Google mean by "minimum criteria"?

Google mentions specific criteria for triggering the mobile-friendly tag but remains vague about their exact nature. Historically, these criteria include no Flash, readable fonts without zoom, a configured viewport, and sufficiently spaced links. However, Google does not publicly provide a comprehensive checklist.

This intentional opacity is problematic: a site can appear mobile-friendly while failing certain internal Google tests. The Mobile-Friendly Test gives an indication but does not guarantee anything regarding ranking signals. The real issue here is that Google is talking about an active ranking signal, not just a cosmetic label in search results.

Does this statement renew the importance of mobile-first indexing?

Not really. Mobile-first indexing has been the norm for several years: Google crawls and indexes the mobile version of your pages first. The mobile-friendly tag is an older marker from the time when desktop indexing was still predominant.

What Google is reminding us is that this ranking signal remains active. In other words, even if your site is indexed with mobile-first, if it doesn't meet the minimum mobile compatibility criteria, it will suffer a penalty in mobile search results. This isn't new, but it is a reminder that this mechanism hasn't been disabled.

Why does Google still emphasize this point?

Because many sites still neglect the real mobile experience. They pass the Mobile-Friendly Test with ease but offer a cumbersome navigation experience: intrusive pop-ups, overwhelming interstitials, disastrous loading times, or misaligned content. Google wants to avoid confusion between "technically compatible" and "truly usable".

This statement also serves to clarify priorities: if your site doesn't meet the minimum criteria, there's no point in hoping to benefit from the mobile ranking signal. It's not a binary system of "compatible or not": there are degrees, and Google only grants boosts to sites that meet a minimum threshold they do not publicly detail. It's frustrating, but it's the reality.

• The mobile-friendly tag remains an active ranking signal, not just an informational label.
• Google sets minimum criteria to benefit from the boost but does not fully document them.
• The Mobile-Friendly Test does not guarantee your site passes the ranking threshold.
• The actual mobile user experience counts as much, if not more, than simple technical compatibility.
• Neglecting this tag can lead to penalties in mobile results, especially if your competitors are compliant.

Is this statement consistent with real-world observations?

Yes and no. On paper, Google has maintained this signal for years, and A/B testing does show a slight advantage for well-optimized mobile sites. However, the impact remains modest compared to other factors like loading speed (Core Web Vitals), content quality, or domain authority. [To be verified]: Google never quantifies the exact weight of this signal in its algorithm, and some tests show that a mediocre mobile-friendly site with solid content can outperform a technically impeccable competitor lacking in content.

Practically speaking, the mobile-friendly tag acts like a basic filter: it does not magically catapult your pages to the top position, but it can penalize them if you do not meet the minimum threshold. It is an entry ticket, not a guarantee of success. The situations where this signal becomes decisive are rare: tight competition, saturated mobile SERPs, or niches where the mobile user experience is critical.

What nuances should be added to this Google assertion?

Google speaks of "specific criteria", but provides no public evaluation grid. In practice, the Mobile-Friendly Test covers the essentials: viewport, font size, touch spacing, and absence of oversized content. However, Google also incorporates behavioral signals: mobile bounce rate, time spent, and interactions. A site that passes the test but drives users away immediately is unlikely to enjoy the boost.

Another nuance: this signal only applies to searches conducted from a mobile device. If the majority of your traffic comes from desktop (B2B, technical niches, certain professional sectors), the impact will be marginal. Conversely, for an e-commerce site or a local business, it's critical. Analyze your traffic before prioritizing this optimization.

In what cases does this rule not apply?

If your site targets desktop exclusively — which is extremely rare today — you can technically ignore this signal. But let's be honest: even B2B sites receive 20 to 40% of their traffic from mobile. The other exception concerns very specific informational queries where Google prioritizes absolute content relevance, even at the cost of mobile experience. This does happen, but it's anecdotal.

Finally, this signal can be neutralized by other negative factors: if your site is slow, filled with intrusive ads, or suffers from a massive backlink disavow, the mobile-friendly tag won't save it. Google frequently states that signals operate in combination, not isolation. A mobile-friendly site that is otherwise poor will remain poorly ranked.

What concrete steps should be taken to ensure compliance?

Run Google's Mobile-Friendly Test on your key pages. If the verdict is positive, then check in Search Console, under "Mobile Usability", to see that Google has detected no issues on your site. These two tools will give you a basic diagnosis. But don't stop there: test the actual experience on multiple devices (iOS, Android, various screen sizes).

Next, audit the Core Web Vitals on mobile: LCP, FID, CLS. Google has merged mobile-friendly evaluation with Core Web Vitals in its overall approach to user experience. A technically mobile-friendly site that is slow or visually unstable will not fully benefit from the signal. Use PageSpeed Insights in mobile mode to identify bottlenecks.

What mistakes should absolutely be avoided?

Don't rely solely on responsive design. Responsive does not mean performant: a site that adapts its layout but loads 5 MB of resources will remain unusable. Avoid full-screen non-closable interstitials, invasive pop-ups, and autoplay carousels that distort CLS. Google penalizes these practices regardless of the mobile-friendly tag, but they also harm your user perception.

Another pitfall: some sites conceal content on mobile through accordions or tabs. Google indexes this content, but if the user experience requires multiple clicks to access essential information, engagement rates will drop. A low engagement rate can nullify the advantage of the mobile-friendly tag. Make your main content immediately accessible, without excessive scrolling or mandatory interactions.

How can I verify that my site meets Google's minimum threshold?

Honestly, Google provides no precise tool for this. The Mobile-Friendly Test tells you "yes" or "no", but does not quantify quality. The "Mobile Usability" report in Search Console flags blocking errors, but not borderline optimizations. Your best approach is to compare yourself to your direct competitors in mobile SERPs. Enter your strategic queries on mobile, analyze the sites ahead of you, and evaluate their mobile experience.

If you want to go further, conduct real user tests: ask beta testers to navigate your mobile site and note their frictions. Heatmaps and session recordings (Hotjar, Clarity) often reveal issues invisible to automated tests. A technically compliant site that is frustrating for the user will never meet the "quality" threshold that Google seeks.

• Validate all your key pages with Google's Mobile-Friendly Test.
• Audit mobile usability in Search Console to detect blocking errors.
• Test mobile speed with PageSpeed Insights and optimize Core Web Vitals (LCP, FID, CLS).
• Eliminate invasive interstitials, non-closable pop-ups, and hidden content without valid reasons.
• Navigate your site with several real mobile devices to check user experience.
• Compare your mobile experience to that of your direct competitors in mobile SERPs.