What goes wrong
Machine-readable agent files appear on checklists, but dropping a static llms.txt without preview, approval, or conflict checks creates new risk.
Agent Files covers llms.txt, agent-map.json, preview, approval, publish state, freshness, kill switch, and rollback where implemented — with llms.txt treated as emerging, not a ranking or citation guarantee.
Govern llms.txt and agent-map.json with preview, approval, and rollback where implemented — llms.txt is emerging, not a ranking guarantee.
Source facts
Public pages and policies
Preview file
llms.txt or agent-map draft
Approved publication
Owner-approved artifact
Machine-readable agent files appear on checklists, but dropping a static llms.txt without preview, approval, or conflict checks creates new risk.
WordPress operators who want governed machine-readable files with preview and approval, and evaluators who need to see whether public agent files exist and match owner intent.
WordPress paths support preview, approval, publish state, freshness, kill switch, and last-known-good on the free local edition without payment lock. Shopify does not ship agent-file checks; store edits stay in Shopify Admin.
Find public llms.txt and agent-map.json routes and physical conflicts.
Generate deterministic preview content from approved evidence selections.
Review exact output before anything publishes.
Owner gate — publish only after explicit approval.
Kill switch and last-known-good where implemented on WordPress.
Illustrative: llms.txt draft preview — 12 lines, owner excluded /promo-archive/
Illustrative: agent-map.json published — last approved timestamp where stored
Kill switch: available on WordPress — reverts to last-known-good where implemented
Run a free scan and find out in about two minutes. No card, no code, and nothing changes without your OK.