Affiliate disclosure
Book titles on this page link to Amazon. As an Amazon Associate, DataField.Dev earns from qualifying purchases — at no additional cost to you.
Chapter 38 — Further Reading
An audit is the whole book applied at once, so the best "further reading" is partly the book's own earlier chapters and its appendices. The external sources below are grouped by how much you can trust them, in the spirit of the chapter — and the single most useful reference is the checklist you can work down today.
Tier 1 — Canonical (start here; free and authoritative)
- Google Search Central — the crawling-and-indexing documentation. The primary reference for the technical
lens:
robots.txt, sitemaps, canonicalization,noindex, status codes, and the index-coverage states you will read in an audit. When a third-party audit claim conflicts with this, believe Google. - Google Search Console Help — the Page indexing report, URL Inspection, and the Manual Actions report. Google's own guidance on the reports that supply the authoritative data for the technical and authority lenses — including the one true penalty verdict.
- Google Search Central — "Creating helpful, reliable, people-first content" and the core-updates guidance. The reference for the questions a crawler cannot answer — intent, originality, and quality — and the reason a technical-only audit is incomplete (Case Study 2).
- PageSpeed Insights and the Core Web Vitals documentation (
web.dev). Google's own tools and thresholds for the speed lens (LCP, INP, CLS; field versus lab data). - This book: Appendix G (Technical SEO Audit Checklist) and Appendix C, Worksheet 5. The working checklist to audit against and the worksheet to record findings and their impact × effort scores.
Tier 2 — Reputable secondary (useful, but verify against Tier 1 and your own judgment)
- The documentation for a site-crawler (e.g., the Screaming Frog SEO Spider user guide). A genuinely useful reference for how to run a crawl analysis and read its output — titles, status codes, canonicals, crawl depth. Remember the tool is your robot, not Googlebot (Chapter 30).
- The audit and site-audit documentation from the major SEO suites (Ahrefs, Semrush, Moz). Good for learning what an automated audit checks — read them for the findings, and ignore the composite "health score" they crown the report with (§38.5). They find issues fast; they do not prioritize for you.
- Reputable practitioner writing on the SEO audit process. The better independent guides frame the audit as a prioritized diagnosis rather than a checklist. Read them for structure; hold every "you must fix X" claim to the impact × effort test before acting.
Tier 3 — Foundational and contextual (for the curious)
- Case-study background. The public reporting on the JCPenney 2011 link scheme (Case Study 1) is a vivid, real illustration of an authority audit catching a manufactured profile. Read it for the anatomy of the finding, not for statistics to quote.
- This book, revisited as an audit. Chapters 14–21 (technical), 3/9/12 (on-page and content), 22–26 (authority), and 30 (competitive and the tool tour) are each a lens; re-reading their Strategy Files in order is the fastest way to see how Rivertown's full audit was assembled.
Suggested order
- Print Appendix G and read it top to bottom once — it is the map of the technical lens.
- Skim the Search Console Help pages for Page indexing, URL Inspection, and Manual Actions — the three reports that supply an audit's authoritative data.
- Read Google's helpful-content and core-updates guidance so you understand the questions no crawler can answer (Case Study 2's whole lesson).
- Try a real crawl with the free crawler tier on a small site, following its user guide.
- Return to the book's earlier Strategy Files (Chapters 14, 15, 22, 25, 27, 30) and watch Rivertown's findings accumulate into the punch list you assembled in this chapter.
The audit habit, distilled: for every finding, ask which lens, how much impact, how much effort — and be as willing to write "leave this alone" as "fix this first." That willingness is what separates a diagnosis from a checklist.