Mobile-first indexing means Google primarily uses the mobile version of your website for crawling, indexing, and ranking. Since 2023 every site is indexed this way, so any content, structured data, or link that appears only on the desktop version is effectively invisible to Google.
What is Mobile-First Indexing?
Mobile-first indexing is Google's approach of using the mobile version of a website's content as the primary source for indexing and ranking, rather than the desktop version.
Google announced mobile-first indexing in 2016 and completed the transition for all websites by October 2023. There is no opt-out. If your mobile site is different from your desktop site. Missing content, different structure, fewer internal links. The mobile version is what Google evaluates.
Statcounter data shows that mobile devices account for 59% of global web traffic. Google's shift simply reflects how most people use the internet. Your desktop version is now the secondary experience, not the primary one.
Why Does Mobile-First Indexing Matter?
If your mobile experience is weaker than desktop, your rankings suffer across all devices.
- Content parity. Content hidden behind tabs, accordions, or "read more" buttons on mobile may not get full indexing weight
- Structured data , Schema markup present on desktop but missing on mobile gets ignored
- Internal linking. If your mobile navigation links to fewer pages, Google may not discover all your content
- Page speed. Mobile page speed directly impacts Core Web Vitals scores, which are confirmed ranking factors
Every SEO audit should start by viewing your site on mobile. That's what Google sees.
How Mobile-First Indexing Works
What Google Crawls
Googlebot uses a mobile user agent (Googlebot smartphone) as its primary crawler. It sees exactly what a mobile visitor sees. Same viewport, same CSS, same JavaScript rendering. If your mobile design hides content, Google may not index it.
Responsive vs. Separate Mobile Sites
Responsive design (one URL, one codebase, adapts to screen size) is Google's recommended approach. Sites with separate mobile URLs (m.example.com) need matching rel="canonical" and rel="alternate" annotations pointing at each other, or the two versions compete as duplicate content. Google recommends migrating to responsive design instead of maintaining the pair.
Common Mobile-First Issues
Lazy-loading images without proper markup, hamburger menus that block internal links from crawlers, smaller text that triggers mobile usability warnings, interstitials that cover content on mobile, and missing meta robots tags on mobile versions that exist on desktop.
Mobile-First Indexing Examples
Example 1: Hidden content loses rankings A B2B company hides their detailed product specs behind "Show More" buttons on mobile. Desktop users see everything. After mobile-first indexing, those spec-related keywords drop because Google only partially indexes the mobile version. Making the content visible by default on mobile restores rankings.
Example 2: A responsive redesign restores coverage A local trades business runs an old separate m.example.com mobile version carrying fewer pages and no blog. Under mobile-first indexing, the blog is effectively invisible: Googlebot crawls the mobile host, and those articles do not exist there. Rebuilding on responsive CSS puts every page back on one URL, and the previously stranded articles become eligible to rank again. The recovery is a coverage fix, not a ranking trick — nothing new was published.
How to check your site for mobile-first problems
The check takes about twenty minutes and needs no paid tool. Work through it in order, because each step depends on the one before it.
- Fetch the page as Googlebot smartphone. Use the URL Inspection tool in Google Search Console, then open the rendered HTML. This is the ground truth: whatever is missing here is missing from the index.
- Diff the text. Copy the visible text from the desktop page and the rendered mobile HTML into two files and compare them. Any paragraph that appears only on desktop is a paragraph Google is not ranking you for.
- Count the links. Open the mobile navigation and count the internal links. If the hamburger menu injects links only after a click and only via JavaScript, crawlers may never reach the pages behind it, which is how orphan pages appear after a redesign.
- Check the structured data on both. Schema markup that exists on desktop and not on mobile is ignored entirely. Run the Rich Results Test against the mobile rendering, not the desktop one.
- Compare the metadata. Titles, meta descriptions, canonical tags, and robots directives should be identical on both. A stray
noindexon a mobile template removes pages silently. - Measure mobile field data. Look at Core Web Vitals for the mobile segment in Search Console, not the lab score on your laptop. Real mobile devices on real networks are what the report uses.
- Check images and lazy loading. Images loaded only on scroll or only after user interaction may never render for the crawler. Native
loading="lazy"is safe; custom JavaScript loaders often are not.
Mobile-first indexing vs mobile-friendly vs responsive design
Three related terms that describe different things. Mobile-first indexing is Google's crawling and indexing behaviour — it is something Google does, not something you configure. Mobile-friendly describes whether a page is usable on a small screen: readable text, tappable targets, no horizontal scroll. Responsive design is one technical method for achieving mobile-friendliness, using a single URL that adapts by viewport width.
You can be mobile-friendly without being responsive, by serving a separate mobile site. You cannot opt out of mobile-first indexing either way. The distinction matters because fixing "mobile usability" warnings does nothing for content parity — a page can pass every usability check and still be missing half its text on mobile.
What it means for a small or local business
Most local search already happens on a phone, so for a local business mobile-first indexing is close to the whole game. The specific risks are narrower than they are for large sites, and easier to fix.
- Hidden service details. Collapsing your service list into an accordion on mobile is fine for usability. It is only a problem if the content is injected on click rather than present in the HTML — check the rendered source before assuming either way.
- Phone-number-only pages. A mobile template that strips the address and hours in favour of a call button removes exactly the text that supports your local SEO signals.
- Location pages behind a dropdown. If location pages are only reachable through a JavaScript selector, they may never be crawled. Link them in the footer as plain anchors.
- Interstitials. A full-screen offer popup on mobile can suppress rankings and blocks the content Google is trying to read.
- Slow hosting on mobile networks. A page that loads instantly on office wifi can time out on a phone in a basement. Field data, not lab data, is what counts here.
Common mistakes
- Auditing on a desktop browser at a narrow width. Resizing a desktop browser is not the same as a mobile user agent. Different CSS, different JavaScript, different result.
- Assuming "it looks fine" means "it indexes fine". Visual parity and HTML parity are separate questions.
- Serving different content to Googlebot to fix the problem. That is cloaking, and it converts an indexing issue into a manual action risk.
- Trimming the mobile version to make it faster. Removing text to improve speed removes the thing you rank with. Compress images and defer scripts instead.
- Forgetting the mobile template after a CMS migration. Migrations commonly drop schema and canonical tags from the mobile view while leaving desktop intact.
Tools and Resources
| Tool | Purpose | Price |
|---|---|---|
| Google Search Console | Search performance data | Free |
| Ahrefs | Backlinks, keywords, site audit | From $99/month |
| Semrush | All-in-one SEO platform | From $130/month |
| Screaming Frog | Technical crawl analysis | Free (500 URLs) |
| theStacc | Automated SEO content publishing | From $99/month |
Frequently Asked Questions
Do I still need a desktop version?
Yes. Mobile-first doesn't mean mobile-only. Google uses the mobile version for indexing but serves the appropriate version to users based on their device. A responsive design handles both automatically without maintaining separate versions.
How do I check if mobile-first indexing is active for my site?
Google Search Console shows which Googlebot agent (mobile or desktop) crawls your site under Settings > Crawl Stats. For all sites migrated after October 2023, mobile is the default. You can also check the URL Inspection tool. It shows the crawled version.
Does mobile page speed affect desktop rankings?
Under mobile-first indexing, yes. Google evaluates your mobile page speed as part of Core Web Vitals. Since mobile metrics are the primary ranking signal, poor mobile speed can hurt your rankings even when users search from desktop.
Is mobile-first indexing a ranking factor?
No. It is an indexing behaviour, not a ranking signal. Google does not score you on being mobile-first — every site is already indexed that way. What affects rankings is what the mobile version contains: if content, links, or structured data are missing there, you rank on less than you thought you had. Page experience signals are separate ranking inputs measured on that same mobile version.
Does content in tabs or accordions still get indexed?
Yes, provided the content is present in the HTML at load and only visually collapsed. Google has stated that content hidden for usability reasons is indexed normally. The problem case is different: content fetched by JavaScript only after a click never enters the rendered HTML, so it is not indexed at all. Check the rendered source to tell the two situations apart.
How do I fix a content mismatch between mobile and desktop?
Move to a single responsive template so there is only one version to keep in sync. If that is not possible immediately, bring the mobile version up to parity first — full body text, the same internal links, the same schema, the same metadata — rather than trimming desktop down. Parity upward preserves what already ranks; parity downward throws it away.
What about a site with no mobile version at all?
Google indexes the desktop version in that case, but the page will be judged on how it behaves on a phone, which usually means poor page experience metrics and a high bounce rate from the majority of real visitors. It is not a penalty so much as competing at a disadvantage against sites that render properly on the device most searchers are holding.
Want SEO content written and published to your site on a schedule? theStacc plans, writes, and publishes it for you. Sign up for free →
Sources
- Google Search Central: Mobile-First Indexing
- Google Blog: Mobile-First Indexing Complete
- Statcounter: Mobile vs Desktop Traffic
