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

Mobile content optimization: write pages that work on phones

Updated · 8 min read

Short answer Google ranks the phone version of your page, so put all your content there, not a cut-down copy. Lead with the answer and the call button, use short paragraphs under clear headings, fold long details into tap-to-open sections, keep text readable without zooming, and use the same keywords on phone and desktop.

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

Book a call

Mobile content optimization: the rules

Mobile content optimization means writing and arranging a page so someone on a phone finds the answer, trusts you and taps to call or book. It is mostly about what you put on the page and in what order, not about design tricks.

RuleWhat it looks like on a service pageWhy
Same content on phone and desktopNothing deleted from the phone versionGoogle indexes and ranks the phone version
Answer firstService, area and price range in the first linesA phone shows a few lines per screen
Call or book button near the topTap-to-call number before any long textThe phone is the dialer
Short blocks under clear headingsTwo to four sentences per paragraphEasier to scan with a thumb
Long details folded, not cutFAQ and fine print in tap-to-open sectionsGoogle allows accordions and tabs
Text readable without zoomingNo sideways scrolling, no tiny printAccessibility standard: works at 320 pixels wide
No full-screen pop-upA small banner insteadGoogle advises against covering the page
Same keywords on both versionsSame title, headings and wordingBoth versions rank for the same searches

Does Google rank the mobile version of my page?

Yes. Since October 2023 Google crawls and indexes sites the way a phone sees them, which it calls mobile-first indexing (Google Search Central Blog, "Mobile-first indexing has landed"). What isn't on the phone version doesn't count:

"Only the content shown on the mobile site is used for indexing." (Google Search Central: Mobile site and mobile-first indexing best practices)

That rules out the old habit of trimming the phone page to save space. Google says so directly, and offers the alternative:

"You can have a different design on mobile to maximize user experience (for example, moving content into accordions or tabs); just make sure that the content is equivalent to the desktop site." (same page)

Many small business sites are responsive: one page that rearranges itself for each screen. Google notes that with responsive design "the content and the metadata are the same" on both versions, so the risk is low. The risk is real if your theme hides blocks on phones, or if your site has a separate phone site (an address like m.yoursite.com). Check what your theme hides on small screens before you assume.

Two more rules from the same Google page: keep the same headings, image alt text (the text description of an image) and structured data (code that labels your hours, prices or reviews for search engines) on both versions. And don't load main content only after a tap or swipe, because "Google won't load content that requires user interactions".

How long should a page be for phone readers?

As long as the question needs, no longer. Google has no preferred length; its helpful-content checklist asks whether you write to a word count and answers "(No, we don't.)" (Google Search Central: Creating helpful, reliable, people-first content).

Phone readers can handle real content. In a 2016 study of 276 people, Nielsen Norman Group found no practical difference in comprehension between phone and computer readers. But hard articles took longer on phones, about 30 milliseconds more per word, and the researchers still advise brevity for most mobile content (Nielsen Norman Group: Reading Content on Mobile Devices).

What that means for a service page:

  • Put the answer in the first screen. What you do, where, and what it roughly costs or how to book.
  • Cut padding, not substance. Drop the "welcome to our website" paragraph. Keep process, price ranges, licenses and reviews.
  • Fold the long parts. A full FAQ, warranty terms or a long list of areas served can sit in tap-to-open sections. Google indexes them.
  • Use plain words. Hard text slows phone readers most. Lawyers, clinics and financial firms feel this first.

How to lay out text for a small screen

Google's SEO Starter Guide asks for text that is "easy-to-read and well organized" and says to "break up long content into paragraphs and sections, and provide headings". On a phone, that matters more:

ElementDoAvoid
ParagraphsTwo to four sentencesWalls of text that fill the screen
HeadingsThe customer's question as the headingClever headings that say nothing
Lists and tablesShort lists; tables of two or three columnsWide tables that force sideways scrolling
Phone numberA tap-to-call linkA number in an image, which can't be tapped
Buttons and linksAt least 24 by 24 pixels, with space betweenLinks packed together in body text
Pop-upsA small bannerA full-screen offer on arrival

The numbers come from these places:

  • Sideways scrolling. The accessibility standard WCAG 2.2 asks that content work at "a width equivalent to 320 CSS pixels" without scrolling both ways (W3C: Understanding Reflow). Your page also needs a viewport tag, a line of code that tells phones to use the screen's real width (MDN: Viewport meta element). Every modern theme includes it.
  • Tap size. WCAG 2.2 sets a minimum target of "24 by 24 CSS pixels", or enough space around smaller ones (W3C: Understanding Target Size). Bigger is easier for thumbs.
  • Tap to call. A phone number linked as a tel: link dials on phones. MDN: "Cellular devices autodial the number." (MDN: The anchor element).
  • Pop-ups. Google's guidance: "Don't obscure the entire page with interstitials", meaning full-page pop-ups, unless the law requires one, such as an age check (Google Search Central: Avoid intrusive interstitials and dialogs).

Google lists "Does your content display well on mobile devices?" among its page experience questions (Google Search Central: Understanding page experience). Speed is the other half of that; see Core Web Vitals: does website speed affect Google ranking?.

Keywords for mobile searches: are they different?

Mostly not. Google says matching content "ensures that the two versions can rank for the same keywords" (Google Search Central: Mobile site and mobile-first indexing best practices). Don't write a separate keyword set for phones. What changes is where the words sit:

  • Lead the title with the main term. Google sets no length limit, but the title link "is truncated in Google Search results as needed, typically to fit the device width" (Google Search Central: Influencing your title links). Put "drain cleaning in Tacoma" before your business name.
  • Put the term in the first heading and first lines. That's the part a phone reader sees before deciding to stay.
  • Say it once, naturally. Google warns against repeating the same words in titles; the same goes for body text.

To see what phone searchers type, open the Performance report in Google Search Console and compare devices. Google's own troubleshooting guide tells you to check whether a change "happened only for specific queries, URLs, countries, devices" (Google Search Central: Debugging drops in Google Search traffic). If phone searches for a page are high but phone clicks are low, the title or first lines are the place to start. Title tags and headings in more depth: On-page SEO for service pages.

How do I check my page on a phone?

Open it on your own phone, on mobile data, and try to do what a customer does. Google's old Mobile-Friendly Test is gone: Google retired it, its API and the Search Console "Mobile Usability" report starting December 1, 2023, while saying mobile usability "remains critical for users" (Google Search Central Blog, April 2023).

A five-minute check:

  1. Can you tell what you offer and where without scrolling?
  2. Can you tap the phone number and have it dial?
  3. Does anything scroll sideways or need pinch-zooming to read?
  4. Does a pop-up cover the page when it opens?
  5. Is anything from the desktop page missing on the phone?

Lighthouse, Google's free audit tool built into Chrome, still flags some layout and accessibility issues. Its version 13 (October 2025) removed the old small-font check (Lighthouse changelog), so read text size with your own eyes.

Example

A plumber's water heater page (US dollars)

On a phone, the page opened with a full-width photo and a welcome paragraph; the price range and phone number sat three screens down, and the theme hid the FAQ on phones. The owner moves "Water heater replacement in Tacoma, from $1,500 to $3,000 installed" and a tap-to-call button to the top, and turns the FAQ into tap-to-open questions shown on phones too. Nothing is deleted.

A family law firm's divorce page (Canadian dollars)

The page runs 2,500 words of dense legal text. The firm keeps every section but adds a plain summary at the top (process, timeline, a consultation fee of $250), splits paragraphs, and puts each step under a question heading like "How long does an uncontested divorce take in Ontario?"

A salon with a booking pop-up

A full-screen "Book now and save 10%" window covered the page on arrival. The salon replaces it with a small banner at the bottom and a Book button under the first heading. The offer stays; the page is visible from the first second.

FAQ

Do most of my visitors use phones?

Probably close to half. In October 2026, Statcounter measured phones at 45% of web traffic in the US and 46% in Canada, against 60% worldwide. Your own analytics show your split.

Is content in accordions or tabs bad for SEO?

No. Google names accordions and tabs as a fine way to save space on phones, as long as the content is in the page and doesn't wait for a tap to load from the server.

Should I have a separate mobile site?

Not usually. A responsive site has one page and one set of content, so phone and desktop can't drift apart. Separate phone sites need the same content kept in step by hand.

What font size should body text be on mobile?

Google sets no number. Use a size you can read without zooming at arm's length, and keep lines from running off the screen.

Different for you?

Keep learning

NextPWA SEO checklist: get a progressive web app indexedWhat Google needs from a progressive web app: HTML it can read, a real URL per page, correct status codes, and a service worker that never hides content.

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-first indexing has landed (2023)
  3. Google Search Central: Creating helpful, reliable, people-first content
  4. Google Search Central: SEO Starter Guide
  5. Google Search Central: Influencing your title links
  6. Google Search Central: Avoid intrusive interstitials and dialogs
  7. Google Search Central: Understanding page experience
  8. Google Search Central Blog: More on page experience (April 2023)
  9. Google Search Central: Debugging drops in Google Search traffic
  10. Lighthouse changelog (13.0.0, October 2025)
  11. Nielsen Norman Group: Reading Content on Mobile Devices (2016)
  12. W3C: Understanding WCAG 2.2, Reflow
  13. W3C: Understanding WCAG 2.2, Target Size (Minimum)
  14. MDN: The anchor element (tel: links)
  15. MDN: Viewport meta element
  16. Statcounter: Desktop vs mobile vs tablet market share, United States
  17. Statcounter: Desktop vs mobile vs tablet market share, Canada
  18. Statcounter: Desktop vs mobile vs tablet market share, worldwide