Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Mobile usability in Search Console: what replaced the report

Updated · 7 min read

Short answer Google retired the Mobile Usability report and the Mobile-Friendly Test on December 1, 2023, and nothing replaced them one for one. Check four places instead: your own phone, PageSpeed Insights on Mobile, the Core Web Vitals report's mobile view, and a live URL Inspection test. AMP isn't needed: Google indexes AMP pages like any other page.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What replaced the Mobile Usability report

No single report. In April 2023 Google said it would retire the Mobile Usability report, the Mobile-Friendly Test and its API starting December 1, 2023, and pointed owners elsewhere:

"But in the nearly ten years since we initially launched this report, many other robust resources for evaluating mobile usability have emerged, including Lighthouse from Chrome." (Google Search Central Blog, April 2023)

On that date Google also removed both tools from all its documentation (Google Search Central: Documentation updates). Any guide that still sends you to the report is out of date.

The old report flagged missing viewports, tiny fonts, content not sized to the screen and links or buttons too close together (Google Search Central Blog, October 2014). Here is where each one is checked now:

Old problemCheck it now inWhat you'll see
Missing viewportPageSpeed Insights or LighthouseThe "Optimize viewport for mobile" insight
Buttons and links too closePageSpeed Insights or Lighthouse, Accessibility section"Touch targets do not have sufficient size or spacing"
Tiny fontsYour own phoneNothing automatic: Lighthouse 13 dropped this check
Page wider than the screenYour own phone, or Chrome's device modeYou have to scroll sideways

Lighthouse moved the viewport check into that insight in version 13 (Chrome for Developers: Lighthouse viewport audit) and turned the tap-target check into an accessibility audit in version 12 (Lighthouse changelog).

How to check your site on a phone, step by step

Google's plain definition still works: a mobile-friendly site is one "you can easily read and use on a smartphone, by only having to scroll up or down" (Google Search Central Blog, October 2014). Check your home page and each page that brings calls.

  1. Use your own phone, on mobile data. Read the page without zooming. Tap the phone number, the booking button and the menu. Fill in the form. If anything needs a pinch, a sideways swipe or a second try, it fails.
  2. Run PageSpeed Insights. Its mobile lab test simulates "a mid-tier device (Moto G4)" on a mobile network (PageSpeed Insights). On the Mobile results, read the Accessibility section for touch targets and the insights list for the viewport.
  3. Open Core Web Vitals in Search Console. It sorts your pages by real visitors' experience "for both mobile and desktop" (web.dev: Core Web Vitals workflows). Look at the mobile side. Small sites often show no data; see Core Web Vitals and website speed.
  4. Test the live URL in URL Inspection. Search Console lets you "test a live URL" (Google Search Central: Get started with Search Console). Google's mobile guide says to check that your content shows on the rendered page, which is "how Google sees your page" (Google Search Central: Mobile-first indexing best practices).
  5. Use Chrome's device mode for a quick look on a computer. Google calls it "a first-order approximation" and says that "when in doubt, your best bet is to actually run your page on a mobile device" (Chrome for Developers: Device mode).

Does mobile usability still affect Google rankings?

Two things matter, and they matter differently.

What your phone version shows decides what Google indexes. Google ranks the mobile version of your pages:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile-first indexing best practices)

Since July 5, 2024, Google crawls every site with its smartphone crawler, and "if your site's content is not accessible at all with a mobile device, it will no longer be indexable" (Google Search Central Blog, June 2024). A service or a review section your mobile theme hides doesn't exist for Google.

Layout polish is for customers more than for rankings. Google's ranking guidance names Core Web Vitals, then adds:

"Beyond Core Web Vitals, other page experience aspects don't directly help your website rank higher in search results." (Google Search Central: Understanding page experience)

The same page says these aspects still make a site "more satisfying to use", which lines up with what Google rewards. When Lighthouse dropped its font-size check in October 2025, Chrome's team wrote "there are no signals that this remains an SEO concern today" (Chrome for Developers: Lighthouse 13). A tiny button won't sink your ranking, but a mis-tapped call button is a lost call.

Pop-ups that cover the page are different. Google says they make your content hard for search engines to understand, "which may lead to poor search performance" (Google Search Central: Avoid intrusive interstitials).

Mobile problems that cost a service business

ProblemWhy it hurtsFix
Mobile page shows less than desktopGoogle indexes only what the phone version showsKeep the same content; Google says accordions or tabs are fine (Mobile-first indexing best practices)
Pop-up covers the page on arrivalVisitors leave; may hurt searchA small banner instead, as Google suggests (Avoid intrusive interstitials)
Call and email buttons side by sideWrong tap, lost callBigger buttons with space between them
Page zoomed out like a desktop siteText unreadable without pinchingAdd the viewport tag `width=device-width, initial-scale=1` (Lighthouse viewport audit)
Old theme you can't editEvery page fails on phonesGoogle suggests finding a new mobile-friendly theme (Mobile-first indexing best practices)
Separate m. siteThe mobile pages may carry different tagsUse the same robots meta tags on both versions (Mobile-first indexing best practices)

Do you still need AMP?

No. AMP (Accelerated Mobile Pages) is a page format Google once required for its Top Stories news carousel. That ended in 2021: "using the AMP format is no longer required", and Google stopped showing the AMP badge (Google Search Central Blog, April 2021). Today:

"Google Search indexes AMP pages just like other web pages, and applies the same standard to all pages, regardless of the technology used to build the page." (Google Search Central: About AMP on Google Search)

On July 1, 2026, Google began sending searchers straight to the AMP pages on your own site instead of a Google cache, and said "AMP content will continue to rank just like any other web page" (Google Search Central: Documentation updates).

If an old plugin made AMP copies of your pages, check them on a phone. Google expects them to let visitors "complete the same actions" as the normal page, where possible (About AMP on Google Search). An AMP copy without your booking form or chat loses leads. To drop AMP while keeping your normal pages, Google says to remove the `rel="amphtml"` link and redirect each AMP URL to its normal page with a 301 or 302. The AMP status report in Search Console then shows indexed AMP pages falling (Remove your AMP pages from Google Search).

Example

Illustrative cases with invented round numbers.

A landscaper with crowded buttons (US dollars)

PageSpeed Insights flags touch targets on the quote page: "Call" and "Email" sit 4 pixels apart, and the owner sees mobile visitors opening an empty email instead of calling. He stacks them with space between. One more $2,000 job a season covers the hour it took.

A dental office whose mobile menu hides services

The desktop site lists implants, whitening and Invisalign. The mobile theme shows only "Contact". URL Inspection's rendered page has no service text. The office restores the services in a collapsible menu, so Google can index them.

A Toronto caterer with an old AMP plugin (Canadian dollars)

AMP copies of the menu pages lack the order form. The caterer turns AMP off, redirects the AMP URLs to the normal pages and watches the AMP status report fall to zero. One C$1,500 event order pays for the fix.

FAQ

Is there still a Google mobile-friendly test?

No. It was retired with the report on December 1, 2023 (Google Search Central Blog). Lighthouse, in PageSpeed Insights or Chrome, is the closest replacement.

Does Google still crawl with a desktop bot?

Rarely. Since July 5, 2024, Google indexes with its smartphone bot. The desktop bot is sometimes used for product listings and Google for Jobs.

Do I need a separate mobile site?

No. Google recommends one responsive site, "the easiest design pattern to implement and maintain" (Mobile-first indexing best practices). A separate m. site still works.

Different for you?

Keep learning

NextGoogle Analytics for a blog: track leads and ad revenueSet up GA4 on a blog and measure what the blog is for: leads and sign-ups for your business, or money from ads, affiliate links and sales.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central Blog: The role of page experience in creating helpful content (April 2023)
  2. Google Search Central Blog: A new mobile friendly testing tool (May 2016, December 2023 update)
  3. Google Search Central: Latest documentation updates
  4. Google Search Central Blog: Tracking mobile usability in Webmaster Tools (October 2014)
  5. Google Search Central: Mobile site and mobile-first indexing best practices
  6. Google Search Central Blog: Mobile-indexing-vLast-final-final.doc (June 2024)
  7. Google Search Central: Understanding page experience in Google Search results
  8. Google Search Central: Avoid intrusive interstitials and dialogs
  9. Google Search Central: Get started with Search Console
  10. PageSpeed Insights: About PageSpeed Insights
  11. web.dev: Core Web Vitals workflows with Google tools
  12. Chrome for Developers: What's new in Lighthouse 13 (October 2025)
  13. Chrome for Developers: Lighthouse viewport audit
  14. Lighthouse changelog: 12.0.0 (April 2024)
  15. Lighthouse source: target-size audit
  16. Chrome for Developers: Simulate mobile devices with device mode
  17. Google Search Central Blog: More time, tools, and details on the page experience update (April 2021)
  18. Google Search Central: About AMP on Google Search
  19. Google Search Central: Remove your AMP pages from Google Search