
Key points
- Google now indexes the mobile version of your pages, so anything missing on mobile may be missing from search.
- The essentials: a viewport tag, text that is readable without zooming, no sideways scrolling, and tap targets big enough for a thumb.
- Google retired its Mobile-Friendly Test, so use Lighthouse, browser device mode and real devices instead.
Why it matters
Search engines index and rank the mobile rendering of a page ("mobile-first indexing"). Visitors on small screens also leave quickly when text is tiny, buttons are hard to hit or the page scrolls sideways. Mobile experience feeds into Core Web Vitals as well, since many real-world measurements come from phones.
The checklist
1. A viewport tag
Without it, phones render the page at desktop width and shrink it. Put this in the head of every page:
<meta name="viewport" content="width=device-width, initial-scale=1">
2. Responsive layout
- Use CSS media queries or fluid layouts so columns stack on narrow screens.
- Avoid fixed widths in pixels on containers, tables, images and embedded frames. Use
max-width: 100%for media. - Wrap wide tables so they scroll inside their own box instead of widening the page.
3. Readable text
- Body text of about 16 CSS pixels is a common baseline. Avoid text that needs pinch-zooming to read.
- Keep sufficient line spacing and contrast.
4. Tap targets
- Buttons and links should be large enough to press accurately, around 48 × 48 CSS pixels including spacing is a widely used guideline.
- Do not place small links right next to each other.
5. Allow zoom
- Do not use
user-scalable=noor a very lowmaximum-scale. Blocking zoom is an accessibility problem and fails Lighthouse checks.
6. Same content on mobile and desktop
- Because mobile is indexed, hiding text, links, images or structured data on mobile means search engines do not see them.
- Collapsible sections are fine when the content is still in the page.
7. Media and speed
- Serve images at sizes suited to the screen, and give them width and height to prevent layout shift.
- Keep page weight down. Phones have slower processors and often slower connections.
8. No intrusive pop-ups
- Full-screen overlays that cover content right after a visitor arrives from search frustrate people and can count against the page. Cookie and age notices that are legally required are treated differently, but keep them compact.
How to test
- Run the mobile-friendly checker. It reads the page source for the viewport, zoom settings, responsive CSS and fixed-width elements.
- Open Chrome DevTools, turn on device mode and try several widths, from about 360 px up to a tablet. Scroll the whole page and look for horizontal scrolling.
- Run Lighthouse in mobile mode for the viewport, tap target and text size checks, as well as performance. See how to read the report.
- Use a real phone if you can. Emulators do not reproduce touch, slow networks or small hardware perfectly.
Google retired its standalone Mobile-Friendly Test and the Mobile Usability report in Search Console in December 2023. Lighthouse and the Core Web Vitals report remain the main official ways to check mobile quality.
FAQ
What is mobile-first indexing?
Google uses the mobile version of a page's content for indexing and ranking. If something is on your desktop page but not on mobile, it may not count.
Do I need a separate mobile site?
No. A single responsive site that adapts to screen width is simpler and is the approach Google recommends.
Why does my page scroll sideways on a phone?
Something is wider than the screen: a fixed-width table, image, embedded frame or long unbroken text. Find it in DevTools device mode and make it fluid or scrollable.
What size should buttons be on mobile?
About 48 × 48 CSS pixels including spacing is a common guideline, and accessibility standards set a smaller minimum. Bigger targets are easier for everyone.
Is there still an official Google mobile-friendly test?
The standalone Mobile-Friendly Test and the Search Console Mobile Usability report were retired in 2023. Use Lighthouse and your own device checks instead.