Paste one private key — articles arrive as entries in your Builder.io space.
Builder.io has a real content-writing API. You paste a private API key, DraftSEO reads the models in your space, and you map which field holds the title, the body, the slug and the cover image. Articles then arrive as native entries on your own blog model — with the full article HTML in a Rich Text field and every image uploaded into Builder’s asset library. Because Builder is headless, your own front end renders the page, so you also tell DraftSEO the URL pattern your blog posts live at.
| Connection | Private API key — from Builder → Space Settings → Private Keys |
|---|---|
| Key permissions | Admin role required — a Developer-role key cannot write content |
| Body format | HTML into a Rich Text field — no block conversion, your markup arrives intact |
| Image hosting | Builder’s CDN — uploaded to cdn.builder.io, never hot-linked |
| Publish modes | Published · draft · scheduled |
Who does what
Nothing — once the key is pasted and the fields are mapped, entries appear in your space and your front end renders them. Want to review first? Send them as drafts and publish from Builder.
Works with whatever your blog model is called and whatever you named its fields.
Setup
In Builder → Space Settings → Private Keys, create a key. Make sure its member has the Admin role.
~1 minute
Connect a site → Builder.io → paste. DraftSEO reads your space and lists the models it can publish into.
~1 minute
Pick your blog model, then confirm which field is the title, the body, the slug and the cover. DraftSEO suggests a mapping for you.
~2 minutes
Tell DraftSEO where posts appear on your site, e.g. https://yoursite.com/blog/{slug}, so it can link them.
~30 seconds
FAQ
A Data model of your choosing — the one you already use for blog posts. DraftSEO lists every Data model in your space that has a Rich Text field and suggests the best match. It deliberately does not write to Page or Section models: those render from Builder’s visual blocks, so an entry made of plain fields would create a page with nothing on it.
Builder only lets Admin-role members write content through the API. A Developer-role key connects and reads your models perfectly well, then fails on the first publish with a “model not found” error that points at the wrong thing entirely. DraftSEO checks for this and tells you plainly if it happens.
On Builder’s CDN. Each image is uploaded into your Builder asset library before the entry is written, so the published article never loads images from our servers.
Only if you want internal linking and the backlink exchange. Builder is headless — it stores the content and your own front end decides the address — so without the pattern DraftSEO can publish articles but has no way to know where they end up.
No card required. Images hosted in your space.