Write into Strapi as structured content.
Strapi is a headless CMS: the payload is data, not a rendered page. Rankow maps title, description, canonical, and cover URL into your existing content type — and leaves schema rendering to your front end.
Before you connect
What you need in hand.
All of it is created inside the platform — none of it requires a developer or a plugin.
Base URL
https://cms.example.com
The Strapi instance root. The REST API lives under /api/.
API token
Strapi admin → Settings → API tokens
A token with access to the target collection. Store it as a secret.
Content type
e.g. articles
The REST name of the collection Rankow writes into. It must already exist.
Field mapping
SEO component + cover URL
The component fields that hold title, description, canonical, and cover.
Connection
Connect, then test with one draft.
The test draft is not optional. It is how you confirm the fields land before a full cycle is approved.
- 01
Create the collection
If it does not exist yet, create the content type and its fields first. Rankow maps into an existing schema; it does not create one.
- 02
Issue an API token
Create a token scoped to the collection, then store it as a secret rather than in a template.
- 03
Map the fields
Point the SEO component and the cover URL at the real property names, so the payload fits your schema.
- 04
Publish a test entry
Run one draft and verify the entry, the SEO component, and the cover URL before a full cycle.
After publish
What this channel actually receives.
These rows mirror the channel capability matrix the engine reads. Nothing here is a field the channel does not get.
SEO component
IncludedTitle, description, canonical, and cover URL are written into your SEO component.
JSON-LD
Not includedStrapi returns JSON, not a rendered page. No script is injected; render schema in your front end.
Images
URL onlyThe cover is delivered as a URL in the payload. The Strapi media library is not written to.
Internal links
IncludedLinks are resolved against real content entries. A target that cannot be confirmed is dropped.
One limitation, stated plainly
Strapi never renders a page, so publishing stops at a document entry and a cover URL. Related-posts blocks and JSON-LD are not injected on this channel.
Questions
Before you connect.
No. You create the collection and its fields; Rankow maps the payload into the schema you already have.
Because Strapi never renders a page. The SEO component carries the data, and your front end decides what structured data to output.
Yes. Updates target the existing document by ID and keep the published status; the URL does not change.
Other guides
Shopify
Shopify is the fully managed publishing path: articles, SEO metafields, JSON-LD, and a WebP cover are written through the Admin API. This is what you need in hand, what happens on connect, and what each article actually receives.
WordPress
WordPress connects with an application password, not a plugin. Posts are created and updated over the REST API, meta fields are written with the body, and the cover lands in the media library as WebP.
Integration guide
Write into Strapi as structured content.
Strapi is a headless CMS: the payload is data, not a rendered page. Rankow maps title, description, canonical, and cover URL into your existing content type — and leaves schema rendering to your front end.
7 days · 1 site · No credit card