Mobile-first indexing means that Google now crawls and ranks a website based on its mobile version rather than its desktop one. In practice, Googlebot visits your pages with a smartphone user agent, and whatever content, links and structured data it finds there is what gets evaluated in search results. Google started experimenting with this in 2016 and announced in late 2023 that it had moved virtually all sites to mobile crawling. The takeaway is simple: if your mobile version is incomplete, your rankings will be too.
What mobile-first indexing actually means
Historically, Google gathered content with a desktop Googlebot and treated the mobile experience as a secondary signal. Mobile-first flipped that relationship. Now the content that is indexed and ranked is the mobile version. Text you show on desktop but hide on mobile is effectively invisible to Google. One important nuance: this is not "mobile-only." There is a single index, and desktop users still receive results from it; that index is simply built from a mobile crawl.
For sites using responsive design, the transition is usually seamless because the same HTML is served to every device. The real risk lies with sites that maintain a separate mobile version (for example m.example.com) or serve different HTML depending on the device.
Content parity: the most critical rule
The most common mistake in a mobile-first world is "simplifying" the mobile version and trimming its content. Google's clear advice is content parity: the main content, headings, images and videos should be the same on mobile and desktop. In practice, check the following:
- Text: All body copy from desktop must also be present on mobile. "Read more" tabs and accordions are fine; as long as the content exists in the HTML, Google reads it.
- Images: The same images, with meaningful
alttext, must be present on mobile. Image search visibility depends on it. - Structured data: Schema.org markup should exist on both versions and reference the same URLs on mobile.
- Metadata: The
titleand meta description should be equivalent on the mobile version.
A technical checklist
To confirm your site is ready for mobile-first indexing, review these technical points:
- Viewport meta tag: It must be present in the
<head>of every page. - Blocked resources: Make sure CSS, JavaScript and images are not blocked from Googlebot in
robots.txt. If Google can't fully render the page, it sees incomplete content. - Readable text and tappable targets: No horizontal scrolling, and buttons that are comfortable to tap.
- Consistent links: Internal links and navigation must be complete on mobile too; links inside a "hamburger" menu are crawled as well.
A correctly configured viewport tag looks like this:
<meta name="viewport" content="width=device-width, initial-scale=1">If you use separate mobile URLs, reciprocal annotations are required to link the desktop and mobile versions. The desktop page uses alternate and the mobile page uses a canonical pointing back to desktop:
<!-- On the desktop page -->
<link rel="alternate" media="only screen and (max-width: 640px)"
href="https://m.example.com/page">
<!-- On the mobile page -->
<link rel="canonical" href="https://www.example.com/page">That said, the easiest approach to maintain — and the one Google recommends — is responsive design with a single URL, so you never have to manage a separate mobile version.
Core Web Vitals and page experience
Mobile-first indexing and performance cannot be separated, because the evaluation happens under mobile-device conditions. Google's Core Web Vitals come into play right here:
- LCP (Largest Contentful Paint): How fast the main content loads; aim for under 2.5 seconds.
- INP (Interaction to Next Paint): The interaction responsiveness metric that replaced FID in 2024; under 200 ms is good.
- CLS (Cumulative Layout Shift): A measure of visual shifting; aim for under 0.1.
These metrics don't directly decide rankings, but they are a differentiating signal between pages of equal quality and they measure user experience. Sizing images with width/height, loading fonts with font-display: swap, and reducing unnecessary JavaScript all yield concrete gains on mobile.
How to test and monitor
Verify the state with tools, not guesses:
- Google Search Console > URL Inspection: Shows which user agent Googlebot used to crawl the page and the rendered HTML. Compare the "tested page" output with your mobile view.
- PageSpeed Insights / Lighthouse: Use the mobile tab to see Core Web Vitals and rendering issues.
- Browser developer tools: Use device emulation (responsive mode) to check how the page behaves on a narrow screen.
Note: Google's old "Mobile-Friendly Test" tool was retired in December 2023; you now run the same analyses through Search Console and Lighthouse.
Frequently Asked Questions
Does my desktop version still matter?
Yes. Even though desktop users receive results from the mobile index, you should still offer them a good experience. But the content that determines rankings is the content you see on the mobile version, so keeping the two at content parity is the safest path.
Will I be penalized for hiding content in tabs or accordions on mobile?
No. Putting content into show/hide components to save space on a mobile screen is normal and not penalized; as long as the content exists in the HTML source, Google indexes it.
I already have responsive design — do I still need to do anything?
Usually no extra migration is needed, but it's still a good habit to verify the viewport tag, the absence of blocked resources, and your mobile Core Web Vitals scores.
Want a full review of your site's mobile performance and search visibility? We can work together on mobile-first compatibility, speed optimization and technical SEO. Get in touch and let's get your site ready for mobile search.