Creates posts
Each post becomes a new item in the blog collection you choose.
The title goes to the Name field, and the slug is made from the title. The article and the other parts go to the fields you pick.
Webflow integration
RankHouse is an AI agent doing SEO work for your business. It writes blog posts made to be found in Google and in AI answers, and the Webflow integration saves each one as an item in your blog collection.
You connect once from your RankHouse account, pick the collection, and check which field gets each part of a post. A post goes live only when you publish it, in RankHouse or in Webflow.
Blog posts only for now. One website per account.
RankHouse plans and writes the posts. The integration is how they reach your Webflow site.
Each post becomes a new item in the blog collection you choose.
The title goes to the Name field, and the slug is made from the title. The article and the other parts go to the fields you pick.
Edit a published post in RankHouse and save it, and the same Webflow item is updated.
Its address (the slug) and its publish date stay as they were.
Delete a post in RankHouse, and it is removed from your live site and from the CMS.
RankHouse asks only for Sites: Read and CMS: Read and write. It writes only to the collection you choose, adds no code or scripts to your site, and never touches your pages, styles or site settings.
A post's address is your site, then the collection's slug, then the post's slug. For example: yoursite.com/post/your-post-title.
Check these once in Webflow. Most setup problems come from one of them.
The quickest way. Webflow asks you to approve RankHouse, and there is no token to copy.
Sign in to RankHouse, open Account, then Integrations, and choose Webflow.
Webflow opens and asks you to approve RankHouse for one or more of your sites.
Pick your site and approve. Webflow sends you back to RankHouse, connected.
Pick your blog collection and check the fields, as shown below.
| Access RankHouse asks for | Why it needs it |
|---|---|
| Sites: Read | To list the sites you approved, with each site's name and address |
| CMS: Read | To list your collections and their fields, so you can pick where each part of a post goes |
| CMS: Write | To create, update and delete the blog posts RankHouse publishes |
Approved more than one site? Choose the one this account writes for. One RankHouse account covers one website.
Use this if Connect with Webflow isn't available to you. A site API token connects one site.
Open your site's settings in Webflow, then Apps & integrations, then API access. Press Generate API token, and give it Sites: Read and CMS: Read and write.
Keep it somewhere safe until you paste it.
Open Account, then Integrations, then Webflow, and paste the token. RankHouse checks it with Webflow straight away.
Pick your blog collection and check the fields, as shown below.
RankHouse stores the token encrypted and never shows it again. To use another token later, paste the new one on the same card.
Every Webflow blog names its fields differently, so RankHouse suggests a match and you check it before anything is saved.
Choose the CMS collection your blog posts live in. RankHouse suggests the one that looks like a blog.
For each part of a post, pick the field that gets it, or leave it empty. Only the article body is required.
Press Connect Webflow. From then on, posts go to that collection, with those fields.
| Part of a post | Webflow field type | Needed? |
|---|---|---|
| Title | Name (Webflow's own field) | Always filled |
| Address | Slug, made from the title | Always filled |
| Article body | Rich Text | Required |
| Summary | Plain text or Rich Text | Optional |
| Main image | Image | Optional |
| Thumbnail image | Image | Optional |
| SEO title | Plain text | Optional |
| Meta description | Plain text | Optional |
| Publish date | Date/Time | Optional |
| Author name | Plain text | Optional |
| Tags | Plain text | Optional |
| Reading time | Plain text or Number | Optional |
You can change the collection or the fields at any time on the same card. Posts published before the change stay in the collection they went to.
Once Webflow is connected, every way of publishing in RankHouse can send a post to it.
Open a post and press Publish to Webflow.
It goes to Webflow straight away.
Open Content, then the Blog posts tab.
Sync sends one post (Re-sync sends your latest edits), Publish selected sends the posts you tick, and Publish all waiting sends every post that isn't live yet.
With Agent Auto Publish on, the agent sends each new post by itself.
On Webflow, these posts land as drafts for you to review.
You press Publish in RankHouse, and the post goes live on your site.
You press Publish in RankHouse, and the post lands in Webflow as a draft.
You publish it in Webflow when you're ready.
The agent sends each new post to Webflow by itself, as a draft.
You review it and publish it there.
Every new connection starts on Manual Publish. Change the mode at any time on the Webflow card, under Account, Integrations.
RankHouse remembers which Webflow item each post became, so later changes reach the same item.
The Webflow integration covers blog posts for now. When anything else reaches the publish step, RankHouse leaves it out and says why.
These are the messages you are most likely to see, and what to do about each one.
The token was deleted in Webflow, or only part of it was copied. Generate a new token and paste the whole of it.
The token doesn't have everything RankHouse needs. Generate a new one with Sites: Read and CMS: Read and write. If you used Connect with Webflow, press it again and approve.
Add a blog collection in Webflow, with a Rich Text field for the article, then reload the list on the card. If the site is on the Basic plan, move it to a plan with the CMS first.
You picked a collection without one. Choose your blog collection, or add a Rich Text field to this one in Webflow.
The card names it. Choose it for one of the parts of a post, or make it optional in the collection settings in Webflow, then save again.
The collection template page has nothing on it from the collection yet. In the Designer, open the collection's template page, add elements connected to its fields (at least the name and the article body), then publish the site.
Webflow saved the post but didn't put it live by itself. This happens on Webflow's free Starter plan and on a site that has never been published. Publish the site in Webflow, and the post goes live. A deleted post leaves the live site the same way, the next time the site is published.
The collection or the site changed after this post was published. To update or delete it from RankHouse, switch the Webflow card back to that collection or site. Or manage the post in Webflow.
Still stuck? Email us the message you see, as described at the end of this page.
Open Account, then Integrations, then Webflow, and press Disconnect. RankHouse stops publishing to the site and forgets its token. If you connected with Webflow, RankHouse also asks Webflow to withdraw its access.
For a pasted token, delete it in your site's settings under Apps & integrations, API access. For Connect with Webflow, remove RankHouse from the apps under Apps & integrations.
Posts already on Webflow stay there. They are ordinary items in your collection, and you can edit or delete them in Webflow like any others. Your posts also stay in your RankHouse account.
| What RankHouse keeps | Why, and for how long |
|---|---|
| Your Webflow access token, encrypted | To publish to your site. It is never shown again, and it is deleted when you disconnect. |
| Your site, collection and field choices | So each post goes to the right place. Deleted when you disconnect. |
| The Webflow item id of each post it published | So it can update or delete that post later. |
RankHouse has no access to your form submissions, your store orders or your site's visitors. The privacy policy lists everything RankHouse keeps.
Email support@rankhouse.ai with your site's address and the message you see, and a person will help you connect.
Webflow is a trademark of Webflow, Inc. RankHouse is not affiliated with or endorsed by Webflow.