Presets
Presets help you start from a policy model instead of a blank robots.txt.
For many WordPress websites, the preset is the smartest place to begin. You can refine later.
For most websites, start with Essential.
Preset decision matrix
| Site profile | Main priority | Recommended preset | Why |
|---|---|---|---|
| Small business site | stay discoverable, reduce obvious waste | Essential | proportionate, safe default |
| Publisher or editorial site | clarify AI usage without hard lockdown | AI-First | search visibility plus AI policy clarity |
| WooCommerce store | reduce waste and keep product pages open | Essential or AI-First | category and transactional hygiene matter more than aggressive blocking |
| Sensitive or archive-averse site | stronger restriction and archive control | Fortress | protection-first starting posture |
| Agency or advanced operator | client-specific composition | Custom | module-level control and reusable workflows |
Essential
Essential is the default starting point for most WordPress sites.
Use it when you want:
- safer defaults
- a public discovery model
- obvious low-value path cleanup
- minimal complexity
Related pattern: Small Business on Essential
AI-First
AI-First is best when the site wants a clearer machine-readable position on search, answer-generation use, and training.
Use it when:
- content is central
- AI policy matters publicly
llms.txtmakes sense- the site wants better separation between machine uses
Related pattern: Publisher on AI-First
Fortress
Fortress is best when archive exposure, scraping sensitivity, or a more restrictive posture matters more than broad openness.
Use it when:
- archive control matters
- stronger bot restriction is justified
- the site accepts a more protection-first trade-off
Related pattern: Fortress for Sensitive Sites
Custom
Custom is best when you already understand the policy trade-offs and want to compose the file module by module.
Use it when:
- you are an agency
- you manage many site types
- you need explicit client-by-client differences
Related pattern: Custom Rollout for Agencies
Common mistakes
- choosing Fortress too early without understanding the trade-offs
- expecting a preset to behave like a firewall
- overblocking social or useful discovery bots without a clear reason
- starting with Custom before understanding the model