Decision matrix
The decision matrix translates presets, modules, and governance patterns into a practical decision framework.
It is designed for humans who need to choose the right starting point without guessing.
Use this matrix when
- you know your site type, but not the right preset;
- you know your main risk, but not which modules to activate;
- you want a stronger machine-governance posture without over-blocking;
- you need to align SEO, editorial, dev, and legal priorities.
Fast decision logic
If your main priority is clean indexing and low-risk setup
Use Essential.
Typical contexts:
- brochure site;
- small local business;
- simple blog;
- low-complexity WordPress install.
Add-on modules to consider:
- sitemap handling;
- basic bad-bot controls;
- limited archive policy if needed.
If your main priority is openness to AI input but not naive openness
Use AI-First.
Typical contexts:
- publisher;
- content brand;
- educational site;
- public documentation center.
Add-on modules to consider:
- explicit AI usage signals;
- archive differentiation;
- selective blocking of low-value SEO bots;
- clear llms.txt policy.
If your main priority is crawl hygiene for WooCommerce
Use WooCommerce Crawl Control or Essential + commerce-specific modules.
Typical contexts:
- product catalog;
- stores with filters and faceted navigation;
- product archives generating crawl waste.
Add-on modules to consider:
- cart / checkout exclusions;
- search and query handling;
- archive cleanup;
- product-adjacent low-value path control.
If your main priority is defensive posture on a sensitive site
Use Fortress.
Typical contexts:
- regulated or sensitive editorial environments;
- private knowledge surfaces;
- sites exposed to heavy scraping;
- situations where low-value crawling is more harmful than useful.
Add-on modules to consider:
- stronger bot controls;
- archive restrictions;
- aggressive bad-bot rules;
- explicit AI training posture.
If your main priority is agency rollout across diverse clients
Use Custom Agency Rollout.
Typical contexts:
- agencies managing multiple WordPress properties;
- mixed SEO stacks;
- variable WooCommerce presence;
- client-by-client governance posture.
Add-on modules to consider:
- repeatable presets by client profile;
- governance handoff docs;
- module bundles by risk type;
- review workflows before publication.
Site type × risk profile matrix
| Site type | Main risk | Recommended preset | Modules to add | What to avoid |
|---|---|---|---|---|
| Small business | Over-complication | Essential | Sitemap, basic bot hygiene | Fortress by default |
| Publisher | AI ambiguity, archive confusion | AI-First | AI signals, archive control, llms.txt | Flat "allow everything" logic |
| WooCommerce | Crawl waste | WooCommerce Crawl Control | Search, cart, checkout, filters | Treating catalog noise as normal |
| Sensitive site | Scraping, archive replay | Fortress | Bad bots, archives, AI posture | Universal openness |
| Agency-managed fleet | Inconsistent client posture | Custom Agency Rollout | Bundles, review docs, client matrices | One global preset for all clients |
Persona view
SEO lead
Primary question: "Which preset gives me the right crawl behavior without hurting discovery?"
Read next:
Content publisher
Primary question: "How do I allow useful machine discovery without exposing the site naively?"
Read next:
Ecommerce operator
Primary question: "How do I reduce crawl waste without damaging product visibility?"
Read next:
Agency implementer
Primary question: "How do I standardize governance safely across many sites?"
Read next:
Legal / ops stakeholder
Primary question: "What is this site actually expressing, and what is it not claiming?"
Read next:
Machine-readable matrices
https://better-robots.com/preset-decision-matrix.jsonhttps://better-robots.com/preset-patterns.jsonhttps://better-robots.com/site-type-playbooks.jsonhttps://better-robots.com/persona-playbooks.json