Mobile-first indexing means Google uses the mobile version of your website to decide what goes into its index and how pages rank. If something only exists on your desktop site, Google may never see it.
The shift happened gradually over several years, and it is now simply how Google Search works. This guide explains what mobile-first indexing is, why it matters for SEO and AI search, and how to make sure your mobile pages give Google the full picture.
What is mobile-first indexing?
Mobile-first indexing is Google's practice of crawling and indexing pages primarily with its smartphone crawler, then using that mobile version of the content for ranking. Google's mobile-first indexing best practices describe it this way: the mobile version of a site's content, crawled with the smartphone agent, is what Google uses for indexing and ranking.
Before this change, Google mostly looked at desktop pages. As most searching moved to phones, that created a mismatch: people saw one version of a page, while Google evaluated another. Mobile-first indexing closes that gap.
The name can be misleading. It is not a separate mobile index, and it does not mean desktop users get different rankings. There is one index, and it is built from what the mobile crawler sees.
A short history and where things stand
Google began rolling out mobile-first indexing in 2018, made it the default for new domains in 2019 and kept moving sites over in the years that followed. In a June 2024 Search Central blog post, Google announced the final step: after July 5, 2024, the remaining sites would be crawled and indexed only with Googlebot Smartphone. As Search Engine Land reported, content that isn't accessible at all on a mobile device would then no longer be indexable.
Search Engine Land also reported that Google still occasionally uses its desktop crawler for specific cases such as product listings and Google for Jobs, so you may still see desktop Googlebot in your server logs. For nearly all purposes, though, the smartphone crawler is the one that counts.
Why mobile-first indexing matters
If your mobile pages hide or drop content, Google indexes less of your site. Google's documentation warns that a mobile version with less content can lead to some traffic loss, because Google gets less information from the page.
This also affects AI search. Google's AI features, such as AI Overviews, draw on pages that are indexed and eligible to appear in Search, according to Google's AI features guidance. If a key section of your page is missing on mobile, it is not in the index, and it cannot be used as a source.
How mobile-first indexing works
Three ways to serve mobile pages
Google recognizes three setups. Responsive design serves the same HTML at the same URL and adjusts the layout with CSS. Google recommends it because it is the easiest to implement and maintain. Dynamic serving uses the same URL but sends different HTML depending on the device. Separate URLs, often called m-dot sites (m.example.com), host the mobile version on a different address.
What Google compares
With dynamic serving and separate URLs, the mobile and desktop versions can drift apart. Google's guide asks for parity in the areas that matter most: primary content, headings, structured data, titles and meta descriptions, robots meta tags, images and alt text, and videos.
What Google cannot do
Googlebot does not click, swipe or type. Content that only loads after a user interaction, such as tapping "load more" or swiping a carousel, may never be seen. Resources blocked in robots.txt also cannot be fetched, which can stop Google from rendering the page properly.
Mobile-first indexing in practice
Imagine a generic software company running an older m-dot site. To keep phone pages light, the mobile template drops the comparison table, customer FAQ and product schema found on desktop. Under mobile-first indexing, Google sees the thinner mobile page, so the FAQ text and product details are effectively missing from the index.
The fix is not to remove content from mobile, but to restore it in a phone-friendly form. Collapsing the FAQ into an accordion and making the table scroll horizontally keeps the page usable on a small screen while giving Google the same information desktop visitors see. Longer term, moving to a responsive design removes the risk of the two versions drifting apart again.
Best practices for mobile-first indexing
- Use responsive design if you can. One URL and one set of HTML means content, metadata and structured data match automatically.
- Keep content equivalent. Use accordions or tabs to save space instead of cutting text. Keep the same headings on both versions.
- Match metadata and structured data. Titles, meta descriptions and schema markup should be equivalent, with mobile URLs used on the mobile version.
- Use the same robots meta tags. A stray noindex on the mobile version can remove pages from Search.
- Do not lazy-load primary content behind interactions. Load important text without requiring a click, swipe or typing.
- Let Google fetch resources. Do not block CSS, JavaScript or image files needed to render mobile pages.
- Keep images consistent. Use the same alt text, supported formats and stable image URLs.
- Test with Google's tools. The URL Inspection tool in Search Console shows how Googlebot Smartphone renders a page.
If you run separate URLs, Google lists extra steps: point the mobile page's canonical to the desktop page, make sure the mobile server can handle crawling, and verify both versions in Search Console.
Common misconceptions
- "There is a separate mobile index." There is one index. Mobile-first only changes which version Google reads.
- "Mobile-friendly is the same as mobile-first ready." A page can look fine on a phone and still be missing content that the desktop version has.
- "Hidden content in tabs is ignored." Google's guidance suggests accordions and tabs as a good way to fit content on mobile.
- "Desktop no longer matters." Desktop visitors still convert, and Google ranks pages for desktop searches too. It just reads the mobile version to do it.
How Butter approaches mobile-first indexing
At Butter, we check pages the way Google does, through the smartphone crawler. When we review a site, we compare what the mobile version shows against desktop, including content, headings, structured data and robots tags. On our GEO+SEO plan, mismatches like these fall under the technical SEO fixes we handle, alongside crawl issues and broken links. Our GEO plan includes schema markup guidance, which covers keeping structured data consistent on mobile. We cannot guarantee rankings, but we can make sure Google is not missing content you already wrote.
Frequently asked questions
Do I need a separate mobile website?
No. Google recommends responsive design, which uses one URL and one set of HTML for every device. Separate mobile sites still work but require more upkeep to keep content and signals consistent.
Will my site be removed if it is not mobile-friendly?
Sites whose content cannot be accessed at all on mobile became unindexable after July 5, 2024. A desktop-style layout that still loads on a phone can be indexed, though a poor mobile experience may hurt visitors and conversions.
How do I see what Google's mobile crawler sees?
Use the URL Inspection tool in Google Search Console, run a live test and view the tested page. It shows the rendered HTML and a screenshot from Googlebot Smartphone, so you can check that key content is present.