Mobile-first indexing and the impact on AI visibility
What is mobile-first indexing?
Since July 2024, Google exclusively uses the mobile version of websites for indexing and ranking. This means Googlebot only visits the mobile rendering of your page and the desktop version is no longer separately crawled. For websites that serve identical content to mobile and desktop users (responsive design), functionally little changes. For websites that show different content to mobile and desktop users, the consequences are significant.
The impact extends beyond Google Search. Because Googlebot provides the data also used by Gemini, the mobile version of your website indirectly also determines your visibility in Google's AI answers. Combined with the requirements other AI crawlers place on technical machine-readability, mobile-first indexing makes it essential to treat your mobile version as the primary version of your website.
Mobile-first indexing is not a preference, it is the only way Google indexes your website. If your mobile version is missing content that exists on the desktop version, that content is invisible to Google and to Gemini.
How mobile-first indexing affects AI visibility
The connection between mobile-first indexing and AI visibility runs through multiple channels.
Googlebot and Gemini
Googlebot exclusively crawls the mobile version and thereby feeds both Google Search and Gemini. If your mobile version contains less content (for example because tabs are collapsed by default, or because certain sections are omitted for mobile), Gemini misses that content. This has direct impact on whether and how you are cited in Gemini answers and Google AI Overviews.
Other AI crawlers
GPTBot, ClaudeBot and PerplexityBot are not bound by mobile-first indexing in the strict sense. They make their own requests and specify their own user-agent. Yet there is an indirect effect: if your website serves a different version to mobile users based on user-agent detection, some AI crawlers may receive the mobile version (if they are not recognized as desktop crawlers).
- Googlebot (mobile) determines your Gemini and Google AI Overviews visibility. Mobile content is everything.
- GPTBot and ClaudeBot typically receive the desktop version, unless your server does not recognize the user-agent and sends a mobile fallback.
- PerplexityBot fetches pages in real-time and can receive either the mobile or desktop version, depending on your server configuration.
- Responsive design eliminates this entire risk: every crawler receives the same HTML, regardless of user-agent.
Responsive design as the foundation
The most robust approach for both SEO and AI visibility is responsive design: a single HTML response that adapts via CSS to the screen size. With responsive design, there is no difference between the mobile and desktop version at the HTML level. Every crawler receives the same content, the same structured data and the same meta tags.
<!-- Responsive design basics -->\n<head>\n <meta name="viewport" content="width=device-width, initial-scale=1.0" />\n <style>\n /* Mobile-first: base is the mobile view */\n .article-content {\n padding: 1rem;\n font-size: 1rem;\n line-height: 1.6;\n }\n\n /* Desktop adjustments via media query */\n @media (min-width: 768px) {\n .article-content {\n padding: 2rem 4rem;\n font-size: 1.125rem;\n max-width: 75ch;\n margin: 0 auto;\n }\n }\n </style>\n</head>\n<body>\n <!-- Identical HTML for all devices and crawlers -->\n <article class="article-content">\n <h1>Article Title</h1>\n <p>Content that is identical for mobile and desktop.</p>\n </article>\n</body>Dive deeper: Schema.org markup for AI | Canonical URLs and duplicate prevention | HTTPS and HSTS as trust signals
Common mobile-first problems
Even with websites that use responsive design, problems regularly creep in that disadvantage the mobile version.
Hidden content on mobile
A common design choice is hiding content on mobile via CSS (display: none) or JavaScript (accordions, tabs that are collapsed by default). Google indicates that content in collapsed elements may receive less weight. For AI visibility, this is problematic: if crucial information is hidden by default on mobile, the mobile Googlebot may miss this content.
<!-- RISKY: content hidden on mobile -->\n<div class="desktop-only" style="display: none;">\n <h2>Detailed technical specifications</h2>\n <p>This content is invisible on mobile and possibly\n also for Googlebot mobile-first indexing.</p>\n</div>\n\n<!-- BETTER: content always in the DOM, visually adjusted -->\n<details>\n <summary>View technical specifications</summary>\n <div>\n <h2>Detailed technical specifications</h2>\n <p>This content is in the DOM and accessible\n to all crawlers, even when visually collapsed.</p>\n </div>\n</details>Missing structured data on mobile
Verify that your Schema.org markup is present in the mobile version of your page. With adaptive designs (where the server sends different HTML based on the device), it can happen that structured data is only included in the desktop version. With responsive design, this is not a risk, because the same HTML is used.
Mobile loading speed
The mobile version of your website is tested on an emulated mobile network (typically a mid-tier device on a 4G connection). Your Core Web Vitals are measured based on this mobile experience. A website that loads in 1 second on desktop but takes 5 seconds on mobile scores poorly in Google's assessment and therefore indirectly also in Gemini's source selection.
Checklist for mobile-first AI visibility
- Use responsive design so every crawler receives the same HTML, regardless of device or user-agent.
- Ensure all content visible on desktop is also present in the mobile HTML. Do not hide essential content with display: none.
- Verify that Schema.org JSON-LD, Open Graph tags and meta descriptions are identical on mobile and desktop.
- Optimize your Core Web Vitals for mobile. Test with the mobile mode of Google PageSpeed Insights.
- Avoid separate mobile URLs (m.example.com). Use a single domain with responsive design.
- Test your pages with the mobile Googlebot user-agent to verify that complete content is served.
- Ensure interactive elements (buttons, links, forms) are sufficiently large and easily reachable on mobile.
# Test whether the mobile version serves the same content as desktop
# Desktop user-agent
curl -s -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
https://example.com/blog/article | wc -l
# Mobile Googlebot user-agent
curl -s -A "Mozilla/5.0 (Linux; Android 6.0.1) AppleWebKit/537.36 \
(KHTML, like Gecko) Chrome/120.0.0.0 Mobile Safari/537.36 \
(compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \
https://example.com/blog/article | wc -l
# If the line counts differ significantly,
# your site serves different content to mobile crawlersAMP and AI visibility
Accelerated Mobile Pages (AMP) was once promoted as the standard for mobile web pages. Meanwhile, Google has removed the AMP advantage in search results. For AI visibility, AMP offers no specific benefit over well-optimized responsive pages. AMP pages have limitations in JavaScript and structure that can complicate implementation of certain Schema.org markup and interactive elements.
The recommendation is to invest in a fast, responsive website instead of AMP. The Core Web Vitals you achieve with that approach weigh more heavily for AI visibility than the AMP format.
Mobile-first is no longer a trend, it is the standard. Your mobile version IS your website in the eyes of Google and Gemini. Every byte of content missing on mobile does not exist for AI.
Key takeaways
- Google has exclusively indexed the mobile version of your website since July 2024. This version also determines your Gemini visibility.
- Responsive design is the most robust approach: every crawler receives the same HTML, regardless of device or user-agent.
- Content hidden on mobile (display: none, collapsed accordions) may receive less weight in indexing and AI citations.
- Schema.org markup, Open Graph tags and meta descriptions must be identical on mobile and desktop.
- Optimize Core Web Vitals specifically for mobile, as this is the measurement point for Google and indirectly for Gemini.
Frequently asked questions
Does mobile-first indexing apply to AI crawlers outside Google?
Mobile-first indexing is a specific Google policy. GPTBot, ClaudeBot and PerplexityBot do not follow a mobile-first policy. They make their own HTTP requests and receive the response your server returns for their user-agent. If your website is responsive, this does not matter: all crawlers receive the same content. If your website serves different versions based on user-agent, the difference can be relevant.
How do I check if my mobile and desktop versions are identical?
The simplest method is to request the same page with a mobile and desktop user-agent via curl, and compare the output. Specifically check for the presence of headings, paragraphs, Schema.org markup and meta tags. Google Search Console also offers a URL inspection tool that shows the mobile rendered version.
Should I migrate my m.example.com subdomain?
Yes, that is strongly recommended. Separate mobile subdomains introduce complexity (hreflang, canonical, redirect chains) and dilute your domain authority. Migrate to a responsive design on your main domain. Google itself recommends responsive design as the preferred configuration for mobile-first indexing.
How heavily do mobile Core Web Vitals weigh for AI citations?
Mobile Core Web Vitals affect your AI visibility through two routes. First, they determine your Google ranking, which indirectly influences your visibility in Gemini. Second, slow mobile pages limit the effectiveness of every crawler (not just Googlebot) in fetching your content. A website with good mobile Core Web Vitals is crawled more efficiently and delivers better data to AI models.
Are progressive web apps (PWAs) suitable for AI visibility?
PWAs are suitable for AI visibility, provided they use server-side rendering for their content. A PWA that operates as an SPA and loads all content via JavaScript has the same problems as any other SPA. A PWA that serves server-side rendered HTML and then enhances with service workers and offline functionality is excellently suited. The PWA aspect (manifest, service worker, offline) has no direct influence on AI crawling.
The mobile version of your website is no longer a derivative of your desktop site. It is the original. Design, build and optimize with mobile as the primary focus, and AI visibility will follow naturally.
How does your website score on AI readiness?
Get your AEO score within 30 seconds and discover what you can improve.
