Paste one API token — articles arrive as published records on your own DatoCMS model.
DatoCMS is built for programmatic content. You paste an API token, DraftSEO reads your models, and you confirm which fields hold the title, the body, the slug and the image. Each article is then written as a record on your own model and published for you, with every image uploaded to the DatoCMS CDN first. DatoCMS is headless, so your own website renders the article — you tell DraftSEO the address pattern your posts live at.
| Connection | One read-write API token — Project Settings → API Tokens |
|---|---|
| Your website | A URL pattern is required — DatoCMS renders no page itself; your front end does |
| Body fields | Text and multi-paragraph text — matched to the field you map |
| Structured text | Supported, but without in-article images — a structured-text image must reference a block record, which DraftSEO cannot create |
| Image hosting | Uploaded to the DatoCMS CDN — never hot-linked |
| Publish modes | Auto · draft · scheduled — draft needs draft mode on for that model |
Who does what
Nothing — once the token is pasted and the fields are mapped, records appear on your model already published, and your website shows them. Want to review first? Send them as drafts and publish from DatoCMS.
Works with whatever your model and its fields are called, including localised projects.
Setup
In DatoCMS open Project Settings → API Tokens and add a token whose role can create and update records and create uploads. The read-only token every project ships with cannot publish.
~2 minutes
Connect a site → DatoCMS → paste the token. DraftSEO reads your project and lists the models an article can go into.
~1 minute
Confirm which fields hold the title, body, slug and image. DraftSEO suggests the mapping from your own schema and prefers a text body field.
~2 minutes
Tell DraftSEO where posts appear on your website, e.g. https://www.yoursite.com/blog/{slug}.
~30 seconds
FAQ
Every DatoCMS project is created with a read-only token, and it is the one most people copy first. It can read your models but cannot create anything, so publishing fails. Add a token whose role allows creating and updating records and creating uploads, and paste that one instead — DraftSEO tells you plainly when the token it has cannot write.
It works for the words, but not for in-article images. A picture inside DatoCMS structured text has to point at a separate block record, and DraftSEO cannot create those on your behalf, so images inside the article are left out. If you want illustrated articles, map the body to a plain text field instead — DraftSEO will suggest that when your model has one.
Your choice, with one catch: the draft option only exists if draft mode is switched on for that model. DatoCMS keeps a single record rather than a draft beside a published copy, so on a model without draft mode there is no hidden state to put an article into — DraftSEO hides the option instead of quietly publishing something you asked to keep back.
Yes. DraftSEO reads which of your fields are localised and writes each value under your project’s primary locale, which is what DatoCMS requires — a plain value on a localised field is rejected outright.
Every image is uploaded to DatoCMS and served from its CDN, so nothing points back at DraftSEO. If an upload fails, the article is published without that image rather than with a broken one, and DraftSEO retries it in the background.
No card required. Images uploaded to your DatoCMS CDN.