How to Add a Blog to a Webflow Site and Keep It Publishing

To add a blog to Webflow, you create a CMS Collection to hold the posts, design one Collection page template that every post inherits, add a listing page at /blog so readers can find them, and check a handful of SEO settings before you publish. Webflow ships with everything you need for this, but nothing arrives assembled, and the part most sites get wrong comes afterwards: keeping the blog publishing once the launch enthusiasm wears off.

This guide covers the setup in order, then the plan and limit questions people often trip over, then the API and token details a developer will want if you plan to automate posting. By the end you should be able to stand up the collection and publish a first post the same afternoon.

Before you start: what you need in place

A Webflow blog relies on the CMS, so check three things first:

• A CMS-capable site plan. Collections, Collection pages and CMS publishing to a custom domain need a site plan that includes the CMS. A basic static plan will not carry a blog, and the free staging plan is for building, not for a live production blog. Check the current plan comparison on Webflow's own pricing page, as plan names and item limits change.
• Designer access to the site. You need to create the Collection and template in the Designer. Content editors can write posts later in the Editor, but someone has to build the structure first.
• A connected custom domain. You can build on the webflow.io subdomain, but the blog should go live on your real domain so the posts build authority for your business, not a staging address.

If your site is already live, adding a blog does not disturb existing pages. You are adding a Collection and one new static page, then a link in your navigation.

Step 1: Create the CMS Collection that holds your posts

In the Webflow Designer, open the CMS panel and create a new Collection. Webflow offers a Blog Posts template with sensible defaults, and it is fine to start from it, but check the fields cover what you actually need. A workable minimum:

• Name: the post title. Webflow creates this and the slug automatically.
• Slug: the URL fragment for the post. Edit it to be short and descriptive rather than accepting the auto-generated one.
• Post body: a Rich Text field. This is where the article lives, headings and all.
• Post summary: a Plain Text field for the excerpt shown on listing pages.
• Main image: an Image field, used on the post and as the social sharing image.
• Published date: a Date field you control, separate from Webflow's internal timestamps, so you can backdate or schedule sensibly.

Resist adding ten optional fields on day one. Every field is a decision someone has to make on every post, and empty fields are a common reason drafts stall. You can add categories, authors and related-post references later once you know you need them.

Step 2: Design the Collection page template

Creating the Collection gives you a Collection page, a single template that renders every item. Design it once and every post inherits the layout. The essentials:

1. Bind a heading element to the Name field. This becomes the H1, so use only one.
2. Bind a Rich Text element to the Post body field, then style each element type (H2, H3, paragraphs, lists, quotes) inside it. Style the Rich Text element itself with a class, not the page, so the styling follows the field everywhere it appears.
3. Bind the Published date and Main image where you want them.
4. Open the page settings and bind the SEO title and meta description to Collection fields. Webflow lets you compose these from fields, so the Post summary can double as the meta description if you write it with that in mind.
5. Bind the Open Graph image to the Main image field, so posts shared on LinkedIn or elsewhere show the right picture rather than a generic site image.

Step 3: Add the listing page and settle the URL structure

Add a static page, usually at /blog, and place a Collection List on it bound to your Blog Posts collection. Show the title, summary, image and date, sorted by Published date, newest first. Add pagination once you pass a dozen or so posts. Then add a Blog link to your main navigation or footer, so both visitors and search engines can reach the listing from every page.

Webflow fixes your post URLs to the pattern /collection-slug/post-slug, so the Collection's own slug matters. Set it to blog before you publish anything, giving you /blog/your-post-title. You cannot nest posts under dated folders or add category paths to the URL, and for a small business blog that is no loss. What you should not do is change the Collection slug later, because every published URL changes with it and you will need 301 redirects, the permanent redirects that pass visitors and search ranking to the new address, for each one.

Optional: categories, authors and related posts

Once you have a handful of posts, a little structure helps readers browse. Each of these is a separate Collection linked to your posts with a reference field:

• Categories. Create a Categories Collection, add a Reference field on Blog Posts pointing to it, and Webflow gives each category its own template page at /category-slug/category-name. Keep the list short. Five categories with ten posts each is more useful than twenty categories with two.
• Authors. Worth it only if more than one person writes. An author page with a short bio helps readers judge who is speaking.
• Related posts. Add a Collection List to the post template filtered to the same category, excluding the current item. It keeps readers on the site without anyone choosing links by hand.

If you are the only writer and have fewer than ten posts, you probably do not need any of this yet.

Step 4: Check the SEO plumbing before the first post

Three settings, all in Site Settings under the SEO tab:

• Sitemap. Turn on auto-generation. Webflow adds every published CMS item automatically at /sitemap.xml.
• Indexing. Make sure your webflow.io staging subdomain is set to be excluded from search engines, and your custom domain is not. Sites do occasionally launch with this backwards.
• Canonical tag. Set the global canonical URL to your live domain, so search engines treat the custom domain as the real site rather than the staging copy.

Then verify the site in Google Search Console and submit the sitemap. If you have never done that, setting up Search Console takes about ten minutes and is the only free way to see whether your posts are actually being indexed.

Step 5: Publish the first post properly

Write the post in the CMS panel or the Editor, fill in the summary and image, set the date, then publish. One Webflow quirk to know: saving a CMS item as published stages it, but the change only goes live when the site itself is published, unless you use the item-level publish option. If a post you swear you published is not on the live site, this is almost always why.

After publishing, paste the post URL into the URL Inspection tool in Search Console and request indexing. It does not guarantee a quick result, but it usually shortens the wait for a new site.

Common problems and how to fix them

• The post is live but looks unstyled. The styling was applied to elements on one page rather than to the Rich Text element's class. Restyle the class in the template.
• The post is not on the listing page. Check the Collection List's filters and sort order, and that the item is published, not just saved as a draft.
• Google shows the webflow.io address. The staging subdomain was left indexable, or the canonical URL is missing. Fix both settings, republish, and resubmit the sitemap.
• Posts are not appearing in Google at all. Give it time first: new sites can take weeks, not days. If Search Console reports the pages as excluded, its report usually says why.

Automating publishing: what a developer will ask about

If a tool or script is going to post for you, the questions your developer raises are predictable, so here are the answers.

• API access. Webflow's Data API (v2) creates, updates and publishes CMS items. You generate a site token under Site Settings, Apps and Integrations. Tokens are scoped, so grant CMS read and write plus sites publish, and nothing broader.
• Creating items. The API creates an item as a draft or as staged content. Publishing it live is a separate call, either publishing the item or republishing the site. A tool that only creates drafts still needs a human to press publish, which defeats the point of automation, so confirm the integration publishes live.
• Rich text. The post body is sent as HTML into the Rich Text field. The template styling you built in step 2 applies automatically, which is why getting that styling right once matters.
• Images. Image fields take a URL that Webflow fetches and hosts. Check the tool sets the Main image too, or every automated post will share as a blank card.
• Rate limits. The API is rate limited per minute. Irrelevant for one post a day, worth knowing if you ever migrate a back catalogue in bulk.
• Plan requirements. API publishing needs a site with a CMS-capable hosting plan. The free staging plan will not carry a production blog.

Keeping it publishing is the real job

The setup above takes an afternoon. The blogs that generate enquiries are the ones still publishing a year later, and that is a scheduling problem, not a Webflow problem. Decide a cadence you can genuinely sustain, put it in the calendar, and plan topics around what you sell rather than what occurs to you on the day. If you are unsure what a realistic pace looks like, we have written before about how often a small business should publish: consistency beats volume every time.

Your realistic options are to write it yourself, pay a freelancer or agency, or use a tool that drafts and publishes for you. Each suits a different budget and level of involvement, and there is an honest comparison of agencies, freelancers and AI tools if you are weighing them up.

Where Helio SEO fits in

Helio SEO publishes natively to Webflow through the API route described above: you connect the site, and it drafts, styles and publishes an article a day in your own voice, with manual approval if you want it. If you have a writer and a routine already, the setup in this guide is all you need. If the Collection is likely to sit empty after week three, this is how Helio SEO works.

Related: How to Add a Blog to a Wix or Squarespace Site (and Publish Automatically), Adding a Blog to a Site You Built With Lovable, Bolt or v0, The Best Blogging Platform for a Small Business in 2026: WordPress, Shopify, Webflow, Ghost or None of Them