There are many ways you can spice up your blog pages to make them easier for users to read, share, and take action. Alongside social sharing buttons, adding in call to actions inside your blog post is starting to become a common spice. In-fact, even Webflow themselves have caught up and implemented it into their blog.
So how exactly is this done? There isn't a 'call to action' option in the rich text block, so we know that it has to be done through a workaround.
Well, there are actually two workarounds that you can use, and they are both a piece of cake, so let’s dig in.
Option 1: Split Your Blog Post in Half
The first option is actually pretty simple - just add in another rich text field.
By adding in a second rich text, you can simply copy half of your blog post into the second field, giving you space to add whatever custom elements you want in between.
This is where it might be a good spot to add your call to action block.
The best part about this is that if the 2nd blog rich text isn't filled in, it'll simply hide itself, meaning you can make this work for only the blog posts you want and not every single one.
Option 2: Add in Custom Embed Blocks
If instead you want more flexibility and the option to add many different CTAs down your blog post, you can instead add the call to actions through code embed blocks.
Firstly you want to design the call to action block, and put it in a hidden page such as your design system page.
Once you've done this, publish and open the page where you designed the block, and inspect the element inside your browser. It's usually easiest to do this by right clicking on the div and selecting "inspect element".
Once you've found the div in your code, right click again and select "HTML" under "copy".
Go back into any blog post, find the space where you want to add in the div, and add a custom code block.
Inject the code we just just copied into this space, hit save, and resave the blog post.
You won't be able to see the block inside of Webflow, so you might want to publish to your staging domain first to make sure it looks how you want it to.
And there it is, a shiny new call to action block that is smack bang in the middle of your post.
Both approaches work, and the right one depends on how many CTAs you need and how often they change.
Split the post in two (Option 1) is best when you want one CTA in the same place on every post. It is quick to set up, it works with the CMS, and the second rich text field hides itself when empty. The limitation is that you only get one break point per post, and it relies on editors dividing the article correctly.
Embed blocks (Option 2) is best when you want different CTAs at different points, or a different CTA on different posts. The trade-off is maintenance. The pasted code is a copy of the design, so if you change the CTA's styling later, you have to update the code in every post that uses it. Embeds also do not show in the editor preview, so you need to check the published page.
If you only need one CTA and you publish regularly, start with Option 1. If you need flexibility and have a small number of posts, use Option 2.
Where to Put a CTA in a Blog Post
A call to action works best when it appears after the reader has got something of value, and when it matches what they came to read about. A few placements that tend to work:
After the first major section: by now the reader has seen that the article is useful, and the CTA gives an early option to act for those who are ready.
Near the end: readers who finish the article are the most engaged, and are the most likely to take the next step.
Beside a relevant paragraph: if the article mentions a service or product, a CTA next to that mention feels like a natural next step instead of an interruption.
More is not better. One or two CTAs in a post is plenty. A post crowded with banners teaches readers to ignore them.
Writing a CTA That Gets Clicked
Make it relevant to the post. A generic "Contact us" banner under every article performs worse than one that picks up from the topic, such as "Need help migrating your site? Let's talk."
Offer one clear action. A single button with a specific label, not three competing links.
Say what happens next. "Get a free site audit" is clearer than "Submit."
Match the reader's stage. People reading beginner content are usually not ready to buy. A newsletter, checklist or guide may suit them better than a sales call. My post on increasing sign-ups on your marketing website goes into how to address objections.
Make it visually distinct, but consistent with the rest of the site. Treat the CTA block as a reusable component in your design system.
Make sure button text has enough contrast against its background, and that the link has a visible focus state for keyboard users.
Use real links or buttons for the action, not an image of a button.
If you use an embed, keep the code small, and avoid loading extra scripts for what is a simple block.
Check how the CTA looks on mobile, where a wide banner may need to stack.
Frequently Asked Questions
Can you add a call to action in the middle of a Webflow blog post?
Yes. You can either split the post into two rich text fields and place the CTA between them, or paste a CTA's HTML into a custom code embed block inside the rich text.
Why doesn't my CTA embed show in the Webflow Designer?
Custom code embeds inside CMS rich text do not render in the Designer or Editor preview. Publish to your staging domain to see how it looks.
How many CTAs should a blog post have?
One or two is usually enough. Place one after the first main section and one near the end, and make each relevant to the topic of the post.
How do I update a CTA that is pasted into many posts?
With embed blocks, each post contains its own copy of the code, so you need to update each one. If you need to change the CTA often, the split rich text approach or a reusable component is easier to maintain.
How can I tell if my blog CTAs are working?
Track clicks on the CTA button as events in Google Analytics, then compare click-through rates by post and by placement.
Written by
Nikolai Bain
I'm a Webflow Premium Partner based in Wellington, New Zealand, with years of experience designing and developing websites for clients across the UK, EU, US, AU, and NZ. I specialize in Webflow migrations and SEO, helping businesses move from WordPress, Squarespace, and custom-coded sites to Webflow without losing search rankings. I share what I learn through in-depth guides and templates to help others get more out of Webflow.
