Most website builders make you choose between design control and a decent content management system. Webflow gives you both.
Learning how to create a blog in Webflow means working with CMS Collections, dynamic templates, and a publishing workflow that non-developers can actually use day to day.
This guide covers everything from setting up your first Collection to configuring blog post URLs, categories, SEO meta fields, and your custom domain.
By the end, you will have a fully functional blog index page, a dynamic post template, and a clear picture of where Webflow’s blog tools are strong and where they have real limits.
What Is a Webflow Blog?
A Webflow blog is a content system built on CMS Collections, not static pages. Each blog post is a Collection Item rendered through a shared dynamic template page, meaning one design automatically generates individual pages for every post you publish.
This is different from how most platforms handle blogging. WordPress depends on plugins and a separate database. Squarespace locks you into its template system. Webflow handles the CMS natively, with no third-party tools required for basic blog functionality.
Understanding what Webflow is as a platform helps set the right expectations. It sits between a no-code site builder and a frontend development tool, and its blog architecture reflects that. The visual design and the content database are built and managed in the same interface.
| Platform | Blog Architecture | Plugin Required |
|---|---|---|
| Webflow | Native CMS Collections | No |
| WordPress | Post Types via Database | Often Yes (SEO, Forms) |
| Squarespace | Template-Locked Blog Blocks | No (Limited Control) |
Webflow currently powers over 822,000 websites globally, with its user base growing 67% in a single year (W3Techs, 2025). That growth is partly driven by design-focused teams who want blog functionality without handing content over to a developer every time a post needs to go live.
Upwork is a real example of this in practice. Their marketing team adopted Webflow to manage landing pages and content without raising engineering tickets for every update, which was the only option they had before.
The blog is one of the most common things people build in Webflow, and for good reason. Websites that blog have 434% more indexed pages than those that don’t (Marketing LTB, 2025), which compounds over time through organic search.
How fast is Webflow growing?
Dive into the latest Webflow statistics: adoption rates, revenue growth, designer trends, and how it's changing the no-code web design space.
See the Insights →What Are the Requirements to Start a Webflow Blog?
You need a paid Webflow CMS plan at minimum to publish a live blog. The free Starter plan lets you build and preview in the Designer, but you cannot publish to a custom domain or make CMS items visible to the public.
What Plan Do You Need for a Webflow Blog?
The CMS plan costs $23/month billed annually as of July 2024, following Webflow’s updated pricing. It supports up to 2,000 Collection Items, 500 monthly form submissions, and 3 content editors.
Here is how the plan tiers compare for blog use:
| Plan | CMS Item Limit | Content Editors | Custom Domain |
|---|---|---|---|
| Starter (Free) | Build Only, No Live Publish | 0 | No |
| CMS ($23/mo) | 2,000 Items | 3 | Yes |
| Business ($39/mo) | 10,000 Items | 10 | Yes |
For most new blogs, the CMS plan is enough. A site publishing 3 posts per week would take roughly 12 years to hit the 2,000-item cap. That said, if your Collections span blog posts, authors, and categories combined, the count adds up faster than you’d expect.
What Else Do You Need Before You Build?
Custom domain: Required for a public-facing live blog. You point your DNS records at Webflow’s servers after adding the domain in Project Settings.
Webflow account type: A free Workspace account is enough to get started. You only pay for the site-level hosting plan.
Existing site vs. new project: You can create a blog on an existing Webflow project or start a blank new site. The CMS setup process is the same either way.
One thing worth knowing before you start: Webflow Designer access is different from Webflow Editor access. Designers build the Collection structure and template pages. Editors (your writers or marketing team) update content through a simplified interface at yourdomain.com/edit without touching the Designer at all.
How to Create a CMS Collection for Blog Posts
The CMS Collection is the database structure that stores every blog post. You build it once, and every future post follows the same field structure automatically.
What Fields Does a Blog CMS Collection Need?
Go to the CMS panel in the Webflow Designer and click “New Collection.” Webflow offers a Blog Posts prebuilt template that adds a sensible default set of fields, though you can customize everything.
Two fields are required and cannot be removed:
- Name (plain text) – the post title
- Slug (auto-generated from Name) – controls the URL
Beyond those, the fields that actually matter for a functioning blog are:
- Rich Text – the post body, supports headings, images, embeds
- Image – thumbnail or hero image for the post card
- Plain Text – short excerpt for index page previews
- Reference – links each post to an Author Collection item
- Date/Time – publish date, used for sorting
- Switch – “Featured” toggle for filtering promoted posts
Webflow allows up to 30 fields per Collection (Webflow Help Center). Adding every possible field upfront is a mistake. Start with what your blog post card and post body actually need, and add fields later if required.
How Does the Slug Field Affect Blog Post URLs?
The slug auto-generates from the post Name, converting spaces to hyphens and stripping special characters. The Collection’s own URL slug (set when you create it) becomes the base path prefix.
If you name the Collection “Blog Posts” and leave the default Collection URL as “blog,” your post URLs follow this pattern: yourdomain.com/blog/post-title-here.
You can change the Collection URL at any time, but doing so after posts are indexed by Google breaks existing URLs. Set it correctly before you publish anything live. Renaming individual post slugs after publishing also requires a 301 redirect to preserve search engine authority, which is covered in a later section.
How to Design the Blog Post Template Page
When you create a CMS Collection, Webflow automatically generates a blank Collection Page. This is a single template that renders individually for every post in the Collection. Design it once, and it applies to all posts.
How to Bind CMS Fields to Text and Image Elements
Access the Collection Page from Pages panel > CMS Collection Pages > [Your Blog Collection] template. The canvas is blank by default.
Add elements the same way you would on any static page. A heading element for the title, a rich text element for the body, an image element for the thumbnail. The difference is what happens next: you bind each element to its corresponding CMS field.
To bind an element, select it on the canvas, then in the Settings panel click “Get text from” (for text elements) or “Get image from” (for images), and choose the matching Collection field. Static elements show blue outlines. Dynamic (bound) elements show purple outlines (Webflow Help Center).
Do this once and every post automatically populates its own data. A blog with 200 posts uses one template, not 200 separate pages.
For image elements, always bind the alt text field to a CMS text field as well. Leaving alt text static or empty hurts both web accessibility and search indexing.
How to Set the Page Title and Meta Description Dynamically
Open Collection Page Settings via the gear icon on the template page in the Pages panel. Here you can set the SEO Title and Meta Description fields to pull dynamically from CMS fields.
Recommended setup: bind the SEO Title to the post Name field (optionally appended with your site name). Bind the Meta Description to a dedicated “SEO Description” plain text field you added to the Collection.
Do the same for Open Graph fields so social media share previews use the correct post title and thumbnail image. Without this step, every blog post shares the same meta title, which is one of the most common Webflow blog SEO mistakes.
How to Build the Blog Index Page
The blog index page lists all published posts in a grid or feed layout. It uses a Collection List element that pulls data from your blog Collection and repeats a card design for each item.
How to Add and Configure a Collection List in Webflow
Webflow University describes this clearly: you create a Collection Page (the individual post template) and separately add a Collection List to any page, which pulls multiple items and displays them in a repeated layout.
To build the index page:
- Open or create your Blog index page in the Pages panel
- Drag a Collection List element from the Add Elements panel onto the page
- Connect it to your Blog Posts Collection when prompted
- Design the list item card: thumbnail, title, excerpt, date, author name
- Bind each card element to its matching CMS field
The Collection List has a 100-item display cap per instance. For blogs under that number this is a non-issue. Once you pass 100 posts, you need pagination or a third-party solution like Finsweet CMS Load to show all items (RapidDev, 2026).
How to Filter and Sort Blog Posts on the Index Page
Sort order matters. Most blogs display newest first, so set the sort to Publish Date descending.
Filtering options available natively in Webflow:
- Exclude items where a Switch field (e.g., “Draft”) is set to true
- Show only items where the Featured switch is on (for a “featured posts” row)
- Filter by a Reference field to show only posts from a specific category
Webflow does not have a built-in search filter for blog index pages. That requires either Webflow’s site search feature (Business plan) or a third-party integration. Worth knowing before you design an index with a visible search bar.
The visual hierarchy of the card design directly affects how visitors scan the index. Thumbnail image, post title, and date should be the 3 dominant elements in that order. Excerpt text is secondary, not primary.
How to Add and Publish Blog Posts in Webflow
Blog posts can be added and published through 2 separate interfaces: the Webflow Designer and the Webflow Editor. They serve different users and have different permission levels.
How to Write and Format Blog Content in the Rich Text Field
The Rich Text field is where blog content lives. It supports headings (H1 through H6), paragraphs, bold, italic, links, images, videos, and embed blocks. You access it from the CMS panel inside the Designer or from the Editor interface.
Key formatting behaviors to know:
- Styles applied to Rich Text elements in the Designer carry through to all content typed in that field
- Custom code blocks are not natively supported inside Rich Text. Use an Embed element as a workaround
- Images added inside Rich Text are not bound to a CMS Image field. They upload directly to the item
For writers who are not designers, the Webflow Editor (accessed at yourdomain.com/edit) is the better tool. It shows content in a clean, simplified view with no access to structural design settings.
What Is the Difference Between Draft, Staged, and Published in Webflow CMS?
Webflow updated its CMS publishing workflow in 2024 to add a clearer separation between content states (Webflow Updates).
Draft – item exists in the CMS but is not visible on the live site. Safe for work-in-progress posts.
Queued to publish – previously called “Stage to Publish.” The item is marked to go live with the next full site publish.
Published – live on the site. Edits to a published item now save in a “Draft changes” state without affecting the live version until you explicitly publish again.
Publish now – available from the canvas via the CMS Status indicator. Publishes an individual item immediately without triggering a full site publish. This lets content editors push a new blog post live without affecting any design work-in-progress in the Designer.
One practical note: 50% of marketers say their blogging ROI increased in 2024 vs 2023 (HubSpot, 2025). A clean publishing workflow where writers don’t need developer access is a direct contributor to publishing consistency, which drives that ROI.
How to Set Up Blog Post URLs and Redirects in Webflow
Blog post URLs in Webflow follow a fixed pattern determined by 2 things: the Collection URL slug and the individual post slug. Both are editable, and both matter for SEO.
How Does the Collection URL Affect the Blog Path?
The Collection URL is set when you create the CMS Collection. Webflow auto-generates it from the Collection name, so a Collection named “Blog Posts” gets a default slug of “blog-posts.”
Most people change this to something cleaner. Common options:
/blog/– standard, clear, widely used/articles/– works well for editorial or magazine-style sites/insights/or/resources/– used by B2B companies to signal content type
Per Webflow’s official documentation, the Collection slug is part of every Collection page path and cannot be removed, only changed. Changing it after posts are indexed breaks all existing URLs unless you set up redirects.
How to Edit Individual Post Slugs and When to Avoid It
Every post gets a slug auto-generated from its Name field. You can edit it manually before publishing. After a post is live and indexed, changing the slug without setting a redirect causes a 404 error for anyone who visits the old URL, including search engines.
To manage redirects: go to Project Settings > Hosting > Redirects. Add the old path as the source and the new path as the destination, set to 301 (permanent). This preserves link equity from any external sites or search results pointing to the old URL.
A useful note from Webflow’s 2026 documentation: if you have the Auto-Redirect toggle active in settings, Webflow automatically creates a 301 from the old URL to the new one when you rename a post slug (Zignuts, 2026). For large-scale Collection URL changes, use a Wildcard Redirect in Site Settings, for example redirecting /old-blog/(.*) to /new-blog/%1 to handle every post with one rule.
If you are moving from another platform to Webflow (say, from WordPress), mapping and redirecting your existing URLs before launch is the single most important technical step for preserving your search rankings. A proper 301 redirect setup in Webflow handles this systematically.
How to Add Categories and Tags to a Webflow Blog
Unlike WordPress, Webflow does not have built-in blog categories out of the box. You build taxonomy manually using a separate Categories Collection linked to your Blog Posts Collection via a Reference or Multi-Reference field (DEV Community, 2024).
This is more flexible than WordPress categories in practice. You control exactly what fields the category has, what the URL looks like, and how it displays on the front end.
How to Create a Categories Collection in Webflow
Step 1: In the CMS panel, create a new Collection named “Categories.”
Step 2: Add 2 fields: Name (required, auto-added) and a Plain Text field for a short description (optional but useful for category page SEO).
Step 3: In your Blog Posts Collection, add a Multi-Reference field pointing to the Categories Collection. Multi-Reference allows one post to belong to more than one category. A plain Reference field restricts each post to a single category.
Webflow’s official documentation describes Multi-Reference as the correct field type for tagging and categorization (Webflow Help Center). This is the same mechanism used for tags if you want a separate taxonomy.
How to Filter Blog Posts by Category on the Front End
Webflow auto-generates a Category Template Page when you create the Categories Collection. This is where category archive pages live.
On that template page, add a Collection List of Blog Posts. Apply a filter: “Blog Category contains Current Category.” Every category gets its own archive page at yourdomain.com/categories/category-name automatically.
One limitation worth knowing upfront: Webflow does not support real-time dynamic filtering on a single page without custom JavaScript. If you want a “filter by category” button bar on the blog index, you need a JavaScript library like Mixitup.js or Finsweet CMS Filter (Flowradar, 2025). The native Collection List filter only works at the template level, not as a live UI interaction.
How to Configure Blog SEO Settings in Webflow
Webflow handles several SEO tasks automatically: it generates clean URLs, adds canonical tags to Collection Pages, and builds an XML sitemap that updates on every publish. The things you need to configure manually are the dynamic meta fields and indexing controls.
68% of online experiences begin with a search engine (Marketing LTB, 2025). Getting these settings right before your first post goes live matters more than going back to fix them later.
How to Set Dynamic Meta Titles and Descriptions for Blog Posts
In the Collection Page template, open Page Settings. Set the SEO Title field to pull from your post Name CMS field, optionally with your site name appended using a separator.
Set the Meta Description to a dedicated “SEO Description” plain text field from the Collection. If that field is empty for a post, Webflow falls back to a static default, so build in a required field or a sensible fallback during collection setup.
| Setting | Where to Configure | CMS Field to Bind |
|---|---|---|
| SEO Title | Collection Page Settings | Name Field |
| Meta Description | Collection Page Settings | Plain Text “SEO Description” |
| OG Image | Collection Page Settings | Thumbnail Image Field |
| Canonical URL | Auto-Set by Webflow | Not Editable Per Item |
Bind the Open Graph title and description fields too. These control how posts look when shared on LinkedIn, X, or Slack previews. Leaving them unbound means every post shares your site’s global OG image and title.
How Does Webflow Handle the XML Sitemap for Blog Posts?
Webflow auto-generates the sitemap at yourdomain.com/sitemap.xml once you enable it in Project Settings > SEO > Auto-generate sitemap. CMS Collection Items are included automatically when they are published and not set to “noindex” (Tahi Studio, 2025).
After enabling, submit the sitemap URL to Google Search Console via Indexing > Sitemaps. Submit your custom domain URL only, never the .webflow.io staging URL (SEOcrawl.ai, 2026).
Pages marked noindex in the Collection Item settings do not appear in the sitemap. That is correct behavior. Use the noindex toggle for draft preview pages, thank-you pages, or any post you want to keep off Google while it is still being worked on.
Google also accepts RSS feeds as supplementary sitemap sources. For a blog that publishes frequently, submitting the RSS feed alongside the XML sitemap gives Google faster signals about new content (Google Search Central, 2024).
How to Connect a Custom Domain to a Webflow Blog
A custom domain requires a paid site plan and about 15 minutes of active work, plus 4 to 48 hours for DNS propagation (The CSS Agency, 2025). The actual configuration is straightforward once you know which records to add.
What DNS Records Does Webflow Require?
Webflow requires 3 DNS records in your registrar’s dashboard to connect a domain correctly (Webflow Help Center, April 2025 update):
- Two A records pointing to Webflow’s IP addresses (check Project Settings > Hosting for current values, as these changed in April 2025)
- One CNAME record on the www subdomain pointing to
proxy-ssl.webflow.com
The CNAME record is what triggers Webflow’s automated SSL certificate provisioning. Without it, the www version of your site will not load securely.
SSL certificates are auto-provisioned and renew automatically, as long as your DNS records continue pointing to Webflow (Webflow Help Center). No manual certificate management is needed on standard plans. Enterprise customers can upload custom SSL certificates if required by their compliance environment.
How to Add a Domain in Webflow Site Settings
DNS propagation alone does not activate the domain. You also need to add it inside Webflow.
Go to Project Settings > Hosting > Production > Add Domain. Enter your domain (with and without www), then publish the site.
One step many people skip: set a default domain in the Hosting tab. Webflow uses the default domain for canonical URL generation and the XML sitemap. If you skip this, your sitemap may reference staging URLs or trigger redirect loops between the www and root versions of your domain (The CSS Agency, 2025).
After connecting the domain, disable indexing on the .webflow.io staging subdomain. Go to Project Settings > SEO and make sure the staging domain is set to noindex. This prevents your blog content from appearing as duplicate content in Google’s index across two domains.
How to Add an RSS Feed to a Webflow Blog
RSS feed support in Webflow is built into CMS Collections and can be activated per Collection without custom code. Once enabled, the feed is available at yourdomain.com/feed.xml by default.
How to Enable and Configure the RSS Feed
Open the CMS panel, select your Blog Posts Collection, and click the Settings icon. Scroll to the RSS feed section and toggle it on. You then map CMS fields to the feed elements.
Required field mappings for a valid RSS feed:
- Title: bind to the post Name field
- Description: bind to your excerpt or SEO description field
- Publish date: bind to the Date/Time field
- Item URL: auto-resolved from the post slug
Author name and post image are optional mappings. Add them if your audience uses RSS readers like Feedly that display rich previews.
How to Submit the RSS Feed to Google Search Console
Google Search Console accepts RSS feeds as a supplementary sitemap submission. Go to Indexing > Sitemaps, enter your feed URL (e.g., yourdomain.com/feed.xml), and click Submit.
Google updates its index faster for sites with an active RSS feed alongside the XML sitemap. The XML sitemap covers all pages. The RSS feed specifically signals new and recently updated posts, which matters for blogs publishing several times per week.
Test the feed output before submitting. The W3C Feed Validator at validator.w3.org/feed checks for malformed XML and missing required fields. A broken feed that passes submission silently can go undetected for weeks.
What Are the Limitations of a Webflow Blog?
Webflow’s blog functionality covers most standard use cases well. But there are real constraints that affect certain teams, and knowing them before you build saves time later.
What Content and Scale Limits Apply?
The CMS plan caps at 2,000 Collection Items total across all Collections on the site, not just blog posts. So if your blog also has an Authors Collection with 20 items and a Categories Collection with 15, those count against the same limit (Webflow Help Center).
The Business plan raises the cap to 10,000 items, with an add-on available to extend further up to 20,000 (Webflow, July 2024 plan update).
The Collection List element displays a maximum of 100 items per instance. Blogs past that threshold need either Webflow’s native pagination or Finsweet CMS Load to show all posts without custom back-end code (RapidDev, 2026).
What Features Does Webflow Blog Not Include Natively?
These are genuine gaps, not minor omissions:
| Missing Feature | Workaround |
|---|---|
| Comment System | Disqus, Hyvor Talk, or Memberstack Commenting |
| Email Newsletter | Mailchimp, ConvertKit, or Audienceful via Zapier |
| Custom Code in Rich Text | Embed Element Inserted Within the Post Body |
| Live Category Filtering | Finsweet CMS Filter or Mixitup.js |
The newsletter gap is the one that catches teams off guard most often. Webflow has no native email broadcast tool. The Audienceful integration is the cleanest current option for publishing to both a Webflow blog and an email list from the same content workflow (Audienceful, 2025).
What Are the CMS API Limits?
The Webflow CMS API enforces 60 requests per minute and 1,000 requests per hour per API key on standard plans (Flowradar, 2024). This matters if you are importing content in bulk, syncing blog posts from an external tool, or using Zapier automations triggered by form submissions.
Cached requests to the Content Delivery API have no rate limit. The cap applies only to uncached write and read operations hitting Webflow’s origin servers (Webflow Developer Documentation). For blogs pulling CMS data to populate a headless front end, serve content via the CDN endpoint to stay within limits at scale.
Knowing these limits upfront also informs whether Webflow’s tradeoffs work for your specific content operation. For most blogs under a few hundred posts with a small editorial team, none of these constraints become active problems. For media companies or high-volume content teams, the limits are real planning constraints that affect the architecture decision.
FAQ on How To Create A Blog In Webflow
Does Webflow have a built-in blog feature?
Yes. Webflow’s native CMS Collections handle blog functionality without plugins. You build a Blog Posts Collection, design a dynamic template page, and add a Collection List to your index page. No third-party tools required for the core setup.
What Webflow plan do I need to start a blog?
The CMS plan at $23/month (billed annually) is the minimum. It supports up to 2,000 Collection Items and allows 3 content editors. The free Starter plan lets you build and preview but cannot publish to a custom domain.
How do I add a new blog post in Webflow?
Open the CMS panel in the Designer and click your Blog Posts Collection. Add a new item, fill in the required fields, set the status to Published, and hit Publish. Writers can also do this through the Webflow Editor without accessing the Designer.
Can I create blog categories in Webflow?
Yes, but not automatically. You create a separate Categories Collection, then add a Multi-Reference field in your Blog Posts Collection linking to it. Webflow generates a category archive page for each category item automatically.
How do I set up SEO for my Webflow blog posts?
In the Collection Page settings, bind the SEO Title and Meta Description fields to CMS fields. Do the same for Open Graph title and image. Enable Auto-generate sitemap in Project Settings and submit the sitemap URL to Google Search Console.
Can non-designers publish blog posts in Webflow?
Yes. Content editors use the Webflow Editor at yourdomain.com/edit. They can create, edit, and publish CMS items without touching the Designer. They cannot modify layout, styles, or Collection field structure.
How do I connect a custom domain to my Webflow blog?
Add your domain in Project Settings > Hosting, then update your DNS records at your registrar: two A records and one CNAME pointing to proxy-ssl.webflow.com. SSL provisions automatically. DNS propagation takes 4 to 48 hours.
Does Webflow support blog comments?
Not natively. Webflow has no built-in comment system. The most common integrations are Disqus and Hyvor Talk, both embedded via a custom code block on the Collection Page template. Memberstack also offers a native Webflow commenting add-on.
How do I display blog posts on my homepage in Webflow?
Add a Collection List element to your homepage and connect it to your Blog Posts Collection. Bind card elements to the title, thumbnail, excerpt, and date fields. Set the sort order to Publish Date descending to show the newest posts first.
What are the main limitations of a Webflow blog?
The CMS plan caps at 2,000 Collection Items total. There is no native newsletter tool, no comment system, and no real-time category filtering without custom JavaScript. The Collection List also displays a maximum of 100 items per instance without pagination.
Conclusion
This conclusion is for an article presenting how to create a blog in Webflow, from building your first CMS Collection to connecting a custom domain and configuring dynamic meta tags.
The blog post template page, Collection List pagination, RSS feed setup, and category filtering all follow the same underlying logic: one structure, applied dynamically across every post.
Webflow’s blog tools are genuinely strong for design-focused teams. The gaps, no native comment system, no built-in newsletter, are real but solvable with the right integrations.
Start with the Collection schema. Get the slug structure and SEO field bindings right before your first post goes live. Everything else can be adjusted as your content grows.
