Bibliography

Sources are grouped by confidence tier, following the book's citation-honesty policy (see _style-bible.md §7). Tier 1 are works, specifications, and institutions we are confident exist; Tier 2 are real ideas and industry practices whose exact publication we have not pinned down; Tier 3 are constructed teaching examples — above all the recurring Rivertown Home Services practice site — labeled where they appear.

Tier 1 — Verified canonical sources (Google's public Search Central documentation and the Search Quality Rater Guidelines; the Schema.org vocabulary and the W3C and IETF specifications such as HTTP and the Robots Exclusion Protocol; named public algorithm updates — Panda, Penguin, Hummingbird, RankBrain, BERT, and the Helpful Content and Core updates; and public institutions and tools — Google Search Console, Bing Webmaster Tools, and the Internet Archive)

• Looker Studio Help — connecting Search Console and Google Analytics 4 data sources; blending/labeling. The tool behind the free one-screen dashboard of §29.3.
• Airbnb, Inc. — Form S-1 / IPO prospectus (2020) and subsequent public earnings commentary (documented basis for Case Study 39.1: majority direct/unpaid traffic; marketing-spend reframing).
• AMP Project — 2015 launch and 2019 move to open (OpenJS Foundation) governance (public record; basis of Case Study 1).
• Appendix A — SEO Metrics, Formulas, and CTR Models (this book): the master identity, CTR-shape model, forecasting formula, and ROI ratio.
• Brin, S. & Page, L. (1998). "The Anatomy of a Large-Scale Hypertextual Web Search Engine." (Origin of PageRank; the link-as-citation argument; chapter epigraph.)
• Chrome UX Report (CrUX) — the real-user field-data source behind the Core Web Vitals / Page Experience report. Named for §27.6; owned by Ch 16.
• Confirmed public Google positions referenced: Googlebot uses an evergreen Chromium engine; rendering is a distinct, resource-intensive step decoupled from crawling; blocked JS/CSS or script errors can prevent Google seeing content; the #! AJAX scheme is deprecated; dynamic rendering is a workaround, not recommended long-term.
• Court of Justice of the EU, Schrems II (Case C-311/18, July 2020) invalidating the EU-US Privacy Shield; and the public decisions of Austria's DSB (2022), France's CNIL (2022), and Italy's Garante (2022) on Google Analytics and GDPR. Primary record for Case Study 28.2. (Public rulings; cited conceptually, not as legal advice.)
• David Segal, "The Dirty Little Secrets of Search," The New York Times, February 12, 2011 (the J.C. Penney paid-link network investigation; Case Study 1).
• Deerwester, S., Dumais, S., et al. (1990), "Indexing by Latent Semantic Analysis" — the original LSI paper (what LSI actually is; why "LSI keywords" misappropriates the name).
• Documented public link-penalty cases: Interflora (UK, 2013, advertorial paid links); the broader 2013–2014 link-scheme enforcement wave.
• Duplicate content: Google's position that duplicate/near-duplicate pages are filtered (one representative chosen), not penalized (applied in §20.7; owned by Ch 14).
• European Commission adequacy decision on the EU-US Data Privacy Framework (July 2023). For Case Study 28.2's "the ground keeps moving."
• GDPR (Regulation (EU) 2016/679) and California's CCPA/CPRA. For the conceptual regulatory framing in §28.7.
• Google (John Mueller), 2014. Public announcements ending Google Authorship — author photos/bylines removed (June 2014) and rel="author" authorship data dropped (August 2014).
• Google / Matt Cutts (Webmaster Central), 2009 — public change to how rel=nofollow handles PageRank (nofollowed links no longer redirect PageRank to other links; the share is not passed on). Basis for retiring "PageRank sculpting."
• Google Analytics 4 — official documentation on attribution models (data-driven, first-click, last-click) and conversion/key-event configuration — the machinery behind §32.5 and §32.7. (GA4 home: Ch 28.)
• Google Analytics Help — "[GA4] Analytics events" and the guides to automatically collected, enhanced measurement, recommended, and custom events. Primary source for the event model (§28.1).
• Google Analytics Help — "[GA4] Data thresholds," data-retention controls (2/14 months), and "How Analytics handles IP addresses" (GA4 does not log/store IPs). Basis for §28.7's "funnel of loss."
• Google Analytics Help — "[GA4] Engaged sessions and engagement rate" and "Average engagement time": the exact definitions (>10s / 2+ views / key event; bounce rate as the inverse of engagement rate) used in §28.4.
• Google Analytics Help — "[GA4] Key events" (formerly "Conversions"), documenting the 2024 rename and how to mark/create/manage key events (§28.5).
• Google Analytics Help — "[GA4] Traffic acquisition" and "User acquisition" reports and "Default channel group" definitions (session- vs. user-scoped; the Organic Search channel) for §28.2.
• Google Analytics Help — consent mode and data thresholds documentation. The Tier-1 basis for the §29.3 caveat that measured conversions undercount reality (a floor, not a census); conceptual privacy framing only (no legal advice).
• Google Analytics Help — GA4 documentation on events, key events (conversions), engagement metrics (engagement rate / engaged sessions), and attribution models (data-driven default). The site-side source for reporting an organic conversion; the basis for "organic-attributed, not caused."
• Google Analytics Help — attribution and attribution models (data-driven as default; the 2023 retirement of first-click/linear/time-decay/position-based from settings) for §28.6.
• Google Analytics — policy prohibiting personally identifiable information (PII) in Analytics data; the basis for the no-PII rule in §28.5.
• Google announcements of RankBrain (2015), BERT (2019), and MUM (2021) — Google's own descriptions and figures (e.g., BERT affecting ~1 in 10 English queries; MUM described as far more capable than BERT).
• Google Business Profile Help — "Guidelines for representing your business on Google" (real-world business name; eligible physical locations; service-area-business settings; prohibited/restricted practices; grounds for suspension).
• Google Business Profile Help — "Improve your local ranking on Google" (the source for relevance / distance / prominence; "review count and score factor into local search ranking"; "there's no way to request or pay for a better local ranking"). Primary reference for the whole chapter.
• Google Business Profile Help — categories, guidelines, and review policies (no gating, no incentives). Basis for the §40.5 local playbook.
• Google Business Profile Help — reviews and prohibited-content policies (rules against fake, incentivized, and gated reviews; guidance to respond to reviews).
• Google confirmation (2009) that the meta keywords tag is ignored for ranking.
• Google confirmed public statements referenced: there is generally no duplicate-content penalty; ordinary 404s do not harm a site's rankings; HTTPS is a lightweight ranking signal (context from Ch 2).
• Google I/O 2018 — "Deliver search-friendly JavaScript-powered websites" (public description of the two-wave indexing model; historical primary source).
• Google I/O 2024 — the announcement of the broad US rollout of AI Overviews (the "answer above the links" shift arriving at scale), public record for Case Study 1.
• Google Panda update (launched February 24, 2011) — public announcement targeting low-quality sites and content farms. Basis for Case Study 2.
• Google public announcement (Aug 2023) — video thumbnails to show primarily when the video is the main content of the page (basis for Case Study 2).
• Google Search Advocates' repeated public statements that word count is not a ranking factor. Tier-1 basis for retiring the length myth (§9.5).
• Google Search blog — the post from the head of Google Search responding to the May 2024 AI Overviews errors (what went wrong, which examples were fabricated, and the mitigations shipped). Primary source for Case Study 1.
• Google Search Central / Google Search representatives' repeated public statements that Google Search does not use Google Analytics data as a ranking signal (§28.1, §28.4 myth-busts).
• Google Search Central / Schema.org. Article, Person, and sameAs structured-data documentation — recognize-don't-write reference for author/reviewer identity; craft deferred to Ch 18.
• Google Search Central / Search Central Blog — Penguin algorithm (2012; later part of core ranking) and the December 2022 link spam update using SpamBrain to neutralize spammy links.
• Google Search Central / Search Console Help — statements on negative SEO and third-party links (Google is good at ignoring links intended to harm; most sites need not worry about competitor link attacks).
• Google Search Central / Search Relations public guidance — removing and consolidating content; the stated position that deleting pages is not itself a ranking tactic and can hurt if you remove pages with value. Basis for §12.3 Evidence Check and Case Study 2's real caution.
• Google Search Central Blog (2019) — announcement of rel="sponsored" and rel="ugc" and nofollow becoming a hint for ranking (effective March 1, 2020).
• Google Search Central Blog (August 2021) — the announcement of the change to how Google generates title links. Basis for Case Study 1.
• Google Search Central Blog / announcements — Hummingbird (2013), RankBrain (2015), BERT (2019): the documented shift from matching strings to understanding meaning and intent (context for why the pillar-cluster model fits modern search).
• Google Search Central Blog / documentation — deprecation of the AJAX crawling scheme (#! hashbang), announced October 2015 and later fully retired.
• Google Search Central Blog — "Googlebot now runs the latest Chromium rendering engine" (evergreen Googlebot, May 2019) — primary source that Google renders modern JavaScript.
• Google Search Central Blog — 2023 announcements reducing FAQ rich results (to authoritative government/health sites) and deprecating HowTo rich results (primary record for Case Study 18.1).
• Google Search Central Blog — July 2019 posts: formalizing the Robots Exclusion Protocol, open-sourcing the robots.txt parser, and ending support for unsupported robots.txt rules (noindex, nofollow, crawl-delay) effective September 1, 2019.
• Google Search Central Blog — Mobile-Friendly Update announcement (February 26, 2015; effective April 21, 2015) — basis of Case Study 17.1.
• Google Search Central Blog — Page Experience update announcements (2020–2021 mobile, 2022 desktop; AMP no longer required for Top Stories).
• Google Search Central Blog, "HTTPS as a ranking signal" (2014) — confirms HTTPS as a signal and characterizes it as lightweight, affecting well under 1% of queries.
• Google Search Central Blog. December 2022 update introducing "Experience" (E-A-T → E-E-A-T) and updated helpful-content guidance.
• Google Search Central documentation — breadcrumb structured data (eligibility for a breadcrumb rich result).
• Google Search Central documentation — crawl-budget management for large sites; "Discovered – currently not indexed" / "Crawled – currently not indexed" explanations (depth and importance affect crawl priority).
• Google Search Central documentation — Crawling and indexing (robots.txt, sitemaps, canonical, noindex).
• Google Search Central documentation — internal links and link best practices (that internal links aid discovery and signal a site's structure and the relative importance of its pages).
• Google Search Central documentation — structured data, Organization, and the sameAs property (entity declaration and linking).
• Google Search Central documentation — the long-standing guidance that the best way to get links is to create unique, relevant content that naturally gains popularity (source of the chapter epigraph).
• Google Search Central documentation — URL structure best practices (descriptive, stable URLs; hyphens over underscores as word separators).
• Google Search Central Help — URL Inspection Tool (viewing rendered HTML, screenshot, and page resources Google could/couldn't load). Deep treatment in Ch 27.
• Google Search Central — "Block Search indexing with noindex" (meta robots + X-Robots-Tag; the warning that a noindex page must not be blocked by robots.txt).
• Google Search Central — "Build and submit a sitemap" / "Manage your sitemaps" (format, 50,000-URL / 50MB limits, sitemap index files, no indexing guarantee).
• Google Search Central — "Consolidate duplicate URLs" and canonicalization guidance (rel=canonical as a signal; no general duplicate-content penalty; user-declared vs. Google-selected canonical).
• Google Search Central — "Control your snippets in search results" / meta description guidance (snippet generation; confirmation that the meta description is not a ranking factor). Primary source for §9.2.
• Google Search Central — "Discover and your website" (no opt-in/guarantee; eligibility via indexing + policies; guidance on compelling non-clickbait titles and large images / max-image-preview:large).
• Google Search Central — "Do you need an SEO?" / hiring-an-SEO guidance (what an SEO does; questions to ask; the explicit warning that no one can guarantee a #1 ranking and that guaranteed rankings are a red flag). Primary source for §37.7 and Case Study 2.
• Google Search Central — "Dynamic rendering as a workaround" (current framing of dynamic rendering as a stopgap, not a recommendation; steer toward SSR/SSG/hydration; caution against divergent content).
• Google Search Central — "Ecommerce" documentation (overview and best practices for online stores: site structure, category and product pages, launching products).
• Google Search Central — "Featured snippets and your website" (snippets are selected programmatically from page-one results; cannot be forced with markup; how to opt out).
• Google Search Central — "Fix search-related JavaScript problems" (lazy-loading, blocked resources, JavaScript-generated content and metadata, checking rendered output).
• Google Search Central — "Google Images best practices" / image SEO documentation (alt text, filenames, surrounding context, structured data, how Google understands images).
• Google Search Central — "Google Search's guidance about AI-generated content" (2023): rewards high-quality content however produced; appropriate use of AI is not against guidelines; automation to manipulate rankings is a spam violation. The core source for §13.1.
• Google Search Central — "How Google Search organizes information" (general-audience overview).
• Google Search Central — "How Google Search works"; Search Quality Rater Guidelines (assessing whether a page meets a query's meaning/need).
• Google Search Central — "HTTP status codes, network, and DNS errors" (how Google treats 2xx/3xx/4xx/5xx; soft 404s; return 503 for planned maintenance).
• Google Search Central — "Image license metadata in Google Images" (IPTC metadata / Schema.org license fields; the "Licensable" badge).
• Google Search Central — "In-Depth Guide to How Google Search Works" (crawling, indexing, serving).
• Google Search Central — "Influencing your title links in search results" (where title links come from; when Google generates its own; how to write a title Google keeps). Primary source for §9.1.
• Google Search Central — "Intro to how structured data markup works" / "Understand how structured data works" (JSON-LD; eligibility is not guaranteed).
• Google Search Central — "Introduction to robots.txt" and "How Google interprets the robots.txt specification" (robots.txt controls crawling, not indexing; matching rules).
• Google Search Central — "Large site owner's guide to managing crawl budget" (crawl capacity limit vs. crawl demand; most sites, generally under ~10,000 URLs, need not manage it).
• Google Search Central — "Link spam policies" (Spam policies for Google web search): buying/selling links, excessive link exchanges, and links intended to manipulate ranking.
• Google Search Central — "Link spam" / Spam policies for Google web search (the authoritative definition and examples of link schemes: buying/selling links that pass ranking signals, excessive link exchanges, large-scale article campaigns and automated guest posting with keyword-rich anchors, automated link creation, requiring links).
• Google Search Central — "Managing multi-regional and multilingual sites" (the language-vs-country distinction; choosing a URL structure with Google's stated no-blanket-preference position; locale-adaptive pitfalls). Primary source for §20.1, §20.2, §20.6.
• Google Search Central — "Mobile-first indexing best practices" (the parity checklist: content, structured data, images, metadata, hreflang; common mistakes).
• Google Search Central — "Page Indexing report" Help documentation (meaning of each index status label, including "Crawled – currently not indexed," "Discovered – currently not indexed," "Indexed, though blocked by robots.txt," "Excluded by 'noindex' tag").
• Google Search Central — "Qualify your outbound links to Google" (the rel="nofollow", rel="sponsored", rel="ugc" attributes; the 2019/2020 move to treating them as hints — source for §22.4).
• Google Search Central — "Review snippet" documentation and the 2019 change ending display of self-serving LocalBusiness/Organization reviews.
• Google Search Central — "SEO Starter Guide" and "Search Essentials." The closest thing to an official holistic checklist; the sanity check for any assembled strategy.
• Google Search Central — "Site moves with URL changes" (planning a move, 301 redirects, sitemaps, the Change of Address tool; the master migration guide).
• Google Search Central — "Site moves without URL changes" (HTTP→HTTPS and same-URL redesigns; canonical host, mixed content, dropped elements).
• Google Search Central — "Structured data general guidelines" (technical + quality): mark up visible content, be representative, no misleading/self-serving markup — basis of the "Spammy structured markup" manual action.
• Google Search Central — "Tell Google about localized versions of your page" (the hreflang specification: HTML tags / HTTP headers / XML sitemap; language + region code format; the return-tag reciprocity requirement; self-referential requirement; x-default). Primary source for §20.3, §20.5.
• Google Search Central — "Understand the JavaScript SEO basics" / how Googlebot renders JavaScript.
• Google Search Central — "Understanding page experience in Google Search results" (page experience as a tiebreaker ranking signal; does not override great, relevant content).
• Google Search Central — "Verifying Googlebot and other Google crawlers." Reverse/forward DNS method and published crawler IP ranges; basis for the log-verification step in §33.4.
• Google Search Central — "Verifying site ownership" and the privacy/anonymization rationale for omitting rare queries. Supports §27.1 and the §27.2 data-anonymization callout.
• Google Search Central — "Video key moments" documentation (automatic detection; Clip and SeekToAction markup).
• Google Search Central — "Video SEO best practices" and the VideoObject structured-data reference (video indexing requirements; rich-result eligibility).
• Google Search Central — "What site owners should know about Google's core updates" (broad quality reassessment; often "nothing to fix" beyond genuine quality; reassessment over time). Basis for §12.1 decay causes and the patience framing.
• Google Search Central — "What web creators should know about our core updates." Canonical source for "there is often nothing specific to fix" and the patient, whole-site response — the capstone's thesis in Google's words.
• Google Search Central — core updates guidance (Ch 6): the basis for honestly explaining an update-driven dip in a report (§29.7) rather than hiding it.
• Google Search Central — announcement retiring the International Targeting report (2022): removal of the manual country-targeting setting and the hreflang-error tab; reasoning (low usage; improved automatic country detection). Primary record for Case Study 1 and §20.6.
• Google Search Central — announcement that INP replaced First Input Delay (FID) as a Core Web Vital (March 2024).
• Google Search Central — Article / NewsArticle structured data documentation (headline, datePublished, dateModified, author, publisher; aids understanding/eligibility, not a ranking factor).
• Google Search Central — canonical / "consolidate duplicate URLs" documentation (Ch 14 reference): why a canonical pointing to another language version drops a locale from the index — the fatal §20.5 canonical conflict.
• Google Search Central — Change of Address tool documentation (applies to domain moves; not protocol-only or subdomain changes).
• Google Search Central — core updates guidance and "How to handle a decline in Google Search" (core-update drops are not manual actions, have no reconsideration path, and recover through genuine quality improvement over time; the link to Ch 6 and §26.6).
• Google Search Central — Core Web Vitals report documentation (the field-data Good / Needs improvement / Poor grouping inside Search Console).
• Google Search Central — crawling and indexing documentation (robots.txt, sitemaps, canonicalization, noindex, HTTP status codes, index-coverage states): the primary reference for the technical audit lens.
• Google Search Central — crawling documentation and the Crawl Stats report help page (response codes, file types, Googlebot type, crawl purpose). The free small-site substitute for raw log analysis.
• Google Search Central — Disavow Links tool documentation (what it does, the file format, that a new upload replaces the prior file, and Google's guidance that MOST SITES SHOULD NOT USE IT — chiefly for a manual action for unnatural links, or self-built links you cannot remove).
• Google Search Central — documentation on rich results and structured-data eligibility (to distinguish featured snippets from rich results; ties to Ch 18).
• Google Search Central — documentation on soft 404s, noindex, and robots.txt (the concepts behind the lazy-homepage soft 404 and the staging-noindex catastrophe; read with Ch 14).
• Google Search Central — documentation on the Helpful Content system and core updates (site-wide quality signal; reassessment over time; "remove unhelpful content").
• Google Search Central — duplicate content / canonicalization guidance (ordinary duplication is consolidated/selected, not penalized). (Canonicalization: Ch 14.)
• Google Search Central — encrypted ("secure") search and the "(not provided)" change (SSL/HTTPS search 2011; full rollout 2013), and the May 2015 rename of Google Webmaster Tools to Google Search Console. Public, dated record behind Case Study 27.1; stated as direction/scale, no fabricated percentages.
• Google Search Central — faceted navigation guidance (managing crawlable/indexable filter URLs; keeping the rest out of the index).
• Google Search Central — Google News documentation and news content policies (automated inclusion; Publisher Center manages presentation, not gatekeeping).
• Google Search Central — Google Search ranking systems and core-update guidance (the confirmed named updates that create algorithm-dependence risk).
• Google Search Central — guidance on how long SEO takes and "how to handle a decline in Google Search" (search changes take time; recovery is genuine improvement over weeks/months). Tier-1 backbone for the long-game expectations conversation (§29.6) and the "results in 30 days" myth.
• Google Search Central — guidance on automatically-generated / machine-translated content (raw unreviewed machine translation published for search engines treated as low value). Backbone of §20.4's myth-bust.
• Google Search Central — guidance on intrusive interstitials and mobile page experience (what counts as intrusive; the mobile-search-arrival trigger; legal/login exceptions).
• Google Search Central — guidance on succeeding in Google's AI experiences: there is no special markup or trick for AI features; the same people-first content, technical soundness, and structure fundamentals apply (Tier-1 antidote to GEO folklore, §36.4).
• Google Search Central — guidance that auto-generated internal search result pages generally should not be crawled/indexed.
• Google Search Central — link best practices / "Qualify your outbound links": the rel="nofollow", rel="sponsored", and rel="ugc" attributes and what they signal.
• Google Search Central — link best-practices / "how to get links" guidance (earn links by creating genuinely useful, relevant content people want to reference).
• Google Search Central — Manual Actions report documentation (location: Security & Manual Actions; the full list of manual-action types: unnatural links to/from your site, thin content, pure spam, user-generated spam, cloaking/sneaky redirects, hidden text/keyword stuffing, hacked site, spammy structured data, site reputation abuse).
• Google Search Central — mobile site configurations and the recommendation of responsive web design (responsive vs. dynamic serving vs. separate URLs).
• Google Search Central — News sitemaps specification (recent-articles window, ).
• Google Search Central — Page Experience update (2020–2021) opening Top Stories to non-AMP pages and removing the AMP badge — basis of §17.7 and Case Study 17.2.
• Google Search Central — Product structured data / merchant listing / Review snippet documentation (Product, Offer, AggregateRating, Review; InStock/OutOfStock availability). (Primary home: Ch 18.)
• Google Search Central — Reconsideration requests documentation (how the process works; genuine documented cleanup required; applies ONLY to manual actions).
• Google Search Central — redirects and canonicalization documentation; handling of irrelevant redirects as "soft 404s"; how 301s consolidate signals. Basis for §12.7 (full migration discipline deferred to Ch 21; status codes to Ch 14).
• Google Search Central — redirects documentation / "How Google Search handles redirects" (301 vs. 302; permanent redirects pass ranking signals; avoid redirect chains; irrelevant redirects treated as soft 404s).
• Google Search Central — rendering-strategy / "Rendering on the Web" guidance (CSR vs. SSR vs. static generation vs. hydration; performance trade-offs).
• Google Search Central — retirement of the Mobile-Friendly Test tool, its API, and the Mobile Usability report (December 2023); Lighthouse recommended instead.
• Google Search Central — reviews system guidance ("Write high quality reviews"; rewards in-depth, first-hand reviews with evidence of actual use).
• Google Search Central — robots.txt guidance (do not block resources Google needs to render), cross-referenced from Ch 14.
• Google Search Central — Search Console Core Web Vitals report documentation (field/CrUX status for LCP, INP, CLS). Source for the CWV KPI and its "tiebreaker, not growth engine" honest weight (Ch 16).
• Google Search Central — Search Console Page Indexing (Index Coverage) report documentation (indexed vs. "crawled — currently not indexed" vs. "discovered — currently not indexed"; index bloat). Source for the "indexed pages" KPI; read with Ch 14 and Ch 27.
• Google Search Central — Search Console documentation: the Pages (indexing) report, URL Inspection tool, sitemaps report, and Crawl Stats (the tools used for migration monitoring; read with Ch 27).
• Google Search Central — Search Console Performance report and Page indexing report documentation (clicks, impressions, average position, CTR over time; crawled-currently-not-indexed). Basis for the §12.1 decay diagnostic and §12.2 audit (tool itself is Ch 27).
• Google Search Central — Search Quality Rater Guidelines and E-E-A-T guidance (why demonstrated expertise/thought leadership matters; how credible sources show it). (E-E-A-T home: Ch 5.)
• Google Search Central — Spam policies (cloaking) and guidance on handling syndicated content (republisher noindex where you don't want copies competing; canonical as a hint).
• Google Search Central — spam policies (scaled content abuse, site reputation abuse, expired-domain abuse; announced March 2024). The documented basis for Case Study 40.1.
• Google Search Central — spam policies and helpful-content guidance (revisited from Ch 6 and Ch 13): the rules did not stop applying because the interface changed.
• Google Search Central — Spam policies for Google web search: "Scaled content abuse" (introduced/expanded March 2024) — many pages to manipulate rankings, no value, regardless of how produced.
• Google Search Central — spam policies, including "scaled content abuse" and "doorway pages" (the primary source for §32.4's caution on mass-templated integration/use-case pages and §32.3's volume-not-depth caution).
• Google Search Central — Spam Policies: "Link Spam" (buying/selling links that pass PageRank, exchanges, automated links, required links — the rulebook for §22.6).
• Google Search Central — Spam policies: cloaking (definition; serving different content to crawlers to manipulate rankings is a violation).
• Google Search Central — statements (John Mueller and others) that Google does not use a single "domain authority" / website-authority score in ranking (source for §22.7 myth).
• Google Search Central — statements that Request Indexing does not guarantee indexing and that being indexed does not guarantee ranking; the crawl-render-index-rank pipeline (owned by Ch 1). Supports the §27.5 Request-Indexing myth.
• Google Search Central — structured data documentation for LocalBusiness (the on-site NAP/entity complement to the profile and citations; deep-dived in Chapter 18).
• Google Search Central — structured-data feature galleries and per-type reference pages (Breadcrumb, Product/merchant listings, Review snippet, Local business, Recipe, Event, Video; current status of FAQ and HowTo).
• Google Search Central — Subscription and paywalled content / flexible sampling documentation (metering and lead-in; isAccessibleForFree and CreativeWork/hasPart paywall markup; introduced 2017 replacing First Click Free).
• Google Search Central — the stronger mobile-friendly ranking boost (May 2016) and the multi-year rollout of mobile-first indexing (announced 2016).
• Google Search Central — Video indexing report (Search Console) documentation (indexed-as-video status and reasons).
• Google Search Central, "A guide to Google Search ranking systems" — Google's own enumeration of named ranking systems (RankBrain, BERT, helpful content system, reviews system, etc.).
• Google Search Central, Page Experience and Core Web Vitals documentation — frames page experience as a tiebreaker; states great content matters more.
• Google Search Central. "Creating helpful, reliable, people-first content." States that E-E-A-T is not itself a specific ranking factor while its systems use signals that align with strong E-E-A-T; includes the who/how/why self-assessment questions.
• Google Search Central. "How Search works" and documentation on search quality and the role of quality raters (basis for "raters evaluate systems, not individual rankings").
• Google Search Central. Documentation and guidance on broad core updates — that a core update is a broad quality reassessment with "nothing to fix," and recovery comes from improving overall quality over time. Backbone of §35.2 and the "no YMYL penalty" myth-bust.
• Google Search Central. Documentation of broad core updates and guidance that a ranking drop after a core update does not necessarily mean a page is "wrong" (context for Case Study 5.2).
• Google Search Central. Guidance that HTTPS is a lightweight ranking signal.
• Google Search Central. Public confirmation/framing of the August 2018 broad core update (the one the community nicknamed "Medic"): confirmed as routine, unnamed by Google, with a pointer to the rater guidance and E-A-T. (Event + Google framing are Tier 1; the "targeted YMYL/E-A-T" reading is Tier 2, below.)
• Google Search Central. Public statements that linking out to authoritative sources is not a ranking boost (basis for the §35.5 myth-bust) and that HTTPS is a lightweight signal.
• Google Search Console Help — "Page indexing report" (Indexed vs. Not indexed buckets and each status reason; the "Validate Fix" flow). Owned in depth by Ch 14; cited here for §27.4.
• Google Search Console Help — "Performance report (Search)" (definitions of impressions, clicks, CTR, average position; "how data is calculated"; the statement that average position is an average; the filtered/anonymized-queries note behind data anonymization). Source for §27.2–§27.3.
• Google Search Console Help — "URL Inspection Tool" (indexed view: on Google, last crawl, crawled-as, chosen vs. declared canonical, enhancements; Test Live URL; View Crawled/Tested Page — rendered HTML, screenshot, HTTP response, page resources; Request Indexing and its quota/limits). Source for §27.5.
• Google Search Console Help — Manual Actions report, including the "Spammy structured markup" action and the reconsideration-request process.
• Google Search Console Help — Sitemaps report, Links report, "Security & Manual Actions" (Manual Actions and Security Issues), Removals tool, and Change of Address tool documentation. Source for §27.6 (each report handed to its home chapter: sitemaps Ch 14, CWV Ch 16, links Ch 22, manual actions Ch 26, migrations Ch 21).
• Google Search Console Help — the Page indexing report, URL Inspection tool, and the Manual Actions report (the one authoritative penalty signal an authority audit checks).
• Google Search Console Help — the Performance report (impressions, clicks, CTR, average position); the only CTR data to forecast with (§39.2).
• Google Search Console Help — the Search Console documentation set (adding and verifying a property; Domain vs. URL-prefix property types; verification methods: DNS record, HTML file, HTML meta tag, Google Analytics, Google Tag Manager). The authoritative source for §27.1.
• Google Search Console — "Links" report documentation (internal links per page).
• Google Search Console — Links report (Google's own view of inbound links: top linking sites, top linked pages, top linking text; the authoritative source for a link audit; read with Ch 27).
• Google Search Essentials (formerly Webmaster Guidelines) — the baseline for being eligible to appear in Search.
• Google Search Essentials + "Creating helpful, reliable, people-first content" — Google's statement of what it rewards (helpfulness, expertise, satisfying the searcher). Ground for §9.5–§9.7.
• Google Search Essentials / spam policies: what constitutes link schemes and unnatural links (the pattern an authority audit is built to detect).
• Google Search Essentials — spam policies (link schemes, cloaking, doorway pages, scaled content abuse): the rules an ethical practitioner never crosses on a client's behalf (rule two of §37.7); collected for readers in Appendix D.
• Google Search Liaison — public announcement of the January 2020 featured-snippet deduplication (a page in a featured snippet is no longer duplicated in page-one organic results). Primary source for Case Study 1.
• Google Search Quality Rater Guidelines — source of E-E-A-T (author/publisher trust signals for news; foundation for Ch 5 and Ch 35).
• Google Search Quality Rater Guidelines — the E-E-A-T framework, incl. "Experience" (context for why first-hand comparisons win; owned Ch 5).
• Google Search spam policies — "Keyword stuffing" named explicitly as a manipulation. Basis for §9.6.
• Google Skillshop — Google Analytics certification (free; the recommended first credential; ties to Chapter 28).
• Google Webmaster Central / Matt Cutts blog posts on the BMW.de doorway-page removal (February 2006), and the contemporaneous ricoh.de action. Primary public record for Case Study 1.
• Google — Chrome User Experience Report (CrUX) documentation (real-user field dataset; 75th percentile over a trailing 28 days; "insufficient data" for low-traffic pages).
• Google — Consent Mode documentation, including the 2024 "Consent Mode v2" requirements for EEA advertising/audience features (§28.7).
• Google — documentation and help pages on AI Overviews / AI features in Search: what AI Overviews are, where they appear, that they link to sources, and that they draw on Google's existing ranking and quality systems (the retrieval link for §36.1).
• Google — knowledge panel help documentation (claiming a panel and suggesting changes; what owners can and cannot do).
• Google — mission statement ("organize the world's information and make it universally accessible and useful"), the chapter epigraph and the anchor for §36.7's principles-endure argument; and "How Search Works" fundamentals.
• Google — PageSpeed Insights (pagespeed.web.dev) and Lighthouse documentation (field vs. lab data; the 0-to-100 lab performance score and its role).
• Google — PageSpeed Insights and the Core Web Vitals reference (web.dev): tools and thresholds for the speed lens (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1; field vs. lab data).
• Google — Panda update announcements (incl. Panda 4.0, May 2014) and "creating helpful, reliable, people-first content" guidance. (Named updates: Ch 6.)
• Google — public confirmations that PageRank is still used internally among many signals, and that Toolbar PageRank was retired (updates ceased ~2013; removed 2016).
• Google — the Universal Analytics sunset announcement (March 16, 2022) and GA4 migration guidance: standard UA properties stopped processing new data July 1, 2023 (Analytics 360 a year later); GA4's event-based model; historical UA data not imported. Public record behind Case Study 1.
• Google — the Panda update (first launched Feb 2011; "Farmer") and the May 2011 "More guidance on building high-quality sites" post. Basis for Case Study 1 (site-wide quality; content farms).
• Google's 2009 statement that Google does not use the meta keywords tag in web ranking.
• Google's 2011 search-encryption / secure-search announcements — origin of "(not provided)"; primary historical source for Case Study 28.1.
• Google's long-standing communication on the freshness signal / "Query Deserves Freshness" (a real, query-dependent freshness capability; not universal; not a date-change trigger). Basis for §12.6.
• Google's public communications on combating fake business profiles and fake reviews (annual updates on enforcement). Cited for direction only; no exact removal figures reproduced.
• Google, "How Search Works" — public overview of ranking factors (meaning, relevance, quality, usability, context) and Google's statement that it uses many signals.
• Google, "Introducing the Knowledge Graph: things, not strings" (Amit Singhal, Google official blog, 2012) — primary source for the entity shift and the graph's launch scale (Google's own figures).
• Google, "Understanding searches better than ever before" (2019) — Google's own explanation of the BERT update, with worked natural-language examples.
• Google. Search Quality Rater Guidelines. Google Search Central (public PDF). Source of E-E-A-T, the Page Quality scale (Lowest–Highest), YMYL, and reputation-research instructions.
• Helpful Content system (2022) as the modern successor establishing that unhelpful, unoriginal content at scale is demoted (Ch 6 is its home; referenced here for decay + pruning).
• HTTP status codes / RFC 9110 (the standardized meaning of 301, 302, 404, 410, etc.); the status-code family is owned by Ch 14 and used here.
• ISO 639-1 (language codes) and ISO 3166-1 Alpha-2 (country/region codes) — the authoritative lists behind valid hreflang values (settles en-gb vs. en-uk).
• Matt Cutts, "The decay and fall of guest blogging for SEO," mattcutts.com, January 20, 2014 (chapter epigraph; Case Study 2). Google's March 2014 manual action against a large guest-blog network (MyBlogGuest), announced publicly by Cutts.
• Named Google updates as public record (Helpful Content 2022–2024; broad core updates; the March 2024 core update folding helpful-content assessment into core systems). Used only as documented public events.
• Page, L. & Brin, S. (1998), "The Anatomy of a Large-Scale Hypertextual Web Search Engine"; Page, Brin, Motwani & Winograd, "The PageRank Citation Ranking." Intuition for "link equity" (full treatment in Ch 22).
• Page, L., Brin, S., Motwani, R. & Winograd, T. (1999). "The PageRank Citation Ranking: Bringing Order to the Web." (The formula and the random-surfer/damping model in depth.)
• Penguin (2012) and its 2016 real-time/granular shift to devaluing rather than penalizing links; SpamBrain (Google's AI spam-prevention system that neutralizes spammy links) — named algorithm history owned by Ch 6, used here.
• Public record of the Feb 2018 removal of the "View Image" button from Google Images, tied to the Google–Getty Images licensing agreement (basis for Case Study 1).
• Public record of United States v. Google (antitrust; tried 2023 before Judge Amit Mehta, ruling August 2024) — testimony and exhibits surfacing click/interaction systems such as NavBoost.
• Public, widely-reported industry history of the content-farm model, incl. Demand Media / eHow as the defining example Panda targeted. Case Study 1 (facts of what changed; no invented per-company figures).
• Recurring public statements by Google Search Advocates that word count is not a ranking factor, that there is no ideal keyword density, and that domain age does not help ranking.
• RFC 9309 — "Robots Exclusion Protocol" (IETF, 2022), the formal internet standard for robots.txt.
• Robertson, S., & Zaragoza, H. (2009), "The Probabilistic Relevance Framework: BM25 and Beyond" — definitive reference for BM25 (saturation and length-normalization terms).
• Schema.org / Google Search Central — structured-data parity requirement on the indexed (mobile) version (cross-ref Ch 18).
• Schema.org and Google "Structured data" documentation — the schema layer underneath the local system.
• Schema.org — VideoObject, ImageObject, and related types (structured-data vocabulary; full treatment Ch 18).
• Schema.org — the vocabulary and type hierarchy (Thing → Organization → LocalBusiness → HVACBusiness/Plumber/Electrician; Product, Service, FAQPage, HowTo, BreadcrumbList).
• Schema.org — vocabulary reference for Organization, Service, and the sameAs property.
• Spärck Jones, K. (1972), "A statistical interpretation of term specificity and its application in retrieval" — origin of inverse document frequency (IDF).
• The disavow tool's launch (Google, October 2012) — a dated public fact used to explain why the JCPenney 2011 cleanup could not use it.
• The Rich Results Test (search.google.com/test/rich-results) and the Schema Markup Validator (validator.schema.org).
• This book — Appendix G (Technical SEO Audit Checklist) and Appendix C, Worksheet 5 (the audit-recording worksheet): the working checklist and record for the reader's own audit.
• U.S. Federal Trade Commission — "Rule on the Use of Consumer Reviews and Testimonials" (2024), banning fake/AI-fabricated reviews, buying reviews, undisclosed insider reviews, and review suppression. (Public rule; cited conceptually, not as legal advice.)
• U.S. Federal Trade Commission — FTC v. Fashion Nova (2022 settlement, \$4.2 million, for suppressing negative customer reviews); the agency's first case focused on review suppression. Used in Case Study 25.2.
• Web Content Accessibility Guidelines (WCAG) — text alternatives for non-text content (the accessibility standard behind alt text).
• Web Stories on Google — developer documentation (format; appearance in Discover and Search; successor to AMP Stories).
• web.dev (Google) — responsive design, the viewport meta tag, tap-target sizing, and legible font-size guidance.
• web.dev — "Optimize LCP," "Optimize INP," "Optimize CLS" (official fix guidance).
• web.dev — "Web Vitals" hub and the metric guides: "Largest Contentful Paint (LCP)," "Interaction to Next Paint (INP)," "Cumulative Layout Shift (CLS)," "Time to First Byte (TTFB)" (definitions, thresholds, methodology).
• Wikidata (wikidata.org) — structured entity data; one of Google's corroborating sources.
• Wikipedia (en.wikipedia.org) — observable public facts on its architecture: dense editorial internal linking, category hub pages, clean/stable /wiki/Title URLs, disambiguation pages, and nofollow on external links (used in Case Study 15.1 with facts only, interpretation labeled).

Tier 2 — Attributed (real industry practice, studies, or figures whose exact citation we have not pinned down)

• "Beginner's Guide to SEO" and reference documentation maintained by established SEO software vendors (concepts sound; verify Google-behavior claims against Tier 1).
• "Local Search Ranking Factors" — the long-running practitioner-consensus survey (Whitespark; historically hosted by Moz) on the relative weight of local signals. Attributed expert opinion and correlation, not Google-published weights.
• 2023 U.S. antitrust-proceeding disclosures referencing Google search signals (e.g., "Navboost") apparently using interaction data. Used only to distinguish Google's own scaled click data from a site's GA4 engagement metrics (§28.4); weight and mechanism explicitly unknown.
• Academic literature on generative-engine citation, e.g. the "GEO: Generative Engine Optimization" research coining the term and studying which content properties (structure, quotations, statistics, authority) correlate with being cited — held as early findings/hypotheses, not rules (§36.4 speculation tier).
• Academic research on AI-detector bias (e.g., Stanford-affiliated work) finding detectors disproportionately flag non-native English writers' text as AI-generated — cited for direction/mechanism, not a single figure.
• Analytics thought leadership on actionable vs. vanity metrics (e.g., Avinash Kaushik's long-running writing on the "so what?" test and tying metrics to business outcomes — acquisition/behavior/outcomes). A way of thinking behind §29.1–§29.2, not a fixed metric list; attribute honestly, do not invent figures.
• B2B / SaaS SEO guides maintained by established SEO software vendors (Ahrefs, Semrush, Moz, and similar) — content-funnel mapping, bottom-of-funnel keyword strategy, comparison and integration pages. Sound on workflow; verify any "how Google behaves" claim against Tier 1.
• Backlink-audit and disavow tutorials from established SEO tool vendors and agencies (useful for reading a profile and building a disavow file WHEN warranted; but the same vendors sell "toxicity scores"/"disavow protection" — confirm any claim about how Google treats links against Google's own docs; never substitute a toxicity score for the provenance question).
• Backlinko / Brian Dean — "The Skyscraper Technique" (public, ~2013): the named method analyzed in Case Study 1; sound workflow, self-reported results (vendor claim), and its decay into templated outreach spam.
• Bing Webmaster documentation on JavaScript/crawling — second-engine perspective; useful for separating universal principles from Google-specific behavior and confirming that non-Google crawlers render less.
• Bing Webmaster documentation on markup/structured data (a second engine's account; useful for separating universal Schema.org principles from Google-specific rich-result rules).
• Bing Webmaster documentation — a second engine's public account of crawling and indexing (useful for separating universal principles from Google-specific detail).
• Bing Webmaster documentation — crawling, robots.txt, and sitemaps (second-engine account; useful for separating universal principles from Google-specific detail).
• BrightLocal — recurring consumer-review and local-search consumer surveys (how people use reviews when choosing a local business). Cite the durable direction, not a specific year's percentage.
• Chrome DevTools / Lighthouse documentation — running the mobile-usability checks after the Mobile-Friendly Test's retirement.
• Community coverage of the August 2018 broad core update nicknamed "Medic" (e.g., Search Engine Roundtable / Barry Schwartz). Documents the event; the "it targeted E-A-T/YMYL" reading is community interpretation, not a Google statement.
• Community coverage of the August 2018 update nicknamed "Medic" (e.g., Search Engine Roundtable / Barry Schwartz, commonly credited with the nickname; Search Engine Land). Documents the event and the observation that YMYL/health sites were disproportionately affected — industry interpretation of winners/losers, not a Google-confirmed mechanism.
• Community coverage of the unofficial local updates "Possum" (September 2016) and "Hawk" (August 2017) — used in Case Study 25.1 for the local-filter and proximity mechanics, with the explicit caveat that Google never named or confirmed them.
• Consumer-privacy and consent-management industry surveys on cookie-banner decline and ad-blocker prevalence. Cited for direction (measurement is shrinking), never a specific figure.
• Contemporaneous journalism on the CNET AI-content episode (2022–2023) — reporting (e.g., Futurism, The Verge) surfacing factual errors, corrections, and disclosure changes. Article counts / correction rates are journalistic figures, not verified internals.
• Contemporary reporting and third-party visibility-index analysis of eBay's 2014 organic decline (SEO news outlets; "search visibility" vendors such as Searchmetrics). Direction and timing useful; figures are third-party ESTIMATES, not Google-verified facts or eBay revenue.
• Contemporary third-party SEO analysis of HubSpot's ~2024 organic-traffic decline (SEO visibility/traffic-estimation tools and industry commentary). Direction and rough scale only; figures are third-party ESTIMATES, not company-confirmed traffic or revenue, and the cause is debated (core/Helpful Content updates, AI Overviews, off-topic content).
• Contemporary trade press coverage of "Mobilegeddon" (April 2015) — primary source for industry sentiment/hype, not measurement.
• Core Web Vitals guides and reference docs from established SEO tool vendors (concepts sound; confirm ranking claims against Google's own docs).
• Coverage of Search Console feature changes — the temporary disabling of Request Indexing (late 2020), the retirement of the standalone Mobile Usability report (2023), and the 16-month data window — used to keep "current behavior" claims honest; verify against live docs.
• Digital-publishing / journalism-industry analyses of traffic diversification, newsletters, and Google/Discover dependence (support for §34.7; treat named-publisher traffic figures as reported estimates, not precise facts).
• Documented manual-action cases: Interflora (2013, advertorial/paid-link manual action and ~11-day recovery — Google never officially named the site; SEO attribution is practitioner reconstruction) and BMW.de (2006, doorway pages / sneaky JavaScript redirects; removed from the index and quickly reincluded after cleanup). Named as Tier-1-adjacent public events; specifics attributed, not invented.
• Documented post-mortems of real, public migrations (retailer replatforms, publisher domain moves, large HTTPS rollouts) in the trade and financial press — valuable for the shape of failure; specific numbers are context-bound and often conflate SEO with UX and business factors. No precise figure asserted as fact.
• E-commerce SEO and faceted-navigation guides maintained by established SEO software vendors (Ahrefs, Semrush, Moz, and similar) — sound on workflow; verify Google-behavior claims against Tier 1.
• Enterprise internal-linking and crawl-optimization write-ups from in-house teams and SEO software vendors — concrete tactics; treat any "we saw X% lift" claim as correlational and unverified (Ch 2).
• Established SEO community publications and job boards — for the reality of roles, day-to-day work, and hiring; read for texture, not for salary figures to quote.
• Established SEO industry publications' coverage of Google News, Discover, and core/Helpful Content update timelines (landscape and practitioner consensus; verify behavior claims against Tier 1; note these outlets are themselves publishers).
• Established SEO publications' Search Console guides (Search Engine Journal, Search Engine Land, Ahrefs, Semrush, Moz "how to use Search Console" material) — strong for workflows and worked interpretation; any "how Google weights X" or precise CTR-by-position figure treated as attributed estimate, not Google-published fact.
• Established SEO references' image- and video-SEO material (major "Beginner's Guide to SEO" resources and tool-vendor documentation); sound on concepts, verify Google-behavior claims against Tier 1.
• Established technical-SEO reference guides from reputable SEO software vendors on JavaScript SEO, rendering, and hydration — concepts sound; verify Google-behavior claims and check dates (topic ages fast).
• Framework rendering documentation: Next.js (SSR/SSG/ISR, App Router server rendering), Nuxt (Vue universal/SSR/SSG), Gatsby (static generation) — authoritative for tool capabilities; pair with Tier 1 for Google behavior. Note publication dates.
• Free platform academies: HubSpot Academy (SEO/content/inbound), Google Digital Garage / Google Ads basics, Semrush Academy, Ahrefs Academy — structured fundamentals and tool proficiency, free; vendor-flavored, verify Google-behavior claims against Tier 1.
• General marketing-finance literature on customer lifetime value, CPA/CAC, payback period, and marketing-mix modeling (standard finance background for the CFO conversation).
• General professional-services consulting / freelancing / client-management references — the non-SEO half of §37.4 and §37.7 (scoping, pricing, communication, running a practice).
• Google's "reasonable surfer" patent and reputable analyses (links more likely to be clicked may pass more weight; placement matters). A patent indicates consideration, not confirmed live use.
• Google's published customer case studies on structured data (direction of the CTR-lift argument; specific percentages are vendor-published and situational, not laws to quote).
• hreflang guides, tag generators, and validators from established SEO tool vendors and international-SEO specialists (helpful for building/checking a set; confirm any ranking/targeting claim against Tier 1; check the publication date against the 2022 tooling changes).
• HTTP Archive "Web Almanac" — annual, large-scale, independent analysis of real-world web performance (context for how sites actually score; verify Google-behavior claims against Tier 1).
• HubSpot and other marketing-software companies' public material popularizing the "topic cluster" / pillar-page model (2016–2017 onward). Framework sound and widely adopted; vendor rankings-lift studies are self-published and correlational — treat magnitude as unverified.
• HubSpot's documented "historical optimization" practice (updating and re-promoting old posts outperformed publishing new for them). Primary popular source for §12.4; one publisher's real experience, not a universal law.
• In-depth featured-snippet and search-intent guides from established SEO tool vendors (Ahrefs, Semrush, Moz, Backlinko) — concepts and screenshots sound; verify Google-behavior claims against Tier 1; do not treat exact figures as fact.
• Independent analyses of the subdirectory-vs-subdomain authority debate (read as reasoning, not proof; the strongest defensible argument is authority consolidation — a first-principles point, Ch 22 — not a Google-confirmed ranking rule).
• Independent clickstream analyses of zero-click search (e.g., work associated with Rand Fishkin / SparkToro) — a large, rising share of Google searches end without a click. Cited for direction/trend, NOT a specific percentage (numbers vary by method/definition; the chapter deliberately quotes none as fact).
• Independent contemporaneous coverage of the Exact-Match Domain (EMD) update (September 2012), announced by Matt Cutts — specifics (percentage of queries affected) reported but treated as attributed.
• Independent technical-SEO practitioner write-ups on out-of-stock/discontinued-product handling and internal-search indexing.
• Independent write-ups of content-pruning failures as well as wins (the real-world version of Case Study 2).
• Independent-publisher accounts of the 2023–2024 Helpful Content / core updates (HouseFresh, "How Google is killing independent sites like ours," 2024; Retro Dodo and similar) — first-person testimony of platform risk (Case Study 39.2); read critically alongside Google's stated position, as the causal story is contested.
• Industry commentary documenting the "(not provided)" expansion (2011–2014) from signed-in users to nearly all organic keyword data, and the paid-vs-organic-data controversy. Used directionally in Case Study 28.1; no exact percentage curve reproduced.
• Industry writing on real medical-review / editorial workflows at established health and finance publishers (writer drafts → credentialed reviewer verifies → dated byline). Basis for the legitimate model in §35.3.
• Industry/trade-press coverage of HARO's ownership trail (Vocus 2010; absorbed into Cision), its 2024 rebrand to "Connectively," and the Connectively shutdown in December 2024 (Case Study 2).
• Investigative reporting (2022–2024) on publishers producing AI-generated content under fabricated author identities and fake "reviewed by" labels. Documented real-world basis for the Case Study 35.2 composite; kept factual, no figures asserted, no real company named in-text.
• John Mueller (Google Search Advocate), public statements that "there's no such thing as LSI keywords" (social media, 2019, widely cited) — on-record debunking from a Google voice (a tweet, not documentation).
• Large-scale backlink correlation studies from SEO tool vendors (Ahrefs, Semrush, Moz, Backlinko): more/higher-authority referring domains correlate with higher rankings — direction only, not exact figures; correlation, not causation.
• Large-scale content-and-links studies from SEO tool vendors (Ahrefs, Moz, BuzzSumo, Semrush): consistent finding that most pages earn few or no referring domains and that original research and tools earn disproportionately — direction robust, exact percentages unverified vendor figures.
• Large-scale content-length correlation studies from SEO tool vendors (e.g., Backlinko and similar) — describe the correlation between length and ranking; cited in §9.5 as the studies commonly misread as an "ideal word count" (correlation, not causation; no fabricated figure asserted).
• Large-scale correlation studies of SERP features / content formats from SEO tool vendors — useful for the direction of a pattern (e.g., comparison queries tend to show table snippets), not for precise percentages.
• Large-scale CTR-by-position studies from SEO tool vendors/researchers (e.g., Advanced Web Ranking CTR data; Backlinko, Sistrix studies) — read for the curve's shape only; do not quote exact percentages as fact.
• Large-scale link/ranking correlation studies from SEO tool vendors (Ahrefs, Semrush, Moz, Backlinko): more referring domains correlate with higher rankings — correlation, not proven causation; report direction, never a fabricated percentage.
• Large-scale ranking-correlation studies from SEO tool vendors (Ahrefs, Semrush, Moz, Backlinko) — useful large-sample evidence; report correlations, not causation; specific percentages unverified.
• Local salary surveys and compensation data (country/city-specific, current) — the honest source for a real, caveated pay range, since this book refuses to quote a figure (§37.2 Evidence Check).
• Log-file-analysis tooling documentation (Screaming Frog Log File Analyser, Botify, OnCrawl, and similar) for the mechanics of parsing and segmenting Googlebot logs at scale. (Pro toolset generally: Ch 30.)
• Long-standing technical-SEO reference guides maintained by established SEO software vendors (crawlability, indexability, canonicalization, faceted navigation) — concepts sound; verify Google-behavior claims against Tier 1.
• Migration guides, checklists, and redirect-mapping tutorials from established SEO tool vendors and agencies (useful as operational checklists and spreadsheet templates; confirm any claim about how Google treats redirects or transfers equity against Google's own docs; treat any "recovered X% in Y weeks" figure as a single self-reported anecdote).
• Nielsen Norman Group — research on how people read online (F-shaped and layer-cake scanning). Independent usability research behind §9.7.
• Nielsen Norman Group — research on web navigation, information scent, and scanning behavior (F-pattern); the usability basis for curated navigation and the honest version of the "three-click" idea.
• noyb (None of Your Business) publications on the coordinated Google Analytics complaints (101, per noyb's own account) and Schrems II. Count and campaign position attributed to the source.
• On-page SEO reference guides from major SEO software vendors (Moz, Ahrefs, Semrush) — mechanics of titles, meta descriptions, and headings (verify Google-behavior claims against Tier 1).
• OpenAI announcement discontinuing its AI Text Classifier "due to its low rate of accuracy" (2023).
• Practitioner content-audit and content-pruning guides (Ahrefs, Semrush, Moz, and established consultants) — sound on process (building the audit sheet, crawling); subject to publication bias on pruning-win magnitudes. Verify percentages against Tier 1.
• Practitioner digital-PR literature: data-led PR (build the asset, pitch the story) vs. "please link to us" outreach.
• Practitioner documentation and guides on resource-page outreach, broken-link building, unlinked-mention reclamation, and digital PR (Ahrefs, Moz, Search Engine Journal, Search Engine Land) — tactics to apply through the §24.1 evaluation filter and the §24.6 line.
• Practitioner guides to programmatic SEO (industry blogs, conference talks) — useful for dataset/template/internal-link patterns; apply this chapter's quality bar to the "whether," as much such advice underweights the doorway line.
• Practitioner literature on entity SEO and topical authority (Search Engine Journal, Search Engine Land, Moz, and similar) — informed professional models, not confirmed Google mechanics; treat with the evidence-tier habit.
• Practitioner literature on the pillar-and-cluster / topic-cluster model (content-marketing community) — the content-strategy framing behind hub-and-spoke (pair with Ch 8).
• Practitioner method for reading the Performance report: branded vs. non-branded segmentation, the high-impressions-low-CTR ("low-hanging fruit") title opportunity, and "striking distance"/page-two queries. Durable technique; specific numbers illustrative.
• Practitioner writing on SEO reporting and stakeholder communication (reporting to owners/managers/CFOs; the long-game conversation; reporting misses). Operational reality for §29.4–§29.7, not a source of numbers.
• Practitioner writing on B2B attribution, MQL/SQL definitions, and pipeline/revenue reporting from reputable demand-generation and revenue-operations sources. Vocabulary and honest limits are useful; treat specific benchmark conversion rates as illustrative, not universal.
• Practitioner writing on content pruning, topic clusters, and SEO reporting (KPIs vs. vanity metrics, the monthly one-pager). Directionally supported by consensus; exact figures are case-specific.
• Practitioner writing on manual-action recovery (removal outreach, documentation, the reconsideration back-and-forth; honest about how grinding the removal step is and how often a first request is rejected). Operational reality for §26.5, not a source of numbers.
• Practitioner writing on SEO traffic forecasting and ROI modeling (industry blogs/conference talks) — method and spreadsheet structure; treat embedded numbers as illustrative.
• Public Google Search Relations statements (e.g., John Mueller) that publishing frequency is not itself a ranking factor — widely reported practitioner-consensus reference; paraphrased, no exact quote fabricated.
• Publicly reported speed-and-conversion case figures from large retailers/publishers (Amazon, Walmart, Pinterest, BBC) — directional evidence that faster is better for business; self-reported, context-specific, not independently verified. No exact figure asserted as fact.
• Published "inbound marketing" methodology and B2B content-marketing case material, including HubSpot's own materials (Case Study 1: founded 2006 by Brian Halligan and Dharmesh Shah; popularized "inbound marketing"; Website Grader / Marketing Grader; the recurring "State of Inbound" / "State of Marketing" reports; HubSpot Academy). Strategy and structure are documented; specific traffic figures are undisclosed or third-party estimates.
• Reported industry response to the 2014 guest-blog-network actions (contested reception; effects on sites that received links through the networks).
• Reporting on the Texas-led multistate antitrust complaint concerning Google ad-tech, which included AMP-related ALLEGATIONS (labeled as allegations, not findings; Google disputes them).
• Reputable analytics-practitioner guides and educators (analytics consultancies, GA4 how-to references) for interface mechanics — explorations, event-creation/modification rules, cross-domain and iframe tracking. Interface specifics are time-stamped; verify in the product.
• Reputable contemporary reporting on the 2018 "View Image" removal and the 2023 video-thumbnail "main content" change (facts of what changed; distrust any attached traffic percentage).
• Reputable local-SEO practitioner sources (e.g., Sterling Sky, Whitespark, Google Business Profile product-expert community) for profile mechanics, the local filter, and suspension-recovery experience.
• Reputable practitioner analyses of the 2024 Google Search API documentation leak — the documents are authentic (Google acknowledged this), but the live-ranking role of each referenced feature is unconfirmed.
• Reputable practitioner writing on the SEO audit process that frames the audit as a prioritized diagnosis rather than a checklist (verify any "must-fix" claim against the impact × effort test).
• Reputable retrospectives and contemporary reporting on Panda (2011) and the content-farm era. Facts of what changed for Case Study 1; distrust any specific traffic figure.
• Reputable technology journalism on the 2024 AI Overviews launch and its errors (e.g., The Verge, Ars Technica) — the documented public record complementing Google's own account in Case Study 1.
• Screaming Frog hreflang crawl/validation documentation (how a crawler reports missing return tags, missing self-references, and inconsistent annotations) — the practical §20.5 validation loop.
• Screaming Frog SEO Spider documentation (crawling a staging site, list-mode crawling, auditing redirect chains and response codes; the standard free tool for building and testing a redirect map, up to 500 URLs free).
• Screaming Frog SEO Spider documentation (free tier) — crawling for crawl depth, orphan pages, and redirect chains.
• Screaming Frog SEO Spider user documentation: how to run a crawl analysis and read its output (status codes, titles, canonicals, crawl depth). The tool is the auditor's robot, not Googlebot (Ch 30).
• Screaming Frog SEO Spider user guide / how-tos (seeing a site as a crawler does: status codes, canonicals, noindex, redirect chains, orphan pages).
• Search Engine Land and trade-press coverage of eBay's May 2014 organic-visibility decline (Case Study 40.2). Attributed reporting and analyst interpretation; exact cause never fully confirmed by Google.
• SEO software vendors' learning centers and long-running industry blogs — mobile-first indexing and mobile-SEO guides; the community record of "Mobilegeddon" (2015) and the post-2021 AMP decline. (Concepts sound; verify Google-behavior claims against Tier 1; distrust precise "% of sites affected" figures.)
• SEO tool-vendor and industry guides to internal linking, orphan-page audits, and site architecture (Ahrefs, Moz, Semrush, Search Engine Journal, Search Engine Land) — good on procedure; treat specific correlation figures as directional, not proven (per §15.4 Evidence Check).
• SEO tool-vendor and trade explainers on E-E-A-T (Moz, Ahrefs, Semrush, Search Engine Journal, Search Engine Land). Useful summaries; several present an "E-E-A-T score" or checklist that overstates the precision of Google's position — flagged in-text as vendor models, not Google metrics.
• SEO tool-vendor guides (Ahrefs, Semrush, Moz, Backlinko) on building an SEO strategy, prioritization frameworks (impact × effort / ICE), and SEO roadmaps — strong on structure; treat any specific stat (CTR-by-position, referring-domain correlation) as direction, not a Google-published fact.
• SEO tool-vendor guides to KPIs, dashboards, and share of voice (Ahrefs, Semrush, Moz). Useful for dashboard mechanics and for the definition of share of voice — but the same vendors sell Domain Authority / Domain Rating, so confirm any claim that a score reflects how Google ranks against Google's own docs, and keep vendor scores off the value report.
• SEO tool-vendor reference guides (Ahrefs, Semrush, Moz, Backlinko) on content strategy, content mapping, content-gap/keyword-gap analysis, and editorial calendars. Useful process; verify any Google-behavior claim against Tier 1; ignore any "ideal posting frequency" figure.
• SEO-community analyses and third-party visibility-index reporting of eBay's May 2014 organic decline (SEO news outlets; visibility vendors such as Searchmetrics). Source of the CAUSAL story in Case Study 2 — informative on direction and timing, but analysis rather than Google confirmation; reported magnitudes vary by source and are third-party ESTIMATES.
• SEO-industry post-mortems of the 2023–2024 Helpful Content and core updates from established named practitioners (shape of events only; per-update traffic percentages are unreliable and Google publishes none — see Ch 6).
• Site-audit documentation from the major SEO suites (Ahrefs, Semrush, Moz): useful for learning what an automated audit checks; read for the findings, ignore the composite "health score" (§38.5).
• Software-review marketplaces (G2, Capterra, TrustRadius, Software Advice) as market context for §32.2 — the sites that structurally own many "[tool] reviews/alternatives" queries.
• Structured-data implementation guides and reference docs from established SEO software vendors and CMS/plugin documentation (workflow patterns; may lag Google's changes — verify feature claims against Tier 1).
• Technology and media press reporting on the AMP era, its 2019 governance change, and post-2021 publisher deprecations (context for Case Study 1; distinguish reported facts from contested antitrust allegations still in litigation — not stated as established wrongdoing).
• The "AMP Letter" (2018, web developers/publishers) — documented public criticism of AMP and preferential search treatment.
• The AMP Project documentation (amp.dev) — the framework's own account (Tier 2 for neutrality since it is the vendor).
• The New York Times — "The Dirty Little Secrets of Search" (David Segal, February 2011): the JCPenney link-scheme investigation; Google's on-record confirmation (Matt Cutts) of a manual action; reported ranking drops. REAL public case (Case Study 1); ranking figures cited as reported, SEO reading labeled analysis; no figure invented.
• Third-party "toxicity score" metrics (e.g., vendor toxicity/spam scores) — described as vendor heuristics, not Google measurements; Google has stated these do not reflect its evaluation of links.
• Third-party authority metrics: Moz Domain Authority (DA), Ahrefs Domain Rating (DR), Majestic Trust/Citation Flow — vendor models of authority used for triage, not Google's signals or ranking factors.
• Third-party rank trackers and their "why our rank differs from Search Console" explainers — used for the §27.2 contrast (average position is a trend; a rank tracker answers a different, location-specific question); owned by Ch 30.
• Vendor and independent SEO analyses of AI Overview click-through impact (established tool companies and analysts) — useful for the shape (informational queries under pressure) with the Ch 2 caveat that per-study percentages are unreliable, methodology-dependent, and disputed (including by Google).
• Vendor content-optimization / topic-clustering tools (Surfer, Clearscope, MarketMuse, and similar) — useful for coverage mapping; misused when treated as term-count targets (see §4.4 myth callout).
• Vendor documentation for content-gap / keyword-gap tools (Ahrefs, Semrush) — for what these reports can and cannot detect (topic gaps yes; coverage/intent gaps no).
• Vendor documentation for third-party authority metrics: Moz (Domain Authority), Ahrefs (Domain Rating), Semrush (Authority Score), Majestic (Trust Flow / Citation Flow) — each a prediction, self-described as not a Google ranking factor.
• Web-platform performance/image-optimization documentation (WebP/AVIF, responsive images, native loading="lazy").
• web.dev (Google's developer site) — rendering-patterns articles (CSR/SSR/SSG/hydration and their performance implications; ties to Ch 16 Core Web Vitals).
• YouTube Creator resources / "How search and discovery works on YouTube" (watch time, click-through, satisfaction) — a platform describing its own system; read the incentives.

Tier 3 — Illustrative / constructed (the recurring Rivertown Home Services practice site and the book's other teaching examples and round numbers, labeled where they appear)

• "SupplementSage" — labeled composite in Case Study 5.2, assembled from documented industry patterns; no real traffic/revenue figures asserted.
• "The AI Overview that took 30% of the clicks" (Figure 2.1) — constructed teaching example; the 30% is illustrative, not measured.
• "The Disavow That Dug the Hole Deeper" (Case Study 2) — a labeled composite built from real, common failure modes; every number illustrative.
• "The Domain Move That Forgot the Map" (Case Study 2) — a labeled composite built from real, common industry patterns; every number illustrative.
• "The Hundred-Point Trap" (Case Study 2) — a labeled composite built from real, common industry patterns; all numbers illustrative.
• "The Ten-Language Launch That Lost Traffic" (Case Study 2, Figure 20.3) — a labeled composite built from real, common industry patterns; all numbers illustrative.
• "Top pages have 3x the referring domains" (Figure 2.2) — constructed teaching example of a vendor correlation study; figures illustrative.
• "WellPath" — constructed YMYL health-and-finance publisher, introduced lightly in §5.7; developed in Chapters 34 and 35.
• "The Dashboard That Looked Great While the Business Shrank" (Case Study 2) — "Northlake Outfitters," a labeled composite built from the real, common pattern of vanity-metric reporting plus attribution overclaim with no baseline; every number illustrative.
• Universal Analytics → GA4 migration (Case Study 1) — a real, public event; dates and mechanics documented (Tier 1 above); FIGURE CS29.1 labeled "reconstruction — illustrative shape"; no invented statistic.
• VitalLedger — clearly-labeled composite in Case Study 35.2, assembled from documented industry patterns; fabricated-persona names ("Dr. Marcus Field," "Dana Reyes, CFP") are illustrative and explicitly fictional; no traffic/revenue figures asserted.
• About.com → Dotdash relaunch (2017) — public counter-example of pruning-and-quality (developed in Chs 8, 12).
• All worked numbers in the TF-IDF/BM25 intuition (document counts, term counts, word counts) — illustrative, chosen for clarity, not measured.
• Appendix C — The SEO Strategy Workbook (the blank version of Rivertown's document) and Appendix G (audit templates), referenced as the reader's build tools.
• ASCII schematics (two-wave index, CSR shell, hash-routing, decision aid) — schematic, not to scale.
• Background on the history of answers-on-the-SERP (featured snippets, knowledge panels, earlier zero-click features; paired with Ch 1 and Ch 10) — context for §36.2's "AI Overviews extend a decade-long curve" point.
• BM25 / TF-IDF information-retrieval literature — the math behind repetition's diminishing returns (revisited in Ch 4).
• Brin, S. & Page, L. (1998). "The Anatomy of a Large-Scale Hypertextual Web Search Engine." (Historical foundation; revisited in Ch 22 for PageRank.)
• Case Study 15.2 — "The redesign that orphaned half the site": a clearly-labeled composite of common documented patterns; all magnitudes illustrative.
• Case Study 19.2 — "Meridian Supply," a labeled composite of the SPA-replatform-tanks-traffic pattern; Figure C19.1; the ~60% traffic-drop figure is illustrative/constructed.
• Case Study 2's velocity-casualty site — a labeled composite of the public Helpful Content Update / core-update pattern (2022–2024); named update and Google guidance are real, specific numbers illustrative.
• Case Study 27.2 — "The Dashboard That Cried Wolf" — a labeled composite of two common Search Console misreads (position-noise panic; impressions-up/clicks-flat misread); every number illustrative; no real business depicted. (Case Study 27.1 is a REAL public event — the "(not provided)" saga — with no invented figures.)
• Composite exact-match-domain operator scenario in Case Study 2 — labeled composite of common industry patterns; no real business's figures asserted.
• Constructed composite: "The Catalog That Crawled Itself to Death" (Case Study 2) — assembled from common real patterns; all figures illustrative.
• Constructed composite: "The SaaS Blog That Ranked for Everything and Sold Nothing" (Case Study 2) — assembled from common real industry patterns; all figures illustrative, the sequence is the lesson.
• Constructed report excerpts in the exercises (Figures E.16, E.17).
• Constructed report excerpts in the exercises: Figure E.26a (a manual-action notice) and Figure E.26b (a link profile of four clusters) — labeled constructed teaching examples.
• Constructed report readings in the exercises and quiz (landing-page tables, the 30-vs-140 call discrepancy, engagement figures) — illustrative, round numbers.
• Constructed report/map excerpts in the exercises (Figures E.21a, E.21b).
• Constructed running project: Rivertown Home Services service×city page system (~15 services × 5 cities ≈ 75 pages) and its anti-doorway checklist (Strategy File). All figures, local details, and license references illustrative.
• Constructed sample artifacts: the technician review-request message, the GBP performance-insights snapshot, and the keyword/labeling examples in the exercises and answers.
• Constructed teaching anchor: Dispatchr (a field-service-management SaaS) and its fictional competitor FleetOps — all products, pricing, competitors, reports, and metrics illustrative; competitor names fictional so no claim is made about a real company.
• Constructed teaching example: Summit Gear Co. (mid-size outdoor-gear retailer) — all SKUs, categories, facet counts, and index numbers illustrative.
• Constructed teaching examples in this chapter (all illustrative and labeled): the 500-post blog audit (Fig 12.2), Rivertown's 48-post blog audit (Fig 12.4), the cannibalization SERP (Fig 12.3), the audited-URL rows (Figs 12.1, E.1), and the "Northwind" over-prune composite (Case Study 2). Numbers illustrative; shapes transferable.
• Constructed teaching examples: Figure 33.1 (two drafts of a page), Figure 33.2 (crawl-distribution report — the 41%/22%/9%/6% split), Figure 33.3 (the service×city system design). Every count, percentage, and log figure illustrative and labeled.
• Constructed teaching examples: Rivertown Home Services; "the website that vanished" composite (Case Study 1.2); Figures 1.1–1.4 (all illustrative numbers).
• Constructed teaching examples: the Rivertown Home Services "can Google see it?" test and findings (the Strategy File); Figure 19.1 (constructed URL-Inspection example); Figure E19.1 (exercise). All illustrative, labeled.
• Constructed teaching examples: the Rivertown structured-data plan (Figure 18.3); the rich-vs-plain listing (Figure 18.1); the Enhancements report (Figure 18.2); the spammy-markup manual-action composite (Case Study 18.2). All illustrative and labeled; no invented statistics.
• Constructed teaching examples: WellPath (health publisher; developed further in Ch 35); Rivertown Home Services (the Strategy File, per _continuity.md §5); the labeled composite "Feed Company" of Case Study 2. All numbers illustrative.
• Contemporary reporting on the content-farm era and Demand Media's January 2011 IPO (briefly valued above The New York Times Company) — public record behind Case Study 2. Directional facts only; no invented per-site traffic percentages.
• Contemporary reporting on the Interflora (2013) advertorial-links penalty and recovery.
• Cross-references (in-book): Ch 3 (search intent), Ch 7 (People Also Ask; keyword metrics), Ch 9 (on-page craft; the length myth), Ch 11 (video), Ch 18 (structured data/rich results), Ch 22–26 (authority/links), Ch 25 (local pack), Ch 36 (AI Overviews/zero-click).
• Cross-references: Chapter 7 (volume, difficulty, CPC as commercial-value proxy — forecast inputs), Chapter 28 (GA4 conversions — real conversion rates/values), Chapter 29 (reporting, KPIs, vanity metrics, expectation-setting), Chapter 40 (assembles this case into the full strategy).
• Epigraph: William Bruce Cameron, Informal Sociology (1963) — the real, correctly attributed source of "Not everything that can be counted counts…" (commonly misattributed to Einstein; the misattribution is noted in-text as a theme-3 device). A genuine published Tier-1-style reference used as the epigraph.
• Figure 27.1 (the water-heater page's four-dimension read) and Figure 27.2 (the page that ranks but doesn't earn the click) in index.md — constructed to illustrate method and honest limits; all numbers illustrative.
• Figure 4.1 ("The knowledge panel is the Knowledge Graph, made visible") — constructed teaching example.
• Figure 4.2 ("One deep guide, forty queries it never targeted") — constructed teaching example; all query counts illustrative.
• Figures 17.1–17.5 — all constructed teaching examples (three-configuration diagram; parity report; viewport sketch; "near me" mobile SERP; Rivertown audit). Illustrative, not real data.
• Figures 20.1–20.3 and the constructed report/crawl excerpts in the exercises (Figures E.20a, E.20b) — all labeled constructed teaching examples.
• Figures 24.1–24.4 — constructed teaching examples (prospect scorecard; resource-page operators; competitor backlink profile; two anchor-text distributions). Percentages are illustrative and are not targets.
• Figures 25.1 (thin vs. genuine Cedar Hills location page), 25.2 (the five-location playbook), and 25.3 (before/after the playbook) in index.md — constructed to illustrate method and honest limits.
• Figures 31.1–31.7 and the case-study figures — all constructed/illustrative; every URL, traffic, and count labeled.
• Figures 32.1–32.4 and the case-study figures — all constructed/illustrative; every query, metric, and dollar figure labeled.
• Figures 34.1–34.2, C34.1–C34.2, and E.1 (all constructed/illustrative teaching examples).
• Figures 40.1–40.8 and the assembled one-page Strategy File — all illustrative; the method (diagnose, prioritize, sequence, measure, decide) is real.
• Google Search Console — Links report (Top linked pages / Top linking sites): free, approximate referring-domain and top-linked-page data for §23.6 measurement.
• Illustrative estimated-lead-value math (~\$450 average job × 20% close → ~\$90 per booking request) and the before/after session comparisons (900 → 1,284 organic sessions) — constructed to show method and honest limits, not measured data.
• Illustrative single log line and status-code distributions in §33.4 — constructed, correct-by-inspection, never presented as real server data.
• Internal cross-references: Ch 12 (content audit/pruning/historical optimization/cannibalization), Ch 6 (core & Helpful Content updates), Ch 13 (AI content / scaled content abuse), Ch 5 (E-E-A-T), Ch 18 (structured data/JSON-LD), Ch 14 (canonical/noindex/sitemaps), Ch 36 (traffic diversification / AI Overviews), Ch 35 (YMYL, WellPath's home).
• IPTC Photo Metadata standard documentation (the licensing/credit fields Google reads).
• Journalist-request platforms current as of writing: Qwoted, Featured (formerly Terkel), SourceBottle, ProfNet, and #JournoRequest on social platforms (names expected to churn).
• Marks & Spencer 2014 relaunch (Case Study 1) — a REAL, public event; documented facts from M&S public reporting and contemporaneous press; the SEO-specific reading labeled practitioner analysis (Tier 2); NO invented traffic figure (the reported online-sales decline described qualitatively as "high single digits of percent," attributed by the company partly to relaunch disruption).
• Ogilvy, D. "Confessions of an Advertising Man" (1963) and "Ogilvy on Advertising" (1983) — source of the chapter epigraph; the case that the headline carries the leverage.
• Plain-language explainers of how large language models work (next-token prediction; training on the existing web) — context for why AI is weak at information gain (§13.2) and why experience is the moat (§13.6).
• Plain-language explainers of retrieval-augmented generation (RAG) and how large language models produce text (next-token prediction; training on the existing web) — context for §36.1 (retrieve-then-summarize) and why an answer engine outputs plausible-not-true text (Case Study 1).
• Public reporting on the JCPenney 2011 link scheme (The New York Times, "The Dirty Little Secrets of Search," David Segal, Feb. 2011) and Google's confirmed manual action — the real, public basis for Case Study 1 (read for the anatomy of the finding, not for statistics).
• Reference to Summit Gear Co. (Ch 31's constructed e-commerce anchor) for the faceted-navigation / index-bloat parallel.
• Rivertown Home Services and "Rivertown's proposed fixes, sorted by evidence" (Figure 2.3) — constructed teaching example; all figures illustrative.
• Rivertown Home Services light parts/filters store (Strategy File) — ~25 SKUs, all figures illustrative.
• Rivertown Home Services — all figures, five cities (Rivertown HQ, Cedar Hills, Northgate, Westbrook, Millhaven), branch reviews, and the before/after result — a constructed teaching example (frozen facts from _continuity.md §5).
• Rivertown Home Services — all figures, the five locations, the GA4 conversion setup (Figure 28.2), and the organic landing-page report (Figure 28.1). Constructed teaching example; frozen facts from _continuity.md §5 (family-owned, founded 1984 by Ray Delgado, run by Marisa and Tony Delgado; HVAC/plumbing/electrical; WordPress; ~8,000 mostly-branded organic visits/mo).
• Rivertown Home Services — constructed running project; the entity-cluster territory map (Heating/Cooling/Plumbing/Electrical) is a constructed teaching example.
• Rivertown Home Services — the constructed running project, assembled across all forty Strategy File checkpoints; every figure (traffic, rankings, dollars, page counts) is a constructed teaching example.
• Rivertown Home Services — the running constructed project; this chapter's four-pillar white-hat link plan (Figure 24.5). All figures illustrative.
• Rivertown Home Services — the running project; the Chapter 17 mobile audit (Figure 17.5) and all its numbers are illustrative and labeled [the Strategy File].
• Rivertown Home Services' 12-month business case and budget (this chapter's Strategy File) — constructed teaching example; all figures illustrative.
• Rivertown Home Services' commercial HVAC line (Strategy File) — B2B lens on the constructed home-services company; all specifics illustrative.
• Rivertown mobile CWV figures reused from Ch 16 (homepage LCP ~4.1s; "AC repair" ~4.8s / INP ~240ms / CLS ~0.22) — illustrative, kept consistent with Chapter 16's Figure 16.3.
• Robots Exclusion Protocol original proposal (Martijn Koster, 1994) — the 25-year informal standard later formalized as RFC 9309.
• Schema.org launch materials (2011) and background on the Google/Microsoft/Yahoo/Yandex collaboration (context for a shared vocabulary).
• Segal, D. (2011). "The Dirty Little Secrets of Search." The New York Times (February 2011) — the JCPenney paid-link investigation and Google's manual action; source for Case Study 1. Public facts only; ranking-drop magnitude described qualitatively where exact figures are not asserted.
• The "500-post blog" content-audit anchor — a constructed content site introduced here (its home/audit is Ch 12). All post counts and traffic figures illustrative.
• The chapter's illustrative CTR table and priority-keyword forecast — teaching numbers matched to the established curve shape, not measured values.
• The illustrative disavow-file text block in §26.3 (format illustration only) and all worked traffic/ranking numbers in the composite — labeled illustrative.
• The New York Times — Segal, D. (Feb. 2011). "The Dirty Little Secrets of Search." (JCPenney paid-link scheme and manual action — Case Study 2.)
• The original 2011 "high-quality sites" self-assessment questions in historical form (how early Google framed quality as a site-wide, human-judgment matter).
• The simplified link-equity division model in §15.4 (authority ÷ number of outgoing links) — an illustrative simplification; the real model is PageRank (Ch 22).
• U.S. Federal Trade Commission (and equivalent regulators) — materials/enforcement on deceptive online-marketing and "guaranteed Google ranking" schemes; documents that the guaranteed-ranking model (Case Study 2) is a real, common pattern. Referenced in general documented terms; no specific figures invented.