Meta Viewport Test
The Viewport Meta Tag Checker reads the <meta name="viewport"> declaration on any URL and validates that it correctly sets width=device-width and initial-scale=1 — the configuration mobile browsers need to render the pa…
- Results in seconds
- Pass / fail + fix guidance
- No account required
The Viewport Meta Tag Checker reads the <meta name="viewport"> declaration on any URL and validates that it correctly sets width=device-width and initial-scale=1 — the configuration mobile browsers need to render the page at the correct width and scale. A missing or misconfigured viewport tag forces mobile browsers to render the page at desktop width and zoom out, producing tiny illegible text and a broken mobile experience that Google flags as a usability issue.
What This Tool Checks
- Presence of <meta name="viewport"> in <head>
- width=device-width attribute
- initial-scale=1.0 attribute
- user-scalable setting (accessibility implication)
- maximum-scale and minimum-scale (avoid restricting zoom)
- Conflict with viewport-fit=cover or other modern values
Why It Matters for SEO
Without a viewport tag mobile browsers render the page at 980px width and scale down — text becomes unreadable, layouts overflow, and Google's mobile-friendly test fails. The fix is one line of HTML. Restricting user zoom (user-scalable=no) breaks accessibility for visually impaired users and triggers WCAG audit failures. Modern best practice is width=device-width, initial-scale=1, and never disable zoom.
How to Fix It
Add <meta name="viewport" content="width=device-width, initial-scale=1"> inside <head> on every page. Do not set user-scalable=no or maximum-scale=1 — they break accessibility. For sites that use the iPhone notch area, add viewport-fit=cover to extend the layout edge-to-edge.
How It Works
We fetch the page, parse the <head> for any <meta name="viewport"> tag, decode each property of its content attribute, and report whether the configuration matches Google's mobile-friendly recommendation. Restrictive zoom settings that hurt accessibility are flagged separately.
Common Mistakes to Avoid
- No viewport meta tag at all (legacy or copy-paste templates)
- Setting user-scalable=no (breaks accessibility)
- maximum-scale=1 (also restricts zoom unnecessarily)
- width=1024 hard-coded (force-renders at desktop width)
- Multiple competing viewport tags (only the first is used)
Quick Checklist
- Viewport tag present in every page <head>
- width=device-width set
- initial-scale=1 set
- user-scalable not disabled
- No maximum-scale less than 5
Put your whole site on autopilot — SEO and AI search
PositionMySite monitors every signal on this page across your entire website 24/7 — plus keyword rankings, competitor moves and AI-search readiness (llms.txt, schema, ChatGPT & Gemini visibility). When something breaks, you know before Google does.
Every feature unlocked · No commitment · Cancel anytimeFrequently Asked Questions
The viewport tag tells mobile browsers how to size and scale the page. The standard value (width=device-width, initial-scale=1) renders the page at the device's natural width with no zoom.
Indirectly but significantly. Google's mobile-friendly test fails without a correct viewport tag, which feeds the page-experience ranking signal. Mobile usability errors also appear in Search Console.
No. user-scalable=no and maximum-scale=1 break accessibility for visually impaired users and may trigger WCAG audit failures. Modern best practice is to allow zoom.
A modern viewport value that lets the page extend into the iPhone notch / safe-area. Combined with env(safe-area-inset-*) CSS, it produces edge-to-edge layouts on devices with display cutouts.
Yes. Every HTML document — SPA, MPA, static page — needs a viewport tag in the initial <head>. The framework cannot inject it after first paint without breaking the initial mobile render.