Paste a Management Token — articles arrive as published entries in your stack.
Contentstack is built for programmatic content. You paste your Stack API Key and a Management Token, pick your region, and DraftSEO reads your content types and environments. You confirm which fields hold the title, the body, the URL and the featured image — then each article is written as an entry, its images uploaded as Contentstack assets, and both published to the environment you chose. Contentstack is headless, so your own website displays the article; you tell DraftSEO the address pattern your posts live at.
| Connection | Stack API Key + Management Token — Settings → Tokens → Management Tokens, Write permission |
|---|---|
| Regions | AWS, Azure and Google Cloud — North America, Europe and Australia |
| Body field | HTML Rich Text or Markdown — the JSON Rich Text Editor is not supported yet |
| Image hosting | Contentstack assets — uploaded and published, never hot-linked |
| Publish modes | Published · draft · scheduled |
Who does what
Nothing — once the token is pasted and the fields are mapped, entries are published to your environment and your website shows them. Want to review first? Send them as drafts and publish from Contentstack.
Works with whatever your content type and its fields are called.
Setup
In your stack open Settings → Tokens → Management Tokens → + Management Token. Give it Write permission and no expiry, then copy the Stack API Key and the token — the token is shown once.
~1 minute
Connect a site → Contentstack → paste the key and token and pick your region. DraftSEO lists your content types and environments.
~1 minute
Pick the content type and environment, and confirm which fields hold the title, body, URL and featured image. DraftSEO suggests the mapping from your own field names.
~2 minutes
Tell DraftSEO where entries appear on your website, e.g. https://www.yoursite.com{url}.
~30 seconds
FAQ
An HTML-based Rich Text Editor field or a Markdown field. The JSON Rich Text Editor stores a structured document rather than HTML and is not supported yet — add an HTML-based Rich Text Editor field to your blog content type and map that.
Your choice. Published articles are pushed to the environment you picked (for example production), together with their images. Drafts are written to your stack and left unpublished until you publish them in Contentstack.
In your own stack, as Contentstack assets served from Contentstack’s image CDN. Each image is uploaded before the entry is written, so the article never loads images from our servers.
Yes, for a trial — but Explorer allows about 200 entries and a limited number of API calls a month, so a real autoblog needs a paid Contentstack plan.
No card required. Images hosted as your own Contentstack assets.