Here’s a question worth sitting with for a second: when Google evaluates your website, which version does it actually look at?
If you said “the desktop version,” you’re behind by about seven years. Google officially completed its move to mobile-first indexing in 2023, meaning the mobile version of your site is now the version that matters most for crawling, indexing, and ranking. The desktop version has been demoted to a secondary concern.
For a lot of website owners, that’s either reassuring news or quietly terrifying, depending on what their mobile site actually looks like.
What Mobile-First Indexing Actually Means
Let’s be clear about what this is and isn’t, because the name trips people up.
Mobile-first indexing doesn’t mean Google only shows your site to mobile users. It doesn’t mean you need a separate mobile website. And it doesn’t mean desktop rankings don’t matter anymore.
What it means is this: when Googlebot crawls your site to understand what it’s about and decide how to rank it, it’s now crawling as a mobile user, not a desktop user. It’s requesting your pages the way a smartphone browser would. It’s evaluating the content visible on mobile screen sizes. It’s the mobile experience that informs Google’s understanding of your site and that understanding is then used to determine rankings for everyone, including desktop searchers.
So if your desktop site has a full, rich article with detailed content and helpful images, but your mobile site collapses that same page into a stripped-down version with half the text hidden behind tabs or not loaded at all, Google is judging you by the stripped-down version. Even for people searching on a laptop.
That’s the part that catches people out.
Why Google Made This Shift
This didn’t happen arbitrarily. The shift to mobile-first indexing was a direct response to how people actually use the internet.
For years, the majority of Google searches have been happening on mobile devices. By the time Google began rolling out mobile-first indexing in 2016, it was already clear that desktop-centric crawling was producing rankings based on a version of websites that fewer and fewer people were actually using. A page could rank brilliantly while delivering a frustrating mobile experience to the majority of its actual visitors.
The change was designed to close that gap. If Google’s job is to connect searchers with the most helpful results, evaluating the experience that most searchers actually get makes more sense than evaluating an experience that’s increasingly secondary.
The Old World vs. The New One
To really understand why mobile-first indexing matters for your site specifically, it helps to understand what changed.
Before mobile-first indexing: Googlebot crawled both desktop and mobile versions of your pages, but the desktop version was the primary source of information for indexing and ranking. Your desktop content, links, and metadata were what Google used to understand your site. Mobile was evaluated separately, largely for mobile-specific ranking signals.
After mobile-first indexing: Googlebot crawls your site using a smartphone user agent (specifically Googlebot Smartphone). This is the version it reads, stores in its index, and uses to determine ranking. Your mobile content, links, structured data, and metadata are now what Google bases its understanding on.
The practical implication: anything that exists only on your desktop site, content, links, images, structured data, is essentially invisible to Google now. If it’s not present and accessible on mobile, Google mostly doesn’t know about it.
Responsive Design: The Cleanest Solution
There are technically a few different ways to handle mobile versus desktop versions of a website, and they’re not all equal under mobile-first indexing.
Responsive design is where one set of URLs serves all devices, with the layout adapting automatically based on screen size through CSS. This is the approach Google explicitly recommends, and for good reason: with responsive design, the same content exists at the same URL regardless of whether someone visits on a phone or a laptop. There’s no separate mobile site to maintain. Google sees exactly what users see, regardless of device. From an indexing perspective, it’s the simplest and cleanest setup.
Dynamic serving is where the same URLs are used but different HTML is delivered to mobile vs. desktop based on the browser’s user agent. This can work fine, but it requires careful implementation. If the mobile HTML version leaves out content, structured data, or links that exist on the desktop version, those omissions now hurt your rankings.
Separate mobile URLs (like m.yoursite.com) are the most complex setup under mobile-first indexing. With this approach, you’re maintaining two completely separate sites. Google will crawl the mobile version as primary, so any content discrepancies between the two are a real issue. If this is your current setup, it’s not necessarily broken, but it requires more careful maintenance to make sure both versions stay in sync.
For anyone building a new site or considering a redesign, responsive design is the obvious starting point.
What Google Is Actually Evaluating on Mobile
This is where things get specific, and where most sites that have “mobile issues” actually have them.
Content Parity
The content visible on your mobile pages should match the content on your desktop pages. This doesn’t mean pixel-for-pixel identical layouts mobile design naturally looks different. But the actual text, the important headings, the product descriptions, the key information that all needs to be present and accessible on mobile.
Content hidden behind tabs or accordions is a slightly nuanced area. Google has generally said it can access and index content that’s hidden in tabs or collapsible sections, as long as the HTML is there in the source code. But content that only loads through user interaction, or only loads on desktop, or is blocked for mobile users that’s genuinely at risk of not being indexed.
Internal Links
The links on your mobile pages are the ones Google follows to discover and understand your site structure. If your mobile navigation is simplified to the point where certain important pages aren’t linked to, Google may have a harder time finding and prioritising those pages.
Structured Data
If you use schema markup to help Google understand specific information about your content — product details, reviews, article metadata, FAQ sections that structured data needs to be present on the mobile version of the page, not just the desktop version.
Images
Mobile-first indexing means Google is also encountering your images through a mobile context. Images should be crawlable (not blocked in robots.txt), should have descriptive alt text, and should actually load on mobile rather than being lazy-loaded in a way that breaks for crawlers.
Page Speed and Core Web Vitals
This one ties directly into how Google measures experience. Core Web Vitals which look at loading speed, interactivity, and visual stability are evaluated for mobile specifically. A page that loads quickly on a desktop connection but is slow to paint on a mobile connection, or has layout elements that jump around as it loads on a small screen, is a page that will struggle to perform well.
Common Mobile-First Indexing Problems
These show up regularly, even on professionally built sites.
Mobile content is thinner than desktop content. Somewhere in the design process, the decision was made to show less text on mobile to keep the layout clean. The result is a mobile page that covers the topic less thoroughly than the desktop version and that’s the version Google is now using to evaluate your site’s depth and usefulness.
Mobile navigation doesn’t link to important pages. Desktop navigation menus often have more options than their mobile equivalents. If certain pages are reachable through the desktop menu but not the mobile hamburger menu, Google’s mobile crawler may discover those pages less reliably.
Images aren’t loading properly on mobile. Sometimes images that display fine on desktop fail to load correctly on mobile due to lazy loading implementations that crawlers can’t trigger, or responsive image configurations that deliver broken sources to certain screen sizes.
Structured data is only on the desktop version. If structured data was added to desktop templates but the mobile templates were built separately (common in older sites), the mobile pages may be missing schema markup that Google is now looking for.
Interstitials blocking content on mobile. A full-page popup that’s easy to dismiss on desktop can be practically unavoidable on mobile. Google has explicitly said intrusive interstitials on mobile are a negative signal, and they’re evaluated through the mobile crawl.
Different canonical tags on mobile vs. desktop. If you’re running separate mobile URLs and the canonical tags are misconfigured pointing to the wrong version or inconsistently set Google can get confused about which page is the authoritative one.
How to Check Your Mobile Status
Google Search Console is the most direct way to monitor how Google sees your mobile site. The URL Inspection tool lets you check any individual URL and see what Google rendered when it last crawled it, including a screenshot of what the page looked like to Googlebot. If the rendered screenshot looks broken, content-poor, or completely different from what a user would see, that’s a problem worth investigating.
The Coverage report in Search Console will also flag mobile usability issues when they’re detected at scale across your site.
Google’s PageSpeed Insights (pagespeed.web.dev) gives you a mobile-specific performance score alongside Core Web Vitals metrics. The mobile tab is the one that matters most for this purpose. It’ll show you exactly where your mobile performance is falling short and what’s causing the slowdown.
Manually browse your own site on a phone. This sounds obvious but genuinely gets skipped. Open your site on a real smartphone not a browser with a reduced window and actually click through the pages you care most about. Is everything readable without zooming? Do all the links and buttons work with a thumb? Does the page feel slow? Does any content appear missing compared to what you’d see on a desktop? Your own experience as a mobile user is a perfectly valid first diagnostic.
Responsive Design Best Practices Worth Following
If you’re confident your site is responsive but want to make sure it’s genuinely well-optimised for mobile-first indexing:
Keep content consistent across all screen sizes. Resist the temptation to hide “extra” content on mobile for design tidiness. If the content matters enough to be on the page, it matters on mobile too.
Use legible font sizes without requiring zoom. Google’s mobile usability guidelines suggest body text should be at least 16px. Text that forces pinching and zooming is both a poor user experience and a mobile usability issue.
Make tap targets appropriately sized. Buttons and links need to be large enough and spaced far enough apart that they can be tapped with a finger without accidentally hitting something adjacent. Tiny, tightly packed links are a common mobile usability flag.
Avoid content that relies on hover states. Hover interactions don’t exist on touchscreens. Navigation dropdowns or content previews that only activate on hover are invisible to mobile users.
Test actual load time on mobile connections, not just WiFi. A page that loads fast on a desktop over a fast connection can be noticeably slower on a phone on a middling mobile data connection. Tools like PageSpeed Insights simulate a slower connection by default, which is why scores sometimes look worse than expected.
Don’t block resources in robots.txt. CSS and JavaScript files tell the browser how to render your page. If those are blocked, your mobile site may look completely different to Googlebot than it does to real users which means Google is indexing a broken version of your page.
The Bottom Line
Mobile-first indexing has been complete for a while now. It’s not a coming change or something to prepare for. It’s the current reality. Google is looking at the mobile version of your site, full stop.
For most sites built in the last few years on any modern platform with a responsive theme, this isn’t an emergency. The fundamentals are already in place. What’s worth doing is a periodic, honest look at how your site actually performs on a real phone, whether your most important content is fully accessible on mobile, and whether your page speed on mobile is where it needs to be.
The gap between “technically mobile-friendly” and “genuinely great on mobile” is where the real ranking opportunity sits because a lot of sites cleared the first bar but not the second.