{"id":312878,"date":"2026-06-08T05:53:18","date_gmt":"2026-06-08T05:53:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/agentic-seo-visibility\/"},"modified":"2026-06-08T05:52:41","modified_gmt":"2026-06-08T05:52:41","slug":"agentic-seo-visibility","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/agentic-seo-visibility\/","author":23232006,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.7.5","stable_tag":"0.7.5","tested":"7.0","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Agentic SEO for Visibility","header_author":"rankth","header_description":"Connect your WordPress site to the Visibility service at https:\/\/app.visibility.so so AI agents in your Visibility project can audit and publish content directly. Every write action is gated by an approval inbox inside WP admin \u2014 pair once with a short code, then review what the AI wants to do before it happens.","assets_banners_color":"","last_updated":"2026-06-08 05:52:41","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/app.visibility.so","header_author_uri":"https:\/\/visibility.so","rating":0,"author_block_rating":0,"active_installs":0,"downloads":44,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.7.5":{"tag":"0.7.5","author":"rankth","date":"2026-06-08 05:52:41"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3564402,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3564402,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.7.5"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Agentic SEO \u2192 Connection, paired state, showing the connected company + project, last-seen heartbeat, and plugin version."}},"plugin_section":[],"plugin_tags":[266129,195933,210511,181641,186],"plugin_category":[55],"plugin_contributors":[239488],"plugin_business_model":[],"class_list":["post-312878","plugin","type-plugin","status-publish","hentry","plugin_tags-agentic-seo","plugin_tags-ai-content","plugin_tags-ai-writer","plugin_tags-content-automation","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-rankth","plugin_committers-rankth"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/agentic-seo-visibility\/assets\/icon-128x128.png?rev=3564402","icon_2x":"https:\/\/ps.w.org\/agentic-seo-visibility\/assets\/icon-256x256.png?rev=3564402","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p><strong>Agentic SEO for Visibility<\/strong> is the official WordPress plugin for <a href=\"https:\/\/app.visibility.so\">Visibility<\/a>, a SaaS platform that runs AI agents to audit websites, generate SEO-optimised content, and publish it directly to WordPress. Pair your site with your Visibility project in under a minute using a short code \u2014 no Application Passwords, no per-user API keys, and no copy-pasting drafts out of an AI tool.<\/p>\n\n<h4>Why use this plugin<\/h4>\n\n<ul>\n<li><strong>No Application Password required.<\/strong> Pairing exchanges a one-time short code for a shared site token, so the plugin and Visibility can talk without a WordPress user password ever leaving your site.<\/li>\n<li><strong>Built for agentic SEO workflows.<\/strong> Visibility's AI agents can list, draft, update, schedule, and publish posts on your behalf \u2014 including categories, tags, featured images, and excerpts.<\/li>\n<li><strong>Drafts by default; publishes only when you allow it.<\/strong> Every post is saved as a WordPress draft unless you've enabled \"Allow publishing\" on the agent in your Visibility project, so a human can always review AI-written content before it goes live.<\/li>\n<li><strong>Compatible with Yoast SEO, Rank Math, and AIOSEO.<\/strong> Posts go through the standard WordPress post-save flow, so SEO-plugin meta boxes, schema generation, and sitemap entries populate the same way they do for posts you write by hand.<\/li>\n<li><strong>Works on any WordPress 6.0+ install.<\/strong> No special PHP extensions, no server tweaks, no host control-panel toggles to flip.<\/li>\n<li><strong>Open source (GPLv2).<\/strong> Plugin source lives at <a href=\"https:\/\/github.com\/doable-team\/agentic-seo-for-visibility\">github.com\/doable-team\/agentic-seo-for-visibility<\/a>.<\/li>\n<\/ul>\n\n<h4>How it works<\/h4>\n\n<ol>\n<li>In your Visibility project, click <strong>Connect via plugin<\/strong> and copy the short pairing code (for example <code>VIS-A7K9-XB<\/code>).<\/li>\n<li>Install and activate this plugin, then open <strong>Agentic SEO \u2192 Connection<\/strong> and paste the code.<\/li>\n<li>Your project and this site are paired. AI agents can now read, draft, and (when enabled) publish WordPress content here.<\/li>\n<\/ol>\n\n<p>You can disconnect at any time from Agentic SEO \u2192 Connection, or from the Visibility dashboard. A Visibility account at <a href=\"https:\/\/app.visibility.so\">app.visibility.so<\/a> is required. See the <strong>External services<\/strong> section below for the full list of network calls this plugin makes.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin connects your WordPress site to <strong>Visibility<\/strong>, an external SaaS service at https:\/\/app.visibility.so. A Visibility account is required. The plugin makes the following outbound HTTPS requests from your site:<\/p>\n\n<ol>\n<li><p><strong>POST https:\/\/app.visibility.so\/api\/wordpress\/plugin\/pair<\/strong> \u2014 sent once when you submit a pairing code on the Agentic SEO \u2192 Connection screen. Body includes: the pairing code, your site URL, site name, WordPress version, and the installed plugin version. Response contains a shared site token plus the connected company + project IDs and names so the plugin can display them.<\/p><\/li>\n<li><p><strong>POST https:\/\/app.visibility.so\/api\/wordpress\/plugin\/heartbeat<\/strong> \u2014 sent at most once per day from WP-Cron while the plugin is paired. Body includes the installed plugin version; the shared site token is sent in the <code>Authorization: Bearer<\/code> header. Used to refresh the \"Last seen\" timestamp and pick up renames of the connected company or project on Visibility's side.<\/p><\/li>\n<li><p><strong>POST https:\/\/app.visibility.so\/api\/wordpress\/plugin\/disconnect<\/strong> \u2014 sent when you click Disconnect on the Agentic SEO \u2192 Connection screen. Body includes the installed plugin version; the shared site token is sent in the <code>Authorization: Bearer<\/code> header. Tells Visibility to remove your site from the project. Local cleanup proceeds even if Visibility is unreachable.<\/p><\/li>\n<\/ol>\n\n<p>Inbound requests from Visibility, authenticated with the shared site token, reach the plugin at <code>\/wp-json\/visibility\/v1\/*<\/code> and are used by your Visibility project's agents to read, draft, publish, update, or delete posts; manage categories, tags, and media; and check site health. No content leaves your site automatically \u2014 content only travels on agent-initiated requests originating from the Visibility project this site is paired to.<\/p>\n\n<p>Service URL: https:\/\/app.visibility.so\nTerms of service &amp; privacy policy: linked from the Visibility dashboard footer.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>agentic-seo-visibility<\/code> folder to the <code>\/wp-content\/plugins\/<\/code> directory, or install through the WordPress Plugins screen.<\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> menu.<\/li>\n<li>Go to <strong>Agentic SEO \u2192 Connection<\/strong> and follow the pairing instructions.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20to%20create%20an%20application%20password%3F\"><h3>Do I need to create an Application Password?<\/h3><\/dt>\n<dd><p>No. Pairing produces a shared site token that the plugin uses \u2014 no WordPress user password is involved at any point, and you don't need to enable Application Passwords in your WP user profile.<\/p><\/dd>\n<dt id=\"can%20ai%20agents%20publish%20to%20wordpress%20automatically%20through%20this%20plugin%3F\"><h3>Can AI agents publish to WordPress automatically through this plugin?<\/h3><\/dt>\n<dd><p>Yes, when you allow it. Each Visibility agent has an \"Allow publishing\" toggle in the Visibility dashboard. With it on, the agent publishes posts directly. With it off (the default), every save is forced to draft so a human reviews and publishes manually.<\/p><\/dd>\n<dt id=\"can%20i%20keep%20ai%20content%20in%20draft-only%20mode%3F\"><h3>Can I keep AI content in draft-only mode?<\/h3><\/dt>\n<dd><p>Yes \u2014 that's the default behaviour. Without the \"Allow publishing\" toggle, every post the AI agent creates or updates is saved as a WordPress draft. You publish manually from wp-admin when you're satisfied with the content.<\/p><\/dd>\n<dt id=\"what%20can%20a%20visibility%20ai%20agent%20do%20on%20my%20wordpress%20site%3F\"><h3>What can a Visibility AI agent do on my WordPress site?<\/h3><\/dt>\n<dd><p>Through the plugin's REST surface (<code>\/wp-json\/visibility\/v1\/*<\/code>), AI agents can list, create, update, and delete posts; manage categories and tags; upload media and set featured images; and read site health info (post counts, WP version, timezone). Nothing outside that \u2014 no theme files, no user accounts, no general WordPress settings.<\/p><\/dd>\n<dt id=\"will%20this%20ai%20content%20plugin%20slow%20down%20my%20wordpress%20site%3F\"><h3>Will this AI content plugin slow down my WordPress site?<\/h3><\/dt>\n<dd><p>No. The plugin adds a small set of authenticated REST endpoints that only respond when called by Visibility, plus one cron heartbeat that runs once a day. There's no extra JavaScript or CSS on the public side of your site and no background polling.<\/p><\/dd>\n<dt id=\"is%20this%20compatible%20with%20yoast%20seo%2C%20rank%20math%2C%20aioseo%2C%20or%20other%20seo%20plugins%3F\"><h3>Is this compatible with Yoast SEO, Rank Math, AIOSEO, or other SEO plugins?<\/h3><\/dt>\n<dd><p>Yes. Posts created by AI agents go through WordPress's standard post-save flow, so SEO-plugin meta boxes, structured-data \/ schema generation, and XML sitemap entries populate the same way they do for posts you write by hand. You can configure agents on the Visibility side to populate Yoast \/ Rank Math \/ AIOSEO fields directly via post meta.<\/p><\/dd>\n<dt id=\"does%20this%20work%20with%20wordpress%20multisite%3F\"><h3>Does this work with WordPress multisite?<\/h3><\/dt>\n<dd><p>Yes. Each subsite pairs independently with its own Visibility project. Network-activate the plugin or activate it per subsite; the pairing flow runs at the subsite level.<\/p><\/dd>\n<dt id=\"can%20i%20use%20the%20same%20wordpress%20site%20with%20multiple%20visibility%20projects%3F\"><h3>Can I use the same WordPress site with multiple Visibility projects?<\/h3><\/dt>\n<dd><p>Each WordPress site pairs with one Visibility project at a time. Disconnect from Agentic SEO \u2192 Connection and re-pair when you need to move the site to a different project.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20the%20pairing%20code%20expires%20before%20i%20paste%20it%3F\"><h3>What happens if the pairing code expires before I paste it?<\/h3><\/dt>\n<dd><p>Pairing codes are valid for 10 minutes and are single-use. If yours times out, click <strong>Generate a new code<\/strong> in your Visibility project to mint another one \u2014 there's no penalty and the old code is discarded automatically.<\/p><\/dd>\n<dt id=\"what%20data%20does%20this%20plugin%20send%20to%20visibility%3F\"><h3>What data does this plugin send to Visibility?<\/h3><\/dt>\n<dd><p>On pairing and once a day for heartbeats, the plugin sends your site URL, site name, WordPress version, and the installed plugin version. Post content only travels when one of your AI agents creates or updates a post in WordPress \u2014 and that always originates from a Visibility project you control. See the <strong>External services<\/strong> section below for the precise endpoint list.<\/p><\/dd>\n<dt id=\"how%20do%20i%20uninstall%20this%20ai%20publishing%20plugin%3F\"><h3>How do I uninstall this AI publishing plugin?<\/h3><\/dt>\n<dd><p>Deactivate it from the Plugins screen, then delete. On deactivation the daily heartbeat cron is unscheduled; on delete the pairing token (<code>visibility_site_token<\/code>) and cached company \/ project names are removed from <code>wp_options<\/code>. Your data in your Visibility project is untouched \u2014 disconnect from this plugin <strong>before<\/strong> deleting if you also want Visibility to forget about this site.<\/p><\/dd>\n<dt id=\"what%20wordpress%20and%20php%20versions%20does%20it%20require%3F\"><h3>What WordPress and PHP versions does it require?<\/h3><\/dt>\n<dd><p>WordPress 6.0 or newer and PHP 7.4 or newer. Tested up to WordPress 7.0.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.7.5<\/h4>\n\n<ul>\n<li>Polished the top-level <strong>Agentic SEO<\/strong> menu icon (now a globe) and\nupdated the in-readme setup steps to point at the new\nAgentic SEO \u2192 Connection location.<\/li>\n<\/ul>\n\n<h4>0.7.3<\/h4>\n\n<ul>\n<li>All plugin screens now live under a single top-level <strong>Agentic SEO<\/strong>\nmenu in the sidebar (its own icon), with three clearly-labelled\nsub-items: <strong>Connection<\/strong>, <strong>Approvals<\/strong> (with a pending-count\nbadge), and <strong>Activity<\/strong>. Previously these were three lookalike\nentries buried under Settings.<\/li>\n<li>Coding-standards pass for the WordPress.org review: added a\ntranslators comment to a placeholder string and made the AJAX nonce\nverification visible to static analysis (the nonce was always\nchecked \u2014 this just satisfies the scanner).<\/li>\n<\/ul>\n\n<h4>0.7.2<\/h4>\n\n<ul>\n<li>Fixed: Text domain now matches the plugin slug (<code>agentic-seo-visibility<\/code>)\nso translations load correctly and the WordPress.org plugin scanner\npasses. The plugin's display name is unchanged.<\/li>\n<li>Bumped \"Tested up to\" to WordPress 7.0.<\/li>\n<\/ul>\n\n<h4>0.7.1<\/h4>\n\n<ul>\n<li>Added: Real-time event-receiver endpoints under\n  \/wp-json\/visibility\/v1\/events\/*. The Visibility server pushes\napproved actions straight here (with their full payload), so\nchanges show up in WordPress within seconds of approval instead\nof waiting on the 5-minute WP-Cron tick.\n\n<ul>\n<li><code>events\/action-approved<\/code> -- executes a single approved action.<\/li>\n<li><code>events\/drain-inbox<\/code> -- bulk catch-up.<\/li>\n<li><code>events\/site-config-changed<\/code> -- mirrors the allow_publish \/\ndisabled flags so admin banners stay accurate without polling.<\/li>\n<\/ul><\/li>\n<\/ul>\n\n<h4>0.7.0<\/h4>\n\n<ul>\n<li>Added: Approval inbox for every AI write action. Two new submenu\npages appear under Settings -- Approvals (pending) and Activity\n(history). Every post, page, media upload, taxonomy edit, SEO\nmetadata change, or redirect that the Visibility AI requests now\nshows up as a card you review and approve (or reject with a note\nthe AI sees in its next run).<\/li>\n<li>Added: Auto-approval rules so trusted action types (e.g. drafts,\nalt-text edits) can flow through automatically with optional time\nand usage limits. High-risk actions never auto-approve unless you\nexplicitly opt in with a separate checkbox.<\/li>\n<li>Added: Background cron (every 5 minutes) that executes\nauto-approved actions even when no admin is logged in.<\/li>\n<li>Tightened: Action payloads are validated server-side against a\ncanonical action-type registry and a hard deny list (plugin\/theme\nops, user changes, permalink structure, custom CSS, arbitrary\noptions\/queries) so no AI request can bypass the approval gate.<\/li>\n<li>Removed: Application Password connection mode. Plugin pairing is\nnow the only supported transport. Existing app-password sites\nmust be re-paired with the plugin.<\/li>\n<\/ul>\n\n<h4>0.6.3<\/h4>\n\n<ul>\n<li>Split the <code>Plugin URI<\/code> and <code>Author URI<\/code> headers \u2014 they were both\npointing at <code>https:\/\/app.visibility.so<\/code> which the WordPress.org\nPlugin Checker flags (the two URIs must describe different things:\nthe plugin product vs. the publisher). Plugin URI stays at the\nproduct page; Author URI now points at the publisher site at\n  https:\/\/visibility.so.<\/li>\n<\/ul>\n\n<h4>0.6.2<\/h4>\n\n<ul>\n<li>Trim the short description from 196 to 131 characters so the WordPress.org\nPlugin Checker stops flagging it for truncation in plugin-directory cards.<\/li>\n<li>Rewrite the long description for clarity, with a \"Why use this plugin\"\nbullet list and a tighter \"How it works\" sequence.<\/li>\n<li>Expand the FAQ from 3 to 12 entries answering the most common questions\nabout AI publishing workflows, draft-only mode, SEO-plugin compatibility,\nperformance, multisite, privacy, and uninstall behaviour.<\/li>\n<li>Refresh the <code>Tags<\/code> line with more specific search terms\n(<code>agentic seo<\/code>, <code>ai content<\/code>, <code>ai writer<\/code>, <code>content automation<\/code>, <code>seo<\/code>).<\/li>\n<\/ul>\n\n<h4>0.6.1<\/h4>\n\n<ul>\n<li>Security &amp; WP-coding-standards pass on the settings page and REST handler\nahead of the WordPress.org re-review:\n\n<ul>\n<li>Status-redirect query args (<code>?visibility_status=...&amp;visibility_msg=...<\/code>)\nare now nonce-protected, so a crafted URL can no longer inject a spoofed\nadmin notice into the Settings page.<\/li>\n<li><code>wp_die(__(...))<\/code> upgraded to <code>wp_die(esc_html__(...))<\/code> on the\npermission-denied paths.<\/li>\n<li>URL output in the settings template now escapes at echo time with\nesc_url() (variables were already escape-on-assign \u2014 this is the\nbelt-and-braces \"escape late\" pattern WP coding standards prefer).<\/li>\n<li>Media-upload route: <code>parse_url()<\/code> \u2192 <code>wp_parse_url()<\/code> and\n@unlink($tmp) \u2192 <code>wp_delete_file($tmp)<\/code> (use the WordPress wrappers\nso filter hooks run and the filesystem op doesn't silent-fail).<\/li>\n<\/ul><\/li>\n<li><code>readme.txt<\/code> <code>Tested up to: 6.9<\/code>.<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>Rebrand to <strong>Agentic SEO for Visibility<\/strong> \u2014 display name, slug\n(<code>agentic-seo-for-visibility<\/code>), text domain, and Settings submenu\n(\"Agentic SEO\") updated to follow WordPress.org plugin-directory naming\nguidance for plugins that integrate with a named external service.\nInternal REST namespace, option keys, and cron action names are\nunchanged so pre-release test installs continue to work after update.<\/li>\n<li><code>readme.txt<\/code> now includes an <strong>External services<\/strong> section listing\nevery outbound network call the plugin makes (pair, heartbeat,\ndisconnect), what is sent, and explaining that a Visibility account is\nrequired.<\/li>\n<\/ul>\n\n<h4>0.4.3<\/h4>\n\n<ul>\n<li>Icon polish \u2014 the bundled brand icon (Settings \u2192 Visibility, and the\nwp.org listing assets) now uses a shifted viewBox so the sonar C-shape\nsits visually centred in the square canvas. Previous renders looked\nlike the icon was cropped on the right because the dot was at the\ngeometric centre but the C's visual mass extends only leftward.<\/li>\n<\/ul>\n\n<h4>0.4.2<\/h4>\n\n<ul>\n<li>Inline paste button in the pairing-code input \u2014 one click pulls the code\nfrom your clipboard so you don't have to right-click \u2192 paste. Falls back\nto focusing the input when the browser blocks clipboard reads.<\/li>\n<\/ul>\n\n<h4>0.4.1<\/h4>\n\n<ul>\n<li>Disconnect now actually disconnects on both sides. The Disconnect button\non Settings \u2192 Visibility used to wipe the local options only, leaving the\nVisibility project still marked \"Connected via plugin\" until the next\nfailed publish reverified it. The plugin now calls a new server endpoint\n(POST \/api\/wordpress\/plugin\/disconnect) before wiping local state, so\nVisibility removes the project's site row immediately. Local teardown\nstill completes even if Visibility is unreachable.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Expanded REST surface \u2014 agents can now manage everything end-to-end through\nthe plugin instead of hitting wp-json directly:\n\n<ul>\n<li>GET \/posts (list with search, status filter, pagination)<\/li>\n<li>DELETE \/posts\/{id} (trash or force-delete)<\/li>\n<li>GET \/categories + POST \/categories<\/li>\n<li>GET \/tags + POST \/tags<\/li>\n<li>GET \/media + POST \/media (upload from a remote source_url)<\/li>\n<li>Post create\/update now accept categories[], tags[], featured_media, date<\/li>\n<\/ul><\/li>\n<li>Post responses now include categories[], tags[], featured media, full content\n\n<ul>\n<li>excerpt \u2014 no need to call out to wp-json\/wp\/v2 for the same data.<\/li>\n<\/ul><\/li>\n<li>\/health response now includes adminUrl, timezone, and post counts (publish,\ndraft, pending, future, private, trash).<\/li>\n<li>Security fix: explicit <code>Cache-Control: private, no-store, no-cache<\/code> headers\non every \/visibility\/v1\/* response so page caches (LiteSpeed, WP Rocket,\nCloudflare, etc.) can't serve a stale unauthenticated body to a different\ncaller. Earlier versions relied on WP's default headers, which LiteSpeed\nwas overriding.<\/li>\n<\/ul>\n\n<h4>0.3.1<\/h4>\n\n<ul>\n<li>Fix <code>modified<\/code> field returning a zero date (\"-001-11-30T00:00:00+00:00\")\nfor freshly created posts where post_modified_gmt hadn't been normalised\nyet. Falls back to current GMT time when the stored value is empty\/zero.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Settings page now shows the connected company and project names (not just\nthe UUID). Names are returned from the pair endpoint and refreshed on each\ndaily heartbeat, so renames in Visibility surface here automatically.<\/li>\n<li>New \"Last seen\" row showing when the daily heartbeat last reached Visibility.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>Settings page links to root of Visibility instead of \/integrations.<\/li>\n<li>Plugin REST: added GET \/wp-json\/visibility\/v1\/posts\/{id} for verification.<\/li>\n<li>Post create\/update responses now include <code>editUrl<\/code> (wp-admin link) so the\nagent + user have something they can open even when the post is a draft\n(drafts return 404 to anonymous visitors, which is normal WP behaviour).<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial release: pairing flow, REST endpoints for post create\/update.<\/li>\n<\/ul>","raw_excerpt":"Pair WordPress with your Visibility project so AI agents can audit and publish content directly. No Application Passwords required.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/312878","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=312878"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rankth"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=312878"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=312878"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=312878"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=312878"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=312878"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=312878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}