Page Is Not Mobile Friendly: What It Means Now and How to Fix It
- December 4, 2022
- Organic and Analytics, Mobile
What this check flags
This check fires when a page fails the basic bar for usability on a phone: text you can't read without pinch-zooming, content wider than the screen forcing horizontal scroll, a missing or broken viewport tag, or controls too cramped to use with a thumb. It matters because Google indexes and ranks the mobile version of your site first — if the mobile experience is broken, that's the version competing in search, and real phone users bounce from it before they read a word.
A real example, and the fix
A publisher migrated to a new theme and, on mobile, every article rendered at desktop width with a tiny, zoomed-out layout you had to pan around to read. The cause was one missing line in the <head>:
<!-- what was there: nothing -->
<!-- the browser fell back to a 980px desktop viewport -->Without a viewport declaration, mobile browsers assume a ~980px-wide desktop canvas and shrink it to fit, which is why everything looked microscopic. The fix was a single tag:
<meta name="viewport" content="width=device-width, initial-scale=1">That one line told the browser to render at the device's real width. Text became legible, the horizontal scrollbar vanished, and the mobile-friendly failure cleared on the next test. Not every fix is this clean — but a missing viewport tag is the most common single cause I see, and it's a one-liner.
What "mobile friendly" actually requires
Google retired the standalone Mobile-Friendly Test tool, but the criteria didn't disappear — they moved into Lighthouse and page-experience signals. Here's what still gets checked.
| Requirement | Fails when | How to check |
|---|---|---|
| Viewport configured | No <meta name="viewport">, or a fixed width | View source; Lighthouse "Has a viewport meta tag" |
| Legible font size | Body text renders below ~12px on mobile | Lighthouse "Document uses legible font sizes" |
| Content fits viewport | Elements force horizontal scroll | Lighthouse "Content is sized correctly for the viewport" |
| Tap targets sized | Controls under 48px or too close together | See Tap Targets Too Small |
| No incompatible plugins | Flash or other non-mobile tech present | Rare now, still audited |
Fail any one of these and the page reads as not mobile friendly, even if the other four pass.
How to detect it on your own site
- Run PageSpeed Insights on mobile. Test the URL in PageSpeed Insights and read the mobile tab. The viewport, legible-fonts, and content-sizing audits map directly to the requirements above.
- Check GSC's page experience signals. The old Mobile Usability report is gone, but Search Console still surfaces mobile problems through indexing and Core Web Vitals reporting. Cross-reference flagged URLs.
- Use Chrome DevTools device mode. Toggle the device toolbar, load the page at a phone width, and look for horizontal scroll, tiny text, or content clipped off-screen.
- Load it on a real phone. The fastest test there is: open the URL on an actual mid-range Android and try to read and navigate it. If you're pinch-zooming or scrolling sideways, it fails.
How to fix it
- Add the viewport meta tag.
<meta name="viewport" content="width=device-width, initial-scale=1">in the<head>. This is the fix for the majority of "not mobile friendly" failures. - Set readable base font size. Body copy at 16px is the safe default; never let mobile text drop under 12px. See Mobile Text Too Small.
- Kill horizontal overflow. Find the element wider than the screen — usually a fixed-width image, table, or an absolute-positioned block — and give it
max-width: 100%. Wrap wide tables in anoverflow-x: autocontainer. - Use responsive layout. Fluid widths, flexbox or grid, and media queries so the layout reflows instead of shrinking. Don't hard-code pixel widths on containers.
- Fix tap targets. Give links and buttons at least a 48px hit area with spacing between them.
- Re-test on mobile. Reload PageSpeed after each change and confirm the audits pass before moving on.
Common mistakes
- Setting the viewport but locking it with
maximum-scale=1oruser-scalable=no, which blocks zoom and hurts accessibility. - Fixing font size in the desktop CSS but not inside the mobile media query.
- Chasing a Core Web Vitals score while ignoring that the page doesn't even fit the screen — mobile-friendliness comes first.
- Assuming a responsive theme guarantees it; one over-wide embedded table or image can still trigger the failure.
FAQ
Isn't the Mobile-Friendly Test gone?
The dedicated tool and GSC's Mobile Usability report were retired, but the criteria live on in Lighthouse and PageSpeed Insights. "Mobile friendly" is still a real, testable bar — you just check it in a different place now.
Does mobile-friendliness affect rankings?
Yes, indirectly and directly. Google uses mobile-first indexing, so the mobile version is what gets ranked, and page experience is a factor. A page that fails on phones is fighting search with its worst foot forward.
What's the most common single cause?
A missing or misconfigured viewport meta tag. It's responsible for the classic "everything is tiny and zoomed out" symptom, and it's a one-line fix.
My theme is responsive — why did this still flag?
Responsive themes handle the layout, but embedded content you added — a fixed-width table, a large image, a third-party widget — can overflow the viewport and trip the check on its own.
How does this relate to tap targets and text size?
They're components of the same overall verdict. A page can pass the viewport and font checks and still fail mobile-friendliness because its tap targets are too small. Fix all the sub-checks, not just the loudest one.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
