Playbooks
Patterns are useful. But teams often need something even more operational: a persona-based decision guide.
That is the purpose of the playbooks section.
Each playbook starts from a real site profile, a real business priority, and a real main risk.
What these playbooks are for
Use playbooks when the question is not "what does this preset do?" but rather:
- what should my type of site actually do first?
- what are the most common mistakes for my profile?
- what modules matter most for my publishing model?
- what should I leave alone until there is evidence I need stricter controls?
Available playbooks
- Local business visibility
- Publisher archive and AI boundaries
- WooCommerce crawl hygiene
- Agency multisite rollout
How to use a playbook
- identify your site profile;
- confirm your main business priority;
- confirm your main crawl or bot risk;
- start with the recommended preset or module sequence;
- apply the caveats before publishing.
Important rule
A playbook is not a promise of outcome.
It is a decision aid designed to lower ambiguity and reduce random configuration choices.