Part III — Technical SEO

You can write the best content in your industry, and it can be worth nothing if a search engine cannot crawl it, render it, index it, or trust the site it lives on. Technical SEO is the foundation the rest of the house stands on — the plumbing and the structure that let content and authority do their work. This is the most technical part of the book, but it is written for the marketer who must brief a developer as much as for the developer who must implement, and it assumes no coding.

We begin with the fundamentals (Chapter 14): robots.txt, sitemaps, canonical tags, meta robots, HTTP status codes, crawl budget, and the Search Console reports that tell you whether Google can actually see your pages. Chapter 15, site architecture, covers how the organization of your pages — flat versus deep, URL structure, navigation, and above all internal linking — determines how authority flows through a site; internal linking is the most underused lever in all of SEO. Chapter 16 tackles Core Web Vitals, the measurable dimensions of page experience (LCP, INP, CLS), with an honest account of how much they actually matter. Chapter 17 addresses the phone-shaped reality of modern search: mobile-first indexing and the fact that Google ranks the mobile version of your site.

The second half of the part goes deeper. Chapter 18 covers structured data and schema markup — how to state explicitly what your content is and earn the rich results that lift click-through. Chapter 19 confronts JavaScript SEO, the very real problem of sites built with React, Vue, or Angular whose content Google may render late or not at all. Chapter 20 covers international SEO — hreflang, ccTLDs, and the most error-prone corner of the discipline — with the honest note that most sites don't need it. Chapter 21 closes with site migrations, the single most dangerous SEO operation, where a disciplined checklist is the difference between a temporary dip and a catastrophe.

The recurring theme here is theme 4: technical SEO is the foundation content and authority build on. You will not need to become an engineer. You will need to understand these systems well enough to find what's broken, to know what "good" looks like, and to have a precise, credible conversation with whoever can fix it. That fluency is rarer — and more valuable — than most people realize.

Chapters in This Part