A mobile-friendly website must do the whole job.

01

Keep the important content complete on mobile.

Google uses the mobile version of a site's content for indexing and ranking. If the phone version removes important text, links, headings, metadata, alt text, or structured data, the reduced version is the one search systems may evaluate.

A responsive layout can rearrange information, place long material in accordions, and simplify decoration. It should not hide the facts and actions a customer needs. Check every important page at a narrow width and compare it with desktop content.

• Same primary copy and meaningful headings
• Same indexable links and destinations
• Same image alternatives and structured data
• Same form fields, instructions, and confirmation
• No important content loaded only after a swipe or click

02

Design for fingers, interruptions, and one hand.

Important controls need enough space, visible labels, and a clear pressed or focused state. Avoid placing small links tightly together or hiding the primary action inside several menu levels. Phone numbers, map links, booking, and form actions should behave as their labels promise.

Test while holding the device rather than resting it on a desk. Rotate it. Increase text size. Open and close the menu. Use only the keyboard when a physical keyboard is available. The goal is not a perfect screenshot at one width; it is a resilient task across widths and input methods.

• Navigation opens, closes, traps no focus, and keeps the main action visible.
• Links and buttons are comfortably separated and have descriptive labels.
• Text can enlarge without clipping or horizontal scrolling.
• Sticky elements do not cover content or controls.

03

Make forms shorter and more forgiving.

Use the right input type so phones can show a useful keyboard. Pair every field with a real label, explain required formats before submission, preserve entered values after an error, and move focus to a clear error summary when needed. Do not ask for information the business does not need at that stage.

After submission, show what happened and what will happen next. Also test the business side: the notification, stored record, spam controls, and reply path. A polished form that silently loses leads is a failed mobile experience.

Related: Check form accessibility in the accessibility guide

04

Measure loading, responsiveness, and stability.

Google's current Core Web Vitals guidance defines a good experience at the 75th percentile as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift below 0.1. These field metrics describe loading, responsiveness, and visual stability.

Treat those thresholds as diagnostics, not a single score to chase. Start with properly sized images, limited third-party scripts, stable dimensions for media, efficient fonts, and pages that do not require a large application bundle to show basic content.

• Test field data in Search Console when enough traffic exists.
• Use lab tools to reproduce a problem, then confirm it on real devices.
• Check a representative page from every template, not only the homepage.
• Re-test after adding chat, scheduling, analytics, video, or advertising scripts.

05

Use a small, repeatable device matrix.

You do not need every phone model. Choose narrow, common, tablet, and desktop widths; use at least one physical phone; and repeat the highest-value task on each. Add slow-network and reduced-motion checks when the site uses large media or animation.

Record failures by route, width, action, expected result, and evidence. Re-run the matrix before every release that changes layout, navigation, forms, fonts, images, or scripts.

Related: Review the full prelaunch website checklist