Signal vs enforcement for AI crawlers
This is the conceptual foundation for AI crawler governance. Once you understand the signal/enforcement distinction, see AI visibility controls for the full technical matrix, then manage AI crawlers on WordPress for implementation.
A mature AI-governance workflow starts by separating signal from enforcement. Signals are still valuable. They clarify posture, reduce ambiguity, and create a cleaner public policy surface. But they should never be mistaken for hard control.
What counts as signal
robots.txt, named crawler rules, AI usage signals, and llms.txt are all public signals. They shape interpretation and expected machine behavior.
What counts as enforcement
Signed-agent verification, WAF rules, edge controls, runtime inspection, and infrastructure-level blocking belong to the enforcement layer.
Why the distinction matters for Better Robots.txt
The plugin is strongest when used honestly: as a publication and governance layer that clarifies intent, not as a false promise of total control.
What Better Robots.txt is not
Better Robots.txt is not a WAF, not a signed-agent verification system, not a legal enforcement layer, and not a guarantee that every crawler will comply. It publishes a clearer WordPress policy surface and a safer workflow for the parts you can actually govern.