Webflow gives you a strong CMS and clean hosting, but it has no built-in comment system for blog posts or CMS pages. You can add one without a plugin or a backend of your own. Webflow supports custom code through an Embed element, and that is all Gabden needs.
What you will add
Two lines of HTML: a container div and a script tag. The script loads asynchronously, and it keys the discussion to each page's canonical URL, so every blog post or CMS item gets its own thread automatically. Here is the embed:
<div id='gabden-conversations'></div>
<script async src='https://YOUR-SITE.gabden.com/conversations.js'
data-page='canonical'
data-theme='auto'></script>Replace YOUR-SITE with the key from your dashboard. You get it after you register a site, and it is the same key across every page on that site.
Add it to a CMS Collection page
For blog posts, you almost always want comments on the Collection page template so every post gets them without manual work.
- Open the Collection page in the Designer (for example, your Blog Post template).
- Drag an Embed element into the layout where you want comments, usually below the post body.
- Paste the two lines above into the Embed code editor, with your real Gabden subdomain.
- Save and close the editor, then publish the site.
Because the thread is keyed to the canonical URL, each published post shows its own discussion. You add the Embed once on the template and every item in the Collection inherits it.
Add it to a single static page
For a one-off page rather than a Collection, the steps are the same: drag an Embed element onto that page, paste the snippet, publish. The container div is where comments render, so place the Embed element where you want them to appear.
Check the canonical URL
Because threads are tied to the canonical URL, it is worth a quick check that Webflow is serving the URL you expect. In your project's SEO settings and page settings, make sure canonical tags point at the live address, not a staging subdomain. If you later move from a webflow.io address to a custom domain, keep the canonical consistent so existing threads stay attached to their pages.
One rule keeps comment migrations painless: the URL is the identity of the thread. Keep the canonical stable and the discussion follows the page.
Turn comments off on specific pages
You may not want comments everywhere. A landing page or a legal page probably should not have a discussion box. Rather than removing the Embed from individual pages, you can use per-page rules to turn comments off for chosen URLs from the dashboard, which is easier to manage as your site grows.
Moderation and theming
Once comments are live, set a moderation mode that fits your audience: pre-moderate everything, auto-approve, auto-approve returning verified people, or moderate only anonymous users. There is a blocked-word filter and a pending queue for anything that needs a look. The widget has light and dark themes with presets, so you can match your Webflow design rather than fighting it.
Why this approach fits Webflow
Webflow sites are usually built for speed and clean markup, and a heavy comment script undermines that. Gabden's embed is about 10KB and loads asynchronously, so it does not block your page render. It sets no tracking cookies and does no fingerprinting, which keeps a design-led marketing site from quietly turning into a tracking surface.
On the free plan you get up to 100,000 widget views per month per website with a small "Powered by Gabden" mark. Plus is 5 dollars per month per website for unlimited views with the mark removed. See pricing for the details. To get started, grab your site's Gabden subdomain from the dashboard and drop the Embed element onto your Blog Post template.
Join the discussion