First public WordPress.org release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3633458,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3633458,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3601417,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3601417,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["5.1.1","5.2.0","5.3.0","5.3.1","5.4.0","5.5.0","5.6.0","5.7.0","5.7.1","5.8.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[5777,6487,726,1117,186],"plugin_category":[55],"plugin_contributors":[270706],"plugin_business_model":[],"class_list":["post-337142","plugin","type-plugin","status-publish","hentry","plugin_tags-meta-description","plugin_tags-open-graph","plugin_tags-redirects","plugin_tags-schema","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-platinumwp","plugin_committers-platinumwp"],"banners":{"banner":"https:\/\/ps.w.org\/audiscale-connector\/assets\/banner-772x250.png?rev=3601417","banner_2x":"https:\/\/ps.w.org\/audiscale-connector\/assets\/banner-1544x500.png?rev=3601417","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/audiscale-connector\/assets\/icon-128x128.png?rev=3633458","icon_2x":"https:\/\/ps.w.org\/audiscale-connector\/assets\/icon-256x256.png?rev=3633458","generated":false},"screenshots":[],"raw_content":"\n
AudiScale Connector is the companion component for the hosted AudiScale service (https:\/\/audiscale.com). It unlocks the SEO actions that WordPress core and the standard REST API do not allow \u2014 most notably printing a This plugin communicates with the third-party AudiScale service. No data is\nsent until you have explicitly paired<\/strong> your site from your AudiScale dashboard.\nOnce paired, AudiScale can remotely apply a fixed catalog of operations<\/strong>\n(listed below), each of which is:<\/p>\n\n The plugin never executes arbitrary code<\/strong>: there is no code-evaluation\nendpoint and no remote code download. \"Almost everything\" means an enumerated,\nhand-coded, audited catalog.<\/p>\n\n The plugin detects Yoast, Rank Math and SEOPress and stands down<\/strong>\nautomatically if one of them already manages the To revoke access at any time: \"Settings \u2192 AudiScale \u2192 Disconnect\", or disconnect\nthe site from AudiScale.<\/p>\n\n\n No. No communication happens until the site is paired, and pairing requires an\nadministrator ( AudiScale Connector detects Yoast \/ Rank Math \/ SEOPress and prints nothing in\nthe Unpairing erases the pairing secret: the command channel becomes inert\nimmediately.<\/p><\/dd>\n\n<\/dl>\n\n\n<meta name=\"description\"><\/code> tag in the <head><\/code> without forcing you to install another SEO plugin.<\/p>\n\nService disclosure (SaaS)<\/h4>\n\n
\n
manage_options<\/code>);<\/li>\n\n
Operation catalog<\/h4>\n\n
\n
<head><\/code>: meta description, SEO title, canonical, robots, Open Graph, Twitter cards, native sitemap exclusion<\/li>\nwp_footer<\/code> (badge install \/ removal)<\/li>\n<head><\/code>, to avoid duplicate\ntags.<\/p>\n\n\n\n
POST \/wp-json\/audiscale\/v1\/pair<\/code> with a secret generated on the AudiScale side.<\/li>\n\n
Does the plugin send data without my consent?<\/h3><\/dt>\n
manage_options<\/code>).<\/p><\/dd>\nWhat happens if I already have an SEO plugin?<\/h3><\/dt>\n
<head><\/code> to avoid duplicates.<\/p><\/dd>\nHow do I revoke access?<\/h3><\/dt>\n
5.8.0<\/h4>\n\n
\n
taxonomy.list<\/code> operation (edit_posts<\/code> capability, read-only): lists the\ntaxonomies that apply to a post type \u2014 categories, tags, and any custom one the\nsite declares \u2014 and, on request, one bounded page of their terms. AudiScale\nreads it so it can only ever propose a term that exists.<\/li>\ncontent.terms.assign<\/code> operation (manage_options<\/code> capability): files a page\nor a post under existing terms. It adds<\/strong> by default: assigning one category\nno longer removes the others, and clearing the existing terms requires spelling\nout mode: \"replace\"<\/code>. It never creates a term<\/strong>: an unknown one is refused and\nreported, so a near-duplicate (\"Actualit\u00e9s\" on a site holding \"Actualit\u00e9\") is\nnever silently created. The complete previous set of terms is written to the\naudit log, and the recorded result is re-read after the write, so it shows the\ndefault category WordPress reassigns to a post left without one.<\/li>\ncontent.trash<\/code> operation (delete_posts<\/code> capability): moves a page or a post\nto the WordPress trash, from where you can restore it. Until now a draft created\nfrom AudiScale could not be removed from AudiScale. Nothing is ever deleted\npermanently: if the trash is disabled on your site the operation is refused\ninstead of destroying the content, and media are out of scope \u2014 WordPress does\nnot trash an attachment, it deletes it and its files for good.<\/li>\npromote<\/code> operation now also approves a page body prepared in draft mode\n(field: \"content\"<\/code>). It previously handled SEO fields only, so a body drafted by\nAudiScale could be approved from WordPress and nowhere else.<\/li>\ncontent.set_page_template<\/code> now honours publishMode<\/code> like every other content\noperation: by default the new template waits on the \"Pending\" screen instead of\nbeing applied to the live site immediately.<\/li>\ncontent.status.set<\/code> and content.trash<\/code> now refuse to unpublish or trash the\npage used as the front page or as the posts page, which would leave the site\nwithout an entry point.<\/li>\n?p=<\/code>,\n ?page_id=, ?attachment_id=<\/code> \u2014 the three WordPress itself honours), then the\nsite's own rewrite rules, then the site root, and refuses otherwise with\n audiscale_url_needs_post_id (404). The slug fallback that used to search the\npath against every content type is removed<\/strong>: a slug read off a crawled URL\nnames the right content only by luck, and every way it named a wrong one ended in\na success on content nobody aimed at \u2014 on a shop holding both a page and a product\nnamed \"contact\", the write landed on whichever the database returned last. A URL\nwhose path WordPress does not resolve now needs an explicit content id; AudiScale\nresolves the target on its side and sends it.<\/li>\nsite_url()<\/code> and the audiscale_trusted_hosts<\/code> filter, and\ninternationalized domains, punycode and a trailing dot compare equal.<\/li>\npost<\/code> and post_id<\/code> are no longer read as content ids \u2014 WordPress\nhonours neither, while plugins use both as ordinary parameters, so a crawled\n\"\/recherche\/?post_id=2\" resolved to the post 2 instead of the search page.<\/li>\ncontent.set_page_template<\/code> \u2014 the operation id alone is the same as\nin 5.7.1, where the template was always applied immediately.<\/li>\ncode<\/code> (and the details behind it,\nsuch as the templates the theme really declares) next to the message, so AudiScale\ncan tell one refusal from another and suggest the right fix. The error<\/code> field is\nunchanged.<\/li>\n<\/ul>\n\n5.7.1<\/h4>\n\n
\n
?page_id=<\/code>, ?p=<\/code>, ?post=<\/code>, ?post_id=<\/code>) was\nread as the site root, because its path is \/<\/code>. Depending on the site it either\nfailed with audiscale_no_front_page<\/code> or \u2014 with a static front page \u2014 applied the\noperation to the home page instead of the content actually targeted. The declared\nid is now read first, and an id matching no content fails instead of falling back\nto the home page. Affects every operation resolving a URL, SEO ones included.<\/li>\n<\/ul>\n\n5.7.0<\/h4>\n\n
\n
media.upload<\/code> operation (upload_files<\/code> capability): sideloads a remote\nimage or video into the media library and returns its attachment id, so a page\nAudiScale drafts can reference a real attachment instead of an external URL.\nThe downloaded bytes are type-checked (no SVG), the source URL is validated\nagainst WordPress' own SSRF guard, the transfer is capped at 25 MB (declared\nsize checked before the download, response size capped during it), and nothing\nexisting is overwritten. This operation is why the plugin requires WordPress\n6.0 or later: download_url()<\/code> fetches through wp_safe_remote_get()<\/code>, which\nre-validates every redirect target against the same SSRF guard rather than\nfollowing it blindly.<\/li>\nblocks.validate<\/code> operation (edit_posts<\/code> capability, read-only): parses\nblock markup the way the editor does and reports content sitting outside any\nblock, unknown block types, or markup that does not survive a parse\/serialize\nround-trip. AudiScale calls it before proposing a draft, so a page never lands\nin the editor showing \"This block contains unexpected or invalid content\".<\/li>\nsite.layout_options<\/code> operation (edit_posts<\/code> capability, read-only):\nlists the page templates the active theme actually declares, and whether the\ntheme renders wide\/full alignments. AudiScale reads it before offering any\nlayout change, so it can only ever propose a layout the theme can render.<\/li>\ncontent.set_page_template<\/code> operation (manage_options<\/code> capability):\nchanges the template of an existing page or post, targeted by post_id<\/code> or\n url. The value must be a template the active theme declares (or default<\/code>);\nanything else is refused rather than written, and the before\/after is recorded\nin the audit log.<\/li>\ncontent.create_draft<\/code> and content.update_fields<\/code> accept an optional\n page_template, validated the same way. On creation the template is checked\nbefore the post is inserted, so a refused template never leaves an orphan\ndraft behind.<\/li>\n<\/ul>\n\n5.6.0<\/h4>\n\n
\n
plugins.check_updates<\/code> operation (update_plugins<\/code> capability): purges the\n update_plugins transient and re-runs WordPress' update check immediately, with\nno staleness guard, then reports how many updates are now visible. WordPress only\nrefreshes that cache about twice a day and its upgrader refuses any plugin the\ncache does not list, so updating a freshly released version from AudiScale failed\nfor hours for no real reason. AudiScale now calls this before retrying, and the\nupdate goes through. plugins.list<\/code> is unchanged.<\/li>\n<\/ul>\n\n5.5.0<\/h4>\n\n
\n
5.4.0<\/h4>\n\n
\n
site.footer_snippet.set<\/code> \/ .clear<\/code> \/ .get<\/code> operations: store a marked\nHTML block (a link and an image, no script) and print it on wp_footer<\/code>. Used\nby AudiScale for the one-click \"Verified\" badge install. The block lives in an\noption, not in the theme's footer.php<\/code>, so a theme update cannot wipe it, and\nre-posing the same marker replaces the block instead of stacking a second one.<\/li>\n<\/ul>\n\n5.3.1<\/h4>\n\n
\n
plugins.update<\/code> no longer leaves a plugin deactivated after a successful\nupdate: a failed reactivation is now reported (reactivationFailed<\/code>) instead\nof being swallowed, and a main file renamed by the update is re-resolved\nbefore reactivating.<\/li>\n<\/ul>\n\n5.3.0<\/h4>\n\n
\n
seo.sitemap.exclude<\/code> operation: flags a content so the native\nwp-sitemap.xml skips it (reversible with excluded: false<\/code>; draft\/approve flow\nsupported). No effect while a third-party SEO plugin provides the sitemap.<\/li>\ncontent.status.set<\/code> operation: switches a content between \"publish\" and\n\"draft\" only (strict whitelist \u2014 no trash, no private, no scheduling),\n publish_pages capability, audited before\/after.<\/li>\n5.2.0<\/h4>\n\n
\n
5.1.1<\/h4>\n\n
\n
plugins.update<\/code> now keeps the target plugin active after upgrading it (the\nWordPress upgrader deactivates during the file swap and does not restore it on a\nprogrammatic call).<\/li>\n<\/ul>\n\n5.0.0<\/h4>\n\n
\n
security.*<\/code> operation family: hardenings applied at the PHP\nruntime, without touching wp-config and always reversible in a single call\n(file editor, REST user enumeration, XML-RPC + pingbacks, HTTP headers\nHSTS\/nosniff\/X-Frame-Options\/Referrer-Policy, minor core auto-updates,\nversion masking, ?author=N<\/code> scan blocking).<\/li>\ndryRun<\/code> (simulation without writing) and logs the before\/after\nvalue for an undo via the inverse op. security.state.get<\/code> exposes the current\nstate. Disconnecting (unpair<\/code>) resets all hardenings.<\/li>\nhsts<\/code> is set only if HTTPS is actually enforced (anti-lockout guard).<\/li>\n<\/ul>\n\n4.0.0<\/h4>\n\n
\n
security.audit<\/code> operation (read-only, manage_options<\/code> capability):\nfree hardening snapshot (versions, configuration flags, admin accounts, core\nintegrity via wordpress.org checksums). No secret is returned.<\/li>\n<\/ul>\n\n3.0.0<\/h4>\n\n
\n
plugins.list<\/code> (read, activate_plugins<\/code>\ncapability) and plugins.update<\/code> (live, irreversible update, update_plugins<\/code>\ncapability).<\/li>\n<\/ul>\n\n2.0.0<\/h4>\n\n
\n
content.update_fields<\/code> op: URL targeting + fields<\/code> object\n(title\/excerpt\/content), respecting publishMode<\/code>.<\/li>\nfiltered<\/code> flag if the user lacks the\n unfiltered_html capability.<\/li>\ndraft<\/code> mode for content: the proposal is queued and approved from the\n\"AudiScale pending\" screen.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
draft<\/code> mode: proposed values are stored \"pending\" without changing the live\nrender.<\/li>\npromote<\/code> operation to approve a field from AudiScale (consent equivalent to\n direct).<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n
<head><\/code> output, redirects, structured data, HMAC-signed\noperation catalog, audit log.<\/li>\n<\/ul>","raw_excerpt":"Server-side companion for AudiScale: SEO tags, redirects, and an enumerated catalog of operations over an HMAC-signed channel.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/337142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=337142"}],"author":[{"embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/platinumwp"}],"wp:attachment":[{"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=337142"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=337142"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=337142"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=337142"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=337142"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/et.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=337142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}