Skip to main content
Webflow has no fixed blog schema — every site names its CMS fields differently. So this connector has an extra step the others don’t: after connecting, you tell us which collection to write to and which of your fields should hold each part of the article. You connect with a Webflow API token generated on your own site. It works with any Webflow account, including one under a different email from your SeoSorted login.

​
Before you start

  • A Webflow site with a CMS collection for your posts (a blog collection created from any Webflow template works).
  • Access to that site’s Site settings in Webflow, so you can generate an API token.
  • The collection needs a Rich text field for the body. Its Name field holds the title.

​
Step 1 — Create a Webflow API token

  1. In Webflow, go to Site settings → Apps & integrations → API access.
  2. Click Generate API token.
  3. Enter a name for your API token, e.g. SeoSorted.
  4. Choose the permissions. The token must have these permission scopes:
    • sites: read
    • assets: read + write
    • cms: read + write
  5. Click the Generate token button.
  6. Copy the generated token to your clipboard.
Webflow shows the token only once. If you lose it, generate a new one — the old token keeps working until you delete it in Webflow.
A site API token reaches only the site it was generated on. We use it to read your collections, create and update CMS items and upload article images. We cannot edit your designs.

​
Step 2 — Connect in SeoSorted

  1. In SeoSorted, open Project Settings → Integrations and click Connect on the Webflow card. (During onboarding, choose Webflow on the publishing step.)
  2. Paste the token into API token and click Connect.
We check the token against Webflow before saving it. If it’s wrong or missing a permission you’ll see why straight away — see Common problems.

​
Step 3 — Choose a collection and map fields

The collection dialog opens as soon as you connect. If you closed it, the card shows Connected — Setup required: pick a collection:
  1. Open the card’s ⋮ menu.
Webflow card marked Connected with Setup required — pick a collection, and the ⋮ menu button highlighted

The card's ⋮ menu

  1. Choose Finish setup. (You can also click Publish on any article and choose Finish setup there.)
Webflow card menu open with Finish setup highlighted above Disconnect

⋮ → Finish setup

Pick the site and the collection that holds your posts. Every field in that collection is then listed, with the fields your collection requires at the top.
  • Each dropdown only offers article values that fit that field’s type — the body can only go into a Rich text field, images only into Image fields, the publish date only into a Date field.
  • We pre-fill the obvious matches from your field names and types — Name, Slug, Post Body, Post Summary, Main Image, Thumbnail, Meta Title, Published Date and so on.
  • Fields that can’t come from an article — an Option such as Category, a Reference such as Author, a Switch, a Link or a Color — can take a fixed value that every post you publish gets. Options and references are chosen from what already exists in your Webflow CMS.
  • Save configuration stays disabled until every field your collection marks as required has a value. Webflow rejects an item with an empty required field, so we stop it here instead of at publish time.
  • Added a field in Webflow while the dialog was open? Click Refresh fields.
Configure Webflow dialog with the Site and Collection dropdowns highlighted and the collection's fields listed below

Site and collection — every field below is pre-filled where we can match it

  1. Check the mapping, then click Save configuration. The card drops the Setup required note.
Bottom of the Configure Webflow dialog with the Save configuration button highlighted

Save configuration

​
What can go where

Plain text values are stripped of formatting and trimmed to the field’s character limit. Images are sent with alt text — the article title, unless you map an alt-text field.
Confirm the pre-filled mapping before saving. A collection with several Rich text fields (body, author bio, disclaimer) needs the body on the one your template renders as the post.

​
Step 4 — Publish

Open an article, click Publish, then Publish now next to Webflow (it reads Finish setup until the mapping is saved). We create one collection item with your mapped fields.
Publish Article dialog with Webflow listed and the Publish now button highlighted

Publish → Publish now next to Webflow

Publish dialog showing Published and a note that the destination returned no public URL

Webflow returns no public URL, so the dialog confirms the publish instead

Items are created live where possible, so they appear on your published site right away if your templates already render that collection.If the site has never been published, Webflow refuses live items. We fall back to staging the item instead: it lands in your CMS immediately and goes out with your next site publish. Either way the publish succeeds.
The dialog confirms Article Published — “Added to your Webflow CMS — publish your site in Webflow to make it live” — with an Open in Webflow → button. Webflow returns no public URL, so there is no View article link.

​
Re-publishing, unpublishing and deleting

  • Re-publish updates the same CMS item in place. If the item was deleted in Webflow, a new one is created.
  • Unpublish removes the item from your live site; it stays in your Webflow CMS.
  • After an unpublish, SeoSorted forgets the item. Publishing the article again creates a new CMS item — if the old item still holds the slug, the new item gets a short suffix. Delete the old item in Webflow first if you want to keep the original slug.
  • Deleting the article in SeoSorted deletes the CMS item.
  • The article’s JSON-LD schema is never placed in the body. Map Article schema (JSON-LD) to a plain-text field and render it in an Embed element if you want it on the page.

​
Tracking AI crawlers on a Webflow site

Webflow doesn’t allow server code, so AI crawler tracking runs in a Cloudflare Worker in front of your site, using Webflow’s supported Orange-to-Orange setup. It needs a paid Site plan. Follow Webflow in the tracking guide.

​
Common problems

The token was mistyped, deleted in Webflow, or copied only partly. Generate a new token in Site settings → Apps & integrations → API access and paste it again.
The token is missing a permission. Generate a new token with sites: read, assets: read + write and cms: read + write, then connect again.
A token belongs to one site. Disconnect Webflow, generate a token on the other site, and connect with it.
Your collection marks that field as required, and Webflow rejects items that leave it empty. Fill it from an article field, or choose Set a fixed value… — for a Category option or an Author reference, pick the value every post should get.
The collection and field mapping were never saved. Click Finish setup there, or open Project Settings → Integrations → Webflow → ⋮ → Finish setup, and save the configuration.
Articles published to Webflow before 15 September 2026 carried the article’s structured data inside the body. Edit the article and Re-publish it to replace the body. Structured data is now a separate value you can map to a field you render in an Embed element.
Webflow only serves CMS content after a site publish. Publish the site in the Webflow Designer, and confirm your templates actually render that collection.