
Google mobile-first indexing is the change that made Google use the mobile version of a page, instead of the desktop version, for indexing and ranking. After about 18 months of experiments, the broad rollout began on 26 March 2018, and Google declared the transition complete in October 2023. It was never a ranking boost: it changed which version of your page Google reads, so sites whose mobile pages were missing content lost out.
See how it fits with other changes in my full list of Google algorithm updates.
| Detail | Information |
|---|---|
| Update name | Mobile-first indexing |
| Type | Mobile (indexing change) |
| Rollout started | 26 March 2018 (broad rollout; experiments from November 2016) |
| Rollout finished | Google declared the transition complete in October 2023 |
| Rollout length | More than five years, site by site |
| Confirmed by Google | Yes, announced on the Google Search Central blog |
| Official source | Google Search Central Blog: Rolling out mobile-first indexing |
What mobile-first indexing changed
Google put it plainly: "Mobile-first indexing means that we’ll use the mobile version of the page for indexing and ranking." Before this, Google mostly crawled and evaluated the desktop page, even when the searcher was on a phone.
Three points are often misunderstood:
- There is still one index. Google did not create a separate mobile index. Only the version of the page it crawls and indexes changed.
- It is not a ranking boost. Mobile-friendly pages did not jump up because of it. What changed is that anything missing from your mobile page effectively became invisible to Google.
- Crawling shifted to Smartphone Googlebot. Migrated sites saw a significantly increased crawl rate from Smartphone Googlebot, which is often the first sign in server logs.
Timeline
| Date | Milestone | Notes |
|---|---|---|
| 4 November 2016 | Experiments announced | Google: "we’ve begun experiments to make our index mobile-first." |
| 26 March 2018 | Broad rollout begins | Google starts migrating sites that follow mobile-first best practices and notifies them in Search Console. |
| October 2023 | Transition complete | Google declares mobile-first indexing complete for the web. |
Who was affected
Sites with responsive design, where the same HTML is served to every device, were largely unaffected. The sites at risk were those whose mobile versions had less than their desktop versions:
- Separate m-dot sites (m.example.com) with shortened articles or missing sections.
- Dynamic serving setups that dropped structured data, reviews or related links on mobile.
- Mobile templates without the same title tags, meta descriptions or hreflang annotations.
- Sites blocking CSS, JavaScript or images from Googlebot in robots.txt, so the smartphone crawler could not render the page properly.
A typical example: an ecommerce site that hid product descriptions and specification tables on mobile to keep the page short. Once Google indexed the mobile version, that text no longer helped the product pages rank.
How to tell if mobile-first indexing hit your site
Unlike most updates, there was no single date to compare against. Each site moved when Google migrated it, so diagnosis starts with finding your own migration date.
- Find your switch date. Google sent migration notices in Search Console. Server logs showing a jump in Smartphone Googlebot requests also mark the change.
- Compare around that date, not around 26 March 2018. Look at the two weeks before and after your own migration.
- Diff mobile and desktop. Load key pages in both versions and compare main content, headings, internal links, images and alt text, structured data and metadata.
- Test rendering as Google sees it. Use the URL Inspection tool in Search Console to view the crawled page and check blocked resources.
- Look at structured data reports. A drop in valid items after migration is a strong sign that mobile pages lack the markup.
How to recover from mobile-first indexing problems
This is the most fixable change on this list, because the cause is concrete: Google is reading a weaker version of your page. Make the mobile version complete and the problem goes away as Google recrawls.
| Problem | Fix |
|---|---|
| Mobile pages have less text or fewer sections | Serve the same primary content on mobile. Use accordions or tabs for layout if needed, but keep the content in the page. |
| Structured data missing on mobile | Add the same structured data to mobile pages, with matching URLs. |
| Different titles or meta descriptions | Use equivalent metadata on both versions. |
| Resources blocked in robots.txt | Allow Googlebot to crawl CSS, JavaScript and images. |
| Images missing or lazy-loaded so Google cannot see them | Make images crawlable, with the same alt text as desktop. |
| Separate m-dot site kept out of step | Move to responsive design where possible; it removes most of these issues at once. |
If you run a separate mobile site or a heavy JavaScript front end, this is technical work best done with a crawl comparison of both versions. My technical SEO services include that comparison, and a move to responsive design is often part of an SEO-friendly web design project.
Is it still relevant today?
Completely. Mobile-first indexing is now the default for the whole web, and Google declared the transition complete in October 2023. Every page you publish is judged on its mobile version. If something matters for ranking, such as copy, links, structured data or images, it must be on the mobile page.
Frequently asked questions
When did mobile-first indexing start?
Google announced experiments on 4 November 2016 and began the broad rollout on 26 March 2018. It declared the transition complete in October 2023.
Is mobile-first indexing a ranking factor?
No. It changes which version of the page Google indexes and ranks. It is not a ranking boost for mobile-friendly pages.
Does Google have a separate mobile index?
No. Google keeps a single index. Only the version of the page it uses changed.
Is content hidden in accordions on mobile still indexed?
Content that is in the mobile page’s HTML, even inside tabs or accordions, can be indexed. Content removed from the mobile version cannot.
Sources
- Google Search Central Blog: Rolling out mobile-first indexing
- Search Engine Land: Google begins rolling out mobile-first index
- Keywords Everywhere: Mobile-first indexing
- Ignite Visibility: Google update history
If you suspect your mobile pages are telling Google less than your desktop pages, request a free audit. My SEO audit compares both versions page by page and lists exactly what is missing.
More Google algorithm updates
- Previous update: March 2018 Core Update (8 Mar 2018)
- Next update: April 2018 Core Update (16 Apr 2018)
Other mobile updates:
- Mobile-Friendly Update (Mobilegeddon) (21 Apr 2015)
