Mobile Usability Report

What the Mobile Usability Report Was

The Mobile Usability report was a Google Search Console feature that scanned your indexed pages and flagged mobile problems — text too small to read, tap targets too close together, content wider than the screen. Here's the thing you need to know up front: Google retired it in December 2023. The report is gone, the Mobile-Friendly Test tool is gone, and the Mobile-Friendly Test API is gone too.

So if you went looking for it in GSC and came up empty, you're not doing anything wrong — there's nothing to find. The stakes now are knowing what replaced it, because "mobile-friendly" didn't stop mattering. Google just stopped giving you that specific dashboard, on the reasoning that the mobile web had matured enough that a standalone report wasn't earning its keep.

A real example

A client pings you in a panic: "The Mobile Usability report disappeared from Search Console — did we get penalized?" No. Google removed the report for everyone on the same date. Nothing changed about their site. The fix isn't to restore a report that no longer exists; it's to move their mobile checks to PageSpeed Insights and hands-on responsive testing, which is where mobile QA lives now.

What replaced it

Note the pattern: mobile QA didn't vanish, it got absorbed into performance and responsive tooling. The Core Web Vitals report in GSC is still very much alive and still splits desktop from mobile — that's the closest thing GSC still offers to a mobile-health dashboard.

How to check mobile-friendliness now

1. Run the URL through PageSpeed Insights and read the Mobile tab. It surfaces both lab and field data for that page.
2. Open the page in Chrome, launch DevTools (F12), and click the device-toolbar icon to emulate phones at real viewport widths. Watch for horizontal scroll, cramped tap targets, and unreadable text.
3. In the same DevTools panel, run a Lighthouse audit in mobile mode for a scriptable, repeatable check you can wire into CI.
4. In Google Search Console, open the Core Web Vitals report and read the Mobile section for real-user field data across your whole site.
5. Test on an actual device. Emulators miss real touch behavior, on-screen keyboards, and OS-level font scaling — grab a phone and use the page like a visitor would.
6. Confirm your viewport meta tag is present and correct: <meta name="viewport" content="width=device-width, initial-scale=1">. Missing or wrong, and responsive layout breaks everywhere.

Common mistakes and how to fix them

• Still looking for the report in GSC. It was removed in December 2023 — it isn't coming back. Fix: stop hunting for it and move your checks to PageSpeed Insights and the Core Web Vitals report.
• Reading its removal as a penalty. Google retired it for every site at once; it says nothing about yours. Fix: reassure stakeholders and redirect the energy to real mobile QA.
• Assuming mobile stopped mattering. With mobile-first indexing, Google predominantly crawls the mobile version of your pages. Fix: keep testing mobile relentlessly — the report died, the priority didn't.
• Trusting emulators alone. Device mode is great for layout but misses real touch and font-scaling quirks. Fix: pair emulator checks with at least one test on a physical phone.
• Chasing dead API endpoints. Old scripts calling the Mobile-Friendly Test API now fail silently. Fix: migrate those workflows to Lighthouse or the PageSpeed Insights API.

FAQ

Why can't I find the Mobile Usability report in Search Console?

Because Google removed it in December 2023, along with the Mobile-Friendly Test tool and its API. It's gone for everyone — not a bug, not a permissions issue, and not specific to your property. Use PageSpeed Insights and the Core Web Vitals report instead.

Does this mean mobile-friendliness no longer affects rankings?

No. Google runs mobile-first indexing, so it predominantly uses the mobile version of your pages to rank you. Mobile experience matters as much as ever — Google just stopped providing that one dedicated report.

What's the closest replacement inside Search Console?

The Core Web Vitals report. It's still in GSC, still separates mobile from desktop, and gives you real-user field data on loading, interactivity, and layout stability — the health signals that matter most on phones.

How do I test a single page's mobile-friendliness fast?

Drop the URL into PageSpeed Insights and read the Mobile tab, or open the page in Chrome DevTools device mode. Both give you an immediate read without the retired tooling. For a hands-on walkthrough, see how to test mobile-friendliness.

Should I still care about mobile-first indexing?

Absolutely — it's the default. Google crawls and ranks primarily from your mobile pages, so any content, links, or structured data missing from the mobile version is effectively invisible. See our guide on verifying mobile-first indexing.