Skip to content

Google's Mobile-Friendly Test is gone: how to test mobile now

Google's Mobile-Friendly Test and Mobile Usability report were retired in December 2023. Here is the free workflow that replaces them, from seeing your page as Googlebot smartphone does to fixing the mobile failures that still cost rankings.

The seoscore team 9 min read

On this page
  1. What happened to Google's Mobile-Friendly Test
  2. Does mobile-friendliness still matter for SEO?
  3. Step 1: See your page the way Googlebot smartphone sees it
  4. Step 2: View your site on mobile, on a real phone and in DevTools
  5. Step 3: Run Lighthouse or PageSpeed Insights in mobile mode
  6. Step 4: Check every template, not one URL
  7. Common mobile-friendly failures and how to fix each
  8. Keep it mobile-friendly after launch
  9. Check your whole site with seoscore
  10. Next steps

Google's Mobile-Friendly Test no longer exists. Google retired it in early December 2023, together with the Mobile-Friendly Test API and the Mobile Usability report in Search Console. To test a page on mobile now, see it the way Googlebot smartphone does with URL Inspection or the Rich Results Test. Then check it in your browser's device mode and on a real phone, run Lighthouse in mobile mode, and finally check the whole site, because one page passing tells you very little.

What happened to Google's Mobile-Friendly Test

Google announced the retirement in April 2023, in a Search Central post on page experience and helpful content. The post said that starting 1 December 2023 it would retire "Search Console's Mobile Usability report, the Mobile-Friendly Test tool and Mobile-Friendly Test API". It added that this "doesn't mean that mobile usability isn't important for success with Google Search".

The tools were due to go on 1 December. Google confirmed they had gone on 4 December 2023, as Search Engine Land reported. Google gave its reason in the April post: in the years since the report launched, other tools for checking mobile usability had appeared, and it named Lighthouse from Chrome as one of them.

Google went further later. In November 2024 it also removed the Page Experience report from Search Console. The Core Web Vitals and HTTPS reports are still there.

The old test gave a simple pass or fail. The Mobile Usability report flagged a short list of problems:

  • Viewport not set, or not set to the device width. The viewport is the visible area of the page on the screen.
  • Text too small to read without zooming.
  • Clickable elements too close together, so a thumb hits the wrong link.
  • Content wider than screen, which forces sideways scrolling.

Those problems still matter. Nothing in Google checks for them on your behalf any more, so the workflow below does it instead.

Does mobile-friendliness still matter for SEO?

Yes, mainly because of mobile-first indexing. This means Google crawls and indexes the mobile version of your pages and ranks from that version. Google said the switch was complete in its October 2023 post, Mobile-first indexing has landed. Googlebot smartphone is now the main crawler for almost every site.

Google then closed the last gap. From 5 July 2024, sites that don't work on mobile are also crawled only with Googlebot smartphone. In Google's words, as quoted by Page One Power, "If your site's content is not accessible at all with a mobile device, it will no longer be indexable." That rule is about whether content can be reached on a phone at all, not about how good the design is. A clumsy mobile layout won't get you removed from Google. The desktop crawler is still used sometimes for product listings and Google for Jobs.

The practical risks are these:

  • Missing content. Text, links, structured data or alt text that only appears on the desktop version may never be indexed. Google's mobile-first indexing best practices ask for the same content on both versions.
  • Page experience. Google says page experience is not a single ranking signal. It does still reward pages that load quickly, stay stable and work well on phones. Core Web Vitals are Google's speed and stability metrics, and they are usually worse on mobile. Our guide to testing Core Web Vitals covers them.
  • Visitors. A page that is hard to use on a phone loses the people who reach it, whatever it ranks.

Step 1: See your page the way Googlebot smartphone sees it

This is the part of the old test people miss most: a screenshot of what Google's crawler actually renders.

Use URL Inspection in Search Console

If your site is verified in Search Console, use the URL Inspection tool:

  1. Paste the full URL into the search bar at the top of Search Console.
  2. Click Test live URL. This fetches the page as it is now, with the smartphone crawler.
  3. Click View tested page. You get the rendered HTML, a screenshot, and a More info tab listing page resources that couldn't load and JavaScript console messages.

What to look for:

  • The screenshot. Is the layout a single column? Is the main content there, or is it hidden behind a pop-up or a cookie banner?
  • Resources that couldn't load. CSS or JavaScript blocked by robots.txt is a common cause of a broken render. The robots.txt file tells crawlers which parts of your site they may fetch.
  • The rendered HTML. Search it for your main heading, key paragraphs and internal links. If they are missing, Google may not index them.

No Search Console access? Use the Rich Results Test

The Rich Results Test works on any public URL without logging in or verifying the site. It uses the smartphone crawler by default and shows the rendered HTML and a screenshot. It is the closest thing left to the old test's "see the page as Googlebot" view, and it is useful for checking a client's or prospect's site.

Step 2: View your site on mobile, on a real phone and in DevTools

The crawler's view tells you what Google gets. You also need to see what a person on a phone gets.

In your browser's device mode

Every major desktop browser can simulate a phone screen:

  • Chrome and Edge: open DevTools (F12), then press Ctrl+Shift+M (Cmd+Shift+M on a Mac) to turn on Device Mode. Pick a device from the list or drag the width.
  • Firefox: Responsive Design Mode, with Ctrl+Shift+M (Cmd+Opt+M on a Mac).
  • Safari: turn on "Show features for web developers" in Settings, Advanced. Then choose Develop, Enter Responsive Design Mode.

Don't test one size only. Drag the width slowly from about 320px up to tablet width and watch for the point where something breaks: a menu that overlaps the logo, a table that spills off the screen, a button that wraps badly. In Chrome you can also turn on network and CPU throttling to get a rough feel for a slow phone on a weak connection.

On a real phone

Emulation doesn't reproduce a real phone's processor, network or touch behaviour, so finish on an actual device. Use one iPhone and one Android phone if you can. You can inspect a connected Android phone from desktop Chrome through chrome://inspect, and an iPhone through Safari's Web Inspector over a cable.

A quick manual pass should cover:

  • Navigation: does the menu open and close, and can you reach every main section?
  • Forms: do the fields fit, does the right keyboard appear (numbers for phone numbers, email for email), and can you submit?
  • Pop-ups and banners: can you close them easily, and do they leave the content visible?
  • Horizontal scroll: swipe sideways on every page type. Nothing should move.
  • Text and taps: can you read without zooming and tap links without hitting the neighbour?
  • Media: do videos play, and do images fit the screen?

Step 3: Run Lighthouse or PageSpeed Insights in mobile mode

Lighthouse is Google's free page-testing tool, built into Chrome DevTools, and it is the tool Google pointed to when it retired the Mobile-Friendly Test. PageSpeed Insights runs the same tests from Google's servers and adds real-user data where Google has enough of it.

  1. In Chrome DevTools, open the Lighthouse tab, choose Mobile, tick the categories you want and run it. In PageSpeed Insights, paste the URL and read the Mobile tab.
  2. Read Performance for loading speed on a simulated phone.
  3. Read Accessibility, SEO and Best Practices for the old mobile checks: the viewport meta tag, text size, touch target size, image sizing and contrast.

Lighthouse has moved, renamed and retired individual audits between versions, so don't hunt for a specific audit you remember. Read what your report lists and open each failed item, which shows the elements involved.

Know the limits. Lighthouse tests one page, once, in a lab. Scores move between runs, and a pass on your home page says nothing about your product or blog templates.

Step 4: Check every template, not one URL

Most sites are built from a few templates: home page, category or listing pages, product or service pages, articles, contact and landing pages. A mobile bug usually lives in a template, so it affects every page built on it. At the very least, run steps 1 to 3 on one page of each template.

That still misses one-off problems, such as a wide table pasted into a single article or an oversized image on one product. Google no longer gives you a site-wide mobile report, so checking every page means using a site audit tool. A site audit crawls your pages and reports the problems on each one.

Common mobile-friendly failures and how to fix each

Problem How it shows up Fix
Missing or wrong viewport tag Phone shows a shrunken desktop page Add the viewport tag below to every page's head
Fixed-width layout Page wider than the screen, sideways scroll Use percentage or flexible widths and CSS media queries instead of fixed pixel widths
Text too small Readers pinch to zoom Set a readable base size (around 16px is common) in relative units
Tap targets too close Wrong link tapped Make buttons and links bigger or space them out; WCAG's target size minimum is 24 by 24 CSS pixels, and 44 to 48 pixels is more comfortable
Oversized images or video Media spills off screen or loads slowly Use responsive images and the CSS below; use video formats phones can play
Intrusive interstitials Pop-up covers content on arrival Follow Google's interstitials guidance: use small banners; cookie, legal and age notices are allowed
Content missing on mobile Text, links or schema only in the desktop version Serve the same content on both; tuck it into accordions rather than removing it
Slow mobile LCP Main image or heading appears late Compress and resize the hero image, don't lazy-load it, cut render-blocking scripts; aim for LCP (Largest Contentful Paint) of 2.5 seconds or less
Horizontal scrolling Page shifts sideways Find the wide element in DevTools; often a table, embed or long URL

The standard viewport tag:

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

A safe default that stops images and embeds breaking the layout:

img, video, iframe {
  max-width: 100%;
  height: auto;
}

table {
  display: block;
  overflow-x: auto;
}

The table rule lets a wide table scroll inside its own box rather than pushing the whole page sideways. For speed fixes beyond LCP, see the Core Web Vitals guide. For crawling and rendering issues, see what technical SEO covers.

Keep it mobile-friendly after launch

Mobile layouts rarely break on launch day. They break later:

  • a theme update changes the header or menu;
  • a new plugin injects a pop-up, a chat widget or a wide embed;
  • a new landing page template is built and only checked on a desktop screen;
  • an editor pastes a wide table or an uncompressed photo into a post.

Build a short habit around those moments. Test on a staging copy before updating the theme, and check one page of each template on your phone after any plugin change. Re-run your site-wide check every few weeks.

Check your whole site with seoscore

The free tools above check one URL at a time. A seoscore SEO audit checks every page and scores the site out of 100. Mobile is one of eight weighted areas, worth 12 of the 100 points. Every fix is ranked by the points it adds, so you can start with the mobile problem that costs you most. The audit is on the free plan, with no card needed.

Every check and weight is published on how the score works, so you can see exactly what the Mobile area tests.

Two paid features cover the after-launch problem. Both are on Starter and up, with a free trial:

  • Automatic audits re-audit the site weekly or daily and email your team when the score drops. A theme update that breaks the mobile layout shows up without anyone having to look.
  • Competitor analysis compares your score with a competitor's, area by area, so you can see whether their Mobile score is ahead of yours.

Next steps

  1. Run URL Inspection's live test (or the Rich Results Test) on your home page and your most important page, and check the screenshot and any resources that couldn't load.
  2. Open those pages in device mode, drag through a range of widths, then do the manual pass on a real phone.
  3. Run Lighthouse in mobile mode and fix what it flags, starting with the viewport, text size and tap targets.
  4. Repeat for one page of each template, then audit the whole site so one-off problems don't slip through.
  5. Re-check after every theme, plugin or template change.

Questions people ask

Is there an official replacement for Google's Mobile-Friendly Test?

No. Google didn't launch a direct replacement and pointed site owners to Lighthouse instead. The closest view of how Google renders a page on a phone is now the live test in Search Console's URL Inspection tool, or the Rich Results Test for sites you don't manage.

Is the Search Console Mobile Usability report coming back?

Google has given no sign that it will return. Google also removed the Page Experience report in November 2024, while keeping the Core Web Vitals and HTTPS reports. Treat site-wide mobile checks as something you now run with your own tools.

Does Google require responsive design?

No. Google supports responsive design, dynamic serving and separate mobile URLs, but it recommends responsive design because it is the simplest to keep right. Whichever you use, the mobile version needs the same content, structured data and metadata as the desktop version, because that is the version Google indexes.

Will Google remove my site if it isn't mobile-friendly?

Not for poor mobile design alone. Since July 2024, content that can't be reached on a mobile device at all can no longer be indexed. A site that works on phones but is awkward to use can still be indexed, though it may lose visitors and do worse on page experience.

Is a separate mobile site on an m. subdomain still a good idea?

It can work, but it is harder to maintain. Every page needs a matching mobile URL with the same content, and the two versions have to be linked correctly. Content added to one version and forgotten on the other is a common cause of problems under mobile-first indexing.

Sources

  1. The role of page experience in creating helpful content  |  Google Search Central Blog  |  Google for Developers developers.google.com
  2. Google officially drops Mobile Usability report, Mobile-Friendly Test tool and Mobile-Friendly Test API searchengineland.com
  3. Google removes Page Experience Report from Search Console ppc.land
  4. Mobile-first indexing has landed - thanks for all your support  |  Google Search Central Blog  |  Google for Developers developers.google.com
  5. Google Won’t Index Sites That Are Inaccessible on Mobile Starting July 5, 2024 www.pageonepower.com
  6. developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing developers.google.com
  7. developers.google.com/search/docs/appearance/page-experience developers.google.com
  8. support.google.com/webmasters/answer/9012289 support.google.com
  9. search.google.com/test/rich-results search.google.com
  10. developer.chrome.com/docs/devtools/device-mode developer.chrome.com
  11. w3.org/WAI/WCAG22/Understanding/target-size-minimum.html www.w3.org
  12. developers.google.com/search/docs/appearance/avoid-intrusive-interstitials developers.google.com

seoscore

What does your site score?

Run a free audit: a score out of 100 and every fix ranked by the points it adds.

Get my free score

Technical SEO

What is technical SEO? Elements, examples and a checklist

Technical SEO is the work that lets search engines and AI crawlers find, render, understand and index your pages. Here is what it covers, how to spot the common problems and what to fix first.

12 min read