Working documents
These playbooks are written for implementation. Each one should help you change a page template, content brief, publishing checklist, or audit workflow.
How to use a playbook
Start with the page or workflow you are actually changing, then choose the playbook that matches the problem. A metadata issue should produce revised titles, descriptions, canonicals, and validation checks. A content structure issue should produce stronger headings, examples, internal links, and a clearer answer for the reader.
The goal is to turn advice into a visible improvement on the site. A useful playbook should leave behind something concrete: a cleaner template, a better brief, a fixed robots or sitemap rule, a content refresh queue, or a repeatable QA step before publishing.
What these workflows protect
Technical SEO and GEO work can become scattered when every article is handled differently. These workflows keep the site consistent across crawlability, metadata, structured data, answer extraction, evidence blocks, and refresh habits.
That consistency matters for readers first. Clear page types, stable URLs, descriptive links, and honest limitations make the site easier to use. They also support the quality bar expected from an advertising-supported publication, where thin pages, confusing navigation, or duplicated intent can weaken the whole site review.
Available playbooks
SEO Implementation Checklist
A step-by-step checklist for titles, descriptions, canonical URLs, headings, internal links, schema, robots rules, sitemap output, and performance.
Metadata and Canonical Examples
Copy-ready examples for HTML templates, Next.js, Astro, WordPress, and static site generators.
GEO Content Structure
Answer-first patterns, evidence blocks, comparison tables, FAQ sections, and source-aware summaries.
llms.txt and AI-Readable Docs
A practical way to publish a concise map of your best pages for AI research tools and answer systems.
