SEO by platform
SEO for Webflow
Articles land as items in the CMS collection you point the connection at, your Webflow templates render them like any other item, and new connections create draft items that wait in Webflow for your publish action.
How publishing works on Webflow
The connection writes generated articles into a CMS collection on your Webflow site, with title, body, slug and metadata mapped into the fields your collection provides, and new connections default to draft items. One Webflow habit matters here: the live site shows CMS changes only after a site publish, so the verifier can only pass after you publish the Webflow site itself.
Items land in your collection, fields mapped
Title, body, slug and metadata map into the fields your blog collection provides. Field mapping follows common collection field names, and a heavily customized collection may leave extra fields for you to fill in Webflow.
Help centre: WebflowDraft items until you flip the connection
New connections default to draft items, so posts wait in Webflow for your publish action until you switch the connection to publish live.
Published means the public URL answered
After every publish we fetch the public URL and record what came back. Published shows only when the page was found, a fresh 404 waits out a grace window, and a server error never concludes the page is missing.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Every article is scored before you ship it
The content score runs 36 fixed checks in 6 categories, with no randomness anywhere: the same page always produces the same score. Each check comes back as a pass, a warn or a fail, and each failure names its specific fix.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send Webflow, not a guess about the platform.
The connection fills collections, it does not design them. A CMS collection for blog posts must already exist on the site. Documented: Webflow
Webflow's own CMS item limits apply. A plan at its item cap refuses new posts, and the connection surfaces that error rather than hiding it. Documented: Webflow
A new item is not on the live site until you publish the Webflow site. The verifier can only pass after that publish. Documented: Webflow
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Create a site API token
In Webflow, open Site settings, then Apps and integrations, and create a site API token with CMS read and write, since a workspace-level token will not be accepted.
Copy the collection ID
Open your blog collection's settings in the CMS panel and copy its ID from that settings screen rather than from the page URL, which is how wrong-collection mistakes happen.
Connect and test
In the project's Publishing tab, choose Webflow, paste the token and collection ID, and send a test publish. Check the item in Webflow's CMS panel, then publish the site.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Items appear in the CMS but the live site shows nothing. Why?
- You have not published the Webflow site since the items arrived. Publish in Webflow, and the verifier flips to live on its next check.
- Does the connection set the SEO title?
- Where your collection has a field for it. Webflow has no fixed SEO field, the designer binds one, so the connection discovers a meta-title-shaped collection field the same way it discovers the description field and writes into it.
- What if my collection is heavily customized?
- The article still lands. Field mapping follows common collection field names, so unusual extra fields stay empty for you to fill in Webflow.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
Framer
Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.
Ghost
Articles arrive in your Ghost site through Ghost's Admin API, with content, images and metadata ready to review in Ghost's editor. New connections publish as drafts, so nothing goes live until someone presses publish in Ghost.
Wix
Wix stores posts in Ricos, its own structured editor format, rather than HTML. So each article is converted, headings, lists, links and images, into that format before publishing, and posts open cleanly in the Wix editor as if written there.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the Webflow connection do the week's work. No card required.