- Free, no sign-up
- Real phone render
- Mobile vs desktop compared
Free Mobile-Friendly Test
Google retired its Mobile-Friendly Test in December 2023, but it still indexes the version of your page its smartphone crawler sees. Paste a URL and see the page on a phone, the viewport and layout problems with the fix for each, and a side-by-side of what Googlebot smartphone and a desktop browser get: the text, the links, the structured data, the canonical and robots tags. No sign-up.
0.0 0 ratings
How useful was this tool?
Be the first to rate it.
How to use it
Test, compare, fix
Paste the URL
One page at a time: a product, a service page, a blog post. We fetch it as Googlebot smartphone and as a desktop browser at once, then render it on a phone with Google's PageSpeed Insights, which takes 15 to 30 seconds.
See what the phone version is missing
The desktop page and the phone render side by side, with what Google reads on each between them: the main text, the structured data, the links, the canonical, the robots tags, the title and the H1. Anything only desktop has does not count for Google.
Fix the problems in order
Each problem comes with why it matters and the fix: the viewport tag to copy, the CSS rule that overflows the screen, the tap targets that are too small, the pop-up that covers the page, the scripts robots.txt blocks. Fix, then test again, and check speed on phones in the Website Speed Test.
Built forWordPress themesShopsm. sitesAudits
Quick answer
What does a mobile-friendly test check?
A mobile-friendly test checks whether a page works on a phone: a viewport tag set to the device width, a layout that fits the screen without sideways scrolling, text big enough to read and links far enough apart to tap. Google no longer gives a pass or fail (its own test was retired on 1 December 2023), but since mobile-first indexing it ranks the version its smartphone crawler sees, so content, structured data and tags missing on mobile are missing for Google. This tool renders the page on a phone, lists each problem with the fix, and compares the mobile and desktop versions.
Google's test is gone
What replaced it
Google retired the Mobile-Friendly Test, its API and the Mobile Usability report in Search Console on 1 December 2023, and pointed people to Lighthouse, which runs in Chrome and inside PageSpeed Insights. Lighthouse 12 then moved the viewport and font-size checks out of its SEO category ("no longer priorities for SEO") and replaced tap targets with the accessibility check for target size; Lighthouse 13 (October 2025) dropped font-size altogether. So there is no Google pass or fail to chase any more. What still matters is that the page works for people on phones and that Googlebot smartphone gets the whole page. Search Console's URL Inspection still shows your own pages as Googlebot smartphone renders them.
The viewport tag
One line in the head
| Part | What it does | Use it? |
|---|---|---|
| width=device-width | The page is laid out as wide as the phone | Yes, always |
| initial-scale=1 | No zoom when the page opens | Yes |
| width=1024 (a number) | The phone shrinks a desktop-width page to fit | No |
| maximum-scale=1 | Stops people zooming in | No |
| user-scalable=no | Stops people zooming in | No |
The tag to copy: <meta name="viewport" content="width=device-width, initial-scale=1">. Without any viewport tag a phone lays the page out about 980 px wide and shrinks it, so the text is tiny.
Mobile-first indexing
What must match on phone and desktop
Google finished moving every site to mobile-first indexing on 31 October 2023: it indexes and ranks the version its smartphone crawler gets. Its documentation asks for the same content, structured data, titles, meta descriptions and robots meta tags on both. The usual breaks on Indian sites: a mobile template that drops the product description or the reviews "to keep it light", a plugin that outputs FAQ or product schema on desktop only, a separate m. site without its canonical, and a phone menu that leaves most internal links out. Collapsing a section into a tab or an accordion is fine; removing it from the phone HTML is not.
m. sites and dynamic serving
Three ways to serve phones
Responsive design (one URL, one HTML, the layout changes with CSS) is what Google recommends. Dynamic serving (one URL, different HTML for phones) needs a Vary: User-Agent header so caches do not mix the two. A separate m. site needs a pair of tags: rel="alternate" media on the desktop page pointing at the m. page, and a canonical on the m. page pointing back to desktop; every desktop URL redirects phones to its own m. equivalent, never to the m. home page. The test tells you which one your page uses and what is missing.
Pop-ups and interstitials
Banners are fine, covers are not
Google's page experience guidance names intrusive interstitials: a pop-up that covers the content as soon as the page opens. Full-screen app-install and newsletter pop-ups are the common ones in India. A slim banner at the top or bottom, a cookie notice, an age check or a login wall for private content are fine. We flag the pop-up scripts we find in the page and show the phone render, so you can see what a visitor meets first.
FAQ
Questions people ask
Does Google still have a Mobile-Friendly Test?
No. Google retired it, with its API and the Search Console Mobile Usability report, on 1 December 2023. Lighthouse and PageSpeed Insights replace it; this tool adds the mobile versus desktop check Google's indexing depends on.
What is mobile-first indexing?
Google indexes and ranks the version of a page its smartphone crawler sees. Text, links, structured data and tags that only the desktop version has do not count.
How do I make my website mobile-friendly?
A viewport tag with width=device-width, a responsive layout with nothing wider than the screen, readable text, links and buttons at least 24 px with room between them, the same content as desktop, and no pop-up covering the page on arrival.
What should the viewport tag say?
width=device-width, initial-scale=1. Do not add maximum-scale=1 or user-scalable=no: they stop people zooming in.
Does mobile-friendliness affect rankings?
Page experience is a set of signals, not one score. The bigger effect is mobile-first indexing: what is missing on the phone version is missing for Google.
What is a good tap target size?
At least 24 × 24 CSS px (WCAG 2.2, which Lighthouse checks as target size); 44 to 48 px is comfortable for the main buttons.
Should I have a separate m. site?
Google recommends one responsive page. An m. site works if every page has the rel="alternate" and canonical pair and phones are sent to the matching m. page.
Why is my page wider than the phone screen?
A fixed-width element (a table, an image, an embed, a width in pixels in the CSS) or a missing viewport tag. The test names the CSS rule when it finds one.
Do pop-ups hurt mobile SEO?
A pop-up that covers the content on arrival is named in Google's page experience guidance. A small banner, a cookie notice or an age check is fine.
My page looks fine on my phone. Why does the test disagree?
Your phone may have the page cached, or the site may serve Googlebot a different version; content shown only after a tap or loaded by a script may also be missing from what Google reads. Compare the two columns.
Keep going
More free tools and guides
- Website Speed Test: server response and page weight, the speed side of phones.
- Robots.txt Tester: the rule that blocks your CSS or JavaScript for Googlebot.
- Canonical Tag Checker and Schema Markup Validator: the tags and the structured data in detail.
- Free Website Audit: the whole page in one pass.
- Core Web Vitals, page experience and mobile-first indexing (Advanced, chapter 3).
Did this tool help you?
Tap a star. It takes a second, no sign-up.
–
0.0 0 ratingsNo ratings yet.
See your page the way Google's phone crawler does
Phone render, layout problems and the mobile vs desktop check. Free, no sign-up.