Paste a Server API key — a managed collection fills your blog.
Framer’s Server API lets DraftSEO manage a CMS collection for you. You paste a Server API key, DraftSEO creates a “DraftSEO Blog” collection, and you bind it to a page once — after that every article becomes a CMS item with images re-hosted by Framer, pushed live on a batched deploy.
| Connection | Server API key — from Framer → Site Settings → General, pasted once |
|---|---|
| Setup | Managed collection — DraftSEO creates and fills it; you bind it to a page |
| Image hosting | Framer-hosted — images re-hosted on framerusercontent.com, never hot-linked |
| Going live | Batched deploy — many articles in a window = one clean site republish |
| Publish modes | Draft · published · scheduled |
Who does what
Nothing — after you bind the collection once, items appear and the site redeploys on their own. Want a gate? Let items land as drafts and publish from Framer when you’re ready.
Bind it once; it just keeps filling.
Setup
In Framer, go to Site Settings → General and create a Server API key.
~1 minute
Connect a site → Framer → paste the key. DraftSEO creates a managed “DraftSEO Blog” collection.
~1 minute
In Framer, point a blog page at the managed collection — a one-time step.
~2 minutes
New articles fill the collection and the site redeploys on a batched cadence.
Ongoing · zero clicks
FAQ
With a Framer Server API key, pasted once. DraftSEO then creates and manages a “DraftSEO Blog” CMS collection inside your project.
On Framer. Featured and body images are re-hosted on framerusercontent.com when items sync, so the published page never links back to our CDN.
DraftSEO upserts the item, then a batched job runs one Framer publish and deploy per site — so several new articles in a window trigger a single clean redeploy.
No card required. Bind the collection once, done.