Mobile Viewport Checker

Check if your page has a proper viewport meta tag for mobile devices. Essential for mobile-first SEO and Google ranking.

Check Viewport Tag

Enter any URL to check its viewport meta tag configuration for mobile devices.
Quick test:

About the Mobile Viewport Checker

The viewport meta tag is important for mobile usability. Since Google uses mobile-first indexing, the mobile version of your page matters for search performance. A missing or misconfigured viewport tag can create mobile usability problems.

Viewport detection

Detects presence of viewport meta tag in your page HTML.

Property validation

Validates width, initial-scale, user-scalable, and other viewport properties.

Zoom-blocking detection

Identifies accessibility violations like user-scalable=no and maximum-scale=1.0.

The Standard Viewport Tag

<meta name="viewport" content="width=device-width, initial-scale=1">

Viewport Properties

  • width — Should always be device-width to match the screen. Never set a fixed pixel width.
  • initial-scale — Start at 1 (100% zoom). Required for proper rendering on rotation.
  • user-scalable — Should be yes or omitted. Setting to no is an accessibility violation.
  • maximum-scale — Avoid setting to 1.0 as it blocks zooming, same as user-scalable=no.
  • minimum-scale — Rarely needed. Omit unless you have a specific reason.
  • viewport-fit — iOS-only. Use cover for full-screen apps on notched devices.
  • shrink-to-fit — iOS Safari specific. Usually set to no to prevent automatic scaling.

Why This Matters for SEO

Google's mobile-first indexing means the mobile version of your page is the primary version used for ranking. A missing or broken viewport tag is one of the most common mobile usability failures detected by Google Search Console. Fixing it can directly improve your mobile rankings and user engagement metrics.

  • Mobile usability — The viewport tag is the #1 requirement for passing Google's mobile-friendly test.
  • User experience — Without it, mobile users must pinch-to-zoom, leading to higher bounce rates and lower time on page.
  • Accessibility — Blocking zoom violates WCAG guidelines and can lead to legal risk in some jurisdictions.
  • Page speed perception — A correct viewport tag ensures content renders at the right size immediately, improving perceived performance.

Google's Requirements

Google's mobile-friendly test checks for viewport configuration. The minimum requirement is width=device-width, initial-scale=1. Pages without this fail Google's test and may lose mobile rankings. Additionally, Google recommends placing the viewport tag within the first 1024 bytes of HTML so it's applied before other CSS and rendering begins.

Frequently Asked Questions

The viewport meta tag tells mobile browsers how to scale and render your page. Without it, mobile browsers render pages at a desktop width (usually 980px) and users must pinch-to-zoom to read content — a terrible mobile experience. It was introduced by Apple in 2007 for the iPhone and is now supported by all mobile browsers.
The recommended standard is: <code>&lt;meta name="viewport" content="width=device-width, initial-scale=1"&gt;</code>. This tells browsers to match the device's screen width and start at 1:1 scale. For complex layouts, you may add additional properties like <code>viewport-fit=cover</code> for iOS notch devices, but width=device-width and initial-scale=1 are the essential minimum.
Yes. Google uses mobile-first indexing, meaning it primarily uses the mobile version of your page for ranking. A missing or incorrect viewport tag can hurt your mobile usability scores and rankings. Google's Page Experience algorithm includes mobile-friendliness as a ranking factor, and the viewport tag is the foundation of mobile-friendliness.
Setting user-scalable=no or maximum-scale=1.0 prevents users from zooming, which is an accessibility violation under WCAG 2.1 Success Criterion 1.4.4 (Resize Text). Google flags this as a mobile usability error. Always allow user scaling — users with visual impairments rely on pinch-to-zoom to read content.
You should only have ONE viewport meta tag per page. If multiple tags are present, browsers use only the first one and ignore the rest. Having duplicates often means a plugin, theme, or snippet is injecting an additional tag. Check for conflicting SEO plugins or hardcoded tags in your theme header.
The <code>viewport-fit=cover</code> property is specific to iOS devices with notches (iPhone X and later). When set, the page extends into the safe area insets (the rounded corners and notch area) instead of being confined to the safe rectangle. This is essential for full-screen web apps and designs with colored headers that should extend edge-to-edge on modern iPhones.
The viewport tag and CSS media queries work together. The viewport tag sets the initial rendering viewport width (ideally device-width), and media queries then apply different CSS based on that width. Without a proper viewport tag, media queries will trigger at incorrect breakpoints because the browser thinks the viewport is 980px wide (desktop) instead of the actual device width.
<code>width=device-width</code> tells the browser to match the device's actual screen width in CSS pixels (e.g., 375px on iPhone, 414px on larger phones). A fixed value like <code>width=1024</code> forces a desktop-width viewport on mobile, causing horizontal scrolling and content zooming. Never use fixed pixel widths — always use device-width for responsive designs.
The viewport meta tag is supported on virtually all mobile browsers including Chrome for Android, Safari iOS, Samsung Internet, Firefox for Android, and Opera Mini. Desktop browsers generally ignore it since they don't have the same viewport scaling needs. It is the most universally supported mobile web standard, backed by every major browser vendor.
Reviewed Jun 2026 · Sources and limitations

Review details: 2026-06-10 · Marc LaClear · v1.0

Reference sources:

Known limits:

  • Checks are based on publicly fetchable HTML, response headers, and browser-side input. They do not use private Google Search Console, analytics, or ranking data.
  • Scores and warnings are diagnostic aids, not guarantees of ranking improvement or Google indexation.
  • Pages blocked by robots.txt, login walls, bot protection, heavy JavaScript, or network timeouts may return incomplete results.
  • Validate critical fixes with official Google tools such as Search Console, Rich Results Test, Lighthouse, and your own crawl data.

Report an issue with this tool