How does authentication work?

With scoped management tokens — a Contentful space and content-management token, or a Sanity project and token. Pasted once, stored encrypted, bound to your site, and revocable from your CMS whenever you choose.

How does content map to my content model?

You map fields once, like the Webflow integration: title, body, slug, SEO fields to your model's fields. Bodies arrive as structured content — rich text for Contentful, Portable Text for Sanity — not an HTML blob in a string field.

Can published entries stay as drafts?

Yes. Entries can arrive unpublished for your team to release through your normal deployment flow — natural for teams whose frontend rebuilds on publish.

Headless CMS Publishing: Contentful and Sanity

The stack nobody in this category serves

Survey the AI SEO tools and a pattern appears: WordPress support everywhere, Shopify and Webflow common — and then the list stops. Run Contentful or Sanity behind a Next.js frontend and you're apparently invisible to the entire category, despite running some of the most serious content infrastructure on the web.

We noticed the gap in our competitive research and built for it deliberately. Teams on headless stacks publish a lot; they deserve better than "export as HTML and paste."

Structured content, taken seriously

The whole point of a headless CMS is structure — content as data, rendered wherever. An integration that dumps HTML into a single rich-text field defeats the architecture. SEOtopilot maps to your content model properly:

Contentful: articles become entries in your chosen content type, body as rich text, title, slug, and SEO fields mapped to your model's fields — mapped once, respected on every publish.
Sanity: articles land as documents with the body as Portable Text — real block content your frontend components render natively — not an HTML string masquerading as structure.

Custom fields your model defines are part of the same one-time mapping, exactly as in the Webflow integration.

Authentication, the headless way

Both platforms use scoped management tokens rather than OAuth: create a token scoped to the space or project, paste it once, done. Tokens are stored encrypted and bound to your site's record — the same envelope treatment every credential gets — and revocation is one action on the CMS side.

Draft entries and deploy pipelines

Headless teams usually control releases: content publishes, a build triggers, the site updates. The integration respects that shape — entries can arrive unpublished, sitting in your CMS for release through your normal pipeline. The review gate has already run on our side; your deploy discipline runs on yours. Two gates, both yours.

And the pipeline is the same one

Headless changes where content lands, not how it's made. Live SERP research, brand voice, claim-by-claim fact-checking, quality scoring — all identical. For stacks with a step we don't cover natively, Zapier, Make, and the API close the loop.

Getting started

Create a scoped management token in Contentful or Sanity, paste it in with your space or project identifier, and map your content model's fields once. Entries arrive respecting your model from the first publish — and if your frontend rebuilds on a webhook, unpublished-entry mode slots into that pipeline without any change on your side.