Guide · mobile testing
Mobile Friendly Test: Google's Tool Is Gone, Test This Way
Google retired the Mobile-Friendly Test tool, its API and Search Console's Mobile Usability report on December 1, 2023. To test a site now, combine Lighthouse or PageSpeed Insights, Chrome DevTools, Search Console URL Inspection and a real-browser check at phone widths.
Facts checked
What happened to Google's Mobile-Friendly Test?
Google's own Search Central update says the Mobile-Friendly Test and the Mobile Usability report were retired on December 1, 2023. The same change retired the Mobile-Friendly Test API. Mobile usability did not become unimportant: Google points site owners to newer resources, including Lighthouse, and still recommends a good page experience.
How to run a mobile friendly test now
- Run PageSpeed Insights. Enter the public URL and read its Lighthouse lab audit alongside any available field data. This is useful for performance, accessibility, SEO and best-practice signals, but it is not a replacement Google verdict for mobile friendliness.
- Use Chrome DevTools. Open the device toolbar, choose a phone-sized viewport, reload the page and run Lighthouse. Check navigation, menus, dialogs and forms at the narrow width; a score cannot tell you whether a visitor can complete your journey.
- Use Search Console URL Inspection. Inspect the live URL to confirm Google can access the page and see the rendered result. This answers a different question from layout testing: crawlability and rendering are not proof that every control fits or works for a person.
- Check the page in a real browser. Test at 375 px, 768 px and 1280 px, then exercise the important path. Look for overflow, clipped text, off-screen dialogs, menus that do not open, and tap targets that are hard to use. A Sybqa free run can check real-browser layout and a reviewed journey; it does not report Google’s verdict.
For the width-by-width checklist, see the responsive design testing guide. For performance scores and field data, compare Lighthouse and PageSpeed Insights with website QA.
What “mobile friendly” means in practice
| Check | What to look for | Best evidence |
|---|---|---|
| Viewport | A viewport meta tag and content that fits without horizontal scrolling. | Lighthouse plus a real-browser width check |
| Readable content | Text, headings and controls remain readable without pinch-zooming. | Real browser; Lighthouse can flag related issues |
| Tap targets | Links and buttons are usable and not packed so taps land on the wrong control. | Lighthouse rules plus manual use |
| Content parity | Mobile exposes the same important content and metadata as desktop. | Search Central mobile-first indexing guidance |
| Journey behavior | Navigation, forms, checkout and dialogs work at phone width. | Real-browser journey test |
| Page experience | Core Web Vitals, HTTPS, intrusive interstitials and other experience signals are reviewed. | PageSpeed Insights and Search Console |
What replaced the Mobile-Friendly Test API?
There is no one-to-one replacement for the retired API. For automated performance and best-practice checks, use the PageSpeed Insights API or Lighthouse CI. For a browser workflow, use a test runner or a service that records the route, viewport, outcome and evidence. Keep the distinction clear: a Lighthouse result is not a Google Search ranking guarantee, and a browser QA result is not Googlebot’s verdict.
If you want the same reviewed check on each release, the run Sybqa on every deploy guide describes the supported CI path. Sybqa checks the live browser experience; it does not claim to replace Google Search tools.
Mobile checks for AI-built sites
Sites built with Lovable, Bolt, v0 or Cursor often look finished at the builder’s desktop preview. Give extra attention to fixed-width hero sections, tables and code blocks that overflow, navigation menus that do not open on touch, and modals positioned outside the viewport. Test the published URL in a signed-out browser, then retest after each fix. The AI-built website testing guide covers the wider release checklist.
Common questions
Is Google's Mobile-Friendly Test still available?
No. Google retired the Mobile-Friendly Test and the Mobile Usability report on December 1, 2023. The Mobile-Friendly Test API was retired too.
What replaced the Google Mobile-Friendly Test?
There is no single replacement. Use Lighthouse or PageSpeed Insights for audits and performance signals, Search Console URL Inspection for Google access and rendering, and a real-browser check for layout and journeys.
Is there a free mobile friendly test API?
There is no one-to-one replacement for the retired API. The PageSpeed Insights API and Lighthouse CI can automate related audits; a browser test runner can automate your own layout and journey checks.
Does mobile-friendliness still affect Google rankings?
Mobile usability remains part of providing a good page experience, but Google says there is no single page-experience signal and a good tool result does not guarantee top rankings. Mobile-first indexing means Google uses the mobile version of site content for indexing and ranking.
How do I test if my website is mobile friendly without coding?
Run the URL through PageSpeed Insights, inspect it with Search Console URL Inspection, and use a phone or browser device mode to try the main journey. Check overflow, text, tap targets, menus and forms. A Sybqa free run can add a real-browser layout and journey check.
Sources
- Google Search Central: The role of page experience in creating helpful content (retirement update)
- Google Search Central: The Search Console mobile friendly testing tool (retired)
- Google Search Central: Mobile-first indexing best practices
- Google Search Central: Understanding page experience in Google Search results
- Chrome Developers: Lighthouse overview
Related
Try Sybqa on your site
Explore bugs, UI consistency and user journeys from a reviewed plan. Inspect browser evidence and visual review leads in the report. The free plan gives 10 runs a month without AI review after you sign up. See pricing.