How to publish a blog post to Webflow CMS

You add a blog post to Webflow automatically by having a tool create a new item in your blog collection through Webflow's API, then publishing that item so it appears on your live site. Every Webflow site with CMS content has collections, and a blog is simply one of them. Each post is one item with a set of fields: a name and a slug, which Webflow adds to every collection, plus whatever fields your site's designer created, such as a post body, a summary, a main image, an author, and categories. Your collection template page decides how those fields appear, so a new item becomes a finished page at an address like yoursite.com/blog/your-post-slug the moment it's published.

There are a few common ways to get a post into that collection. The simplest is to add the item yourself in the Designer's CMS panel or in the Editor, pasting the body into the rich text field and filling in the rest. Webflow can also import a CSV file into a collection, which works well for moving a batch of existing posts. Automation tools such as Zapier and Make have Webflow actions that create an item, either staged or live, whenever something happens elsewhere, such as a new row in Airtable or a finished document in Google Drive. Developers can call Webflow's CMS API directly to do the same thing.

Each of those routes copies what you give it into the fields you mapped. None of them decides what the slug should be, writes a summary that reads well in search results, picks the right author and categories, or adds links to your related posts. Rich text is also easy to break along the way. A body pasted from a document can lose its headings, carry stray formatting, or arrive with images that never made it into Webflow. And because Webflow keeps a difference between an item that is saved and an item that is published, an automation can create a post that nobody sees until someone publishes it.

A good result is a post that looks as if your best editor entered it by hand. Every field your template uses is filled in, the body keeps its headings and links, the post links to the right author and categories, the slug is short and readable, and the post is live at the address you expect.

Kite does that work for you. It learns how your blog collection is built, prepares each field to match, creates the post, and publishes it once you approve.

Start by telling Kite in Slack which post you want on your Webflow blog. You can hand it a finished draft:

"Publish the Google Doc I just shared to our Webflow blog under the Guides category, with Priya as the author."

Or you can ask Kite to write the post first:

"Write a post on how to choose a payroll provider for a 20-person company and publish it to our Webflow blog."

Kite is an AI marketer in your Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask, it already knows your brand voice, your products, and your customers from that research, so a post it writes sounds like you and links to the pages you care about.

You'll need to connect Webflow through OAuth so Kite can work in your site. Only a Webflow workspace owner or admin can authorize the connection, and one authorization covers every site in that workspace. Once it's connected, your Webflow site appears in your Kite website list next to any sites Kite built for you, and you never have to move your site off Webflow.

By default, Kite asks for your approval before it publishes anything to your live site. It shares the finished post in Slack, and you reply in the thread to approve it or ask for changes.

Kite starts by finding the collection your blog lives in and reading how it's built. It lists the collections on your site, picks out the one that holds your posts, and reads its fields: each field's name, its type, and whether Webflow requires it. That tells Kite exactly what a complete post looks like on your site. A typical blog collection has these fields:

• Name, which is usually the post's title
• Slug, which becomes the end of the post's address
• Post body, a rich text field that holds the article with its headings, links, lists, and images
• Post summary, a short plain text field that often appears on the blog index and as the search description
• Main image and thumbnail image
• Author, a reference to an item in a separate Authors collection
• Categories or tags, a reference to items in another collection
• A featured switch and a publish date, on many sites

Your collection may use different names or add fields of its own, such as a reading time, a call to action, or a separate SEO title. Kite works from the fields your collection actually has rather than from a standard list.

Kite reads your recent posts before it fills anything in, so the new one fits in with them. It looks at how long your summaries run, how your slugs are formed, how the body uses headings, and which authors and categories you already use. It also checks the collection for a post that already covers the same topic or already holds the slug it plans to use, because Webflow allows each slug only once in a collection.

Those existing posts are also where internal links come from. Kite picks the related posts and product pages a reader of this article would want next and links to them in the body.

Kite turns the post into content that fits each field, whether it wrote the post or you handed it one. When you share a document, Kite reads it from the Slack thread and keeps your words. When Kite writes the post, it researches the topic first, including the questions people search for and the pages that already rank, then writes in your brand voice.

Either way, Kite formats the body as rich text, so headings stay headings, links stay links, and lists stay lists in Webflow. It writes a summary that reads well on its own, because that line often shows up on your blog index and in search results. It chooses a short slug made from the post's main idea rather than the full title. For the main image, it uses one you supply or creates one in your brand's style, and it writes alt text that describes the picture.

Kite links the post to the author and categories that already exist on your site, so the post shows up in the right places. In Webflow, an author or category on a post isn't plain text. It's a link to an item in another collection, which is what lets your site show an author's bio or list every post in a category. Kite reads those collections, matches the author and categories you named, or the ones that fit the topic, and connects the post to them.

Kite creates the post as a new item in your blog collection, with every field filled in, and then publishes it once you approve. Before anything goes live, it shares the post in your Slack thread with its title, slug, summary, author, categories, and image, so you can review exactly what will appear.

Webflow treats saving and publishing as separate steps, and Kite always tells you which one it has done. An item can be saved without being published, and visitors only see it after it's published. Webflow can publish a single item, or it can publish the whole site. A whole-site publish ships every staged change on the site, including anything a teammate is still working on in the Designer, so it's worth knowing which kind of publish a post needs. Kite reports whether each change it made is staged or live, and you can ask it to keep the post saved but unpublished if you'd rather give it a final read in Webflow.

After the post is published, Kite reads the item back from Webflow and opens the page on your site to confirm it's there. It checks that the title, body, image, author, and categories appear the way your other posts do, and it posts the live link in the Slack thread where you asked.

From there, Kite can keep the post working. It can turn the article into social posts for your connected accounts, update the post later when something changes, or ask the questions the post answers in ChatGPT, Gemini, Perplexity, and Claude to see whether answer engines start citing it. If you want a steady publishing rhythm, ask Kite to research, write, and publish a new post every week, and it will share each one for your approval in the same thread.

When Kite finishes, your Webflow blog has a new post that looks like the rest of your blog, and your Slack thread records what was published and where.