Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Improve Mobile User Experience: Fixes That Also Help SEO

Updated · 8 min read

Short answer Fix five things on your own phone: buttons at least 24 by 24 pixels (48 for the call button), no full-screen pop-up over the page, text you can read without zooming, short forms that open the right keyboard, and a phone number you can tap. Google ranks the mobile version, but most of these win calls more than rankings.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Mobile user experience fixes: the list

Open your site on your own phone, with Wi-Fi off, and try to call or book. Every place you squint, zoom or mis-tap is a fix.

ProblemHow you spot it on your phoneFixDoes Google count it?
Tiny or crowded buttonsYou tap "Email" when you meant "Call"At least 24 by 24 pixels; 48 by 48 for call and book buttons, with space around themNot directly; it costs calls
Full-screen pop-upAn offer covers the page before you see anythingSwap it for a small banner that leaves the page visibleGoogle warns it can hurt search performance
Small textYou pinch to read the pricesBody text you read at arm's length; never block zoomingNot directly
Long or fiddly formThe phone field opens a letter keyboard; eight fields to fillThree or four fields, right field types, autofill onNot directly; it costs leads
Number you can't tapThe phone number is text or an imageMake it a tap-to-call linkNot directly
Page built for desktopThe page looks shrunk, with sideways scrollingAdd the viewport tag; use a responsive themeYes: Google ranks the mobile version

Google indexes your phone version: it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking" (Google Search Central: Mobile-first indexing best practices). Whatever is missing or broken on the phone is missing or broken for Google too.

Google's own phone checker is gone. The Mobile-Friendly Test and Search Console's Mobile Usability report were retired on December 1, 2023 (Google Search Central Blog). Your phone is now the test.

Tap targets: how big should buttons be on mobile?

At least 24 by 24 pixels, and bigger for the buttons that make you money. The web accessibility standard says:

"The size of the target for pointer inputs is at least 24 by 24 CSS pixels" (W3C: Target Size Minimum, WCAG 2.2 level AA)

It has exceptions, such as a small target with enough empty space around it. Google's Lighthouse guide sets a roomier bar: targets of "48 px by 48 px never fail the audit," with 8 pixels between them as "a good starting point" (Chrome for Developers: Tap targets).

What to do:

  • Make the call and book buttons full width or close to it, at least 48 pixels tall.
  • Keep "Call" and "Email" apart, or stack them, so a thumb can't hit both.
  • Put a link's tap area on the whole line or card, not just the word.

On Wix, Squarespace or WordPress, check button size in the mobile editor or the theme's mobile settings; most let you change it without code.

Pop-ups on mobile: which ones Google minds

Google's problem is a pop-up that hides the page. Its guide says:

"Intrusive dialogs and interstitials make it hard for Google and other search engines to understand your content, which may lead to poor search performance." (Google Search Central: Avoid intrusive interstitials)

An interstitial is a window over the whole page; a dialog covers part of it. Google lists two mistakes to avoid, unless the law requires them (same page):

"Don't obscure the entire page with interstitials."
"Don't redirect the user to a separate page for their consent or input."

Its fix: "use banners that take up only a small fraction of the screen." Pop-ups the law requires, such as an age check, are exempt (same page). A cookie notice is not named; keep it a small bar at the bottom so it doesn't hide the page.

Pop-upKeep or change
"10% off" window over the whole page on arrivalChange to a small banner
Newsletter box that fills the screenChange to a banner or an inline box in the page
Live chat bubble in a cornerKeep, if it doesn't cover the call button
Age check a law requiresKeep; show it over the page, not on a separate page

Font size: how big should text be on a phone?

Big enough to read without zooming. Lighthouse used to flag a page when "40% or more of the text" was under 12 pixels (Chrome for Developers: Font size audit). Treat 12 pixels as the floor for fine print, not a target for body text.

Google removed that check in Lighthouse 13 in October 2025, saying:

"While small fonts is a legibility issue, there are no signals that this remains an SEO concern today." (Chrome for Developers: What's new in Lighthouse 13)

So text size is about people, not rankings. Two things to check:

  • The viewport tag. Without it, phones draw the page at desktop width and shrink it, "making them difficult to read" (Chrome for Developers: Viewport audit). Your site builder adds it on any modern theme; an old custom site may not have it. The tag should read `width=device-width, initial-scale=1`.
  • Zoom stays on. Don't let a theme block pinch-to-zoom. The accessibility standard asks that text can be enlarged "up to 200 percent" (W3C: Resize Text).

Also check contrast: light gray text on white is hard to read in sunlight, outside where your customers often are.

Mobile forms: fewer fields, the right keyboard

Ask only for what you need to call someone back. web.dev puts it plainly:

"The simplest way to reduce form complexity is to remove unnecessary fields." (web.dev: Payment and address form best practices)
FixWhyHow
Three or four fieldsLong forms get abandonedName, phone, what you need, and maybe ZIP or postal code
Right field typeOpens "the right keyboard on mobile" (web.dev: Sign-up form best practices)Phone field type "tel", email field type "email"
Autofill onThe phone fills in name and number`autocomplete="name"`, `autocomplete="tel"`, `autocomplete="email"`
Real labelsA placeholder disappears once typing starts (web.dev: Payment and address form best practices)A label above each field, not gray text inside it
Big submit buttonSame as any tap targetFull width, 48 pixels tall, says what happens: "Get my quote"

Form builders (Jotform, Typeform, Gravity Forms, the Wix and Squarespace form blocks) let you pick the field type; choose "Phone" and "Email," not "Text."

Tap-to-call: the fix most service sites miss

Write your phone number as a link that starts the call. The link address starts with `tel:` and then the number, such as `tel:+15555550123` (MDN: Linking to telephone numbers). Most site builders have a "phone" link option. Put it in the header and repeat it near each call to action. Never use an image of the number: a phone can't tap it, and Google may not read it as text.

Do mobile user experience fixes help SEO?

Some do, most indirectly. Google's page experience guide says:

"Core Web Vitals are used by our ranking systems." (Google Search Central: Understanding page experience)

The same page says other page experience aspects "don't directly help your website rank higher in search results." Its self-check still asks whether your content displays well on mobile and whether pages avoid intrusive interstitials.

What that means for you:

  • Counts for ranking: the mobile version having the same content as desktop, speed and stability (Core Web Vitals), and no page-hiding pop-ups.
  • Counts for calls: button size, text size, forms and tap-to-call. These rarely move a ranking, but they decide whether a phone visitor becomes a customer.

Speed has its own guide: Core Web Vitals and website speed.

How to tell the fixes worked

Count what the fixes are for: calls, form sends and bookings from phones. Set them up as key events in Google Analytics and compare phone visitors for a month before and after (GA4 key events). Make one change at a time so you know which one moved the number. A menu that is hard to open counts too: keep it to a few plain links, with the call button outside it.

Example

Illustrative cases with invented round numbers.

A plumber whose call button was a word (US dollars)

The header says "Call us" in 14-pixel text, 4 pixels from "Email." Visitors open blank emails. The owner makes a full-width "Call now" button, 52 pixels tall, as a tap-to-call link. One extra $400 drain job a month pays for the hour.

A Vancouver dental office with an arrival pop-up (Canadian dollars)

A "Free whitening" window covers the whole page on every phone visit. The office moves the offer into a slim banner at the top and keeps the page visible. Nothing else changes, so it can see whether booking requests rise. One new patient worth C$1,000 a year covers the change.

A cleaning company with a nine-field form (US dollars)

The quote form asks for address, square footage, pets, frequency and more. The owner cuts it to name, phone, ZIP and a "What do you need?" box, with the phone field set to "tel." Details get collected on the callback. Each recurring client is worth about $150 a visit.

FAQ

Does Google penalize pop-ups on mobile?

Google doesn't call it a penalty. It says page-hiding pop-ups "may lead to poor search performance" (Google Search Central). Small banners and legally required pop-ups are fine.

What is a good font size for a mobile website?

Body text well above 12 pixels, the old Lighthouse floor. Read your page at arm's length on your phone, and never block zoom.

Is there still a Google mobile-friendly test?

No. Google retired it on December 1, 2023 (Google Search Central Blog). Test on your own phone; use PageSpeed Insights' Mobile tab for speed.

Should my mobile site have less content than desktop?

No. Google ranks the phone version and wants it to have "the same content as your desktop site" (Google Search Central). Fold long sections instead of deleting them.

Different for you?

Keep learning

NextOptimize your website for mobile: test, fix and retestA hands-on mobile test for a small business site: what to tap on real phones, which free Google tools to run, how to fix what fails, and when to retest.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Mobile site and mobile-first indexing best practices
  2. Google Search Central: Understanding page experience in Google Search results
  3. Google Search Central: Avoid intrusive interstitials and dialogs
  4. W3C: Understanding Success Criterion 2.5.8 Target Size (Minimum)
  5. Chrome for Developers: Tap targets are not sized appropriately (Lighthouse)
  6. Chrome for Developers: Document doesn't use legible font sizes (Lighthouse)
  7. Chrome for Developers: What's new in Lighthouse 13 (October 2025)
  8. Chrome for Developers: Viewport audit (Lighthouse)
  9. W3C: Understanding Success Criterion 1.4.4 Resize Text
  10. web.dev: Sign-up form best practices
  11. web.dev: Payment and address form best practices
  12. MDN: The anchor element (linking to telephone numbers)
  13. Google Search Central Blog: A new mobile friendly testing tool (December 2023 update)