Mobile-First Indexing
Google indexes and ranks from the mobile version of a site’s content, crawled with its smartphone agent. A mobile version is not required but very strongly recommended.
Reviewed by Alexander Yarovenko · Updated: 2026-10-08
Mobile-first indexing means that Google uses the mobile version of a site’s content, crawled with its smartphone agent, for indexing and ranking. Having a mobile version is not required for content to be included in results, but Google very strongly recommends it. In practice the question is simple: whatever your mobile pages do not contain or let Google load, Google may not see, even if the desktop version shows it.
What it is and where the boundary lies
The change concerns which version Google reads, not how people see your pages. For a responsive site that serves the same HTML on the same URL, there is almost nothing to do: content and metadata are the same on every device. The guidance matters for the other two configurations. Dynamic serving uses one URL but sends different HTML by device, and separate URLs, often called m-dot, serve different HTML on different addresses. In both, the mobile version is the one that feeds the index.
How it differs from similar terms
| Term | What it is | Relation to mobile-first indexing |
|---|---|---|
| Mobile-first indexing | Google indexes from the mobile version | the subject here |
| Mobile SEO | making a site work well for mobile users and search | the wider practice |
| Page experience | how a visit feels to the user | related to quality, not to which version is indexed |
| Indexability | whether a page can be put in the index | needs to hold for the mobile version |
| JavaScript SEO | making script-rendered content visible to Google | matters for content hidden behind interaction |
Why it matters
Google states the consequence directly. If the mobile page has less content than the desktop page, you can expect some traffic loss when your site is enabled for mobile-first indexing, because Google cannot get as much information from the page as before. Having the same content on both versions ensures that the two can rank for the same keywords. Design can differ: Google suggests moving content into accordions or tabs rather than removing it.
What to check
- Same content. The primary content on mobile should be equivalent to desktop, with the same headings.
- Same robots meta tags. A different noindex or nofollow on the mobile page can stop Google from crawling and indexing it.
- No content that needs interaction to load. Google does not load content that requires swiping, clicking or typing, so lazy-loaded primary content must appear without it.
- Resources not blocked. If images, scripts or styles have separate mobile URLs, do not disallow them in robots.txt.
- Same structured data and metadata. Title, meta description and structured data should be equivalent, with correct mobile URLs where they appear.
- Same images and alt text. Use the same alt text, and keep image and video URLs stable instead of changing on every load.
- For separate URLs. Return the same error status on both, avoid URL fragments on the mobile version, give every desktop page an equivalent mobile page and verify both versions in Search Console.
Practical example
| Difference | Why it matters |
|---|---|
| Specification table only on desktop | Google indexes the mobile version, so the table is not seen |
| Reviews load only after a tap on mobile | Google does not load content that needs a click |
| Breadcrumb markup only on desktop | structured data should be on both versions |
| Product text moved into tabs on mobile | fine, as long as the content is present and equivalent |
The examples apply the guidance’s rules to common cases.
Common mistakes
- A shorter mobile page: Google says to expect some traffic loss when mobile has less content.
- Different robots tags on mobile: a noindex only on mobile can keep a page out of the index.
- Hiding primary content behind an interaction: Google does not swipe, click or type to reveal it.
- Blocking mobile resources: resources on separate mobile URLs need to be crawlable.
- Forgetting to verify the mobile site: with separate URLs, verify both versions to see their data and messages.
How to validate the result
Use the URL Inspection tool on a key page and open the crawled page to see what the smartphone Googlebot received, including HTML and resources. Compare it with what you expect on desktop. Compare equal periods of clicks and impressions in Search Console after any change, with the same filters.
More questions
Do I need a separate mobile site?
No. Google recommends responsive design as the easiest pattern to implement and maintain.
Does a desktop-only site get indexed?
Google says a mobile version is not required for content to be included, but it is very strongly recommended.
Can I use tabs and accordions on mobile?
Yes. Google suggests them to save space, provided the content is equivalent to the desktop version.
Next practical step
Pick your five most important pages, inspect each in URL Inspection and compare the crawled page with the desktop version. Fix any missing content first. See also mobile SEO.
Related concepts
- Mobile SEO — the wider practice.
- Indexability — whether a page can be indexed.
- Structured data — markup that should match on both versions.
- JavaScript SEO — content that needs scripts to appear.
- Page experience — how the visit feels.