Persona playbooks
Use this section when you need the fastest route from a site profile to the right Better Robots.txt reading path.
This section is different from two nearby sections:
- /playbooks/ gives scenario-based guidance by site type and business priority.
- /governance/playbooks/ gives role-based reading paths for SEO, editorial, ecommerce, agency, and legal or ops teams.
- /personas/ is the shortest path when you want to know what to read first, which preset to test first, and what to leave alone until there is evidence.
Quick chooser
| If this sounds like you | Start here | Best first preset | Read next |
|---|---|---|---|
| You run a brochure, consultant, clinic, restaurant, or other local business site | Local business owner | Essential | Quick Start and Small Business on Essential |
| You run a publisher, newsroom, editorial archive, or content-heavy WordPress site | WordPress publisher | AI-First | Publisher archive and AI boundaries |
| You run a WooCommerce store with filter, cart, search, or crawl-noise issues | WooCommerce operator | Essential or AI-First | WooCommerce Crawl Control |
| You deploy rules across many client sites | Agency implementer | Custom | Agency multisite rollout |
| You lead crawl strategy, migrations, or high-risk policy decisions | Technical SEO lead | Matrix-driven | Decision matrix and Output constraints |
Persona paths
Local business owner
Start here when the main job is staying discoverable without turning a small site into an overblocked configuration project.
WordPress publisher
Start here when search visibility must stay open while AI usage, archive posture, and editorial boundaries become more explicit.
WooCommerce operator
Start here when the real problem is crawl hygiene: cart, checkout, filters, search URLs, and other low-value store paths.
Agency implementer
Start here when repeatability matters, but one preset for every client would be a strategic mistake.
Technical SEO lead
Start here when you need a tighter decision frame, clearer caveats, and better separation between policy signals and technical enforcement.
Important rule
Start with the lightest posture that solves the real problem.
Then escalate only when the site has a real archive, crawl-cost, scraping, or AI-policy boundary to manage.