Webflow Integration

How the Webflow Integration Works

RankPush connects to one Webflow site through a site-scoped API token and writes every finished article into the CMS collection you choose — title, body, featured image, meta description, and publish date land in the fields you map. Editing an article in RankPush later updates the same Webflow item in place, without changing its URL. There's no plugin to install and nothing added to your published site.

Before you begin, make sure you have:

• A Webflow site with CMS hosting (the integration writes to a CMS collection)
• A blog-style collection on that site (most templates ship one — usually called Posts or Blog Posts)
• Access to Site settings so you can generate an API token

Setup Instructions

Step 1: Generate a site API token

1. In Webflow, open Site settings → Apps & Integrations → API access
2. Click Generate API token
3. Give it a name (e.g. “RankPush”) and grant CMS: Read and write plus Sites: Read
4. Copy the token — Webflow shows it only once

This is a site token, scoped to one site. RankPush stores it encrypted, and it can never be viewed again from our side — to change it later, disconnect the integration and reconnect with a fresh token.

Step 2: Pick your site and collection

In RankPush, open Settings → Integrations → Webflow, paste the token, and choose the site it belongs to, then the collection your posts live in. RankPush reads the collection's schema directly from Webflow, so the next step always reflects your real fields.

Step 3: Review the field mapping

Every field in your collection is individually mappable, and RankPush pre-matches the obvious ones. For each field you can choose what feeds it:

• Text and rich-text fields — Title, Main Content, Meta Description, or Slug
• Image fields — the article's generated image
• Date fields — the publish date
• Reference, multi-reference, and option fields (Author, Category, Tags…) — a concrete item you pick, applied to every article
• Switch fields — a fixed on/off value

Required fields must all be mapped — Webflow rejects live items with any required field empty, so the form won't let you connect until each one has a value. Fields with character limits are handled automatically: RankPush trims to the limit at a word boundary instead of letting Webflow reject the item.

The mapping stays editable after connecting — it's always open on the integration page, and saving applies to every article published after the change.

Step 4: Choose publishing behavior and connect

Pick how articles should go live — Publish Immediately, Stage for review, or Save as Draft (each is described under Publishing Options below) — set the Article Tables preference, and click Connect.

Article Tables: Webflow's rich text has no table styling of its own, so comparison tables would render as bare unstyled rows. Leave Style tables for me on and RankPush adds clean borders and spacing on publish; turn it off if your site's stylesheet already styles table elements.

What Gets Published

Every article arrives complete — nothing needs manual cleanup:

• Title and slug — the slug is set once at creation and never changed by updates
• Full article body as Webflow rich text, with in-body images hosted on our durable CDN
• Featured image into the image field you mapped
• Meta description and publish date
• Your fixed choices — author, category, tags, and switch fields from the mapping

Publishing Options

Publish Immediately

The item is created and published to your live site in one step — full autopilot.

Stage for review

The item lands in the CMS but isn't published; it goes live with your next site publish from Webflow. Good for teams that batch-review before releasing.

Save as Draft

The item is created as a CMS draft for manual review and publishing.

How updates work

When an article is edited or improved in RankPush after publishing, the same Webflow item is updated in place — the slug (and therefore the URL) never changes on an update. Items published live are re-published live; staged items stay staged until your next site publish.

Known limitations

• Image alt text: Webflow's rich-text importer strips alt attributes from in-body images — a Webflow API limitation, not a mapping problem. RankPush articles carry descriptive alt text on every image, and it survives on WordPress and webhook targets; on Webflow it currently renders empty. We're tracking a fix through Webflow's asset metadata API.
• One collection per site — the integration writes to the single collection you picked. Reconnect to switch collections.
• Reference items must exist first — the Author or Category you map must already exist in Webflow; RankPush picks from existing items and never creates new ones.

Troubleshooting

“Invalid token” or a 401 while connecting

The token is wrong, expired, or missing scopes. Generate a new one with CMS Read/Write + Sites Read and try again.

“Field is required” on publish

A required field in the collection has no mapping (this can happen if you add a new required field in Webflow after connecting). Open the integration page — missing fields are flagged there — map it, and save.

Articles publish but don't appear on the live site

Publishing behavior is set to Stage or Draft. Either switch to Publish Immediately or publish the site from Webflow to push staged items live.

Tables look unstyled

Turn on Style tables for me under Article Tables in the mapping panel.

Security & Best Practices

• Your API token is stored encrypted and is only decrypted at publish time — it can never be read back out of RankPush
• Grant only the scopes the integration needs: CMS Read/Write + Sites Read, nothing else
• To rotate the token, disconnect and reconnect — then revoke the old token in Webflow
• Disconnecting never deletes anything from your CMS

Frequently Asked Questions

• Can I see or change the API token after connecting? No — it's stored encrypted and can't be read back. Disconnect and reconnect with a new token.
• Does deleting the integration delete my published articles? No. Disconnecting only stops future publishing; everything already in your CMS stays put.
• Can different RankPush websites publish to different Webflow sites? Yes — each RankPush website has its own integration with its own token.

Other integrations

Publishing somewhere else? See WordPress or the API Webhook for any custom CMS.