---
title: "Mobile SEO: How Mobile-First Indexing Works | Aemorph"
url: https://aemorph.com/guides/mobile-seo/
description: "Mobile SEO explained: how Google indexes the mobile version of every site, what has to match desktop, pop-ups, AMP, retired tools and AI answers on phones."
schema_type: Article
publisher: Aemorph
publisher_entity: https://aemorph.com/entitymap.json#org_aemorph
language: en-SG
updated: 2026-10-29
---

Guides

# Mobile SEO: How Google Reads the Mobile Version of Your Site, and What to Fix First

**Mobile [SEO](https://aemorph.com/glossary/#seo-search-engine-optimisation) is the work of making the mobile version of a website complete, readable and fast, because Google crawls and indexes every site with its smartphone crawler, so the mobile page is the page that ranks and the page Google's AI answers read.** Since 5 July 2024, Google has crawled and indexed sites with Googlebot Smartphone only, and a site whose content is not accessible on a mobile device is no longer indexable. The sections below set out what mobile-first indexing checks, what has to match between mobile and desktop, how to test mobile pages now that Google's own mobile tools are retired, where pop-ups and AMP stand, and how the mobile page feeds AI answers and AI chats.

[See Aemorph's technical SEO service](https://aemorph.com/services/technical-seo/)

Written by [Kevin Dam](https://aemorph.com/about/), founder of Aemorph, who has practised SEO since 2010 and sits on the [Forbes Agency Council](https://councils.forbes.com/profile/Kevin-Dam-Global-Search-Architect-%7C-SEO-GEO-AEO-IMO-LLM-Visibility-Aemorph/4c8c7a38-1285-470d-8ea8-e517a310a00b). Aemorph is a [Google Partner](https://www.google.com/partners/agency?id=4441861842). [LinkedIn](https://www.linkedin.com/in/kevindam)

*Originally published 13 September 2024 in the SEO section of aemorph.com. Updated October 2026.*

---

## What Is Mobile SEO?

**Mobile SEO is the part of technical and on-page SEO that makes sure the page a phone receives carries the same content, links, structured data and metadata as the desktop page, loads quickly on a mobile connection and stays usable with one thumb.** A responsive template is the starting point, not the finish line. Plenty of responsive sites still load tab content only when a visitor taps, send phone-sized screens images built for a desktop monitor, or cover the page with a sign-up dialog, and every one of those faults sits in the version Google indexes.

| Area | What it covers | Why it matters for search | How to confirm | Deeper guide |
| --- | --- | --- | --- | --- |
| Content parity | The same text, headings and links on mobile and desktop | Content missing from the mobile page is missing from the index | URL Inspection live test in Search Console | [Technical SEO](https://aemorph.com/services/technical-seo/) |
| Metadata and markup | The same title, meta description, robots meta tags and structured data | A mismatch changes what Google indexes and shows | Page source of both versions compared | [Schema markup errors](https://aemorph.com/guides/schema-markup-errors-diagnostic/) |
| Layout | Viewport tag, readable text, tap targets sized for fingers | Without a viewport tag a phone renders the page at desktop width | Lighthouse and Chrome DevTools device mode | [On-page SEO audit](https://aemorph.com/guides/on-page-seo-audit/) |
| Speed | Core Web Vitals measured on mobile page loads | Google's thresholds are assessed separately for mobile | PageSpeed Insights field data | [Technical SEO](https://aemorph.com/services/technical-seo/), [Core Web Vitals](https://aemorph.com/guides/core-web-vitals/) |
| Images and video | The same image URLs and a stable video URL on both versions | Image URLs that differ by device cost image search traffic | Image URL comparison | [Image SEO](https://aemorph.com/guides/image-seo/) |
| Interruptions | Pop-ups, interstitials and full-screen dialogs | Full-page overlays block people and search engines from the content | The page loaded on a real phone | [On-page SEO audit](https://aemorph.com/guides/on-page-seo-audit/) |
| AI answers | An indexed mobile page that is eligible for a snippet | AI Overviews and AI Mode link to indexed pages | Search Console performance report | [AEO guide](https://aemorph.com/guides/aeo/) |

*Mobile SEO areas, checked against Google Search Central and Chrome documentation in October 2026.*

*[Sources: Google Search Central, December 2025 and others](https://aemorph.com/sources/#google-search-central-december-2025-and-others-mobile-seo)*

## How Does Mobile-First Indexing Work?

**Mobile-first indexing means Google crawls a page with its smartphone crawler, then indexes and ranks the content that mobile version returns, and from 5 July 2024 Google applies it to every site.** By June 2024 Google already crawled and indexed almost all websites with the smartphone crawler. On 3 June 2024 it set 5 July 2024 as the date the small set of sites still crawled with the desktop crawler moved to Googlebot Smartphone, and from that date content not accessible at all on a mobile device is no longer indexable. Googlebot Desktop still appears in server logs for a few features, such as product listings and Google for Jobs, so a desktop crawl in the logs is no sign that indexing has gone back to desktop. Aemorph's guide to [how search engines work](https://aemorph.com/guides/how-search-engines-work/) explains how Google crawls, renders, indexes and ranks pages.

Google describes three ways to serve a site to phones and recommends one of them:

| Configuration | What it serves | URLs | Google's position | What to watch |
| --- | --- | --- | --- | --- |
| Responsive design | The same HTML on the same URL to every device | One URL per page | Recommended, as the easiest pattern to implement and maintain | Primary content that loads only after a tap; text already in the page inside an accordion or tab is fine |
| Dynamic serving | Different HTML by device on the same URL | One URL per page | Listed as a configuration, not the recommended one | The mobile HTML dropping content the desktop HTML carries |
| Separate URLs | Different HTML on separate mobile and desktop URLs | Two URLs per page | Listed as a configuration, not the recommended one | Every mobile URL carrying the same content, metadata and structured data as its desktop pair |

*Mobile configurations from Google's mobile-first indexing best practices.*

### Does a desktop-only site still rank?

**A site whose content does not load on a mobile device is no longer indexable, so it has no pages in Google to rank.** A site that loads on phones but serves a thinner mobile page ranks on that thinner page, because the mobile page is the one Google indexes. Restoring the missing content on mobile, rather than adding more to desktop, is the fix.

*[Sources: Google Search Central blog, June 2024 and others](https://aemorph.com/sources/#google-search-central-blog-june-2024-and-others-mobile-seo)*

## What Has to Match Between Mobile and Desktop?

**The mobile page has to carry the same primary content, headings, structured data, title, meta description and robots meta tags as the desktop page, because the mobile version is the only version Google indexes.** Google's mobile-first indexing guidance lists each of these and adds rules for lazy loading, images and video. On a responsive site most of these match by design; the faults appear where a template, plugin or script treats phones differently.

| Check | Google's rule | Common fault | How to confirm | Fix |
| --- | --- | --- | --- | --- |
| Primary content | The mobile site contains the same content as the desktop site | Paragraphs trimmed on mobile to save space | Rendered text of both versions compared | Restore the text and save space with layout, not removal |
| Headings | The same clear and meaningful headings | Headings replaced by icons on small screens | Heading outlines of both versions compared | Keep the heading text on mobile |
| Structured data | The same structured data on both versions | Product or article markup missing from the mobile template | Rich Results Test on the mobile page | Add the same JSON-LD to the mobile template |
| Title and meta description | Equivalent across both versions | A separate mobile template writing shorter titles | Page source of both versions | Use one title and one description |
| Robots meta tags | The same robots meta tags on both versions | A noindex left on the mobile template | URL Inspection in Search Console | Match the tags on both versions |
| Lazy loading | Primary content not lazy-loaded on user interaction | Text that loads only after a tap, swipe or typed input | Rendered HTML in the URL Inspection live test | Load primary content without any interaction |
| Images | High quality images, with the same image URLs on both versions | Mobile image URLs that differ from desktop | Image URL comparison | Serve the same image URLs to every device |
| Video | Stable video URLs, placed where a phone visitor finds them | A video URL that changes on every page load | Two page loads compared | Keep one stable video URL |

*Parity checks from Google's mobile-first indexing best practices, last updated December 2025.*

*[Source: Google Search Central, December 2025](https://aemorph.com/sources/#google-search-central-december-2025-parity-mobile-seo)*

## How Do You Test Mobile Pages Now Google's Mobile Tools Are Retired?

**Google retired Search Console's Mobile Usability report, the Mobile-Friendly Test and the Mobile-Friendly Test API on 1 December 2023, so mobile testing now runs through URL Inspection, Lighthouse and Chrome DevTools.** Google stated that mobile usability remains critical for users and remains part of its page experience guidance; only the tools went. Chrome's Lighthouse was one of the resources Google named in their place.

| Test | Tool | What it shows | Pass mark | Source |
| --- | --- | --- | --- | --- |
| Rendered mobile page | Search Console URL Inspection, live test | The page as Google fetches and renders it | Primary content and links present in the rendered HTML | Search Console Help |
| Viewport | Lighthouse | Whether the page declares a viewport | `width=device-width, initial-scale=1` in the viewport meta tag | Chrome for Developers |
| Text size | Chrome DevTools device mode | Whether text reads without zooming | Lighthouse's former audit flagged pages where 40% or more of text was under 12 CSS pixels | Chrome for Developers |
| Tap targets | Chrome DevTools device mode | Whether buttons and links take a fingertip | At least 24 by 24 CSS pixels, WCAG 2.2 success criterion 2.5.8 (Level AA), with exceptions such as adequate spacing and inline links | W3C |
| Speed | PageSpeed Insights | Core Web Vitals field data for mobile loads | LCP within 2.5 seconds, INP 200 milliseconds or less, CLS 0.1 or less, at the 75th percentile | web.dev |

*Mobile tests that replace the retired Google tools, October 2026.*

Without a viewport meta tag, a phone renders the page at a typical desktop width and scales it down, which makes the text hard to read. Lighthouse 13 removed the font size audit, so the 12-pixel figure works as a reference point for a manual check. Core Web Vitals carry their own depth: Google assesses them at the 75th percentile of page loads, segmented across mobile and desktop, and Aemorph's [technical SEO](https://aemorph.com/services/technical-seo/) work covers the fixes.

*[Sources: Google Search Central blog, April 2023 and others](https://aemorph.com/sources/#google-search-central-blog-april-2023-and-others-mobile-seo)*

## Do Pop-Ups Hurt Mobile SEO?

**Google's guidance is to avoid interstitials that cover the whole page and to use banners that take up only a small fraction of the screen, because intrusive dialogs make content harder for people and search engines to reach, and Google links them to poor search performance.** Google also tells sites not to send visitors to a separate page for their consent or input. Interstitials that a site is required to show by law, such as an age gate on a casino site, are named as acceptable, and the same small banner containers serve other notices, such as a newsletter sign-up prompt.

| Pattern | Example | Google's guidance | Effect on a phone | Better option |
| --- | --- | --- | --- | --- |
| Full-page interstitial | A sign-up overlay that covers the article on arrival | Avoid obscuring the entire page | The visitor sees no content until they dismiss it | A banner along the top or bottom edge |
| Redirect to a consent page | A separate page that asks for input before the content | Avoid redirecting the user for consent or input | The content sits one step further away | An inline banner on the page itself |
| Legally required interstitial | An age gate on a gambling site | Named as acceptable | Shown because the law requires it | Keep it, and keep it to the legal requirement |
| Small banner | A strip that takes a small fraction of the screen | Recommended | Content stays readable from the first load | Reuse it for sign-ups and notices |

*Interstitial patterns from Google's guidance on intrusive interstitials and dialogs, last updated December 2025.*

### Is mobile-friendliness a ranking factor?

**Google names no single page experience signal: its core ranking systems look at a variety of signals that align with overall page experience, and mobile usability stays part of that guidance.** Google states that Core Web Vitals are used by its ranking systems, and that good results in its reports do not guarantee top rankings. A mobile-friendly page earns its place through the content Google indexes from it, with page experience as one consideration among many.

*[Sources: Google Search Central, December 2025 and others](https://aemorph.com/sources/#google-search-central-december-2025-and-others-popups-mobile-seo)*

## Is AMP Still Needed for Mobile SEO?

**AMP is optional: Google indexes AMP pages like other web pages, and since its April 2021 page experience announcement any page that meets Google News policies is eligible for the Top Stories carousel without the AMP format.** In the same announcement Google stopped showing the AMP badge in results, and its current AMP documentation states that AMP on desktop gets no search-specific features. All of Google's general best practices apply to AMP pages too, so AMP adds a second version of each page to maintain without a ranking advantage that Google documents. Aemorph's view is that a new site gets more from one fast responsive page per URL than from a parallel AMP build.

*[Sources: Google Search Central blog, April 2021 and others](https://aemorph.com/sources/#google-search-central-blog-april-2021-and-others-amp-mobile-seo)*

## How Does Mobile SEO Affect AI Search?

**Google indexes the mobile version of a page, so a complete mobile page is the version Google's AI Overviews and AI Mode draw on and link to, while ChatGPT, Claude and Perplexity reach pages through their own crawlers, each documented by its provider.** [GEO](https://aemorph.com/glossary/#geo-generative-engine-optimisation), getting a business cited inside the AI chats, leads the work: OpenAI reported more than 900 million weekly ChatGPT users in February 2026. OpenAI states that a site disallowing OAI-SearchBot is not shown in ChatGPT search answers, though it can still appear as a navigational link; Anthropic states that blocking Claude-SearchBot stops it indexing content for search and reduces a site's visibility in Claude's search results; and Perplexity uses PerplexityBot to surface and link sites in its search results. Fetches a user asks for follow other rules: OpenAI says robots.txt rules are not guaranteed to apply to ChatGPT-User, and Perplexity states that Perplexity-User generally ignores robots.txt. Each core fact written as one plain sentence in the page text gives a model something precise to quote, which is the basis of Aemorph's [GEO](https://aemorph.com/guides/geo/) work.

[AEO](https://aemorph.com/glossary/#aeo-answer-engine-optimisation) covers Google's own answer surfaces. Google states that a page appears as a supporting link in AI Overviews or AI Mode when it is indexed and eligible to be shown in Google Search with a snippet, with no additional technical requirements. Because indexing is mobile-first, content missing from the mobile page is missing from what these features draw on. Google reported that AI Mode passed 1 billion monthly active users in July 2026. The [AEO guide](https://aemorph.com/guides/aeo/) covers AI Overviews, AI Mode and featured snippets.

| Surface | Run by | How it reaches your page | What the page needs | Discipline |
| --- | --- | --- | --- | --- |
| ChatGPT search | OpenAI | OAI-SearchBot | OAI-SearchBot allowed in robots.txt; facts in plain page text | GEO |
| Claude | Anthropic | Claude-SearchBot | Claude-SearchBot allowed in robots.txt; facts in plain page text | GEO |
| Perplexity | Perplexity | PerplexityBot | PerplexityBot allowed in robots.txt; facts in plain page text | GEO |
| AI Overviews | Google | Google's mobile-first index | An indexed mobile page eligible for a snippet | AEO |
| AI Mode | Google | Google's mobile-first index, with related searches run across subtopics | An indexed mobile page eligible for a snippet | AEO |

*AI surfaces and the crawlers or indexes that feed them, October 2026.*

*[Sources: OpenAI and others, 2026](https://aemorph.com/sources/#openai-and-others-2026-mobile-seo)*

## Which Mobile SEO Advice Is Out of Date?

**Several mobile SEO tips still repeated online, including tips in earlier versions of this guide, rely on tools Google has retired or on claims that Google's documentation does not support.** Each one is checked below.

| Earlier advice | What the documentation says | Source | What to do instead | Status |
| --- | --- | --- | --- | --- |
| Check pages with Google's Mobile-Friendly Test | Google retired the test, its API and the Mobile Usability report on 1 December 2023 | Google Search Central blog | Use the URL Inspection live test and Lighthouse | Corrected |
| Mobile responsiveness is a key ranking factor | Google names no single page experience signal; core ranking systems look at a variety of signals | Google Search Central blog | Keep mobile content complete for indexing and fix usability for visitors | Corrected |
| AMP raises rankings and lifts impressions by 50% | Google indexes AMP pages like other pages; AMP stopped being required for Top Stories in 2021; the 50% figure carried no source | Google Search Central blog and AMP documentation | Build one fast responsive page per URL | Corrected |
| Use 12 to 16 point fonts on mobile | Google sets no font size rule; Lighthouse's former audit flagged pages where 40% or more of text was under 12 CSS pixels | Chrome for Developers | Set the viewport tag and test text at phone width | Corrected |
| Make pop-up close buttons bigger | Google's guidance is to avoid full-page interstitials and use small banners | Google Search Central | Replace full-page pop-ups with banners | Corrected |
| Optimise for SGE, the Search Generative Experience | Google's documentation describes AI Overviews and AI Mode, and requires an indexed page eligible for a snippet | Google Search Central, AI features | Make the mobile page complete, indexed and eligible for a snippet | Updated |
| Track mobile usability errors in Search Console | The Mobile Usability report was retired on 1 December 2023 | Google Search Central blog | Use Lighthouse and PageSpeed Insights for each template | Corrected |

*Advice from the 2024 and 2025 versions of this guide, checked against current documentation in October 2026.*

*[Sources: Google Search Central blog, April 2023 and others](https://aemorph.com/sources/#google-search-central-blog-april-2023-and-others-outdated-mobile-seo)*

## Fix the Mobile Page First

**A site whose mobile pages carry the full desktop content, metadata and structured data, render without any interaction, load fast on a phone and stay clear of full-page pop-ups gives Google one complete version to index, and that same version feeds Google's AI Overviews and AI Mode while leaving nothing hidden from the crawlers the AI chats send.** Aemorph's [technical SEO](https://aemorph.com/services/technical-seo/) audit checks mobile parity with Lighthouse, Screaming Frog and the Google and Bing webmaster tools. The [SEO checklist](https://aemorph.com/guides/seo-checklist/) runs the mobile check alongside the rest of an audit. Your developers make the fixes from Aemorph's specification, and Aemorph verifies them. Mobile work then runs inside the [LLM Influencer System](https://aemorph.com/glossary/#llm-influencer-system), where [GEO](https://aemorph.com/guides/geo/) carries the same facts into the AI chats. The result below comes from the same team and SEO discipline the entity-first method grew from:

> **Case study · Dental, Singapore**
>
> **Casa Dental grew organic traffic 94% in 10 months.**
>
> Monthly organic visits rose from 3,641 to 7,074 between March 2023 and January 2024, and keywords in Google's top three positions rose from 69 to 130. [Read the Casa Dental case study](https://aemorph.com/case-studies/casa-dental/)

*Organic search results, not AI citations. [Source: Ahrefs, August 2026](https://aemorph.com/sources/#ahrefs-august-2026-7385) [How results are measured](https://aemorph.com/case-studies/#every-case-study-records-visits-before-after-and-over-time)*

[Book a strategic conversation](https://aemorph.com/contact/)

THE STRATEGIC CONVERSATION

## Start with a free *strategic conversation*.

Every Aemorph engagement starts with a free strategic conversation. It is the fastest way to see whether Aemorph fits your business before you commit budget.

[Book a strategic conversation →](https://aemorph.com/contact/)

STARTING POINT

Free

You talk through your goals with Aemorph, and Aemorph quotes your engagement after the conversation.