Google's crawler doesn't just check whether your site works on a phone anymore. It uses the phone version of your site as the actual basis for indexing and understanding what your business is, which quietly flips the old assumption that mobile was the secondary, "also works on phones" version of a real desktop site.
What mobile-first indexing actually means
Google's own documentation is direct about this: it uses "the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." This transition started in 2016, and Google announced the migration was complete for the web as a whole in October 2023, with the last sites still being crawled by a desktop-only agent switched over by July 2024. In practical terms, whatever your mobile page shows, or hides, is what Google understands your page to say.
The mistake this exposes: content that only exists on desktop
A common, quietly damaging pattern is a site where the desktop version has a full paragraph of detail and the mobile version, built to look tidier on a small screen, has that same content trimmed or hidden behind a "read more" that never gets tapped. Under mobile-first indexing, the version Google actually reads is the trimmed one. Content that only exists on desktop, functionally, doesn't exist to Google at all.
Why this isn't just a technical detail
Beyond indexing, the practical reality is that most visitors to a local trades site are already on a phone, often while standing in the middle of the exact problem that sent them searching. See designing a website for emergency service searches for what that moment looks like specifically. Building for phones first isn't a concession to a secondary audience; for most of these businesses, phone visitors are the primary one, and desktop is what a minority sees.
What "built for phones first" actually looks like
- Design the layout starting from a phone-width screen, then expand for larger screens, rather than designing for a wide desktop screen and shrinking it down as an afterthought.
- Keep all real content available on mobile, not trimmed or hidden behind extra taps that most visitors won't take.
- Make sure interactive elements (the phone number, buttons, forms) are easy to tap with a thumb, not sized for a mouse cursor. See click-to-call: why your phone number belongs in the header for one specific, high-stakes example of this.
- Test real pages on a real phone, on a real cell connection, not just a resized browser window on a desktop, which behaves differently from an actual mobile device in ways that matter.
The speed connection
A phone-first site tends to be a faster site by necessity, since designing for a small screen and a variable connection naturally discourages the heavy, unnecessary elements that slow a page down. See core web vitals in plain English for the specific thresholds Google measures, and note that those thresholds are explicitly measured across mobile and desktop, with mobile performance carrying real weight in the result.
Questions
Does my site need a separate mobile version?
No, and building one separately from your main site is usually the wrong approach today. A single responsive design that adapts to any screen size, built with mobile as the starting point, is the standard, recommended approach.
How do I check what Google actually sees on mobile?
Google's PageSpeed Insights and the Rich Results Test both render and report on the mobile version of a page, which is a reasonable proxy for what Google's crawler is working with.
Is desktop design still worth attention?
Yes, but as an expansion of a solid mobile foundation rather than the starting point content gets trimmed down from.