Webflow
Publish your articles straight to a Webflow CMS collection, with optional field mapping and two-way sync.
RankTurn publishes your articles directly to a Webflow CMS collection. Each article becomes a CMS item that RankTurn can publish live right away or leave as a draft. You can also turn on two-way sync, so edits you make in Webflow flow back into RankTurn.
For an overview of how all integrations work, see Integrations. For how the two-way flow behaves across platforms, see Bidirectional Sync.
Prerequisites & API Token Scopes
You need:
- A Webflow account with at least one published site
- A CMS collection on that site (Webflow's built-in Blog Posts template works out of the box)
- A site API token with the right scopes
To create the token:
- Log in to Webflow and open the site you want to publish to
- Go to Site settings → Apps & integrations → API access
- Click Generate API token
- Copy the token immediately — it is shown only once
Grant the token at least these scopes:
| Scope | Permission | Why |
|---|---|---|
| CMS | Read and write | Create, read, and update collection items |
| Sites | Read | Verify the site and list collections during the connection test |
If you plan to turn on two-way sync, RankTurn sets up the instant-update notifications for you using this same site API token, so make sure the token has permission to manage site notifications.
Finding Site ID & Collection ID
RankTurn needs both your Site ID and the Collection ID of the collection that will hold your articles.
Site ID
- Open the Webflow dashboard and select your site
- Go to Site settings → General, where the Site ID is listed; or
- Read it from the settings URL:
https://webflow.com/dashboard/sites/{site-id}/general
Copy the {site-id} portion.
Collection ID
- From the dashboard, open your site's CMS
- Select the collection you want to publish to (e.g. "Blog Posts")
- Copy the
{collection-id}from the URL:
https://webflow.com/dashboard/sites/{site-id}/cms/{collection-id}
When you connect, RankTurn checks both IDs by looking up the site's collections and confirming the Collection ID exists.
Field Mapping
RankTurn writes your article data into specific Webflow field slugs. Two fields use Webflow's standard blog defaults; the rest are written only when you map them to a field slug in your collection. Every field is optional except the always-present name and slug.
| Article data | Default field slug | Notes |
|---|---|---|
| Title | name | Always set; standard in every collection. Clamped to 256 characters. |
| URL slug | slug | Always set; generated from the title. |
| Body (HTML) | post-body | Override with Content Field Name if your collection uses a different slug. |
| Summary / meta description | post-summary | Uses the article excerpt or meta description, clamped to 500 characters. Override with Summary Field Name. |
| Tags | unmapped by default | Written only if you set Tags Field Name. Tags are joined into a comma-separated plain-text string (Webflow multi-reference fields aren't supported here). |
| Author | unmapped by default | Written only if you set Author Field Name. |
| Canonical URL | unmapped by default | Written only if you set Canonical Field Name. |
| Structured data (Schema.org) | structured-data | The article's structured data is written into this field. Override with Structured Data Field Name. |
To find a field's slug in Webflow:
- Open the collection and go to its Settings
- Each field shows a Field slug beneath its name
- Enter that slug in the matching field-name input when connecting in RankTurn
If you use the built-in Blog Posts template, the content and summary defaults match, so you can leave those inputs blank. The thumbnail/feature image is set by Webflow's own feature-image field — RankTurn removes the thumbnail from the body so it isn't duplicated, and sizes inline images to fit your layout.
Connecting in RankTurn
Connecting Webflow requires an active paid subscription — the Connect step (and therefore publishing to Webflow) is blocked on the free plan. See Plans & Billing.
- Go to Settings → Integrations
- Find the Webflow card and click Connect
- Fill in the form:
| Field | Value |
|---|---|
| API Token | The site token from the Prerequisites step |
| Site ID | Your site's ID |
| Collection ID | The target collection's ID |
| Publish Format | Publish (live) or Draft |
| Content Field Name | Optional — leave blank to use post-body |
| Summary Field Name | Optional — leave blank to use post-summary |
| Tags Field Name | Optional — leave blank to skip tags |
| Author Field Name | Optional — leave blank to skip author |
| Canonical Field Name | Optional — leave blank to skip canonical URL |
| Structured Data Field Name | Optional — leave blank to use structured-data |
- Click Connect. Before saving, RankTurn tests the connection by looking up the site's collections and confirming the Collection ID exists.
To change any of these later, click the Settings button on the connected Webflow card. Leave the API Token blank when editing to keep the existing token.
Your token is stored encrypted. For more, see Credentials & Security.
Bidirectional Sync & Import New
After connecting, the Webflow card shows a Bidirectional Sync toggle.
When you enable it, RankTurn automatically asks Webflow to send an instant update whenever something happens to an item in your collection:
- An item is created
- An item is changed
- An item is deleted
- An item is unpublished
When any of these happen, Webflow notifies RankTurn. RankTurn always pulls the latest version of the item straight from Webflow, then matches it up with your articles:
- Created or changed: RankTurn finds the matching article and updates its title, content, and summary to match Webflow.
- Deleted or unpublished: the matching article goes back to Draft in RankTurn.
- Conflicts: if you edited the article in RankTurn after the last sync, the Webflow version wins, and the change is noted in the sync log.
- No-op: if the incoming content matches what RankTurn last sent, nothing changes — this keeps the two sides from updating each other in a loop.
Turning on two-way sync also shows an Import New toggle:
- Off (default): updates only apply to articles that already exist in RankTurn. Brand-new items you create directly in Webflow are ignored.
- On: new Webflow items with no matching article are brought into RankTurn as Draft articles. These imports do not count against your article generation quota — they're imports, not generations.
Turning two-way sync off again removes the update notifications RankTurn set up.
Bidirectional sync requires an active paid subscription. See Plans & Billing.
Publishing Behavior & Troubleshooting
Once Webflow is connected, it shows up as a destination when you publish or schedule an article. For each article, RankTurn:
- Creates a URL slug from the title (and uses an automatic fallback slug if the title can't produce one, for example a title with no Latin characters)
- Removes the thumbnail from the body and sizes inline images to fit
- Creates a CMS item with your mapped field data
- If you chose the Publish format, pushes the item live in Webflow
- Links the new Webflow item back to your article
Common errors:
| Message | Cause & fix |
|---|---|
| Collection not found | The Collection ID isn't in this site. The error lists the available collections — copy the correct ID from the CMS URL. |
| Invalid credentials | The API token is wrong or expired. Regenerate it in Webflow's site settings and update the connection. |
| Failed to create item | A mapped field slug doesn't exist in the collection. Verify each field name matches the actual field slug in Webflow. |
| Item created as draft but publish failed | The CMS item was created, but publishing it failed (often because of a site publish restriction). Publish it manually from the Webflow Designer. |
Even when an item publishes successfully, Webflow may require a full site publish before your CMS changes show up on the live site. RankTurn publishes automatically, but if your site has publish restrictions, you may need to publish from the Webflow Designer.
For scheduling and automatic publishing, see Publishing & Scheduling.