Mobile-first indexing means Google uses the mobile version of your pages, crawled by Googlebot Smartphone, for indexing and ranking. Google completed the migration on 31 October 2023 and moved the last holdout sites after 5 July 2024, so anything that exists only on desktop is not indexed. This guide covers how it works, where sites lose traffic, and which tool checks each fix.
In This Article
Share On:
Mobile-first indexing is not a change you’re still waiting on. It’s the only way Google indexes your site today, and has been since Google called the migration complete on 31 October 2023 and moved the last holdout sites to the mobile crawler after 5 July 2024. If it isn’t in your mobile HTML, Google doesn’t see it.
This guide covers what mobile-first indexing does, what Google Search Central says about it, where sites lose traffic, and which tool checks each fix. See also our note on mobile first indexing meaning and best practices.
What is mobile-first indexing?
Mobile-first indexing means Google uses the mobile version of your page, crawled by Googlebot Smartphone, as the version it indexes and ranks. Google Search Central states it directly: “Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.” There is 1 index, and it is built from mobile.
This is not mobile-only indexing. When Google announced the shift in November 2016, it said the search index “will continue to be a single index of websites and apps”. Desktop and mobile searchers get results from that index. What changed is which rendering of your page fills it.
What the mobile first index is not
Not a separate mobile index. One index serves both device types, populated from the mobile rendering.
Not the same as mobile-friendliness. Indexing is which version Google reads. Usability is how it behaves for people.
Not optional, and not upcoming. Google’s June 2024 post: “If your site’s content is not accessible at all with a mobile device, it will no longer be indexable.”
Is mobile-first indexing still optional in 2026?
No. On 31 October 2023 Google wrote that “the trek to Mobile First Indexing is now complete”. On 3 June 2024 it confirmed the last sites still crawled by desktop Googlebot would move after 5 July 2024. Any advice framing this as a project to plan for is out of date.
When the mobile first index rolled out
November 2016: Google starts mobile-first crawling, and confirms the index stays a single index.
March 2020: Google announces the switch for the whole web, noting 70% of sites in results had moved.
31 October 2023: Google calls the migration complete and turns off the indexing crawler line in Search Console settings.
5 July 2024: the remaining desktop-crawled sites move, and Google indexes them “with only Googlebot Smartphone”.
You will still see Googlebot Desktop in server logs. Google says it is “sometimes used when crawling for product listings and Google for Jobs”. Both crawlers answer to one robots.txt token, Googlebot, so you can’t allow one and block the other.
How does mobile-first indexing work?
Googlebot Smartphone requests your page with an Android mobile user agent, renders it, and stores that rendering. Content, links, structured data and metadata are read from the mobile HTML. Those signals then rank the page for mobile and desktop searchers alike, because both are served from the same index.
What Google reads from the mobile version
Primary content and headings
Internal and external links, and the equity they pass
Structured data (Breadcrumb, Product, VideoObject)
The title element and meta description
Images, videos and alt text
What that means in practice
If your desktop page carries 3,000 words and only 1,500 reach the mobile HTML, Google indexes 1,500. The guidance is plain: if your mobile site has less content, “consider updating your mobile site so that its primary content is equivalent to your desktop site.”
Accordions and tabs are fine. Google recommends them: “Instead of removing content, consider moving content into accordions or tabs to save space.” The failure mode isn’t collapsed content, it’s content that never reaches the mobile HTML, or that appears only after a swipe or tap. Google “won’t load content that requires user interactions”.
Markup has to ship on the mobile version too. Google’s troubleshooting list names a “Missing structured data error” for this exact case. If you’re auditing that, start with how schema markup works.
Mobile-first indexing vs desktop-first indexing
The only real difference is which rendering Google reads, and everything else follows from it. Desktop-first indexing is retired. Since 5 July 2024 Google crawls and indexes sites with Googlebot Smartphone only, keeping Googlebot Desktop for a small set of Search features.
Mobile first index vs desktop-first indexing (source: Google Search Central, 2023 and 2024)
Factor
Mobile-first (2026)
Desktop-first (legacy)
Primary crawler
Googlebot Smartphone
Googlebot Desktop
Content evaluated
The mobile rendering
The desktop rendering
Ranking basis
Content, links and metadata in the mobile HTML
The same, from the desktop HTML
Index
1 index, filled from the mobile version
1 index, filled from desktop
Structured data
Must be present on the mobile version
Could exist on desktop only
Status
Default for every site since 5 July 2024
Retired. Googlebot Desktop now serves only features such as product listings and Google for Jobs
Search Console
Crawl stats report shows your current crawler
Settings used to name your indexing crawler
Why the shift matters for your rankings
Because mobile is where the audience already is, and anything that exists on desktop alone is now invisible. Statcounter put mobile at 64.45% of web traffic in India in August 2026, against 49.36% worldwide. Your ranking signals come from the rendering most visitors already see.
That alignment is the benefit: a fast, complete mobile page is rewarded, and you stop maintaining 2 sets of signals. Google’s page experience guidance asks whether content displays well on mobile, whether pages avoid intrusive interstitials, and whether Core Web Vitals are good. Our Core Web Vitals fixes guide covers the usual causes.
3 ways sites still lose traffic to the mobile index
Nearly every loss traces to 1 pattern: something exists on desktop and never reaches the mobile HTML. The 3 cases below (specifications dropped from mobile markup, a legacy m-dot site, and dynamic serving that strips elements) cover most of what turns up in audits.
Example 1: specifications that load only on tap
Problem: an ecommerce site shows a full specification table on desktop, but on mobile a “View more” control loads it only after a tap. Google won’t tap, swipe or type to reveal content, so those specifications never reach the index.
Fix: put them in the mobile HTML that ships with the page. Collapsing them into an accordion is fine, and Google suggests exactly that. Managing display with CSS is safe. Loading on interaction is not.
Example 2: a legacy m-dot site with thinner content
Problem: a business still runs m.example.com next to http://www.example.com, and the mobile site has fewer pages, shorter copy and no markup. Only the mobile version is indexed, so that gap becomes the ceiling. Google also warns that when several desktop URLs redirect to one mobile URL, those pages go missing.
Fix: move to 1 responsive site. Until then, match error status codes, keep the desktop URL canonical with the mobile URL as its alternate, and pair hreflang mobile to mobile.
Example 3: dynamic serving that strips elements
Problem: a publisher serves different HTML by user agent on one URL. The desktop response carries author bios, related links and FAQ markup; the mobile response drops them for speed. Google indexes the mobile response, so all 3 are absent.
Fix: ship every search-critical element in the mobile response, then buy the speed back with efficient CSS and correct lazy loading.
Mobile-first indexing best practices
Run 1 responsive site, send the same content, markup and metadata to every device, and keep Googlebot Smartphone unblocked. Google recommends responsive design because it “serves the same HTML code on the same URL regardless of the users’ device”, which removes most parity problems.
Responsive design: 1 URL, 1 HTML source, layout handled by CSS
Equivalent primary content in the mobile HTML: text, images and video
Same structured data on both versions. If you have to sequence the work, Google says start with Breadcrumb, Product and VideoObject
Same title element and meta description on both versions
Same robots meta tags: no noindex or nofollow on the mobile page alone
Same headings and alt text, supported image formats, and stable image URLs
No primary content lazy-loaded on user interaction, and no CSS, JS or images disallowed in robots.txt
Mobile page speed: LCP within 2.5 seconds, INP of 200 ms or less, CLS of 0.1 or less, at the 75th percentile
No intrusive interstitials, and tap targets of at least 48 px by 48 px, spaced apart
Most of this is routine hygiene, so run it alongside our technical SEO checklist rather than as a separate project.
What to check, and which tool to check it with
Start in Search Console with URL Inspection and Crawl stats, then use Chrome Lighthouse for mobile usability. Google retired the Mobile-Friendly Test and the Mobile Usability report on 1 December 2023, so any guide still pointing you at search.google.com/test/mobile-friendly is stale.
Does the mobile rendering carry your content? Search Console URL Inspection. The rendered page and screenshot come from the mobile version.
Which crawler is visiting? Search Console, Settings, then Crawl stats, which Google points to now that the indexing crawler line is gone.
Is your markup on the mobile page? The Rich Results Test on the live URL, compared against your desktop response.
Is the page usable on a phone? Chrome Lighthouse, which Google’s page experience documentation names as the toolset covering “mobile usability”.
Are your mobile Core Web Vitals good? The Core Web Vitals report in Search Console, or PageSpeed Insights on the mobile tab.
Are resources blocked? Your robots.txt file, cross-checked against the page resources in URL Inspection.
Pick 1 template that already earns traffic, inspect it in Search Console, and compare the rendered mobile HTML with what you see on desktop. Missing content, links or markup is your ranking gap, and the fix is usually at template level.
upGrowth’s organic search marketing work covers mobile content parity, structured data coverage and Core Web Vitals. Contact us for an audit that names the gaps.
Mobile-first indexing FAQs
What is mobile first indexing in simple terms?
Google looks at the mobile version of your page to decide what it is about and how it ranks. Google Search Central puts it this way: Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking. Desktop-only content doesn’t count.
Is there a separate mobile index?
No. Google has kept 1 index throughout. When the shift was announced in November 2016, Google said the index would continue to be a single index of websites and apps. What changed is which rendering of your page fills it. Both device types are served from it.
When did the mobile first index roll out?
Google began mobile-first crawling in 2016 and announced the switch for the whole web in March 2020. It declared the migration complete on 31 October 2023, then said on 3 June 2024 that the last desktop-crawled sites would move after 5 July 2024, to Googlebot Smartphone only.
Does the mobile first index affect desktop rankings?
Yes. Because 1 index serves both device types, content, links or structured data missing from your mobile HTML contribute nothing on either device. A desktop searcher sees results built from your mobile rendering, which is why content parity beats any separate desktop optimisation.
What happens if my site has no mobile version?
Google’s June 2024 post is direct: if your site’s content is not accessible at all with a mobile device, it will no longer be indexable. A desktop-only site that still loads on a phone is crawled, but it competes against responsive pages on speed and usability, and usually loses.
How do I confirm Googlebot Smartphone is crawling my site?
Open Search Console, go to Settings, then the Crawl stats report, and read the breakdown by Googlebot type. Google directed site owners here after removing the indexing crawler line in October 2023. Server logs work too: those requests carry an Android user agent that names Googlebot.
Can I still use Google’s Mobile-Friendly Test?
No. Google retired the Mobile-Friendly Test and the Search Console Mobile Usability report on 1 December 2023. Use Chrome Lighthouse instead, which Google’s page experience documentation names as the toolset covering mobile usability, plus URL Inspection to see the rendered mobile version of a page.
For Curious Minds
Mobile-first indexing means Google exclusively uses the mobile version of your page, crawled by Googlebot Smartphone, to build its single search index. This version's content, links, and data determine your rankings for both mobile and desktop searchers. Your mobile site is the definitive source of truth for Google's index. If critical content exists only on your desktop page, it is completely invisible to the index and offers zero ranking value. This requires you to ensure your mobile experience is not just functional but also informationally complete. You must prioritize:
Content Parity: Your primary text, images with alt attributes, and videos must be identical on mobile and desktop.
Markup Consistency: All structured data, such as Product or Breadcrumb schema, must be present in the mobile HTML.
Link Structure: Navigational and contextual internal links must be the same to distribute page authority correctly.
As of Google's 5 July 2024 deadline, sites not accessible by a mobile device are no longer indexable at all. Discover the specific tools needed to audit each of these parity points in our complete guide.
The finalized shift makes a desktop-only site functionally obsolete for Google Search, as its content will not be indexed. Because Googlebot Smartphone is now the agent that populates the index, your mobile site is the only version that matters for ranking. A disparity between your desktop and mobile versions directly results in lost ranking signals. For example, if your desktop page has 3,000 words but the mobile HTML only contains 1,500, Google will only index and rank you based on those 1,500 words. This principle extends to all ranking factors, including structured data, internal links, and image metadata. Achieving success now hinges on perfect equivalence; your mobile version must contain all the content and markup you want to rank for. Any other approach risks significant traffic loss. Our full analysis provides a checklist for auditing this equivalence.
Mobile-first indexing and mobile-friendliness are related but distinct concepts that require separate validations. Mobile-first indexing is a technical requirement concerning which version of your site Google reads, while mobile-friendliness is a usability factor concerning how that version behaves for a human visitor. A site can be indexed via its mobile version but still offer a poor user experience. To satisfy both, you need to run specific checks:
For Indexing: Confirm that all content, links, and structured data are present in the mobile HTML. Use tools that show you the rendered DOM as seen by Googlebot Smartphone.
For Friendliness: Check for usability issues like tap targets being too close, text being too small to read, or the presence of intrusive interstitials.
Satisfying the crawler ensures your content is seen, while satisfying the user helps it rank better and convert visitors. Read our guide for a full breakdown of the tools that test for each of these distinct requirements.
This extended timeline reveals Google's methodical and deliberate shift to align its index with user behavior. The transition, starting in November 2016 and concluding after the 5 July 2024 deadline, shows a clear strategic direction away from the desktop-centric web. This was not a sudden change but a phased-in reality, giving webmasters years to adapt. The key milestones teach us important lessons for future strategy:
November 2016: The initial announcement signaled the future. This shows that Google telegraphs major changes years in advance.
March 2020: Announcing that 70% of sites had already moved demonstrated that the web was adapting, putting pressure on the remaining sites.
October 2023 & July 2024: The final deadlines show that patience runs out; what begins as a best practice eventually becomes a mandatory requirement.
Your strategy should involve monitoring Google's announcements for long-term trends and acting on them before they become urgent. The full article explores how to interpret these signals for what might come next.
The most damaging mistake is presenting a stripped-down or incomplete version of your content on mobile devices. This directly leads to traffic loss because if content is not in the mobile HTML, Google does not see it and cannot rank your page for related queries. Many sites lose rankings because valuable text, internal links, or structured data present on desktop are missing from the mobile render. Ensuring complete content parity is the direct solution. This means every piece of content you want to rank for must be present in the HTML that Googlebot Smartphone crawls. This includes:
The full body of your articles or product descriptions.
All images with their alt text.
All structured data, such as Product or Recipe schema.
The same set of internal and external links.
By making your mobile version a 1:1 match of your desktop version in substance, you close the gap that causes these ranking drops. Learn how to perform a content parity audit with the right tools in our detailed guide.
Seeing Googlebot Desktop in your logs is expected and does not mean your site is being indexed incorrectly. Google Search Central has confirmed that the desktop crawler is still used for specific, secondary purposes, even though indexing is handled by Googlebot Smartphone. Think of Googlebot Desktop as a specialist crawler, not the main indexing agent. You will see it when Google is crawling for:
Product listings for Google Shopping.
Information for Google for Jobs.
Other specialized vertical searches.
Your primary content for web search results is still being crawled and indexed exclusively by the smartphone agent. To confirm this, you should focus on the user-agent strings in your logs, looking for the majority of organic crawling activity to come from Googlebot Smartphone. Our complete guide explains how to filter server logs to isolate each crawler's activity.
A systematic audit is essential for an e-commerce site to ensure no ranking signals are lost in the mobile-first index. You should compare the rendered HTML of your mobile and desktop pages for critical ranking elements. A successful audit moves beyond visual checks to programmatic comparisons of the underlying code. Follow this three-step process:
Crawl Both Versions: Use a web crawler configured to use both the Googlebot Smartphone and Googlebot Desktop user-agents. Crawl a representative sample of your key pages, including category, product, and informational pages.
Extract Key Elements: From both crawls, extract and compare the word count, internal link counts, image alt text, and the full contents of your JSON-LD or microdata for Product schema.
Identify and Remediate Gaps: Create a spreadsheet to highlight discrepancies. Prioritize fixing pages where structured data or a significant amount of content is missing from the mobile version.
This process ensures that Google receives the same rich information from your mobile site that it previously did from desktop. Read our guide for specific tool recommendations to automate this audit.
Google correctly indexes content within accordions and tabs, provided it is included in the initial page HTML. The crawler sees all content present in the Document Object Model (DOM) upon page load, regardless of whether it is visible by default. The critical mistake to avoid is dynamically loading content into these elements only after a user interaction like a click or tap.Googlebot Smartphone does not perform these actions, so any content loaded this way will never be seen or indexed. To ensure your content is indexed, follow these rules:
Load All Content in HTML: The text, images, and links inside your tabs or accordions must be in the HTML source code sent from your server.
Use CSS for Visibility: Rely on CSS (e.g., `display: none;`) to manage the show/hide functionality, not on JavaScript that fetches content from an endpoint.
Test with URL Inspection Tool: Use the tool in Google Search Console to view the rendered HTML and confirm your 'hidden' content is present.
Following this approach allows for a clean user interface without sacrificing SEO value. Explore the full article for code examples that illustrate safe and unsafe implementations.
The continued use of Googlebot Desktop for specific verticals like product listings suggests a future of more specialized, purpose-driven crawling. It indicates that Google may use different renderers or crawlers best suited to extract specific types of structured information. This signals a move away from a one-size-fits-all crawling model toward a more efficient, segmented approach. For different content types, this could mean:
E-commerce Sites: Must continue to ensure their desktop product feeds and on-page structured data are flawless, as this content may be processed differently.
Informational Blogs: Will remain almost entirely dependent on Googlebot Smartphone, as their value lies in primary content rather than structured product data.
Job Boards: Similar to e-commerce, they will need to pay close attention to both crawlers to ensure visibility in specialized job search features.
This trend suggests your technical SEO strategy may need to account for multiple types of crawlers in the future. Our article explores how this evolution could reshape technical SEO.
The long-term implication is that mobile web development is now just web development. The concept of a separate 'mobile site' is obsolete, and responsive design is the baseline standard for performance and discoverability. Your digital strategy must treat the mobile experience as the primary and canonical user experience, not an adaptation. To stay ahead, businesses should:
Adopt a Mobile-First Design Philosophy: New features and designs should be conceived and built for mobile screens first, then scaled up to desktop.
Invest in Mobile Performance: Page speed and Core Web Vitals are evaluated based on the mobile experience. A slow mobile site is a slow site, period.
Unify Development Teams: Silos between 'desktop' and 'mobile' teams must be eliminated. There is only one site, and its mobile rendering is what Google indexes.
This shift permanently elevates the importance of mobile performance and usability from a secondary concern to the central pillar of your digital presence. Explore our guide for more on how to future-proof your development pipeline.
The 70% of sites that transitioned early likely shared a core characteristic: a modern, responsive web design. These sites were already built to provide a consistent experience across all devices, making the switch to mobile-first indexing a technical non-event for them. Their success was rooted in a proactive strategy of treating all users equally, which aligned perfectly with Google's direction. Common traits of these sites included:
Responsive Design: A single URL and HTML codebase that adapts to different screen sizes.
Content Parity by Default: No 'm-dot' subdomain with a separate, often limited, set of content.
Focus on Mobile Performance: They were likely already optimizing for mobile page speed and user experience.
We can infer that the holdouts were predominantly older sites with separate mobile URLs (m-dots) or those with dynamic serving where the mobile version had significantly less content. Their delay was a symptom of technical debt. Discover how to resolve this debt in our full analysis.
A site would fail this fundamental check if its server configuration or robots.txt file explicitly blocks mobile crawlers. This hard-line stance from Google means that certain outdated practices will now completely de-index a website. The most common cause is a misconfigured robots.txt file that disallows the Googlebot-Mobile user-agent. Other potential failure points include:
User-Agent Sniffing: Server-side logic that detects mobile user-agents and serves an error page or an empty response.
Separate Mobile Site Errors: A dedicated 'm-dot' site that is broken or incorrectly configured, preventing content from being served.
Incorrect Vary HTTP header: Misuse of this header can lead to caching issues that prevent the mobile version from being served to the crawler.
You can diagnose these issues using the URL Inspection Tool in Google Search Console. It allows you to test a live URL and see exactly how Googlebot Smartphone renders the page, revealing any blocking issues or errors. Our guide provides step-by-step instructions for using this tool effectively.
Amol has helped catalyse business growth with his strategic & data-driven methodologies. With a decade of experience in the field of marketing, he has donned multiple hats, from channel optimization, data analytics and creative brand positioning to growth engineering and sales.
Growth Strategy and Planning
Inbound Growth
Growth Hacking
Fractional CMO
Search Engine Optimization
Paid and Performance Marketing
Social Media Marketing
Demand Generation
AI-Driven Growth Strategy
AI-Native Workflow Automation
Generative Engine Optimization
Grove — AI Growth Strategist
AI Automation
Framework
Case Study
Tools
Growth Tools
Decision Tree
Compare
Custom GPT's
AI Answer Gap
Offer
Webstories
Quizzes
Blog
AI-powered Apps
Social Media Tools
Agency Fit Score
