Contact, about, and the trust surfaces nobody audits
How to audit the about, contact, editorial, and policy pages behind a site, and keep organization details consistent across pages, footer, and markup.
18 posts
How to audit the about, contact, editorial, and policy pages behind a site, and keep organization details consistent across pages, footer, and markup.
How to make a pricing page readable by machines: prices as text, Offer markup that matches it, real comparison tables, dated price changes, and billing FAQs.
Why outbound links to primary sources help readers and make claims checkable, which rel values Google documents, and what not to link.
How to write figures, units, ranges, and dates so a lifted sentence still means the same thing: the rules, the fixes, and how to find the vague ones at scale.
Google documents query fan-out in AI Overviews and AI Mode: one question becomes many searches. What it means for sub-questions, page scope and internal links.
How to write Organization JSON-LD with a logo, sameAs links to your official profiles, and one consistent name, then check it by hand and across a site.
A visible byline, an author page, and Person JSON-LD that agrees with both. What Google documents for author markup, and how to audit it across a site.
The page-side half of GEO: citable sentences, authorship, entity clarity, honest dates, trust surfaces, and linking out, mapped to signals you can check.
The full AEO and GEO audit loop: access, extraction, answer-readiness, citability and entity, then measurement. By hand, at scale, and re-crawled to prove it.
What datePublished and dateModified mean, what Google's date guidance asks for, why a bumped date is a trust failure, and how to audit dates across a site.
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.
Should you block GPTBot? Which AI agents train, which search, which fetch for a user, what each block costs, and four robots.txt policies to copy.