Webflow uses API tokens with scoped permissions. Grant the cms:read and cms:write scopes (Read and Write for CMS) to publish, update and delete articles. Test Connection validates your field slugs against the collection.

What you'll need#

A Webflow site with a CMS collection for blog posts.
CMS API access enabled on your Webflow project.
Read and Write permissions on the API token.

Step 1 — Get your credentials#

1
Go to your Webflow project → Project Settings.
2
Click the Integrations tab.
3
Scroll to API Access and click "Generate API token".
4
Set permissions to Read and Write for CMS.
5
Copy and save your API token securely.
6
To find your Collection ID: CMS tab → gear icon on your blog collection → copy the Collection ID.
7
Make sure the collection has a rich-text body field (default slug "body"). Optional "meta-description" and "seo-title" fields are only filled when they exist; otherwise map your own slugs in the fields below.

Reference: Webflow CMS API Documentation.

Step 2 — Connect in Rankealo#

In Rankealo, open Integrations, choose Webflow, and fill in these fields:

Field	Required	Where to find it
Webflow Site URL	Required	Your published site URL, e.g. https://yoursite.webflow.io.
API Token	Required	Generated from Project Settings → Integrations → API Access.
Collection ID	Required	The CMS collection ID for your blog posts.
Content field	Optional	CMS field slug for the article body (default: body).
Excerpt field	Optional	CMS field slug for the meta description (default: meta-description).
SEO title field	Optional	Optional CMS field slug for a dedicated SEO title (default: seo-title). Skipped if the collection has no such field.
Thumbnail image field	Optional	Optional image field slug that receives the featured image URL. Rankealo does not upload to Webflow assets; inline article images stay hotlinked from their original URLs.
Blog path	Optional	Optional URL segment of your blog collection, e.g. /blog. If empty, Rankealo reads the collection slug from Webflow to build article links (site URL + /collection-slug/article-slug).

If your collection uses different field slugs, set the optional mapping fields so Rankealo writes to the correct CMS properties.

Click Test Connection. Rankealo verifies your credentials — you must see a successful test before Save Integration becomes available.

Updating credentials later

Secrets are write-only. When you reopen a saved integration, secret fields show “leave blank to keep existing” — only re-enter them if you are rotating keys.

What gets synced#

When Rankealo publishes, each article carries:

TitleThe article title.
ContentFull article body as HTML (or markdown where the platform supports it).
Meta descriptionSEO meta description / excerpt, where the platform has a field for it.
SlugGenerated from the title when the item is created (an existing item with that slug is adopted). Never changed on update.
SEO titleWritten only if the collection has the SEO title field.
ExcerptThe meta description is written to the excerpt field only if the collection has it.
Featured imageOnly when a Thumbnail image field is set; sent as an image URL, not uploaded to Webflow assets.

Slug, featured image, tags and SEO title depend on the platform and your field mapping. Each platform guide lists exactly what it sends.

Updates & re-publishing#

Rankealo tracks the post it created for each article. When an article is edited — or automatically re-optimized by Improvements — Rankealo updates the same post in place rather than creating a duplicate.

Troubleshooting#

Test connection fails+

Confirm the API token has the cms:read and cms:write scopes and that the collection ID matches your blog collection. Test Connection also reports configured field slugs that do not exist in the collection.

Publish succeeds but content lands in the wrong field+

Check the Content, Excerpt, and SEO title field slugs against your Webflow collection schema.

403 or permission errors+

Regenerate the token with CMS Read/Write scope. Site Designer-only tokens without CMS access will not work.

Webflow