Poliris

Poliris links this site to your Poliris account (a paid brand-intelligence and SEO platform). Once paired:

• SEO fixes you approve in Poliris (SEO titles, meta descriptions, image alt text, content improvements) are applied to your posts and pages directly.
• Page-level fixes (Open Graph tags, canonical URLs, structured data, on-page text corrections) are applied server-side to the rendered HTML — no JavaScript snippet needed, and search engines see the fixes in the raw HTML.
• Content drafts generated in Poliris land in your wp-admin as drafts, ready for your review — nothing is ever auto-published.
• Every change is reversible from the Poliris dashboard.

The plugin is intentionally minimal. It has no settings beyond a pairing screen, stores no Poliris data beyond the list of fixes you approved, and adds two REST endpoints (status probe, and SEO title/description read-write for Yoast SEO or Rank Math — fields core REST cannot write). How access works. At pairing, the plugin creates a WordPress Application Password for your admin user and hands it to Poliris over HTTPS. All subsequent operations authenticate with WordPress's own REST security. Revoke the "Poliris" password from your profile at any time to instantly cut access. A Poliris account is required: https://poliris.io

0.2.2

• Review feedback: the server-side pixel output buffer is now always explicitly closed. On WordPress 6.9+ the plugin uses the core template enhancement output buffer (no own buffer at all); on older versions the buffer opened on template_redirect is paired with an explicit flush on shutdown.
• Pairing error messages are no longer passed through the URL — only fixed notice codes are, with the message stored server-side.
• Uninstalling now removes all plugin options and revokes the "Poliris" Application Passwords, so deleting the plugin fully cuts the service's access.

0.2.1

• Review feedback: admin-page CSS enqueued via wp_add_inline_style, /status endpoint restricted to manage_options, direct legal-page URLs in the readme.

0.2.0

• Server-side fixes: approved page-level fixes (Open Graph, canonical, structured data, on-page text) are now applied to the rendered HTML on the server — the JavaScript snippet is no longer needed on WordPress sites.

0.1.0

• Initial release: pairing flow, status endpoint, Yoast/Rank Math SEO meta read-write.