Write into WordPress through the REST API.
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.
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.
Site URL
https://example.com
The WordPress root. The REST API lives under /wp-json/wp/v2/.
Username
A dedicated editor account
Use an account created for the integration, not a shared administrator login.
Application password
Users → Profile → Application Passwords
A generated password, not the account login password. It can be revoked at any time.
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 an editor account
Least privilege: the integration needs to create and update posts, not administer the site.
- 02
Generate an application password
From the user profile page. Copy it once — WordPress does not show it again.
- 03
Enter the connection
Add the site URL, username, and application password. Rankow verifies that the REST API responds before planning starts.
- 04
Publish a test draft
Check the body, the meta fields, and the media-library cover before running 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 meta
IncludedSEO title and meta description are written through the REST API meta fields.
JSON-LD
Not includedNo JSON-LD script is injected for WordPress. Structured data stays with your SEO plugin.
Images
IncludedThe cover is uploaded to the WordPress media library as WebP. Inline images are served as WebP from the CDN.
Internal links
IncludedLinks are resolved against real permalinks, and WordPress also receives the related-posts block.
One limitation, stated plainly
The body is stored as HTML through the REST API, so Gutenberg renders it as classic content rather than native blocks. JSON-LD is not injected.
Questions
Before you connect.
The body is written as HTML through the REST API, so it renders as classic content inside the editor rather than as native blocks.
None in particular. Rankow writes the core meta fields through the REST API, and any plugin that reads those fields will display them. Schema output stays with the plugin.
Yes. A post is located by its slug, its title and meta can be updated without changing the URL, and a snapshot is kept before the 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.
Strapi
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.
Integration guide
Write into WordPress through the REST API.
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.
7 days · 1 site · No credit card