Mobile SEO checklist for small business websites

Can a customer call you without copying your number?

Start on your homepage with the phone you use every day. Find the number in the header, near your main service description and in the contact section. Tap each one. A working tap-to-call link should open the phone app with the correct number ready to dial. A number that looks clickable but does nothing is a lost opportunity, especially when someone needs an electrician or plumber in a hurry.

Check the number itself, too. It should be current, readable and consistent with the contact details you use elsewhere. If you have a mobile number for emergency calls and a separate office number, make the distinction clear. Do not force visitors to open a contact page just to find out which number to use.

Tap the number in the header and confirm that the phone app opens with the right digits.
Repeat the test on the contact page and any service page with a call button.
Check that the number is visible without opening a menu or scrolling through several blocks of text.
If you advertise emergency work, make the route to calling you clear on the relevant service page.

You can often spot a broken link yourself. If the number is plain text rather than a link, the person who built the website may need to add the correct telephone link. Fix this before spending time on smaller design details.

Is the text readable, and can people tap the right button?

Read your homepage at the size you normally hold your phone. If you have to pinch the screen to read a service description, increase the text size or ask for the mobile layout to be adjusted. Body text around 16 CSS pixels is a sensible starting point, although the right size depends on the font and design. Check headings separately because large headings can wrap awkwardly or push the important information too far down.

Next, test the buttons with your thumb. A call button beside a tiny email link can lead to accidental taps. The same problem occurs when a menu icon sits close to a search icon or when two booking options are packed into one narrow row.

Check that the main call or quote button is large enough to tap comfortably.
Leave enough space between links and buttons that a tap does not activate the neighbouring control.
Look for text that spills outside its container or overlaps an image.
Make sure menus open and close properly, and that their links remain easy to select.

WCAG 2.2, the Web Content Accessibility Guidelines, sets a 24 by 24 CSS pixel minimum target size for many pointer targets, subject to exceptions. That is a useful baseline, not a guarantee that every button will feel comfortable on a phone. Larger controls with clear spacing are often easier for customers to use.

Do pop-ups or banners cover the information people need?

Open the homepage in a private browser window so you can see the page without relying on an old saved session. Check what appears after the page loads, then wait a few seconds and scroll. A newsletter prompt, cookie notice, chat window or promotional banner may appear only after a delay.

Look at how much of the screen remains usable. If a pop-up covers the phone number, the main heading or the first service description, a visitor may struggle to understand what you offer. A close button that sits partly outside the screen is another common nuisance. Google has also documented that intrusive interstitials can make mobile content harder to access, which is why page-covering prompts deserve attention.

Test the close button and any consent controls. Dismissing a notice should reveal the page, not leave a blank overlay behind. If you use a chat widget, make sure it does not sit directly over the call button. Some changes can be made in a pop-up plugin's settings, while others require the website developer to adjust the mobile layout or timing.

Does the page load quickly on a phone connection?

A page that feels instant on office Wi-Fi can be slow on a mobile connection. Test the homepage and one important service page with Wi-Fi switched off. Reload each page and watch how long it takes before you can read the main heading and use the call button. Repeat the test if the connection is unusually poor, since one result does not tell the whole story.

For a more useful measurement, run your URLs through PageSpeed Insights. It reports lab data from a controlled test and, where available, field data from real Chrome users. Look at mobile results separately from desktop results. The Core Web Vitals are Google's measures of loading performance, responsiveness and visual stability. Their good thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less, assessed at the 75th percentile.

LCP measures how quickly the main content appears. INP measures how quickly a page responds to user interactions. CLS measures unexpected movement while the page loads. These figures help identify specific issues, but do not treat one test score as a direct prediction of rankings.

Check whether the main image is much larger than it needs to be.
Look for videos, sliders or chat tools that delay the page or make it slow to respond.
Check whether images and banners jump into place after you start reading.
Run the test on the homepage and a service page, because their images and scripts may differ.

Compressing an oversized image or removing an unused plugin may be within your reach. Changes to caching, scripts or the website's underlying code usually need the person who maintains the site. Fix the issue identified by the test rather than chasing a perfect score for its own sake.

Is any useful content missing from the phone version?

Compare the desktop and phone versions of your main pages. Do not stop at the homepage. Open the pages for individual services, your contact page and any area-specific pages you use to attract local customers. Check that the phone version contains the same important information, even if the layout puts it in a different order.

Look for missing service descriptions, prices or price explanations, opening hours, coverage areas, qualifications and answers to common customer questions. Some sites hide entire blocks on mobile to save space. Others leave the text in an expandable section that visitors never realise they can open. If the desktop page explains that you repair a particular boiler brand but the phone version omits that detail, a potential customer may never find the answer.

Google primarily uses the mobile version of a site's content for indexing. Indexing means storing a page in Google's search index so it can be considered for search results. If important content exists only on desktop, Google may not have the same information available from the mobile version. Responsive design can rearrange content without removing it, so check whether a block is genuinely absent or simply lower down the page.

If the content is present but collapsed in an accordion, test that the section opens and that its text is readable. If an entire service or location section is missing, ask your developer to compare the mobile template with the desktop version. You can also use the URL Inspection tool in Google Search Console to check a page's indexing status and, where available, inspect Google's rendered view of it.

How do you turn the checklist into a repair plan?

Write down each fault with the page where it appears, what you tapped or saw, and what should happen instead. For example, note that the phone number in the homepage header opens the wrong number, or that a cookie banner covers the call button on an iPhone-sized screen. A precise note gives your developer something concrete to fix.

Fix broken call links and controls that stop customers from contacting you.
Correct text that is hard to read, crowded buttons and overlays that block the page.
Address the specific loading problems reported by PageSpeed Insights.
Restore missing service details and check that important content is available on mobile.
Repeat the same tests after each change, using the same pages and phone where possible.

If you want a second pair of eyes, FixGuider provides a free SEO audit with screenshots of your own pages on desktop and phone. Each problem is circled, numbered and explained in plain words, with costly issues listed first. The audit checks eight areas, including mobile usability, speed, indexing and content. You can see the eight areas we check and the sample audit for a plumber before deciding if the service fits your business.

For now, take your phone, open your homepage and tap the main phone number. Then test the same action on your busiest service page. Record the first fault you find and fix that one before moving to the next item on the checklist.