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

Mobile SEO best practices: the complete checklist

Updated · 7 min read

Short answer Google ranks the phone version of your site, so start there. Keep the same content, titles and structured data on mobile as on desktop, use one responsive design, and meet Core Web Vitals. Then make calling easy: a tappable phone number, big buttons, short forms, no full-screen pop-ups, and a complete Google Business Profile.

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

Book a call

Mobile SEO checklist: the short version

Work top to bottom. The first rows decide whether Google can rank you at all; the rest decide whether a phone visitor calls.

AreaCheckWhy it matters
What Google readsPhone version shows all the text, photos and reviews desktop showsGoogle indexes the phone version only
What Google readsSame page titles, meta descriptions, structured data and alt text on bothGoogle's mobile guide asks for it
LayoutOne responsive site with a viewport tagGoogle's recommended setup
SpeedCore Web Vitals pass on mobileUsed by Google's ranking systems
LocalGoogle Business Profile complete, same name, address and phone as the siteDecides who shows in the map on phones
CallingPhone number is a tap-to-call link, visible without scrollingThe call is the goal
ButtonsAt least 24 by 24 pixels, with space betweenWrong taps lose calls
FormsFew fields, right keyboard for eachTyping on glass is slow
Pop-upsNothing covers the page on arrivalGoogle says it can hurt search
TestingYour own phone plus PageSpeed Insights, monthlyGoogle's old mobile report is gone

Is the phone version really what Google ranks?

Yes. Google says so plainly:

"Google 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)

Since July 5, 2024, Google indexes sites with its smartphone crawler only. If content can't be reached on a phone, Google says it "will no longer be indexable" (Google Search Central Blog, June 2024).

So the most common mobile SEO mistake isn't speed. It's a mobile theme that hides things. Check these against your desktop pages:

  • Content. Every service, price note, FAQ and review section. Tucking text into accordions or tabs on phones is fine, Google says, as long as it's equivalent.
  • Metadata. Google asks that "the title element and the meta description are equivalent across both versions of your site."
  • Structured data. The code that tells Google your hours, address and services must match. See local business schema.
  • Images. Same alt text (the short description of a photo for search engines and screen readers).
  • Lazy loading. Google's rule: "Don't lazy-load primary content upon user interaction." Text that appears only after a tap or swipe may never be seen.

Technical checks: layout and speed

Use one responsive site. Responsive means the same page rearranges itself for any screen. Google prefers it "because it's the easiest design pattern to implement and maintain" (Mobile-first indexing best practices). A separate "m." site still works but doubles the work of keeping both equal.

Add the viewport tag. Without it, web.dev warns, a page "loads very zoomed out, making the text hard to read." The tag is one line in the page head: `width=device-width, initial-scale=1`. If your site is old or hand-coded, ask whoever built it to confirm it's there.

Meet Core Web Vitals on mobile. These are Google's three measures of how a page feels to real visitors (web.dev: Web Vitals):

MeasurePlain meaningGood
LCP (Largest Contentful Paint)Main photo or text appears2.5 seconds or less
INP (Interaction to Next Paint)Page reacts to a tap200 milliseconds or less
CLS (Cumulative Layout Shift)Layout doesn't jump0.1 or less

INP replaced FID (First Input Delay) on March 12, 2024 (web.dev). A checklist still naming FID is out of date. The usual fixes on a small site: smaller photos, fewer plugins and chat widgets, and reserved space for images so text doesn't jump. Details in Core Web Vitals and website speed.

Does readable text or a nice layout help rankings?

Not directly. Google draws the line itself:

"Beyond Core Web Vitals, other page experience aspects don't directly help your website rank higher in search results." (Google Search Central: Understanding page experience)

The same page adds that they make a site "more satisfying to use", which matches what Google rewards. So write for phones because people buy from pages they can read: the answer or offer first, two- or three-sentence paragraphs, headings that say what's below, and prices or service areas in a list rather than a block of text.

Local mobile searches: what to set up

Someone who types "emergency plumber" on a phone usually wants to call within minutes. Three things put you in front of them.

  1. A complete Google Business Profile. Google says local results "are mainly based on relevance, distance, and popularity", and that the number of reviews and sites linking to you feed that last factor (Google Business Profile Help, archived November 2026). Fill in categories, services, hours and photos, then ask every happy customer for a review. Full steps: local SEO checklist.
  2. The same name, address and phone everywhere. Site, profile and directories should match word for word.
  3. A tap-to-call number. Make the phone number a link that dials when tapped, in the header of every page, not an image of a number.

Menus. Keep every main service and the phone number one tap from any page. Short labels in plain words beat nested dropdowns, which are hard to open with a thumb.

Buttons. The web accessibility standard WCAG 2.2 sets a minimum target of "at least 24 by 24 CSS pixels" (W3C: Target Size Minimum). Its stricter level asks for 44 by 44 (W3C: Target Size Enhanced). For a call or book button, aim for the larger size and keep space between it and the next link. More on the legal side: ADA website compliance.

Forms. Ask only for what you need to call back: name, phone, what's wrong. web.dev advises using the right field type "to provide the right keyboard on mobile", so the phone field opens a number pad, and adding autofill values such as `autocomplete="tel"` so the phone fills in details for the visitor.

Pop-ups. Google warns:

"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)

Its advice covers pop-ups that aren't legally required; a cookie notice you must show is a different case. For offers, use "banners that take up only a small fraction of the screen" instead of a full-page window.

How to test your mobile site now

Google retired Search Console's Mobile Usability report and the Mobile-Friendly Test on December 1, 2023 (Google Search Central Blog, April 2023), so advice to "check the Mobile Usability report" no longer works. Do this monthly instead:

  1. Open your main pages on your own phone, on mobile data. Tap the phone number, the menu and the form.
  2. Run PageSpeed Insights on the Mobile tab. Its lab test simulates "a mid-tier device (Moto G4)" on a mobile network (PageSpeed Insights).
  3. In Search Console, read the mobile side of the Core Web Vitals report. Small sites often have too little traffic to show data; then rely on steps 1 and 2.

Example

Illustrative cases with invented round numbers.

A roofer whose mobile theme dropped the service list (US dollars)

On desktop the home page lists roof repair, replacement and gutters. The phone version shows a photo and a "Contact" button. Google indexes only the phone version, so the services barely exist for search. The roofer adds them back in a collapsible section. One $9,000 replacement job pays for the afternoon it took.

A Calgary physiotherapy clinic with a full-screen offer (Canadian dollars)

A "10% off your first visit" window covers the page on every phone visit, and many visitors close the tab. The clinic swaps it for a thin banner above the booking button. Two extra C$100 first visits a month cover the change.

A cleaning company with a nine-field form

The quote form asks for address, square footage, number of rooms and more. Phone visitors stop halfway. Cut to name, phone and service, it gets more finished requests, and details are gathered on the callback.

FAQ

Does Google still use a desktop crawler?

Rarely. Since July 5, 2024, Google indexes with its smartphone crawler; the desktop crawler is sometimes used for product listings and Google for Jobs.

Do I need AMP for mobile SEO?

No. Google "indexes AMP pages just like other web pages" (Google Search Central: About AMP). A responsive page that passes Core Web Vitals does the job.

Is a 16-pixel font a Google ranking rule?

No. It's a readability habit, not a Google rule. Text people can read without zooming keeps them on the page, which is reason enough.

How often should I check mobile SEO?

Monthly is enough for most small sites, plus after any theme change, redesign or new plugin.

Different for you?

Keep learning

NextMobile Search Optimization: Site Search That Works on PhonesWhen a small business site needs a search box, and how to build the box, filters and results page so they work on a phone and stay out of Google's way.

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 Blog: Mobile-indexing-vLast-final-final.doc (June 2024)
  3. Google Search Central: Understanding page experience in Google Search results
  4. Google Search Central: Avoid intrusive interstitials and dialogs
  5. Google Search Central Blog: The role of page experience in creating helpful content (April 2023)
  6. web.dev: Web Vitals
  7. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
  8. web.dev: Responsive web design basics
  9. web.dev: Sign-up form best practices
  10. W3C: Understanding WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum)
  11. W3C: Understanding WCAG 2.2 Success Criterion 2.5.5 Target Size (Enhanced)
  12. Google Business Profile Help: Tips to improve your local ranking on Google (archived November 13, 2026)
  13. Google Search Central: About AMP on Google Search
  14. PageSpeed Insights: About PageSpeed Insights