Most small business sites are written on a laptop and judged on a phone, usually by a stranger standing in a parking lot. Google builds its index the same way. Its guide to mobile-first indexing says Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking. A mobile version is not required for a site to appear in Search, the page says, but it is very strongly recommended. So the phone version is not an extra. For the crawler and for the customer it is the site.
No formal mobile audit was run for this post, and no results from one are claimed. The advice comes from Google’s documentation and from web.dev, not from a test. The pages cover more than a small shop needs, so what follows is a short list of things worth checking, in the order that usually matters.
Start with one design that fits every screen

Google’s recommended setup is responsive design, which serves the same HTML on the same URL and lets the layout adapt. The mobile-first page says its specific advice applies mostly to the other two setups, dynamic serving and separate mobile URLs, so a responsive site has less to worry about. The earlier posts on a one-page website for a small business and on website builders for a small shop cover the choices that lead here.
There is one rule in the guide that is easy to break by accident. The mobile pages should carry the same content as the desktop pages. The layout may differ, and Google gives accordions and tabs as examples of acceptable differences, as long as the content is equivalent and the headings stay clear and consistent. A menu page that trims the descriptions “for mobile” has changed what Google indexes.
The same equivalence applies behind the scenes. The page says title elements and meta descriptions should be equivalent across both versions, that structured data should be marked up the same way on both, and that the mobile site should use the same alt text as the desktop site. It also says to keep image URLs stable, because changing them can cause a temporary loss of image traffic.
The viewport tag

If a page looks like a tiny desktop site on a phone, the usual cause is a missing line in the head of the document. The web.dev article on responsive design basics gives it as:
<meta name="viewport" content="width=device-width, initial-scale=1">
The article says the tag tells the browser how to control the page’s dimensions and scaling, and that without it mobile browsers render the page at a desktop screen width, which makes text hard to read. The first half of the tag, width equal to device-width, matches the page to the screen width so content can reflow. The second half sets a one-to-one relationship between CSS pixels and device-independent pixels.
Some older snippets add minimum-scale, maximum-scale or user-scalable to the tag. The article does not recommend them, because they can prevent the user from zooming. A customer with poor eyesight who cannot enlarge the hours on your page will not write to complain. They will call somebody else.
To check, open the page source on your site and search for the word viewport. A custom page or an old template is the likeliest place for it to be missing.
No sideways scrolling, and images that behave

The same article is blunt about horizontal movement. Forcing the user to scroll horizontally or to zoom out to see the whole page causes a poor user experience. The usual causes are an image wider than the screen, a table with fixed-width columns, or an embedded element with a hard-coded width.
For images, the article gives two lines of CSS: a maximum width of 100 percent and a display value of block, so that the picture shrinks to fit its container. It recommends flexbox, grid or multi-column layouts over fixed pixel layouts, because content shouldn’t rely on a particular viewport width to render well. And for the style sheet itself it suggests starting with the small screen: design the content to fit a small screen first, then widen the screen until a breakpoint becomes necessary, and add a media query there.
Image size is a second question from image fit. The web.dev guide to responsive images notes that images often account for most of the bytes a page downloads, and that a large image wastes bandwidth on a small screen. It describes the srcset and sizes attributes, which let the browser pick the best file for the screen. An oversized original on a phone page spends a customer’s data on pixels the screen cannot show.
Text size and tap targets
A page can fit the screen and still be hard to use. Two numbers come up. The first is text. The Lighthouse audit for legible font sizes flagged a page when 40 percent or more of the text was smaller than 12 pixels, and it said at least 60 percent should be 12 pixels or larger, because small text forces people to zoom in. The documentation also says the audit was removed in Lighthouse 13. The figure is useful as a floor, and it is no longer something a test will tell you about.
The second is the size of what a finger has to hit. The web.dev article on tap targets says a minimum recommended touch target size is around 48 device-independent pixels, which it puts at about 9 millimeters, roughly the size of a finger pad. A 24-pixel icon can still meet that if you add padding to bring it up to 48. Targets should also sit roughly 8 pixels apart, in both directions, so a press on one does not land on its neighbor. The article says this helps everyone and is especially helpful for anyone with a motor impairment.
For a restaurant or a shop, the elements this applies to are the ordinary ones: the phone number, the menu link, the directions link, the cart button. A row of five links set tightly in the footer is a likely place for trouble. The article offers a tidy technique for it, which is to use the media query (any-pointer: coarse) to enlarge links only for touchscreen users instead of guessing from the viewport size.
Layout that jumps
Anyone who has tapped a link just as the page rearranged itself knows what layout shift feels like. The web.dev article on optimizing layout shift lists the common causes: images without dimensions, ads, embeds and iframes without dimensions, dynamically injected content, and web fonts. Its advice for images is direct: always include width and height size attributes on images and video elements, and reserve space with CSS aspect-ratio if you cannot. With the attributes in place, the browser can set aside the right amount of room before the image arrives.
The article gives thresholds for the score it uses, where good values are 0.1 or less and poor values are greater than 0.25. A small site cannot do much with those numbers except notice when a page feels jumpy and look at the images and embeds first. An embedded video with no reserved space is on the article’s list for the same reason: it arrives late and pushes everything below it down.
One related caution comes from Google’s mobile-first guide: avoid loading primary content only after a user interaction, because Google won’t load content that requires user interactions. If the menu only appears after a tap or a scroll, the crawler may never see it.
How to test it without owning ten phones
Chrome has a free tool for this. The DevTools documentation on device mode says to use it to approximate how your page looks and performs on a mobile device. You open DevTools and click the Toggle device toolbar button. It can simulate preset device sizes, rotation, and throttled network and CPU speeds.
The same page is honest about the limit. Device mode is a first-order approximation, and the page recommends running the page on a real device when in doubt. So use it for the quick pass, and then hold the actual phone in your hand. Open the home page, find the phone number, find the hours, try to get from the menu to the directions with one thumb. If any of that takes more than a few seconds, a customer in a hurry will not do it.
One last note on expectations. Google’s page on page experience says there is no single signal, and it frames mobile display as a question for site owners: “Does your content display well on mobile devices?” It also says Core Web Vitals are used by Google’s ranking systems and that other page experience aspects do not directly help a site rank higher. A well-built phone site will not carry a weak page to the top of search results. It does stop a good page from losing a customer at the door.
For informational purposes only. Search and browser guidance changes often, so check the linked pages for current wording, and ask a web developer before editing a live site’s code.
Sources
- Google Search Central, Mobile-first indexing best practices: https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing
- Google Search Central, Understanding page experience in Google Search results: https://developers.google.com/search/docs/appearance/page-experience
- web.dev, Responsive web design basics: https://web.dev/articles/responsive-web-design-basics
- web.dev, Accessible tap targets: https://web.dev/articles/accessible-tap-targets
- web.dev, Responsive images: https://web.dev/articles/responsive-images
- web.dev, Optimize Cumulative Layout Shift: https://web.dev/articles/optimize-cls
- Chrome for Developers, Lighthouse legible font sizes: https://developer.chrome.com/docs/lighthouse/seo/font-size
- Chrome for Developers, Device mode: https://developer.chrome.com/docs/devtools/device-mode
- Google Search Central on YouTube, [Basics of a mobile website for SMBs] 2. Bring it in: Viewports, zoom and plugins: https://www.youtube.com/watch?v=1ZcWPGPTe8I
