Chapter 17 — Key Takeaways: Mobile SEO
A one-page field card. If you remember nothing else from this chapter, remember this.
The one big idea
Google reads your site as a phone. Mobile-first indexing means the mobile version of your page is what gets indexed and ranked. Content that lives only on the desktop layout is, for ranking purposes, invisible. So the whole game is: (1) don't hide your own content from the mobile crawler, and (2) don't repel the hurried human once they arrive on a small screen.
Core claims
- There is one index, built from the mobile version — not a separate "mobile index."
- Mobile-first indexing is a visibility prerequisite, not a big ranking boost. It decides what Google can see, not how much of a bump "mobile-friendliness" grants (that's modest).
- Responsive design wins because it makes content parity automatic — one URL, one HTML document.
- Responsive design does not by itself make you fast (Ch 16) or usable (§17.4). It's the floor.
- On mobile local search, the conversion is often a phone call, and the gap between interested and customer is one tap. Engineer for that tap.
- AMP is a faded requirement, not a live necessity. "You still need AMP" is a myth.
The mobile checklist (run this on any page)
| Check | Good | Where |
|---|---|---|
| Parity | Content, schema, images, links all in the mobile HTML | §17.3 |
| Viewport | <meta name="viewport" content="width=device-width, initial-scale=1"> present |
§17.4 |
| Tap targets | ~48px, ~8px apart; thumb-reliable | §17.4 |
| Text | Readable without zoom (~16px base) | §17.4 |
| Interstitials | No content-covering pop-up on mobile search arrival | §17.4 |
| Speed | Passes Core Web Vitals on mobile (the number that counts) | §17.5 / Ch 16 |
| Click-to-call | Phone number is a one-tap tel: link, visible without scrolling |
§17.6 |
Myths busted
| Myth | Reality |
|---|---|
| "There's a separate mobile index." | One index, built from the mobile version. |
| "Hidden accordion content is discounted on mobile." | Fine if it's in the mobile HTML (not JS-fetched after a tap). |
| "You still need AMP to rank." | No — Page Experience removed the Top Stories requirement; a fast responsive page competes. |
| "I'll just run the Mobile-Friendly Test." | Retired December 2023. Use Lighthouse (Chrome DevTools) instead. |
Key terms
Mobile-first indexing · responsive design · viewport · tap target · content parity · interstitial · AMP (Accelerated Mobile Pages) · click-to-call
Do this on your own site tomorrow
Open your homepage on your actual phone and try to call your business one-handed. If the number isn't
a single tap — if it's plain text or an image you have to copy — that is your highest-ROI fix, and it
takes minutes. Then view the page source and confirm the viewport tag is present. Two checks, huge
payoff.