Skip to content
atlookup

Mobile Viewport Not Set

Without <meta name="viewport">, mobile browsers render the page at desktop width and zoom out — making the page unreadable on phones.

warning Impact: high WCAG 1.4.10 (Level AA) VIEWPORT_MISSING 2 min read Updated

Why it matters

Without <meta name="viewport">, mobile browsers render the page at desktop width and zoom out — making the page unreadable on phones. Google's Mobile-Friendly Test will fail.

Schedule a fix in your next sprint. Warnings won't block your site but they consistently leave performance on the table. Estimated SEO impact: high — direct effect on rankings or impressions.

How to fix

  • Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • Place it in <head> before any CSS
  • Do not set maximum-scale=1 (breaks accessibility zoom)

Common causes

If the rule is firing across many pages, the root cause is almost always one of these:

  • Mixed-content sub-resources from before HTTPS migration that escaped the rewrite.
  • CDN or upstream proxy strips a security header that was set at the origin.
  • Legacy redirects send HTTPS traffic through HTTP first.
  • Test/staging hostnames leak into production HTML via hard-coded URLs.

Anti-patterns to avoid

Even with the best intentions, these "fixes" make the issue worse — recognise them so you don't ship them:

  • Mixed HTTP/HTTPS resources after migration.
  • Self-signed or expired certificates on production.
  • Long-lived secrets in client-rendered HTML or JS bundles.

Example

Here's a typical instance — the problematic line is highlighted in red:

example.html HTML 
<head>
  <title>Page</title>
  <!-- no viewport -->
</head>

And the fix — the corrected line, highlighted in green:

example.html HTML · fixed 
<head>
  <title>Page</title>
  <meta name="viewport" content="width=device-width, initial-scale=1">
</head>

How atlookup detects this

Our crawler renders each page with a real headless browser, then inspects HTTPS state, response headers, mixed content, and certificate validity. Pages where the rule fires for mobile viewport not set are flagged on the report.

If you'd like to see this rule fire on your own site, run a free 60-second audit — every page is reported with the exact lines that triggered it.

Tools to verify the fix

Once you've applied the fix, double-check with these external validators:

Frequently asked questions

Why does Mobile Viewport Not Set matter for SEO?

Without <meta name="viewport">, mobile browsers render the page at desktop width and zoom out — making the page unreadable on phones. Google's Mobile-Friendly Test will fail.

How do I fix mobile viewport not set?

Add <meta name="viewport" content="width=device-width, initial-scale=1"> Place it in <head> before any CSS Do not set maximum-scale=1 (breaks accessibility zoom)

Is this a critical SEO issue?

Schedule a fix in your next sprint. Warnings won't block your site but they consistently leave performance on the table. Estimated SEO impact: high — direct effect on rankings or impressions.

How does atlookup detect mobile viewport not set?

Our crawler renders each page with a real headless browser, then inspects HTTPS state, response headers, mixed content, and certificate validity. Pages where the rule fires for mobile viewport not set are flagged on the report.

Does this affect accessibility?

Yes. This issue maps to WCAG 1.4.10 (Level AA). Fixing it improves both SEO ranking signals and the experience for users on assistive technology.

FRAME_TAG_PRESENT

Deprecated frame/frameset Tag Present

<frame> and <frameset> are removed from HTML5 — not supported in modern browsers, bad for SEO, and catastrophic for accessibility.

FLASH_OBJECT_PRESENT

Flash Object on Page

Adobe Flash has been end-of-life since December 2020 — no browser runs it.

FORM_INSECURE_ACTION

Form Action Uses HTTP on HTTPS Page

A form that POSTs to an HTTP endpoint on an HTTPS page sends user data in the clear — a serious security and privacy failure.

MIXED_CONTENT_IFRAME

Mixed Content: HTTP iframe on HTTPS Page

HTTP iframes on HTTPS pages are blocked by modern browsers entirely — the embedded content simply does not render, breaking the user experience.