Keep Your Webflow Blog URLs in WordPress

If your WordPress site will use the same domain as your Webflow site, you can keep every blog post's address. Give WordPress a custom permalink with the same folder as your Webflow Collection URL, such as /blog/%postname%, import the posts with their original slugs, and your old links keep working without a redirect.

If the addresses do change, add a permanent (301) redirect from each old address to its new one. We checked the Webflow, WordPress and Google details below on 13 November 2026, on their own websites or on live Webflow blogs. This guide covers URLs and redirects. For the whole move, from hosting to DNS, see how to migrate Webflow to WordPress.

How Webflow builds blog addresses

Every Webflow blog post is an item in a CMS Collection, and its address has two parts:

• The Collection URL. Webflow calls it the slug for the folder that holds the Collection's pages. Webflow generates it from the Collection's name, and you can change it. A Collection called Blog posts gets /blog-posts unless you rename it, and many sites change it to /blog or /post.
• The item slug. Each post's own Slug field, as in /blog-posts/hello-world.

The Collection template page can also sit inside a folder, which adds that folder to every address, as in yoursite.com/content/blog/example-post. Your category pages, if you have them, come from a separate Collection with its own Collection URL.

Webflow addresses don't end in a slash. On the Webflow blogs we checked, a post address with a final slash redirected (301) to the same address without one.

Save your current addresses first

Webflow can auto-generate a sitemap at /sitemap.xml. Open it in your browser and save a copy. If it returns "not found", turn on Auto-generate sitemap under Site settings → SEO and publish your site. The sitemap lists every address you want to keep, and it disappears once your domain points to WordPress.

Look at a few post addresses, including your oldest. Note the folder in front of the slug. That's what you'll copy into WordPress.

Same domain: match Webflow's structure in WordPress

This works when your domain, such as www.yourdomain.com, moves from Webflow to your WordPress host. Google treats this as a move without URL changes: the addresses stay the same, so there's nothing to redirect.

1. In WordPress, go to Settings → Permalinks.
2. Choose Custom structure and enter your Collection's path followed by %postname%, for example /blog-posts/%postname%/. If the template sits in a folder, include it: /content/blog/%postname%/. %postname% is the post's slug.
3. Click Save Changes.

Then import the posts with their original slugs. Blog Porter keeps each Webflow item slug, so a post at /blog-posts/hello-world becomes /blog-posts/hello-world/ in WordPress. The order doesn't matter, because WordPress builds each address from the current permalink setting.

The final slash is the only difference. WordPress answers the address without it with a 301 to the address with it, so old links still land on the post. If you'd rather the addresses match Webflow's exactly, leave the final slash off: /blog-posts/%postname%.

Finish the details

• The blog page. If your post list lives at /blog, create a WordPress page with the slug blog and choose it as the Posts page under Settings → Reading.
• Categories. Blog Porter imports a post's category when the post page links to the category page. Create any it misses in WordPress, and check that each one has the same slug as its Webflow category item. If your category pages lived at /blog-categories/news, set Category base under Settings → Permalinks to blog-categories. WordPress's default base is category.
• Your other pages. Give your About, Contact and other WordPress pages the same slugs they had on Webflow.
• Images. Your images get new addresses in your WordPress Media Library. Their old addresses are on Webflow's own image domain, which you don't control, so they can't be redirected. Make sure every post uses the WordPress copy before you close the Webflow site.
• Redirects you already made in Webflow. These stop working when your domain leaves Webflow. Export them as a CSV file from Site settings → Publishing → 301 redirects, then add them to WordPress. Webflow writes wildcards as (.*) with %1 in the new path, and puts a % in front of some special characters, so rewrite those rules for your WordPress redirect plugin.

New addresses or a new domain: use 301 redirects

If your posts will live somewhere else, such as /hello-world/ or a new domain, every old address needs a permanent redirect to its new one. Google's guide to site moves with URL changes says to:

• map every old address to its new equivalent
• use server-side permanent redirects (301 or 308) where you can
• redirect straight to the final address, without chains
• avoid sending lots of old addresses to an unrelated page, such as your home page
• keep the redirects for as long as you can, and generally for at least a year

Build the list of old and new addresses

Blog Porter doesn't create redirects or export a list of them, so you build it:

1. Take the old addresses from the Webflow sitemap you saved.
2. Take the new ones from WordPress's built-in sitemap at /wp-sitemap.xml, or from Posts → All Posts.
3. Put them side by side in a spreadsheet and match the rows by slug.

Option 1: redirect from WordPress

Use this when WordPress takes over your old domain with a new structure. Install a redirect plugin such as Redirection, which makes 301 redirects, imports CSV files and logs 404 errors. If only the folder changes, one rule can cover every post: tick Regex and redirect ^/blog-posts/(.*) to /$1/. Test it on a few posts.

Option 2: redirect from Webflow while it's still live

Use this when WordPress goes on a new domain and Webflow keeps the old one. Webflow's 301 redirects live in Site settings → Publishing → 301 redirects. A few rules apply:

• You need a paid plan. Redirects need a paid Site plan, or a site in a paid Workspace.
• The post must be gone first. Webflow says that to redirect a Collection item page, you need to archive, delete or unpublish the item, save it as a draft, or change its slug.
• Use one rule per folder. Old path /blog-posts/(.*) with a new path ending in /%1 covers every post. Webflow suggests no more than 1,000 redirects in total.
• Languages need their own rules. Webflow says redirects don't apply to localized subdirectories, so /es/ addresses need separate rules.
• Test the destination. Webflow's help pages show redirects to paths on the same site. We couldn't confirm there that a full address on another domain is supported, so test one rule before you rely on it.

These redirects last only as long as the Webflow site stays published on your domain. Webflow says canceling a paid Site plan removes your custom domains and unpublishes the site at the end of the billing period. Since Google suggests keeping redirects for at least a year, it's often simpler to move the old domain to your WordPress host as well and redirect from there.

After launch

1. Open a sample of old addresses: a few posts, including your oldest, plus a category page and the blog page. Each should show the right content. Where one redirects, a redirect checker should show a 301, not a 302.
2. In WordPress, go to Settings → Reading and make sure Discourage search engines from indexing this site is unticked. While it's ticked, WordPress turns off its sitemap.
3. In Google Search Console, submit your new sitemap. If your addresses changed, Google's site move guide suggests submitting the old sitemap you saved as well. If your domain changed, also use the Change of Address tool.
4. Watch Search Console for crawl errors over the next few weeks.
5. Keep your Webflow site until you've checked posts, images and redirects. How to migrate Webflow to WordPress covers the order.

Move the posts with Blog Porter

Blog Porter imports your Webflow posts into WordPress with their original slugs, so with the permalink settings above they keep their addresses. It imports each post's main rich text field and copies available images into your Media Library, in resumable batches.

It costs $0.20 per post, with a minimum of 5 posts, paid once. Enter the public page that lists your posts. Blog Porter reads the post links in that page's Collection list, so a list at /blog finds posts at /blog/hello-world or at /blog-posts/hello-world. The free analysis lists every post it found and the exact price before you pay. How to export your Webflow blog covers what it imports and what it doesn't.

Install the Blog Porter plugin to run the free analysis, or read more about moving from Webflow to WordPress.