Coywolf Robots.txt Manager

Coywolf Robots.txt Manager turns robots.txt into a managed list of rules you build from the WordPress admin — no FTP, no hand-editing. It ships the full catalog of bots from the Cloudflare Bot Directory, grouped by category (AI Crawler, Search Engine Crawler, Advertising, Security, and more), so you can disallow whole categories of unwanted bots with a click.

• Rules table — every directive as a row with a name and plain-English description, with bulk delete and pagination. Identical directives are consolidated.
• Direct editor — a Robots.txt page shows the current file in an editable box; saving re-parses and optimizes your hand edits into managed rules.
• Guided rule editor — choose a Rule Type (Disallow or Allow) and a Rule Path (folder, prefix, file type, query string, allow-exception, and more); the editor builds the correct directive, with auto-filled name and description, plus a URL testing tool.
• Conflict checking — every add or edit is checked against existing rules; if it duplicates or contradicts one, the editor explains the clash and won’t save until it’s resolved.
• Bot catalog — every bot from the Cloudflare Bot Directory, plus a curated set of well-known AI crawlers it doesn’t list yet (ClaudeBot, CCBot, Google-Extended, Applebot-Extended, and more), grouped by category, with select-all per category. The catalog ships with the plugin and is refreshed through plugin updates.
• Curated robots.txt tokens — the exact User-agent token each bot obeys is curated for all 600+ bots (the directory’s own match data is often a URL, operator name, or generic word), so rules block the right token and imported robots.txt files match the right bot.
• Commented output — each rule is written as its own section prefixed with a comment carrying its name and description; a rule’s bots are stacked under User-agent: lines with the directive written once.
• Physical or virtual — write a real robots.txt in your site root, or let WordPress serve it virtually. On install, an existing physical file is detected, managed, and imported automatically.
• Backup & restore — your original robots.txt is captured before the plugin reads, parses, or rewrites anything; on deactivation it asks whether to restore that original or keep the rules it built (markers removed).
• Optional comments — the per-rule description comments can be excluded from robots.txt under Settings → Rule comments, and added back any time.
• Role-based access — under Settings → Access, choose which user roles can see and use the plugin; Administrator is always allowed and can’t be locked out. Only administrators can change the access list and the serving mode.
• Cleans up on import — fixes misspelled directives, missing colons, and missing leading slashes; consolidates duplicate user-agent groups and resolves Allow/Disallow conflicts; strips deprecated/unsupported directives (Crawl-delay, Noindex, Nofollow, Host, Request-rate, Visit-time); removes render-blocking /.css and /.js blocks and the overly broad /wp-content/; fixes malformed wildcards; and makes Sitemap links absolute and de-duplicated, dropping any that point at a different domain (also handles a UTF-8 BOM and Google’s 500 KiB limit).
• XML sitemaps — add sitemap URLs under Settings → XML sitemaps (written at the end of robots.txt), or exclude sitemap links entirely.
• Owns the virtual robots.txt — in virtual mode the plugin serves the whole file. WordPress’s own default rules (Disallow: /wp-admin/) are imported and reconciled into your managed rules when you activate or switch to virtual (WordPress’s rules win, so its “*” rule absorbs a matching per-bot rule), and WordPress stops adding a duplicate block on top. Other SEO plugins’ additions (e.g. Yoast) are excluded too. Physical mode is served by WordPress directly.

Conflict resolution

When rules are imported, or you hand-edit the Robots.txt page and save, the plugin re-parses everything and resolves conflicts automatically with opinionated, deterministic decisions:

• Identical directives that differ only by user-agent are consolidated into one rule listing every agent; duplicate User-agent groups are merged case-insensitively.
• When an agent both allows and disallows the same path, the later rule wins, and a blanket Disallow: / is dropped for an agent that has more specific rules.
• If a directive applies to * as well as named bots for the same path, it collapses to just * (the wildcard already covers them).
• In virtual mode WordPress’s own User-agent: * base rules (the /wp-admin/ block) win and absorb any matching per-bot rule, and are served once instead of duplicated on top.
• Deprecated/unsupported directives are removed (Crawl-delay, Noindex, Nofollow, Host, Request-rate, Visit-time).
• SEO-harmful blocks are removed (render-blocking /.css and /.js, and the overly broad /wp-content/).
• Syntax is repaired (misspelled directives, a missing colon, a missing leading slash, malformed wildcards).
• Sitemap links are made absolute and de-duplicated (preferring https); cross-domain ones are dropped; a UTF-8 BOM is stripped and Google’s 500 KiB limit is honored.

Bot tokens

Blocking a bot only works if robots.txt uses the exact User-agent token that bot obeys. The bundled Cloudflare Bot Directory isn’t reliable for this — its match data is often a URL, the operator’s name, or a generic word like “Bot” — so every one of the 600+ bots has a curated robots.txt token, researched against each operator’s documentation and the product token in its real user-agent (e.g. Toutiao → Bytespider, Internet Archive → archive.org_bot, BrightEdge Bot → BrightEdge). Each entry records the variant spellings that should map to it, so importing an existing robots.txt matches the right catalog bot. The tokens are bundled with the plugin and kept current through plugin updates. Bots that publish no robots.txt-targetable token (e.g. “signed agents” that identify cryptographically) are left out of the list, since robots.txt can’t target them.