Desk rules and source notes
Clippings from the desk.
These are Ryan's source notes, annotations, and working rules. They are not case studies or performance claims.
Desk rule. Captured: July 28, 2026Start with the words already on the page.
A title tag, page heading, and visible offer should tell the same story. When they disagree, a visitor has to decide which one counts.
Read the deeper noteCondition: compare the first screen and the page source. Limit: it does not test conversion or crawler access.
Source note. Captured: July 28, 2026Structured data describes visible facts.
Structured data helps search engines understand visible content. Ryan's note: add matching markup after the facts and explanation are already clear on the page.
Read the deeper noteRead Google's structured-data introduction. Limit: not a claim about AI citations.
Desk rule. Captured: July 28, 2026One useful page can carry a small answer without copying the whole guide.
The short version belongs here when it adds an observation, a source, or context. The original long-form guide remains on Ryan's main site.
Read the deeper noteRead Ryan's GEO guide. Limit: not a replacement guide.
Desk rule. Captured: July 28, 2026Can a person repeat what you sell after the first paragraph?
If the answer depends on a slogan, the page may need a plain-language line before the clever line. That is a writing check, not a markup fix.
Read the deeper noteRead: Can AI read your store?. Limit: not a technical audit.
Desk rule. Captured: July 28, 2026Keep the source next to the claim.
A result without its starting point makes a clean number look larger than it is. A reader should be able to find the condition, date, and evidence without guessing.
Read the deeper noteRead the measurement stack. Limit: not a cause.