How to shape a page, a hub and a site so both a reader and a machine can take the answer out of it.
How search and assistant systems build a picture of a company, and the unglamorous consistency work that improves it.
How internal links are read when the reader is a retrieval system, and the five patterns worth applying across a knowledge hub.
Why the pillar-and-cluster model survives the shift to AI search, with one change: the cluster pages get more important than the pillar.
The trade-off in plain terms, the cases where each one is right, and why the decision is harder to reverse than it looks.
Which structured data types are worth the effort for a knowledge site, how to connect them, and what to leave alone.
What FAQPage and QAPage markup still do, where each one belongs, and the mistakes that get a page's structured data ignored.
A working method for the opening paragraph, the headings and the specifics that decide whether a passage gets lifted or skipped.
An answer hub is a section of your own domain where each question your market asks has its own page, written to be quoted.