{"id":321760,"date":"2026-06-04T13:54:18","date_gmt":"2026-06-04T13:54:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/coywolf-robots-txt-manager-2\/"},"modified":"2026-06-04T23:04:45","modified_gmt":"2026-06-04T23:04:45","slug":"coywolf-robots-txt-manager","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/coywolf-robots-txt-manager\/","author":115787,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.54","stable_tag":"1.0.54","tested":"7.0","requires":"5.3","requires_php":"7.2","requires_plugins":null,"header_name":"Coywolf Robots.txt Manager","header_author":"Coywolf","header_description":"Manage your robots.txt rules from the WordPress admin \u2014 add, edit, and remove directives on the physical or virtual robots.txt, and disallow unwanted bots by category using the full list from the Cloudflare Bot Directory.","assets_banners_color":"","last_updated":"2026-06-04 23:04:45","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/coywolf.com\/notes\/robots-txt-manager-manage-your-robots-txt-rules-from-the-wordpress-admin\/","header_author_uri":"https:\/\/coywolf.com\/jon-henshaw\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":53,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","changelog"],"tags":{"1.0.52":{"tag":"1.0.52","author":"jonhenshaw","date":"2026-06-04 13:53:44"},"1.0.53":{"tag":"1.0.53","author":"jonhenshaw","date":"2026-06-04 22:32:21"},"1.0.54":{"tag":"1.0.54","author":"jonhenshaw","date":"2026-06-04 23:04:45"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3561079,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3561079,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.52","1.0.53","1.0.54"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3561079,"resolution":"1","location":"assets","locale":"","width":1800,"height":945},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3561079,"resolution":"2","location":"assets","locale":"","width":1800,"height":945},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3561079,"resolution":"3","location":"assets","locale":"","width":1800,"height":945},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3561079,"resolution":"4","location":"assets","locale":"","width":1800,"height":945}},"screenshots":{"1":"The Robots.txt Rules screen in the Coywolf Robots.txt Manager plugin, listing managed rules such as \"Block all the things!\" and several folder and file rules, with each rule's description, the bots it applies to, and its resulting robots.txt directive.","2":"The Edit Rule screen in the Coywolf Robots.txt Manager plugin, configuring a Disallow rule named \"Block all the things!\" for the entire site, with bot categories expanded to select individual Advertising &amp; Marketing crawlers.","3":"The Robots.txt editor in the Coywolf Robots.txt Manager plugin, showing the generated physical robots.txt file with a list of User-agent directives that the plugin parses and optimizes into managed rules.","4":"The Robots.txt Manager plugin Settings page in WordPress, showing access controls for user roles, the choice between Virtual and Physical file modes (with Physical selected and the robots.txt file confirmed as writable), XML sitemap options, and rule comment settings."}},"plugin_section":[],"plugin_tags":[4866,12928,12753,186,1557],"plugin_category":[55],"plugin_contributors":[265832],"plugin_business_model":[],"class_list":["post-321760","plugin","type-plugin","status-publish","hentry","plugin_tags-bots","plugin_tags-crawlers","plugin_tags-robots-txt","plugin_tags-seo","plugin_tags-sitemap","plugin_category-seo-and-marketing","plugin_contributors-jonhenshaw","plugin_committers-jonhenshaw"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/icon-128x128.png?rev=3561079","icon_2x":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/icon-256x256.png?rev=3561079","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/screenshot-1.png?rev=3561079","caption":"The Robots.txt Rules screen in the Coywolf Robots.txt Manager plugin, listing managed rules such as \"Block all the things!\" and several folder and file rules, with each rule's description, the bots it applies to, and its resulting robots.txt directive."},{"src":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/screenshot-2.png?rev=3561079","caption":"The Edit Rule screen in the Coywolf Robots.txt Manager plugin, configuring a Disallow rule named \"Block all the things!\" for the entire site, with bot categories expanded to select individual Advertising &amp; Marketing crawlers."},{"src":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/screenshot-3.png?rev=3561079","caption":"The Robots.txt editor in the Coywolf Robots.txt Manager plugin, showing the generated physical robots.txt file with a list of User-agent directives that the plugin parses and optimizes into managed rules."},{"src":"https:\/\/ps.w.org\/coywolf-robots-txt-manager\/assets\/screenshot-4.png?rev=3561079","caption":"The Robots.txt Manager plugin Settings page in WordPress, showing access controls for user roles, the choice between Virtual and Physical file modes (with Physical selected and the robots.txt file confirmed as writable), XML sitemap options, and rule comment settings."}],"raw_content":"<!--section=description-->\n<p>Coywolf Robots.txt Manager turns robots.txt into a managed list of rules you build from the WordPress admin \u2014 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.<\/p>\n\n<ul>\n<li><strong>Rules table<\/strong> \u2014 every directive as a row with a name and plain-English description, with bulk delete and pagination. Identical directives are consolidated.<\/li>\n<li><strong>Direct editor<\/strong> \u2014 a Robots.txt page shows the current file in an editable box; saving re-parses and optimizes your hand edits into managed rules. A copy button puts the whole robots.txt on your clipboard.<\/li>\n<li><strong>Guided rule editor<\/strong> \u2014 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.<\/li>\n<li><strong>Conflict checking<\/strong> \u2014 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.<\/li>\n<li><strong>Bot catalog<\/strong> \u2014 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.<\/li>\n<li><strong>Curated robots.txt tokens<\/strong> \u2014 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.<\/li>\n<li><strong>Commented output<\/strong> \u2014 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.<\/li>\n<li><strong>Physical or virtual<\/strong> \u2014 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.<\/li>\n<li><strong>Backup &amp; restore<\/strong> \u2014 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).<\/li>\n<li><strong>Import &amp; export<\/strong> \u2014 on the Import \/ Export Rules page, download all rules and settings preferences as one JSON file, then import it to restore them or copy the setup to another site. Import replaces the current rules; sitemap URLs aren't included (they're site-specific).<\/li>\n<li><strong>Optional comments<\/strong> \u2014 the per-rule description comments can be excluded from robots.txt under Settings \u2192 Rule comments, and added back any time.<\/li>\n<li><strong>Role-based access<\/strong> \u2014 under Settings \u2192 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.<\/li>\n<li><strong>Cleans up on import<\/strong> \u2014 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 \/<em>.css and \/<\/em>.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).<\/li>\n<li><strong>XML sitemaps<\/strong> \u2014 add sitemap URLs under Settings \u2192 XML sitemaps (written at the end of robots.txt), or exclude sitemap links entirely.<\/li>\n<li><strong>Owns the virtual robots.txt<\/strong> \u2014 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.<\/li>\n<\/ul>\n\n<h3>Conflict resolution<\/h3>\n\n<p>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:<\/p>\n\n<ul>\n<li>Identical directives that differ only by user-agent are consolidated into one rule listing every agent; duplicate User-agent groups are merged case-insensitively.<\/li>\n<li>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.<\/li>\n<li>If a directive applies to * as well as named bots for the same path, it collapses to just * (the wildcard already covers them).<\/li>\n<li>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.<\/li>\n<li>Deprecated\/unsupported directives are removed (Crawl-delay, Noindex, Nofollow, Host, Request-rate, Visit-time).<\/li>\n<li>SEO-harmful blocks are removed (render-blocking \/<em>.css and \/<\/em>.js, and the overly broad \/wp-content\/).<\/li>\n<li>Syntax is repaired (misspelled directives, a missing colon, a missing leading slash, malformed wildcards).<\/li>\n<li>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.<\/li>\n<\/ul>\n\n<h3>Bot tokens<\/h3>\n\n<p>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 \u2014 its match data is often a URL, the operator's name, or a generic word like \"Bot\" \u2014 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 \u2192 Bytespider, Internet Archive \u2192 archive.org_bot, BrightEdge Bot \u2192 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.<\/p>\n\n<!--section=changelog-->\n<h4>1.0.54<\/h4>\n\n<ul>\n<li>Move Import \/ Export to its own page, exclude sitemap URLs from the export, rename Rules to All Rules, and pad the copy button (#57).<\/li>\n<\/ul>\n\n<h4>1.0.53<\/h4>\n\n<ul>\n<li>Add JSON import\/export for rules and a copy button on the Robots.txt page (#56).<\/li>\n<\/ul>\n\n<h4>1.0.52<\/h4>\n\n<ul>\n<li>Refuse a new rule already covered by a broader Disallow (#55).<\/li>\n<\/ul>\n\n<h4>1.0.51<\/h4>\n\n<ul>\n<li>Update Settings screenshot and caption to show the new Access controls (#54).<\/li>\n<\/ul>\n\n<h4>1.0.50<\/h4>\n\n<ul>\n<li>Keep readme.md in the WordPress.org build so the Documentation page works there (#53).<\/li>\n<\/ul>\n\n<h4>1.0.49<\/h4>\n\n<ul>\n<li>Add role-based access control (Settings \u2192 Access) and clear all Plugin Check warnings (#52).<\/li>\n<\/ul>\n\n<h4>1.0.48<\/h4>\n\n<ul>\n<li>Fix WordPress.org review: get_home_path() for robots.txt path, prefix class names (#51).<\/li>\n<\/ul>\n\n<h4>1.0.47<\/h4>\n\n<ul>\n<li>Fix WordPress.org review issues: dynamic admin-ajax path, no remote calls, matching text domain (#50).<\/li>\n<\/ul>\n\n<h4>1.0.46<\/h4>\n\n<ul>\n<li>CI: upgrade actions to Node 24-native versions (#49).<\/li>\n<\/ul>\n\n<h4>1.0.45<\/h4>\n\n<ul>\n<li>CI: run bundled JS actions on Node 24 (#48).<\/li>\n<\/ul>\n\n<h4>1.0.44<\/h4>\n\n<ul>\n<li>Set distinct Plugin URI and Author URI (#47).<\/li>\n<\/ul>\n\n<h4>1.0.43<\/h4>\n\n<ul>\n<li>Add WordPress.org screenshots + captions (#46).<\/li>\n<\/ul>\n\n<h4>1.0.42<\/h4>\n\n<ul>\n<li>Fix readme Contributors\/Tags header line (#45).<\/li>\n<\/ul>\n\n<h4>1.0.41<\/h4>\n\n<ul>\n<li>Set readme Contributors to jonhenshaw (#44).<\/li>\n<\/ul>\n\n<h4>1.0.40<\/h4>\n\n<ul>\n<li>Fix all WordPress.org Plugin Check errors (#43).<\/li>\n<\/ul>\n\n<h4>1.0.39<\/h4>\n\n<ul>\n<li>Add WordPress.org variant build + gated SVN deploy (#42).<\/li>\n<\/ul>\n\n<h4>1.0.38<\/h4>\n\n<ul>\n<li>Migrate existing rules and robots.txt when a bot token is renamed (#41).<\/li>\n<\/ul>\n\n<h4>1.0.37<\/h4>\n\n<ul>\n<li>Replace 38 guessed bot tokens with the documented user-provided tokens (#40).<\/li>\n<\/ul>\n\n<h4>1.0.36<\/h4>\n\n<ul>\n<li>Exclude bots with no robots.txt token (Link CLI); auto-exclude in the maintenance flow (#39).<\/li>\n<\/ul>\n\n<h4>1.0.35<\/h4>\n\n<ul>\n<li>Update the Cloudflare bot list (+4 bots) with curated tokens (#38).<\/li>\n<\/ul>\n\n<h4>1.0.34<\/h4>\n\n<ul>\n<li>Security and performance audit \u2014 all checks passed (no functional changes) (#37).<\/li>\n<\/ul>\n\n<h4>1.0.33<\/h4>\n\n<ul>\n<li>Add a Documentation page; document conflict resolution + bot-token curation (#36).<\/li>\n<\/ul>\n\n<h4>1.0.32<\/h4>\n\n<ul>\n<li>Own the virtual robots.txt: import &amp; reconcile WordPress's base rules (#35).<\/li>\n<\/ul>\n\n<h4>1.0.31<\/h4>\n\n<ul>\n<li>Use bedrockbot for all Amazon Bedrock AgentCore Browser variants (#34).<\/li>\n<\/ul>\n\n<h4>1.0.30<\/h4>\n\n<ul>\n<li>Set ThousandEyes token to TE\/1.0 (its documented identifier) (#33).<\/li>\n<\/ul>\n\n<h4>1.0.29<\/h4>\n\n<ul>\n<li>Curate robots.txt tokens for all 603 bots + add a bot-list update process (#32).<\/li>\n<\/ul>\n\n<h4>1.0.28<\/h4>\n\n<ul>\n<li>Override Yoast SEO's robots.txt output when this plugin is active (#31).<\/li>\n<\/ul>\n\n<h4>1.0.27<\/h4>\n\n<ul>\n<li>Add a curated AI-crawler supplement so imported AI bots match the catalog (#30).<\/li>\n<\/ul>\n\n<h4>1.0.26<\/h4>\n\n<ul>\n<li>Make the Edit Rule Delete control a bordered red button, aligned with the row (#29).<\/li>\n<\/ul>\n\n<h4>1.0.25<\/h4>\n\n<ul>\n<li>Tint robots.txt directive chips by type (light red Disallow, light green Allow) (#28).<\/li>\n<\/ul>\n\n<h4>1.0.24<\/h4>\n\n<ul>\n<li>Move rule Edit\/Delete into row-actions; add Delete to the edit screen (#27).<\/li>\n<\/ul>\n\n<h4>1.0.23<\/h4>\n\n<ul>\n<li>Space out the physical\/virtual resolver buttons (#26).<\/li>\n<\/ul>\n\n<h4>1.0.22<\/h4>\n\n<ul>\n<li>Match imported User-agents to catalog bots instead of adding them as custom (#25).<\/li>\n<\/ul>\n\n<h4>1.0.21<\/h4>\n\n<ul>\n<li>Pad the Cancel button on the deactivation modal (#24).<\/li>\n<\/ul>\n\n<h4>1.0.20<\/h4>\n\n<ul>\n<li>Security + performance audit: sanitize bot catalog on ingest; cache hot paths (#23).<\/li>\n<\/ul>\n\n<h4>1.0.19<\/h4>\n\n<ul>\n<li>Add an editable Robots.txt page that re-parses rules on save (#22).<\/li>\n<\/ul>\n\n<h4>1.0.18<\/h4>\n\n<ul>\n<li>Back up the original robots.txt before any parse\/import; add a Settings option to exclude per-rule comments (#21).<\/li>\n<\/ul>\n\n<h4>1.0.17<\/h4>\n\n<ul>\n<li>Importer drops cross-domain sitemaps; Rules table bulk delete + pagination; reactivation cleans orphaned comments (#20).<\/li>\n<\/ul>\n\n<h4>1.0.16<\/h4>\n\n<ul>\n<li>Back up robots.txt on activation; offer restore-or-keep on deactivation (#19).<\/li>\n<\/ul>\n\n<h4>1.0.15<\/h4>\n\n<ul>\n<li>Harden robots.txt import: repair syntax, resolve conflicts, drop deprecated\/SEO-bad, fix patterns &amp; sitemaps (#18).<\/li>\n<\/ul>\n\n<h4>1.0.14<\/h4>\n\n<ul>\n<li>Add Rule: show a Cancel button when no Rule Path is selected (#17).<\/li>\n<\/ul>\n\n<h4>1.0.13<\/h4>\n\n<ul>\n<li>Rework Auto-update settings to match the Link Checker auto-run UX (#16).<\/li>\n<\/ul>\n\n<h4>1.0.12<\/h4>\n\n<ul>\n<li>Split editor into Rule Type + Rule Path; move XML sitemaps to Settings; unwrap physical file on deactivate (#15).<\/li>\n<\/ul>\n\n<h4>1.0.11<\/h4>\n\n<ul>\n<li>Per-rule comments in robots.txt; remove import button; block conflicting saves (#14).<\/li>\n<\/ul>\n\n<h4>1.0.10<\/h4>\n\n<ul>\n<li>Fix stuck readme.txt Stable tag (1.0.0) and make the release bump robust (#13).<\/li>\n<\/ul>\n\n<h4>1.0.9<\/h4>\n\n<ul>\n<li>Sitemap URL editor; default \"All robots\" off + lock for whole-site rules; manage existing robots.txt on activation (#12).<\/li>\n<\/ul>\n\n<h4>1.0.8<\/h4>\n\n<ul>\n<li>Fix duplicated rule on physical\u2192virtual switch; delete file on that switch (#11).<\/li>\n<\/ul>\n\n<h4>1.0.7<\/h4>\n\n<ul>\n<li>Updater: Atom-feed fallback + visible failure when GitHub API is rate-limited (#10).<\/li>\n<\/ul>\n\n<h4>1.0.6<\/h4>\n\n<ul>\n<li>Sitemap rule type, auto-switch to virtual, Link-Checker-style auto-update with email (#8).<\/li>\n<\/ul>\n\n<h4>1.0.5<\/h4>\n\n<ul>\n<li>Fix stray Disallow: \/ under User-agent: * when a rule mixes * with specific bots (#7).<\/li>\n<\/ul>\n\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>Sitemap at end of robots.txt; resolver button labels + spacing; scrollable preview (#6).<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Rules UX + round 2: consolidation, conflicts, Yoast override, sitemap-exclusion, physical resolver (#5).<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>\"Import from robots.txt\" appears only when a physical file exists; in virtual mode existing rules are imported automatically on first use. On install, an existing physical robots.txt is managed by default and its rules imported.<\/li>\n<li>The current robots.txt is always shown on the Rules page (white background, scrolls on overflow); heading renamed to \"Current robots.txt\".<\/li>\n<li>robots.txt output consolidates user-agents that share the same rule under stacked User-agent: lines.<\/li>\n<li>Rule descriptions say \"selected\" where they refer to the chosen crawlers.<\/li>\n<li>After a bot-list update, newly added bots are checked in a rule only if its whole category was selected.<\/li>\n<li>Bot category lists are indented with the checkbox in the list-marker position so wrapped lines hang-indent.<\/li>\n<li>New rules are checked for conflicts before saving, with a dialog to fix or save anyway.<\/li>\n<li>Settings: option to exclude XML sitemap link(s) from robots.txt (also suppresses the one WordPress adds).<\/li>\n<li>If Yoast SEO is active, this plugin overrides it and controls robots.txt.<\/li>\n<li>When in virtual mode while a physical robots.txt exists, the Rules page warns and offers to switch to physical (import the file's rules), switch to physical (overwrite the file with the current rules), or delete the physical file.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<\/ul>","raw_excerpt":"Manage robots.txt from the WordPress admin: build rules, block bots by category, and serve a physical or virtual robots.txt.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/321760","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=321760"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jonhenshaw"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=321760"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=321760"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=321760"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=321760"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=321760"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=321760"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}