Free Mobile-Friendly Test: 4 Responsive Signals per URL

If you followed a guide here looking for Google's Mobile-Friendly Test, it no longer exists. Google announced the shutdown in April 2023 and executed it on 1 December 2023: "Also starting December 1, 2023, we'll be retiring Search Console's 'Mobile Usability' report, the Mobile-Friendly Test tool and Mobile-Friendly Test API" (Google Search Central). The old search.google.com/test/mobile-friendly address returns nothing.

Google's reasoning was that the mobile web had matured and that plenty of third-party tools cover the same ground. What it did not say is that mobile usability stopped mattering — the same post is explicit that it "remains critical for success with Google Search". The signal moved out of Search Console; the requirement did not move at all.

This is why so many mobile-friendliness articles now contain a dead link. The advice was written against a tool that Google removed, and nobody went back.

The test at the top of this page fetches your URL twice — once with a desktop user-agent, once with a phone's — and returns four things rather than a verdict.

Redirect. If the mobile request finishes on a different URL than the desktop one, you are serving a separate mobile site and we show you the destination.

Viewport. We read meta[name="viewport"] and print its content value verbatim. A tag that exists but sets a fixed width, or blocks zooming, looks identical to a good one in a pass/fail tool.

Media query. Whether @media rules appear inline in the HTML itself, which is how most themes and page builders ship responsive layout.

Stylesheet. Up to three linked stylesheets are downloaded and each is checked for media queries, then reported on its own row. This is the row that usually does the work: a page can pass overall and still name the one sheet with no responsive rules in it.

This check reads HTML and CSS. It never executes JavaScript and never paints the page, and that boundary is worth stating plainly rather than hiding.

It cannot see tap targets sitting too close together, body text below a readable size, or a layout that overflows horizontally at 360px — all of which need a rendered page. It stops at three stylesheets, so a responsive rule living in a fourth is invisible to it. And because it matches any @media rule, a stylesheet whose only media query is a print block will pass.

The practical consequence: treat a pass as "the responsive plumbing is present", not as "this page is good on a phone". For the rendering half, open your browser's device emulation — Ctrl/Cmd + Shift + M in Chrome and Firefox — and set the width to around 360px.

Across the 100K+ websites we audited between January and July 2026, only 11.8% carried a critical failure in the Mobile category, while 58.4% failed Largest Contentful Paint above 2.5 seconds on mobile — the single most-failed rule in our entire 251-rule set. A further 29.6% failed Interaction to Next Paint above 200ms.

Read those two numbers together and the state of the mobile web comes into focus. Responsive layout is close to solved: themes ship it, frameworks assume it, and a site built any time in the last decade almost certainly has a viewport tag and media queries. Speed is not solved at all.

That is the honest limit of every mobile-friendly test, ours included. Passing means your page fits the screen. It says nothing about whether the visitor is still there when it finishes loading.

Source: SEOmator crawling and analytics data, January–July 2026 (100K+ websites audited, 50M+ pages crawled).

A missing or fixed-width viewport tag. Without it, mobile browsers assume a canvas around 980px wide and shrink the page to fit, which is what produces the zoomed-out look. The conventional value is width=device-width, initial-scale=1. A tag that pins a fixed pixel width, or sets user-scalable=no, is worse than a missing one because it looks present in most tooling.

One stylesheet with no media queries. Almost always a legacy or vendor file that survived a redesign. It rarely breaks the whole layout; it breaks one component, usually a table, a pricing block or a footer.

An m-dot redirect nobody remembers setting up. If a phone user-agent lands somewhere else, you are maintaining two sites and Google is indexing the mobile one.

Templates, not the homepage. Homepages get design attention. Run one URL per template — a product page, an article, a form — because that is where an unresponsive stylesheet survives for years.

Google finished the migration in 2024: "the small set of sites we've still been crawling with desktop Googlebot will be crawled with mobile Googlebot after July 5, 2024" (Google Search Central). Every site is now crawled and indexed from its mobile rendering.

The most common misreading of this is that it only affects mobile rankings. It does not. Google does not maintain a separate desktop index — it indexes the mobile version and serves that index to every device. Content, internal links or structured data that exist only on desktop are not "desktop-only"; they are absent, including from desktop results.

The rule that follows is parity. The mobile version should carry the same content, the same internal links and the same structured data as the desktop one. Collapsed accordions and tabs are fine — Google renders and indexes content hidden behind them — but content genuinely removed from the mobile HTML is content you have deleted.

Once the layout passes, the next question is cost: run the free website speed test for what a phone connection actually experiences, or the full SEO audit for all 20 categories at once.