Edition Overview

Better Robots.txt is distributed in three editions. Each edition unlocks additional capabilities across the 14 wizard steps. The product surface is identical — what changes is the depth of control available at each step.

Free

Free is the right choice when the goal is a safer default robots.txt and a guided starting point. It covers:

• the Essential preset;
• the core search-engine visibility tiers (Minimal and Recommended);
• basic Bad Bots Protection;
• the Core WordPress Protection rules;
• the Review & Save preview;
• the standard Resources & Assets and Ads & Revenue allow rules.

For most small WordPress sites with no specific AI or protection-first requirement, Free is enough.

Pro

Pro is the right choice when deeper governance matters. It adds:

• the AI-First preset and the Custom preset;
• deeper AI & LLM Governance controls;
• broader SEO Tool Protection coverage;
• optional llms.txt support;
• the Extended Visibility preset and Custom Control per-bot UI;
• Advanced Controls for module-level overrides;
• the Physical File mode for robots.txt delivery.

Pro fits publishers, AI-aware sites, and operators who want module-level adjustments without going all the way to protection-first defaults.

Premium

Premium is the right choice when protection-first or strict posture is needed. It adds, on top of everything Pro offers:

• the Fortress preset;
• Block Archiving for archive and Wayback control;
• the broader AI-curated Bad Bots Protection list;
• the strictest combinations across categories, suitable for sensitive or archive-averse sites.

How to decide

Use the Mode Selection page to pick the right preset for the site profile. The edition matters mostly because some presets and some advanced toggles are gated:

• Essential → available on every tier;
• AI-First → Pro and Premium;
• Fortress → Premium only;
• Custom → Pro and Premium.

For pricing details, see the Pricing page.

What edition does not change

The edition does not change:

• the underlying robots.txt specification;
• crawler obedience — no edition can compel a bot to follow the published rules;
• the need for a separate WAF or infrastructure layer when the real problem is abusive request volume.

Related

• Presets overview
• Mode Selection
• Pricing
• Pattern Library