Boilerplate ratio: how nav and footers shrink your page
Main-content extraction keeps one block of your page and drops the rest. How to measure what survives, by hand and across a site, and the markup that helps.
13 posts
Main-content extraction keeps one block of your page and drops the rest. How to measure what survives, by hand and across a site, and the markup that helps.
Is llms.txt worth it? The proposal, the file format with a worked example, what is documented about who reads it, and when the afternoon pays off.
Four positions cover almost every site. The copy-paste file for each, the matching rules that quietly break them, and the maintenance the file needs.
The rich result that justified most FAQ blocks is gone. What still earns one, the test for whether a question belongs in the body, and what filler costs.
Real markup is only half of it. What flattening does to a table lifted out of your page, and the four fixes that keep one readable on its own.
A page is retrieved in pieces of a few hundred words. What splitting does to ordinary prose, and the three edits that make a section survive it.
An element-by-element inventory of what AI crawlers keep, discard, and only conditionally read — plus the parts you can exclude on purpose.
What happens to a page between fetch and answer, the eight signals answer-readiness turns on, and how to check every one of them by hand and at scale.
Three acronyms, one page. Here is what answer engines and generative search changed about optimization, and what they did not.
Every AI bot worth naming in your robots.txt, what each one actually controls, and which ones decide whether an assistant can find you at all.
Which AI bots exist, what each one actually controls, why robots.txt is only half the answer, and how to check whether assistants can reach your pages.
The highest-weighted answer-readiness signal is a passage that answers its own heading in one breath. What it is, how to write one, how to check it.