Each one is a procedure with real code and real checks, written from work we do for clients rather than from a summary of somebody else's article. If a step has a common failure mode, it is named in the pitfalls section rather than left for you to discover.
Pair them with the free tools if you want to check your output as you go.
Published
Start here
Intermediate
Write schema markup that validates
Most schema markup on small business pages is broken in ways Google Search Console never flags. This walks through building a single connected JSON-LD graph for Organization, LocalBusiness, Service, FAQPage, and BreadcrumbList, and testing it properly.
Answer engines like ChatGPT, Perplexity, and Google's AI Overviews extract short passages, not whole pages. This is a manual, repeatable audit process using curl and a browser to check whether a page is actually extractable, in under twenty minutes per page.
Conversion tracking breaks quietly: a redesign changes a button's DOM structure, consent mode gets misconfigured, or two tags fire the same event twice. This walks through building tracking that keeps working after the next site change, and setting realistic expectations for cross-platform numbers.
Learn to audit a page for answer engines first. It costs an hour, it needs no deployment, and it tells you whether your schema and tracking problems are worth solving yet. Structure comes before instrumentation.
Related
Use these alongside
Want this done rather than learned
We run these procedures as part of a program, with the checks automated where they can be.