SEO articles, published to Webflow on auto-pilot
For a designer or a marketing lead running a Webflow site. One API token and a collection ID connect Rankli to your CMS, and 30 finished articles a month arrive as items in the collection your blog template already renders.
Cancel any day from the app. Unused articles refunded.
Four steps, and the last one is ours
A token with CMS write access, the collection to write into, and the field slugs your collection actually uses. Nothing is sent until all three check out.
Connect WebflowGenerate an API token
Site settings → Apps and integrations → API access → Generate API token. Give it the CMS capability with write access. Webflow shows the token once, so copy it then.
Find the collection ID
Open the CMS panel, select the collection your posts live in and open its settings. The collection ID is the 24-character hex string in the URL and on the settings panel.
Map your field slugs
The mapping defaults to Webflow’s own blog template. Change any that differ: a field called Post Body usually has the slug post-body, and the slug is what the API uses.
We verify it before anything is sent
Saving fetches the collection and checks every mapped field exists and is the right type. A rich-text field mapped onto a plain-text one is caught here rather than at the first article.
Five concepts, your field names
These are the defaults, taken from Webflow’s own blog template. Change any that differ on your collection. The full walkthrough is in the Webflow guide.
Live or staged, per connection. Live publishes the item to the live site in the same call. Staged puts it in the CMS as a draft item for someone on your team to publish.
15 checks on every draft. Nine can stop it.
The rules are enforced in code on every article, and the verdict is written on the article itself, so a review is a scorecard rather than a full read.
- No invented specifics. An unsourced percentage, an academic-style citation, a dated study, a quote attributed to a person: each is a hard failure.
- Subject coverage. A draft that covers the topic without covering your subject is refused rather than scheduled.
- 1,500 to 3,000 words, with every section measured, so no heading arrives with two sentences under it.
- Your banned phrases. A list you set, enforced across the title, the summary and the body.
- Keyword placement without stuffing. In the title, the first hundred words and an H2, under a density ceiling.
- Internal links to your own pages. Contextual links into real articles and product pages, never into your terms page or your login screen.
9 of the 15 are hard: a draft that fails one does not reach your collection.
Then we measure what the items did
Your own Search Console
Impressions, clicks and position per published page, and the queries each one actually ranks for, read from Google’s report on your property.
4 answer engines
ChatGPT, Perplexity, Gemini and Claude, asked your tracked questions every month, 6 times each.
A pre-registered experiment
A held-out control and a prediction written down first, so a rise in citations is a result rather than a coincidence.
A rewrite when it is close
An item on the edge of page one gets a proposed rewrite aimed at the query it is nearest to winning, written back to the same item.
Running a store, a SaaS or a local service? For ecommerce, for SaaS, for local business.
Webflow publishing, answered
My collection does not use Webflow’s default field names. Does that matter?
No, that is what the mapping is for. Webflow has no fixed blog schema, so the connection carries a mapping from our five concepts onto your collection’s own field slugs, and you can change any of them. Everything is checked against the live collection when you save.
Does an article go straight onto the live site?
Your choice, per connection. In live mode the item is published to the live site as part of the same call. In staged mode it appears in the CMS as a draft item and someone on your team publishes it. Start staged, read a month of writing, then switch it to live.
Where do the images end up?
Images are handed to Webflow by URL and Webflow re-hosts them on its own CDN, so the item does not depend on our storage. Every article gets a cover image and in-article images with alt text.
What happens if a mapped field does not exist?
The save fails with the field named, not the first article three weeks later. Checking the collection up front is why the commonest opaque Webflow 400 does not happen on a Rankli connection.
Webflow limits CMS items per plan. How should I plan for that?
Publishing reports Webflow’s own message when the limit is reached, so it is worth sizing the collection for the cadence you want. 30 articles a month is what Growth publishes, and the calendar is visible a month ahead so you can see what is coming.
What does it cost?
Growth is $99 a month for 30 finished articles with research, images, publishing and measurement included. Start on the $1 trial for 3 of them in your own collection, and nothing renews.
Connect Webflow in about five minutes.
$1 once buys 3 finished articles in your own collection. One of 10 connections Rankli publishes to.
Cancel any day from the app. Unused articles refunded.