Mobile Usability Report Changes: What Search Console Dropped

I still get asked, periodically, “where did the mobile usability report in Search Console go?” It’s a fair question — the report quietly disappeared, and unlike most Search Console changes, Google didn’t replace it with something that does the same job. It’s been almost three years, which is long enough that the gap it left is worth actually explaining rather than assuming everyone already adjusted.

What Got Dropped and When

Google first signaled the change in an April 24, 2023 Search Central blog post titled “The role of page experience in creating helpful content.” The actual removal landed later that year: Google confirmed on December 4, 2023 that, effective December 1, 2023, it had officially retired the Mobile Usability report, the Mobile-Friendly Test tool, the Mobile-Friendly Test API, and the broader Page Experience report from Search Console.

Why Google Said It Did This

The Mobile Usability report and the standalone Mobile-Friendly Test tool both dated back to 2016 — roughly the mobile-first indexing era’s opening years. Google’s stated reasoning, in its own words, was that “many other robust resources for evaluating mobile usability have emerged, including Lighthouse from Chrome,” and that maintaining a dedicated legacy tool for a narrower slice of that work no longer made sense nearly a decade later. Google was careful to frame this as a tooling decision, not a signal that mobile usability stopped mattering — mobile-first indexing means Google crawls and indexes the mobile version of a page as the default baseline for virtually every site at this point, so mobile experience is arguably more embedded in ranking than ever. What went away was the dedicated report surfacing it.

What You Lost, Specifically

The old Mobile Usability report flagged specific, per-URL errors that nothing in current Search Console replicates directly:

• Text too small to read on a mobile screen without zooming.
• Clickable elements — buttons and links — placed too close together for a touch target.
• Content wider than the screen, forcing horizontal scrolling.
• Viewport not set, or set incorrectly, for mobile rendering.

None of those specific error categories are surfaced anywhere in current Search Console at the URL level. That’s the actual gap, and it’s easy to miss because Search Console doesn’t show you an absence — it just doesn’t show you anything about it at all.

What to Use Instead

• PageSpeed Insights, which runs a Lighthouse mobile audit and flags some overlapping issues — tap target sizing and viewport configuration among them — bundled in with performance metrics rather than as a dedicated usability report.
• Chrome DevTools’ device emulation mode for manual, page-by-page mobile review, which is slower but catches things automated tools miss.
• The Core Web Vitals report still in Search Console, which remains available but measures loading, interactivity, and visual stability — performance, not layout usability in the old report’s sense.
• Manual responsive QA as part of any template or theme change, since nothing currently flags these issues proactively at scale the way the old report did across an entire site.

Google didn’t decide mobile usability stopped mattering — it decided that flagging it one narrow error category at a time, through a tool built for 2016’s mobile web, wasn’t worth maintaining. The gap that left is real: nothing in Search Console today will tell you, page by page, that your tap targets are too close together the way that old report did.

Don’t read a clean Search Console dashboard as confirmation your site is fine on mobile — it means Google stopped telling you either way. The burden shifted to manual checks and general-purpose tools like Lighthouse, which cover adjacent ground but were never built to replace the specific report that disappeared.