Chapter 17 — Further Reading: Mobile SEO

Sources are grouped by the book's three evidence tiers (see Chapter 2 and the style bible). Tier 1 is canonical and can be relied on; Tier 2 is credible but treat specifics with care; Tier 3 is this book's own constructed teaching material. Start with Google's own documentation — on mobile, it is unusually clear and current.

Tier 1 — Verified canonical (start here)

  • Google Search Central — "Mobile-first indexing best practices." The primary source for this whole chapter: what mobile-first indexing is, the content-parity checklist (content, structured data, images, metadata, hreflang), and the common mistakes. If you read one thing, read this.
  • Google Search Central — "Mobile site and mobile-first indexing" / responsive design guidance. Google's documentation of the three configurations (responsive, dynamic serving, separate URLs) and its explicit recommendation of responsive design.
  • Google Search Central — guidance on intrusive interstitials and mobile page experience. The official account of what makes an interstitial intrusive, when a demotion applies (mobile search arrival), and the exceptions (legal notices, login dialogs, reasonable banners).
  • Google Search Central Blog — the Mobile-Friendly Update announcement (February 2015). The primary record behind Case Study 17.1 ("Mobilegeddon") — the hard date, the global scope, and the framing of mobile-friendliness as a mobile-search ranking signal.
  • Google Search Central — the Page Experience update and the removal of the AMP requirement for Top Stories (2020–2021). The documented change at the center of §17.7 and Case Study 17.2: any qualifying page, AMP or not, became eligible for Top Stories.
  • Google Search Central — announcement retiring the Mobile-Friendly Test tool and the Mobile Usability report (December 2023). The source for the §17.4 Evidence Check; explains what was retired and why, and points to Lighthouse as the replacement.
  • web.dev (by Google) — responsive design, viewport, tap targets, and font-size guidance. Practical, current documentation for the mobile-usability specifics in §17.4, including the viewport meta tag and tap-target sizing.
  • The AMP Project documentation (amp.dev). The framework's own account of what AMP is and how it works — useful for understanding a technology whose SEO role has faded but which still exists.

Tier 2 — Credible, verify specifics

  • Established SEO publications' mobile-SEO and mobile-first-indexing guides (the major SEO software vendors' learning centers and long-running industry blogs). Good for practical walkthroughs and the community's collective experience of the 2015 update and the AMP exodus — but check any Google-behavior claim against the Tier-1 documentation above, and distrust any confident, precise "X% of sites were affected" figure.
  • Contemporary trade coverage of "Mobilegeddon" (April 2015) and of the post-2021 AMP decline. Valuable as a record of what the industry believed at the time — including the hype — which is itself the lesson of Case Study 17.1. Read it as primary-source sentiment, not as measurement.
  • Chrome DevTools / Lighthouse documentation. For actually running the mobile checks recommended in §17.4 now that the standalone Mobile-Friendly Test is gone.

Tier 3 — This book's constructed material

  • Rivertown Home Services — the running project; the mobile audit in this chapter's Strategy File (Figure 17.5) and all its numbers are illustrative and labeled.
  • Figures 17.1–17.5 — all constructed teaching examples (the three-configuration diagram, the parity report, the viewport sketch, the "near me" SERP, and the Rivertown audit). Use them to reason, not as real data.

Suggested order

  1. Google's "Mobile-first indexing best practices" — the spine of the chapter; internalize the parity checklist first.
  2. The responsive-design guidance and the viewport/tap-target material on web.dev — the "how to build it right" layer for §17.2 and §17.4.
  3. The intrusive-interstitials documentation — short, and it settles a question people get wrong.
  4. The 2015 Mobile-Friendly Update announcement, then a piece of contemporary "Mobilegeddon" coverage — read them together to feel the gap between hype and reality (Case Study 17.1).
  5. The Page Experience / AMP-Top-Stories change and the 2023 tool-retirement notice — the two Google changes that date-stamp §17.4 and §17.7, and anchor Case Study 17.2.
  6. Only then, the AMP Project docs — with the context to see AMP for what it now is.