Mobile-Friendly Test: 6-Point Check Google (Still) Uses in 2026
A mobile-friendly test is a technical evaluation that checks whether a webpage displays and functions correctly on a smartphone or tablet screen, measured against six core criteria: a valid viewport configuration, readable font size, adequately spaced tap targets, no horizontal scrolling, no unplayable plugin content, and no intrusive interstitials blocking the page. These six criteria originated from Google's own testing standards and remain the working definition of "mobile-friendly" across the web today, even though Google's standalone testing tool no longer exists.
The main benefit of running a mobile-friendly test is confirmation; it tells you, in seconds, whether a visitor on a phone can actually read your content and tap your buttons without pinching, zooming, or missing a link entirely. On the technical side, a page that loads its layout correctly across screen widths from roughly 320px up to tablet size, without elements overlapping or spilling off-screen.
This guide walks through each of the six criteria Google's testing standard is built on, explains why the standalone Google tool disappeared and what replaced the checking process, and shows you where to run a free test right now.
1. Valid Viewport Configuration
A viewport configuration tells the browser how to scale and size a page on a mobile screen, and it is the single most foundational criterion in a mobile-friendly test. Without it, a phone browser renders the page at a fixed desktop width, typically 980px, and then shrinks the entire layout down to fit the screen, leaving text microscopic and unreadable until a visitor manually zooms in.
The fix is a single line of code in the page's HTML head: <meta name="viewport" content="width=device-width, initial-scale=1">. This tells the browser to match the page's width to the device's actual screen width and start at a 1:1 zoom level. Three of the most common viewport failures are: a missing viewport tag entirely, a viewport tag with a fixed pixel width instead of device-width, and a viewport tag that disables user zooming (user-scalable=no), which creates accessibility problems even when the layout itself looks correct.
2. Readable Font Size Without Zooming
Readable font size means body text renders large enough that a visitor can read it at a normal viewing distance without pinching to zoom in. A mobile-friendly test flags any font smaller than 12px as a likely failure, and Google's own guidance recommends a 16px base size as the safer standard for body copy.
Font size failures usually trace back to one of three sources: a desktop-first stylesheet that never defines a separate mobile font scale, inherited styles from a theme or template that weren't checked on a real device, or text nested inside a fixed-width container that forces the browser to shrink everything proportionally to fit. Because font size is a CSS-level setting, it should scale relative to the viewport rather than sitting at a single fixed pixel value across every screen size.
3. Adequately Spaced Tap Targets
A tap target is any clickable element, a button, a link, a form field, and its spacing determines whether a visitor can accurately tap it with a finger instead of a mouse pointer. Google's mobile usability standard sets the minimum comfortable tap target at 48x48 pixels, with at least 8px of space between adjacent targets, based on the average size of a human fingertip.
Small or crowded tap targets create a specific, measurable problem: a visitor intending to tap one link instead taps its neighbor, lands on the wrong page, and frequently abandons the site rather than navigating back. This failure shows up most often in navigation menus condensed for mobile, inline text links placed too close together in a paragraph, and footer link lists that were never restyled for a narrower screen.
4. No Horizontal Scrolling
No horizontal scrolling means every element on the page fits within the width of the device screen, so a visitor never has to swipe sideways to see content that runs off the edge. This is one of the fastest signals a mobile-friendly test checks, because it can be detected simply by comparing a page's total rendered width against its viewport width.
Horizontal scroll issues almost always originate from one of three causes: an image or embedded video set to a fixed pixel width wider than the screen, a table that wasn't given a responsive wrapper, or a container element with padding or margin values that push its total width past 100% of the viewport. Because this criterion is purely layout-based, it's typically the fastest of the six to diagnose and fix.
5. No Unplayable or Incompatible Content
Unplayable content refers to any embedded element a mobile browser cannot render, most commonly Adobe Flash, which was retired across every major browser by the end of 2020 and is treated as an automatic mobile-friendly failure wherever it still appears. A visitor on a phone sees a blank space or a broken plugin icon in place of the intended video or animation.
The fix here is a full replacement rather than a patch: Flash-based video and animation should be re-exported as an HTML5 video file or an animated format such as GIF, WebP, or a CSS/JavaScript animation. Sites migrated from an older content management system are the most common source of this failure, since Flash embeds were common in page builders from the early 2010s and often survive silently in older blog posts or landing pages.
6. No Intrusive Interstitials
An intrusive interstitial is a pop-up, overlay, or banner that covers the main content immediately after a page loads on mobile, and Google has treated intrusive interstitials as a Mobile Usability Penalty Since January 2017. A cookie notice, an age gate, or a legally required disclosure banner is not penalized the same way, provided it uses a reasonable amount of screen space and doesn't block the content a visitor came to see.
The distinguishing factor is size and timing: a small banner confined to the top or bottom of the screen passes, while a full-screen pop-up requiring a tap to dismiss before any content is visible fails. Email capture pop-ups and app-download prompts are the two most common intrusive interstitials still found on mobile pages today.
Quick Reference: All 6 Criteria at a Glance
The table below summarizes the pass condition and the most common failure cause for each of the six criteria, so you can scan it before or after running a test.
How Do You Test if Your Site Meets These Criteria?
Snapzain's Free Mobile-Friendly Test Tool checks all six criteria above in under ten seconds, enter a URL, and it returns a clear pass or fail result for viewport configuration, font size, tap target spacing, horizontal scroll, plugin compatibility, and interstitial behavior. No account, install, or technical setup is required to run it.
This kind of instant, criteria-by-criteria check has become the standard replacement for manual testing, because until late 2023 this was Google's own job to do.
How to Read Your Mobile-Friendly Test Results
A test result should be read one criterion at a time rather than as a single overall score, because a page can pass five of the six checks and still lose mobile visitors over the one it fails. Start with viewport configuration first, since a missing or incorrect viewport tag tends to cause secondary failures elsewhere, a page rendered at the wrong scale will often also misreport font size and tap target spacing until the viewport itself is corrected.
Three practical steps make the results actionable rather than just informational. First, note which specific criterion failed rather than treating "mobile-friendly: no" as one problem, the fix for a font size failure is unrelated to the fix for an interstitial failure. Second, check the result on your two or three highest-traffic pages individually, since a template issue on a product page won't necessarily show up when testing the homepage. Third, re-test after each fix rather than batching several changes together, so a persistent failure doesn't get masked by a change that only fixes a different criterion.
Why the Definition Changed: Google Retired Its Own Tool
Google retired its Mobile-Friendly Test tool, along with the related Mobile Usability report in Search Console, on December 1, 2023, after roughly a decade of operation. Google's stated reasoning was that mobile usability had become a standard, expected part of web design rather than a separate concern needing its own dedicated report, and it pointed site owners toward Lighthouse and PageSpeed Insights for future testing instead.
The retirement didn't change what "mobile-friendly" means, the six criteria above are unchanged and still form the technical basis for how Lighthouse and other tools evaluate a page today. What changed is where a site owner goes to check them, and that gap is exactly what drives so many people to still search for a mobile-friendly test today, only to land on a dead Google URL. A closer look at what happened to Google's tool and what to use instead covers the full timeline if you want the details.
Mobile-First Indexing: Why This Still Affects Rankings
Mobile-first indexing means Google uses the mobile version of a page, not the desktop version, as the primary basis for indexing and ranking that page in search results. Google completed the transition to mobile-first indexing for effectively the entire web by July 2024, which means the six criteria covered in this guide are no longer a secondary consideration; they describe the exact version of a page Google evaluates first.
A page that fails several of these criteria on mobile can rank lower even if its desktop version looks flawless, because the desktop version is no longer what search engines are primarily indexing. If a test already flagged specific failures on your site, this guide to fixing common mobile-friendly test issues walks through each fix in order of how often it appears.
Mobile-Friendly vs. Responsive vs. Adaptive Design
Mobile-friendly is an outcome, a page either meets the six usability criteria on a mobile screen or it doesn't, while responsive and adaptive are two different technical approaches used to achieve that outcome. A responsive design uses a single flexible layout that reflows automatically to fit any screen width using CSS, while an adaptive design serves a small number of fixed layouts chosen based on detected device type.
Both approaches can pass a mobile-friendly test if implemented correctly, and both can fail it if implemented poorly. Responsive design has become the more common approach industry-wide because it requires maintaining one layout instead of several, but the mobile-friendly test itself doesn't check which method was used, only whether the six usability criteria are met on the rendered result. A full comparison of a mobile-friendly test against PageSpeed Insights breaks down how these different tools each fit into a complete mobile audit.
How Often Should You Re-Test Your Site?
A website should be re-tested for mobile-friendliness after any theme change, template update, or new page template goes live, and as a baseline check at least once per quarter even without a known change. Sites that publish frequently, such as blogs or e-commerce catalogs adding new product templates, benefit from testing any new page type before it goes live rather than after an issue has already affected rankings.
A single passing result is not permanent. A plugin update, a new embedded widget, or a redesigned navigation menu can silently reintroduce a failure, most commonly a tap target spacing issue or a new pop-up, without any other part of the site changing.
What Happens If Your Site Fails a Mobile-Friendly Test?
A site that fails a mobile-friendly test doesn't get manually removed from search results, but it competes at a structural disadvantage: visitors on mobile devices,which account for the majority of global website traffic, encounter a broken or frustrating layout, leading to higher bounce rates and shorter session times, both of which are signals search engines weigh when ranking pages against competitors that pass. Over time, a site consistently failing these criteria tends to lose ranking position to comparable competitors that pass them, even without any single dramatic penalty ever being applied.
The reverse is also true: fixing even a single failing criterion, such as adding a missing viewport tag, can produce a measurable improvement in mobile usability metrics almost immediately, since it directly changes what every mobile visitor experiences on their very next visit.
Common Misconceptions About Mobile-Friendly Testing
A passing mobile-friendly test is often mistaken for a guarantee of good mobile SEO performance, but the two are related, not identical, the test measures usability criteria only, while ranking also depends on factors like page speed, content quality, and backlinks that a mobile-friendly test does not evaluate at all. A site can pass every one of the six criteria and still rank poorly for other reasons, just as a site can fail one minor criterion and still outrank competitors on the strength of its content.
A second common misconception is that a responsive theme or "mobile-ready" template guarantees a pass automatically. Templates marketed as mobile-ready commonly still fail on tap target spacing or interstitials, because those two criteria depend on how individual pages are configured; a pop-up plugin installed after the theme was set up, for example, can introduce a failure the template itself never had. Passing a mobile-friendly test is a property of the live, current page, not a permanent feature inherited from a theme purchase.
Frequently Asked Questions
What Does a Mobile-Friendly Test Actually Check?
It checks six criteria: a valid viewport meta tag, a minimum 16px font size, 48x48px tap targets with adequate spacing, no horizontal scrolling, no unplayable plugin content, and no intrusive interstitials blocking the page.
Why is Mobile-Friendliness Important for SEO?
Google has used mobile-first indexing universally since July 2024, meaning it evaluates a page's mobile version, not its desktop version, as the primary basis for ranking that page in search results.
How Do I Test if My Website is Mobile-Friendly?
Enter your URL into a free mobile-friendly test tool, such as Snapzain's, which checks all six core criteria in under ten seconds and returns a clear pass or fail result for each one.
What's the Difference Between Mobile-Friendly and Responsive Design?
Mobile-friendly is an outcome measured against six criteria, while responsive design is one technical method, a single flexible layout that reflows by screen width, used to achieve that outcome.
How Often Should I Re-Test My Site for Mobile-Friendliness?
Re-test after any theme, template, or navigation change, and at minimum once per quarter as a baseline, since a single plugin update can silently reintroduce a failure that previously passed.
What Happens if My Website Fails a Mobile-Friendly Test?
It isn't penalized directly, but it competes at a disadvantage: higher mobile bounce rates and shorter sessions are signals search engines weigh against competitors whose pages pass the same criteria.
