By RankPine
Publish SEO articles from RankPine to Strapi 5 with secure pairing, explicit field mapping, media uploads, localisation, and drafts.
released August 28, 2026
npm install @rankpine/strapi-plugin-rankpineSecurely connect one Strapi 5 collection type to RankPine publishing. The plugin discovers the live schema, exposes a small native settings screen, and accepts only Ed25519-signed RankPine document upserts.
>=5.33.2 <6npm install @rankpine/strapi-plugin-rankpineRestart Strapi and rebuild the Strapi admin panel as required by your deployment workflow. RankPine does not publish or deploy your Strapi project.
For local package development, link the repository with the Strapi Plugin SDK/yalc workflow described in the official Strapi 5 documentation.
Open Settings → RankPine in Strapi:
The pairing code expires after ten minutes and works once. It is sent to RankPine through a top-level HTTPS form POST, never a query string, and is immediately held in an encrypted, signed, HTTP-only cookie. Rotating creates a new key and invalidates the previous RankPine signing key when pairing completes. Disconnect removes the stored public key immediately.
documentId valuesComponents and dynamic zones are discovered but not written. Required components/dynamic zones block the connection or publish request. Optional ones are listed in diagnostics. The publishing layer never invents values for custom fields.
The plugin does not request or store a Strapi API token, password, or RankPine shared secret. Pairing stores an Ed25519 public key. RankPine stores the private key encrypted in its tenant-scoped integration record.
Every publish/discovery request includes a key ID, Unix timestamp, random nonce, and Ed25519 signature over the method, route, timestamp, nonce, and SHA-256 body digest. The plugin rejects stale requests and atomically claims nonce hashes to prevent replay.
Admin settings routes require Strapi admin authentication and plugin RBAC permissions. Public plugin routes accept only a one-time pairing code or a valid RankPine signature. Featured media downloads require public HTTPS, pin DNS to validated public addresses, revalidate redirects, cap files at 10 MB, and accept JPEG, PNG, WebP, or GIF only. SVG is rejected.
The plugin sends no analytics or telemetry. Pairing codes, keys, signatures, and article content are not logged by the plugin.
See SECURITY.md for private vulnerability reporting.
The RankPine dashboard also supports a direct Strapi 5 API-token connection without this plugin. Use a custom Content API token limited to find, findOne, create, and update on the selected collection plus Upload find and upload. RankPine encrypts that token at rest.
Support covers the current Strapi 5 major and the latest stable RankPine plugin release. Security fixes are prioritized; compatibility fixes target supported Strapi 5 releases.
The package is published on npm. It has not been submitted to Strapi Marketplace because current rules prohibit plugin features gated by an offsite paywall. RankPine will not submit this connector unless Strapi confirms eligibility or the plugin-assisted feature is made independently free under those rules.
MIT
Share your work with the community and get it listed in the Strapi ecosystem for everyone to discover and use.
Submit
