1001Ferramentas
📱 SEO

Viewport Meta Mobile Check

Checks whether a viewport meta snippet contains width device-width initial-scale 1 for mobile-friendly.

Checking your viewport meta before deploy

The page loads on a phone looking like a shrunken desktop, with two-millimetre type and mandatory pinch zoom. Nine times out of ten the culprit is a single line: a missing viewport meta, or one carrying a bad value inherited from an old template. It slips through code review because nobody reads the head carefully.

Paste the whole tag, not just its content value. The check runs three independent tests: it looks for the meta name viewport tag, for width equal to device-width, and for initial-scale equal to 1 or 1.0. It also warns when it finds user-scalable no. That is why the value prefilled in the field, which is only the attribute content, comes back as failing for a missing tag — paste the complete line from your head and the verdict flips to OK.

Two limits worth knowing. The match is textual and unanchored, so initial-scale=1.5 passes because the 1 matches; eyeball the value yourself. And maximum-scale=1, which together with user-scalable no stops readers from zooming, is not flagged here — avoid both. A correct viewport is the first item of mobile friendliness, not the only one: font size, tap target spacing and horizontal overflow matter too. Runs in the browser.

Frequently asked questions

Why does the prefilled value come back as failing?
Because the checker looks for the full tag, including meta name equals viewport. Paste the entire line from your head rather than just the content attribute value.
Should I set maximum-scale?
Better not. Combined with user-scalable no it blocks zooming and fails the accessibility criterion on resizing content.
Is initial-scale=1.0 accepted?
Yes, the check accepts both 1 and 1.0. Browsers treat the two forms as equivalent.

Related Tools