Tutorials
Procedures with real code. Schema that validates, answer engine audits, and conversion tracking that survives a platform change.
Read the tutorials
Resources
None of this is gated behind a form except the report, and that is only because a person has to write it. The method is published because the method is not the moat. Running it every week, measuring it honestly, and cutting what does not work is the moat.
If something here is wrong or out of date, tell us. We would rather correct it than leave a bad instruction in circulation.
What is here
Procedures with real code. Schema that validates, answer engine audits, and conversion tracking that survives a platform change.
Read the tutorialsPaste JSON-LD and check structure, types, and required properties in your browser. Nothing is uploaded.
Open the validatorLength checks and a live result preview for title tags and meta descriptions.
Open the checkerOur documented method for local visibility. Six pillars, four phases, and a week by week implementation guide.
Read the blueprintPlain definitions for the terms that get used loosely, each linked to the page where the work happens.
Open the glossaryDirect answers to the questions that come up in every first conversation, grouped into five clusters.
Browse answersLonger pieces organised into pillar and cluster sets rather than a chronological feed.
Read the blogA human-written review of rendering, indexation, internal links, and answer engine readiness.
Request the reportStart with the answers library to frame the problem, then run the answer engine audit tutorial on one important page. That combination tells you within an hour whether your site has a structure problem, a content problem, or neither.
Related
A diagnosis is written, specific, and yours to keep whether or not we work together.