Module 04
Structure a Machine Can Read
What has to be true about the page itself - for a parser, for a performance measurement, and now for an agent operating it on someone's behalf.
5 lessons · 13 videos · 5h 19m
- 04.01
Semantic HTML: Writing for a Parser Without Writing for One
Mark up a page so its structure is legible to a machine without distorting it for a reader, and explain why Google says chunking content for AI is unnecessary.
- 04.02
Structured Data: What It Earns and Where It Is Not Required
Add the schema types that actually produce a result feature for a given page, and say plainly which claims about structured data and AI visibility are unsupported.
- 04.03
Core Web Vitals: LCP, INP and CLS
Say what each of the three metrics measures, at which percentile and over what window, and diagnose which one a slow page is actually failing.
- 04.04
Field vs Lab: CrUX, RUM and Lighthouse
Explain why a Lighthouse score and a CrUX report disagree, and choose which one to trust for a given decision.
- 04.05
The Page an Agent Sees: DOM, Screenshot, Accessibility Tree
Describe the three ways a browser agent perceives a page, and change a component so an agent can operate it - which is the accessibility audit restated.