Google indexes the mobile version of your site. Not primarily, exclusively. If something exists on your desktop layout and not on your phone layout, as far as search is concerned it does not exist.
Most sites now pass the basic responsive test and still fail on the phone in ways nobody checks: tap targets too close together, forms that require pinching, sticky bars covering the button, text at 14 pixels because it looked tidy in the design tool.
Quick Info
What Google indexes
The mobile version, exclusively
Minimum tap target
44 by 44 pixels, with 8px of space around it
Minimum body text
16px, ideally 18px
Most common failure
Content present on desktop and hidden on mobile
How to test
On a real phone, on mobile data, using your own site
Design order
Phone layout first, then widen
Mobile-only indexing, and what it actually means
The practical consequences catch people out because they are counterintuitive.
—Content hidden on mobile to tidy the layout is content search engines may not credit you for.
—Structured data must be present in the mobile markup, not only the desktop version.
—Internal links removed from a condensed mobile navigation weaken the pages they pointed at.
—Images and alt text missing from the mobile layout do not count.
So the rule is: same content on both, arranged differently. Reordering is fine. Removing is not.
Design for the phone first, genuinely
Designing at desktop width and then squeezing produces the shape everybody recognises: a hero that works, then a long undifferentiated column of paragraphs where a three-column layout used to be.
Starting narrow forces the useful decisions. What is the one thing this page must say in the first screen? What can be collapsed? What is actually navigation and what is a link somebody put in the header years ago?
A phone screen is a brutal editor. Design there first and the desktop version arrives already edited.
Touch, not pointing
—Tap targets at least 44 by 44 pixels, with enough space that a thumb cannot hit two.
—Primary actions in the lower two thirds of the screen, where a thumb reaches without regripping.
—No hover-dependent behaviour. There is no hover on a phone, and anything hidden behind it is unreachable.
—Sticky elements: one at most. Two sticky bars on a phone leaves a letterbox of content.
—Check that your cookie banner does not cover the primary button, because it usually does.
Typography that survives a phone in daylight
—Body text 16px minimum, 18px is better. Nothing under 14px, ever, including captions and footers.
—Line length around 60 to 70 characters. On a phone this happens naturally; on a tablet it does not.
—Line height around 1.6 to 1.8 for body copy.
—Left-aligned. Centred paragraphs are hard to read at any width and worse on narrow screens.
—Real contrast. A grey that looks refined on a calibrated monitor is illegible outdoors.
Forms are where mobile sites lose money
The single highest-return mobile fix on most business sites, because a form that is annoying on a phone is a form that is abandoned on a phone.
01Set the right input type so the correct keyboard appears: email, tel, number.
02One field per row. Side-by-side fields on a phone mean mis-taps.
03Label above the field, not inside it as a placeholder that vanishes when typing starts.
04Cut every field you do not need. Name and email will do for most enquiries.
05Make the submit button full width and unmistakable.
06Validate inline, with the error next to the field rather than in a summary at the top.
Performance is a mobile design decision
Phones have slower connections and less patience. Every design choice has a weight: a video background is a design choice that costs three seconds, a carousel is a design choice that loads five images to show one.
—Serve appropriately sized images to phones, not desktop images scaled down.
—Skip the video background on mobile. Use a still.
—Load the phone layout's critical content first, not a desktop-width hero the phone will crop.
—Test on mobile data rather than office wifi. It is a different experience.
The speed checklist covers the technical side; the point here is that most mobile performance problems originate in the design.
How to test properly
01Use your own site on your own phone to complete the task a customer would: find a price, send an enquiry, book something.
02Do it one-handed, walking, outdoors. That is the real usage condition.
03Check the Mobile Usability and Core Web Vitals reports in Search Console for site-wide problems.
04Compare the mobile and desktop page source for content that only appears on one.
05Watch one real person use it. Ten minutes of this beats a week of guessing.
Browser device emulation is useful for layout and useless for the things that actually go wrong: thumb reach, keyboard behaviour, connection speed and glare.
The desktop habits that still break phone layouts
—Tables. A wide table on a phone either overflows or shrinks to unreadable. Restructure as cards or allow horizontal scroll deliberately.
—Multi-column comparison layouts, which stack into a meaningless list of features.
—Fixed-width elements from a page builder, which produce sideways scroll.
—Large text set in viewport units, which becomes tiny on a narrow screen.
—PDFs as content. They are unreadable on phones and largely invisible to search.
Frequently Asked Questions
Is mobile-first still relevant in 2026?
More than ever, because indexing is mobile-only. Any content that exists solely on your desktop layout may as well not exist.
Can I hide content on mobile to simplify the page?
Collapsing it behind an accordion is fine; removing it from the mobile markup is not, because that is the version search engines read.
What is the minimum font size for mobile?
16px for body text, and I would use 18px. Below 14px anywhere is a usability problem regardless of how it looks in the design.
Do I need a separate mobile site?
No. One responsive site is the standard approach and separate mobile sites create duplication and maintenance problems.
How do I test mobile usability without lots of devices?
Use your own phone for the real tasks, then rely on Search Console's mobile reports for site-wide issues. Emulators are for layout only.
Does mobile design affect conversion or just rankings?
Both, and the conversion effect is larger. Most sites I audit lose more enquiries to a bad mobile form than to any ranking factor.
Before You Go
Mobile-first in 2026 is not a philosophy, it is an accurate description of your audience and your crawler. The work is unglamorous: bigger text, bigger buttons, shorter forms, same content on both layouts.
Do the phone test yourself this week, trying to complete the thing a customer would. It takes ten minutes and it usually finds something.
Same content, different arrangement. Test on a real phone.
WRITTEN BY TARIQ SALLAM
Marketing Consultant. Entrepreneur. Content Creator.
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →
Keep reading