Which Strapi versions work?

Strapi 5 first, with Strapi 4 supported too. Self-hosted or Strapi Cloud — Edward only needs your Strapi URL and an API token.

What does the API token need?

Full access is simplest. A Custom token works with find, findOne and create on your collection, plus upload so covers land in the Media Library. You can revoke it anytime from Settings → API Tokens.

Where do the posts appear on my site?

That's up to your frontend, so you tell Edward the pattern — like https://your-site.com/blog/{slug} — and it uses that for links, social shares and internal linking.

Can I review entries before they go live?

Yes. Choose “save as draft” and each entry waits in Strapi for you to publish, as long as Draft & Publish is on for the type.

Strapi integration

Edward AI SEOon Strapi.

Edward writes each article straight into your Strapi collection over the REST API — title, slug, body, description and cover, mapped to the fields you already have. Live or as a draft, on Strapi 5 or 4, self-hosted or Strapi Cloud.

Get started All integrations

Connects with a Strapi API token. Works with Strapi 5 and Strapi 4.

Built for your content type.

Your fields, not ours.

Strapi has no built-in blog, so Edward maps onto whatever you named your fields. Fetch them once, pick where the title, slug, body, description and cover go, and every post lands in the right place.

Markdown, HTML, or Blocks.

Rich text (Markdown), Rich text (Blocks) or a plain Text field your frontend renders — Edward writes the body in the format your field expects, cover and body images uploaded to your Media Library.

Live or draft, your call.

Publish the moment an entry is created, or save it as a Strapi draft to review before it goes live.

Why Strapi + Edward

A headless CMS gives you a fast, custom frontend — and an empty content type nobody has time to fill. Edward keeps your Strapi collection stocked with search-ready articles that your site renders like everything else, so the SEO compounds while you keep building.

How it works

Connect in three steps.

01
Create an API token.
In Strapi, open Settings → API Tokens → Create new API Token, choose Full access and an unlimited duration, and copy it.
02
Map your collection.
Paste your Strapi URL, the token and the collection's API ID into Edward, fetch its fields and pick where each part of the article goes.
03
Publishing begins.
Tell Edward where your site shows each post, and it starts writing entries on your cadence.

Already a customer? Log in to connect Strapi from your dashboard.

FAQ

Questions, answered.

Which Strapi versions work?: Strapi 5 first, with Strapi 4 supported too. Self-hosted or Strapi Cloud — Edward only needs your Strapi URL and an API token.
What does the API token need?: Full access is simplest. A Custom token works with find, findOne and create on your collection, plus upload so covers land in the Media Library. You can revoke it anytime from Settings → API Tokens.
Where do the posts appear on my site?: That's up to your frontend, so you tell Edward the pattern — like https://your-site.com/blog/{slug} — and it uses that for links, social shares and internal linking.
Can I review entries before they go live?: Yes. Choose “save as draft” and each entry waits in Strapi for you to publish, as long as Draft & Publish is on for the type.