By Mehdi HassanHow do you import WordPress blog posts into Webflow CMS?
You import WordPress blog posts into Webflow CMS with an export, transform and import flow: export from WordPress, reshape the data into CSV files that match your Webflow collections, then import authors and categories before posts. Images and inline media need their own step.
This is the practical, content-only part of a move. For the full picture, including page rebuilds and SEO, read our SEO-safe WordPress to Webflow migration guide, and if you're still choosing a platform, start with where to go when you migrate from WordPress.
How do you export a WordPress blog for Webflow?
Export a WordPress blog for Webflow using the built-in XML export, the REST API, or an export plugin that writes CSV. The built-in export includes posts, authors, categories and tags, but not SEO plugin fields or every custom field.
Export method | What you get | Good for |
|---|---|---|
Tools then Export (XML) | Posts, pages, authors, categories, tags, comments, media references | Most blogs, as a starting point |
REST API | Posts with rendered HTML, featured image URLs, taxonomy IDs, custom fields if exposed | Scripted, repeatable exports |
CSV export plugin | Chosen fields as columns, sometimes including SEO and ACF fields | Non-developers who want a spreadsheet |
SEO plugin export | Titles, meta descriptions, canonicals | Carrying metadata across |
Our guide to exporting a WordPress site's content compares these in more depth. Whatever you choose, also take a full database and file backup so nothing is lost if the export misses something.
Which Webflow collections do you need to move a WordPress blog to Webflow?
Set up three collections for a typical WordPress blog: Authors, Categories and Posts. Posts reference an author and one or more categories, and the post template pulls fields from all three.
WordPress field | Webflow collection | Webflow field type |
|---|---|---|
Post title | Posts | Name (plain text) |
Post slug | Posts | Slug |
Post content | Posts | Rich text |
Excerpt | Posts | Plain text |
Featured image | Posts | Image |
Publish date | Posts | Date |
Author | Authors, referenced from Posts | Reference |
Categories | Categories, referenced from Posts | Reference or multi-reference |
SEO title and description | Posts | Plain text, bound to template SEO settings |
Set the Posts collection's URL slug to match your WordPress blog path, for example blog, so post URLs stay the same where you can. Tags often add little value; many teams fold them into categories or drop them. For the bigger picture on blog structure, see our blog setup guide for startup websites.
How do you transform WordPress XML into Webflow CSV?
Transform WordPress XML into Webflow CSV by parsing the export into rows, one CSV per collection, with column names that match your Webflow fields. A short script is the most reliable way; spreadsheets work for small blogs.
Parse the export
Read the XML or API output and extract each post's title, slug, content, excerpt, date, author, categories and featured image URL.
Build the Authors and Categories CSVs
One row per author and per category, each with a name and a slug that match WordPress.
Clean the post content
Strip shortcodes, page-builder wrappers and inline styles. Convert anything Webflow's rich text can't hold, like custom blocks and galleries, into simple HTML or a note to fix by hand.
Rewrite internal links
Replace links to old WordPress URLs inside post content with the new Webflow URLs, so you don't rely on redirects for your own links.
Map references
Add author and category columns using the same names or slugs as the Authors and Categories collections.
Add SEO columns
Join the SEO plugin export on post slug to add title and description columns.
What to do about Gutenberg blocks and page-builder posts
Clean Gutenberg posts are mostly standard HTML (headings, paragraphs, lists, images, quotes), which Webflow's rich text accepts. Custom blocks like columns, buttons, tables and callouts don't keep their layout.
Posts built with Elementor, Divi or similar builders are harder: the content is buried in nested wrappers and shortcodes. For these, extract the text and images, rebuild the post in clean HTML, and check it by hand.
Sort affected posts by traffic. Clean the top performers carefully, simplify the rest, and consider retiring posts with no traffic and no backlinks rather than migrating them.
How do you handle featured images and inline media?
Handle featured images by putting their URLs in an image column so the CSV import pulls them into Webflow. Handle inline media separately, because our research found Webflow's CSV import turns images inside rich text into placeholders.
- Featured images: include the full image URL in an image column; the import fetches and hosts it in Webflow. Keep the old site live until the import finishes.
- Inline images: either import posts through Webflow's API, which can carry rich-text images, or re-upload images into each post after a CSV import. For large blogs, an API import saves a lot of manual work.
- Alt text: carry alt text across for every image; it's easy to lose in transformation.
- Video and embeds: re-add YouTube, Vimeo and social embeds in the rich-text editor or as embed fields.
- PDFs and downloads: re-upload important files and redirect their old wp-content URLs if they earn links.
Our guide to importing a CSV into Webflow CMS without breaking rich text and images covers the import screen and its pitfalls step by step. Webflow's own page on CSV import and export describes what the feature supports.
How do you check the import and fix the URLs?
Check the import by comparing a sample of posts with the live WordPress versions, then fix URLs with redirects for every post whose path changed. Do both before you switch the domain.
- Open ten varied posts in Webflow and in WordPress side by side: long, short, image-heavy, embed-heavy and your top traffic posts.
- Check authors and categories are linked correctly and category pages list the right posts.
- Confirm post slugs match WordPress and the collection path is right.
- Add 301 redirects in Webflow for root-level, date-based or category-prefixed post URLs, plus any old tag and author archives.
- Bind SEO title and description fields to the post template and spot-check the page source.
- After launch, run the old URL list through a redirect checker and watch Search Console for 404s.
If you ever need to go the other way, our guide to exporting Webflow CMS content covers that, and if you're comparing builders, importing into Framer CMS shows how the same flow looks there.
Should you do the import yourself or get help?
Do the import yourself if the blog is clean, you're comfortable with a spreadsheet or a short script, and you'll test carefully. Get help when posts are built with page builders, there are custom post types or several languages, or the blog drives a large share of your leads.
A careful import is one part of a migration; the template design, redirects and launch QA are the rest. Our WordPress to Webflow migration cost guide shows how those parts affect price. Our website package is $8,000 for up to six pages plus $500 per extra page, built in Next.js. Migration work like the blog import is scoped on the intro call; see pricing.
