Test on real phones
Browser device emulators help, but nothing replaces handling an actual phone. Try an older, smaller model if you can, and use mobile data rather than office wifi. Open your home page, a service page and the contact page. Note anything that feels slow, cramped or confusing.
Ask a friend or customer who has never seen the site to find your phone number and hours. Watch where they hesitate.
Text and layout
Body text should be readable without zooming, generally at least 16 pixels. Lines should not run to the screen edge. Paragraphs should be short. The page should fit the screen width with no sideways scrolling. Check that tables, images and embeds shrink to fit, and that a viewport tag is present in the page code.
Avoid text inside images for important details, since it does not scale or read well.
Tap targets and menus
Buttons and links need enough space to tap accurately. A common guideline is a target around 44 to 48 pixels square with spacing around it. Menus should open with one tap and close easily. Dropdowns that need hover on desktop need a tap alternative.
Make the call button obvious. A phone number set up as a tel link lets visitors tap to dial. An address linked to a maps app saves effort.
Forms and pop-ups
Keep forms short. Use the right input types so phones show a number pad for phone fields and an email keyboard for addresses. Make labels visible and fields large enough. Turn on autofill friendly names.
Pop-ups that cover the screen on load annoy users and can trigger search engine penalties when they block content. If you must use one, make it easy to close and delay it.
Speed, stability and content parity
Run your pages through a mobile speed test and check layout stability. Make sure the mobile version contains the same main content as desktop, since search engines primarily use the mobile version for indexing. Do not hide key text behind features that do not work on touch.
Re-test after every redesign, new plugin or new banner. Keep the checklist and run it quarterly.
Local intent shortcuts
People searching on a phone for a local service often want one of three things: call now, get directions, or check hours. Put a tap-to-call button at the top of every page, link your address to a maps app, and show hours near the top of the contact page and in the footer.
If you serve customers at their location, say so in one clear line near the top, such as the types of jobs you handle and the hours you take calls. Then back that up with a short form that works well with thumbs.
Keep a record of the devices and browsers you tested, along with the date. When a customer reports a problem, you can quickly see whether it was covered, and repeat the same test after a fix.
Common questions
Do I need a separate mobile site?
No. A responsive design that adapts to screen width is the standard approach.
How big should buttons be?
Aim for roughly 44 to 48 pixels with space between neighbors. Exact guidelines vary by platform.
How do I check Google's view of my mobile page?
Use the URL Inspection tool in Search Console to see how Google renders the page.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.