maximum-scale=1 or user-scalable=no to your viewport meta tag blocks pinch to zoom. It hurts real users who need to enlarge text, it fails accessibility audits, and modern browsers often ignore it anyway. Delete those two directives and let people zoom.What this check flags
Every responsive page carries a viewport meta tag in the <head>. It tells the browser how to fit the page onto a phone screen. A clean one looks like this:
<meta name="viewport" content="width=device-width, initial-scale=1">
This check fires when that tag also contains maximum-scale set to a low value (usually 1 or 1.0) or the directive user-scalable=no. Both do the same thing from the user's side: they stop pinch to zoom. Someone who wants to enlarge a small photo, a tiny caption, or a cramped form label finds the gesture dead. The page will not grow.
Designers add these directives for a specific reason. They built a layout that looks pixel-perfect at one zoom level and they do not want users breaking it. That instinct is understandable and, on a public web page, it is the wrong call.
Why blocking zoom is a problem
Zoom is not a nice-to-have. For a large slice of the population it is the difference between reading your page and bouncing off it. People with low vision, older users, anyone reading on a bright sidewalk, someone squinting at 6pt legal text: they all pinch to zoom dozens of times a day without thinking about it. When you disable it, you are telling those people their needs do not matter on your site.
There is a formal side too. The Web Content Accessibility Guidelines, success criterion 1.4.4 (Resize Text), require that text can scale up to 200 percent without loss of content or function. Locking zoom is a direct violation. If your organization has any legal exposure around accessibility, and most consumer-facing businesses now do, this one line of markup is low-hanging liability.
Google Lighthouse and the accessibility audits baked into Chrome DevTools both flag user-scalable=no and a maximum-scale under 5 as failures. That failure drags down your Lighthouse accessibility score, which is one of the signals product and marketing teams watch. Search rankings are not directly penalized for this today, but Google has been vocal for years that page experience and accessibility feed the broader quality picture, and a broken zoom experience is exactly the kind of friction that pushes mobile users away.
How to detect it
You do not need anything exotic. Pick whichever of these fits your workflow.
| Tool | How to check | Scope |
|---|---|---|
| Lighthouse / DevTools | Run the Accessibility audit, look for "[user-scalable=no] is used" | Single page |
| Screaming Frog | Custom Search or extraction for maximum-scale in the viewport tag | Whole site |
| Sitebulb | Mobile Friendly hints surface locked zoom automatically | Whole site |
| View source | Search the raw HTML for user-scalable | Spot check |
For a site-wide sweep I lean on Screaming Frog. Set up a custom extraction that grabs the full content attribute of the viewport meta, then sort the export and every offending template shows up in one column. Because this almost always comes from a shared header or theme file, you usually find it on every page at once, which is good news: one fix clears the whole site.
How to fix it
The fix is deletion, not replacement. Find your viewport meta tag in the site header, theme template, or layout component, and strip out the two bad directives.
Change this:
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
To this:
<meta name="viewport" content="width=device-width, initial-scale=1">
That is the whole job. You do not need maximum-scale, you do not need minimum-scale, and you almost never need user-scalable. Leave width=device-width and initial-scale=1 and stop there.
Two caveats worth knowing. First, iOS Safari has ignored user-scalable=no since iOS 10, so on iPhones your restriction was probably never working anyway, which makes keeping it pure downside. Second, if a developer added the restriction to stop the page zooming when a user taps a form field, the correct fix is to set the input font size to at least 16px in CSS. That stops the auto-zoom without ever touching the viewport tag.
- Ship
width=device-width, initial-scale=1and nothing more - Set form inputs to 16px or larger to kill tap-zoom
- Test the fix by actually pinching on a real phone
- Fix it in the shared template so every page inherits the change
- Re-run Lighthouse to confirm the accessibility flag clears
- Add
user-scalable=noto protect a fragile layout - Cap
maximum-scaleat 1 to force a fixed look - Assume iOS respects the restriction (it does not)
- Disable zoom to hide a layout that breaks when enlarged
- Treat this as cosmetic when it is an accessibility failure
What good looks like
A healthy page lets a user pinch a caption up to 200 percent and beyond, the text reflows or grows cleanly, and no content gets clipped or lost. Your Lighthouse accessibility audit shows zero viewport warnings. Form fields do not trigger a jarring auto-zoom because their font size already clears the 16px threshold. Nobody on your team is quietly relying on locked zoom to paper over a layout that cannot survive being enlarged.
FAQ
Does disabling zoom hurt my Google rankings?
Is it ever acceptable to disable zoom?
My inputs zoom when tapped. How do I stop that without locking the viewport?
font-size:16px (or larger) on your inputs, selects, and textareas in CSS. The auto-zoom stops and users keep full manual zoom control.If iOS ignores user-scalable=no, why bother removing it?
A locked viewport is usually a symptom of a wider set of small technical misses. Our advanced SEO audit reviews your accessibility, mobile usability, and crawl health line by line and hands you a prioritized fix list.
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!
