Wix Blog Export: Every Route That Actually Works (2026)

There is no Wix blog export. Wix's own help centre says so in a page it files under feature requests: as of September 2026, Wix Blog Request: Exporting Blog Posts to Other Platforms states that it is currently not possible to export blog posts to other platforms, and invites you to vote for the feature. There is no ship date on the page and no commitment that it will ever ship.

That is the honest answer to the query, and it is not the end of the story. Your posts are reachable through four routes, in descending order of completeness: a direct API pull by the platform you are moving to, the RSS feed, a CSV export if your blog was built on CMS collections rather than the Wix Blog app, and copy and paste. Each one loses something different. This page covers what each route gets you, what breaks on the way out, and where the archive can land.

Why a Wix blog export button does not exist

A Wix blog export means getting your posts, images and SEO fields out of Wix Blog in bulk and into a platform you control, and Wix ships no feature that does it.

Wix Blog is an app inside the Wix platform, not a content store you own a copy of. The rest of Wix has an export path: any CMS collection you created yourself can be downloaded as CSV. Wix Blog posts sit outside that system. On Wix's page about working with app collections, the examples Wix gives are Stores and Bookings, and Blog is not among them (verified September 2026). The page names those as illustrations rather than a closed list, but the absence is consistent with what the CMS actually shows, and it is why the CSV route that works for a products table does not work for a 300-post archive.

WordPress states the same thing from the other side. WordPress.com's Wix importer brings across static pages, images, the site title and menus, and its documentation says plainly that blog posts cannot come with them, pointing users at an RSS plugin instead (verified September 11, 2026). When the destination platform's own importer gives up on your posts, the gap is real.

The four Wix blog export routes, ranked by what survives

Route 1: let the destination pull from the Wix API

Wix has no export button, but it does have an API, and a token you generate can read your blog posts. A platform with a Wix importer uses that token to fetch posts directly, which is the only route that reads your content from Wix itself rather than from a public page. It is also the only route that scales past a handful of posts. What it does not do is move your SEO fields: Wix's API hands over post data, not the contents of the SEO panel, so meta titles, meta descriptions and alt text stay behind no matter which importer you use. Superblog's Wix import works this way, on an API token plus the site ID, and it moves up to 500 posts per run. Re-run it for a larger archive. If the platform you are evaluating offers a Wix import, ask whether it authenticates against the Wix API or just parses the RSS feed. The difference is hundreds of posts versus your last 20.

Route 2: the RSS feed at /blog-feed.xml

Every Wix blog publishes a feed at yoursite.com/blog-feed.xml. It is the route most tutorials point at, and it has two hard limits. Wix's RSS button documentation states that the feed can only display up to 20 of the most recent blog posts, and that a feed for an individual blog category is not possible (verified September 11, 2026). If you have 40 posts, the feed shows you 20 of them and there is no paging parameter that reveals the rest.

The second limit arrived quietly. Wix blog owners reported in March 2025 that the feed stopped returning full post bodies and began returning links only, with no announcement and no setting to reverse it. So the feed route now gives you 20 titles and 20 URLs. Anything that imports from it either scrapes the live page for the body or brings across an excerpt.

Use this route only if your blog is small, recent and you are prepared to re-paste the bodies.

Route 3: CSV export, for blogs built on CMS collections

If your writers publish through a collection you created in CMS rather than through the Wix Blog app, you have a real export. Open CMS, select the collection, use the More Actions menu and choose Export to CSV. Wix's export documentation notes two details worth knowing before you open the file: time fields come out as UTC+0, and collections containing non-Latin characters are exported as UTF-8 (verified September 11, 2026).

Two caveats. The CSV carries image URLs, not image files, so every picture in the export still points back at Wix. And the CSV only contains the fields the collection was built with. If nobody added a meta description field, no meta descriptions come out, because there was never anywhere to put them.

Route 4: manual copy and paste

For an archive under about 30 posts, moving each post by hand is often faster than debugging a scraper, and it is the only route that loses nothing, because you are the migration script. Budget five to ten minutes per post and do the SEO fields at the same time, not later. Open-source scrapers and paid migration services cover the middle ground, but they read your public blog pages rather than a real export, so check what a given tool does with images and meta fields first.

What breaks on the way out of Wix

Images. Every picture in your posts is served from static.wixstatic.com. Those URLs keep working only while you keep paying Wix, and a hardcoded Wix image URL sitting inside a migrated post body will break the day the site comes down, as Rovela's migration write-up points out. Any route that does not download and re-host the image files leaves you with a time bomb in every post.

SEO metadata. Title tags, meta descriptions and alt text are entered in Wix's SEO panel, one post at a time. No route collects them in bulk, including the API route, because those fields sit outside the post data Wix's API returns. So plan for a rebuild: export a list of your URLs, write the meta title and description for each one, and fill them in on the new platform after the import lands. Doing it at import time is cheaper than discovering six months later that 200 posts carry auto-generated titles.

Your post URLs. Wix blog posts live at yoursite.com/post/post-title. Wix's documentation on blog post URLs says the post prefix cannot be removed entirely, though it can be renamed, and the blog and post prefixes cannot share the same value (verified September 11, 2026). That prefix matters on the way out: every ranking URL you own has /post/ in it, so your redirect map is /post/{slug} on the old site pointing at /blog/{slug} on the new one. Write that map before you cancel anything. The slug on the end is the piece you want to carry across unchanged.

Where to take the archive

1. Superblog, which pulls from Wix through the API

Superblog imports Wix directly. You give it a Wix API token and your site ID, it queries Wix for your posts, then reads each post page for the body, because Wix does not return post HTML through the API. One run brings across up to 500 posts. Re-run it for a larger archive and it skips every slug already in your site, so nothing duplicates. Slugs, tags and original publish dates come across from Wix's own fields, so the {slug} half of every URL stays identical and your redirect map is a single pattern rather than a spreadsheet of exceptions. Most imports finish in five to ten minutes, or up to thirty if the blog carries a lot of images.

Three things to know before you run it. Image re-hosting onto Superblog's CDN runs only once a paid plan is active, so a trial import leaves your pictures pointing at Wix. Authors do not migrate: every imported post is attributed to the account that ran the import, so multi-writer archives need bylines reassigned afterwards. And the import carries titles, bodies, slugs, publish dates, tag names and the cover image, nothing more, so meta titles, meta descriptions, alt text and any category structure are rebuilt on this side. The editor's SERP preview turns that into a per-post pass rather than a research project.

What you get on the other side:

• Nothing to patch. There is no server to keep alive, no plugin list, no update queue. Every page ships as a pre-built static file from a CDN, which leaves no database at runtime and no code for an attacker to reach.
• The URL you want. Point a subdomain at it, give it its own domain, or run it at yoursite.com/blog through a reverse proxy while Wix keeps serving the rest of the site. SSL costs nothing on any plan. The blog for Wix use case walks through the proxy setup.
• The metadata written for you from here on. Every post you publish gets structured data emitted automatically: Article, WebPage, Organization, ImageObject and FAQ in JSON-LD. Sitemaps, canonical tags, Open Graph tags, an IndexNow ping on publish and an llms.txt file come with it, on all plans. Translations with hreflang start on Super.
• Somewhere a team can work. The editor autosaves, a post can carry more than one byline, and permissions come in three levels: Admin, Editor, Writer. Pro is where scheduling and collaborative review switch on, with 5 seats. Super raises that to 10, Business to 25.
• Traffic numbers without a consent popup. Pirsch runs from Pro upward and sets no cookies, so there is nothing for a visitor to consent to. Google Analytics works whichever plan you pick.
• Fast with no tuning pass. Pictures convert to WebP and come off the CDN, and every page is built to clear 90 on Lighthouse.
• Room to grow into. On Business, the dashboard does keyword research for you, returning live volume, competition and CPC on as many as 25 terms at a time, and it generates featured and Open Graph images from the post at one credit apiece.

On capacity: Pro holds up to 1,000 posts and Super is unlimited under fair use, and that ceiling is not theoretical, because 23 blogs on Superblog currently hold 1,000 posts or more, drawn from a library of over 150,000 published posts across the platform. Pricing sits on the pricing page and starts at $49 a month for Pro. Nothing is charged for the first seven days and no card is asked for. There is a 30-day money-back guarantee.

2. WordPress

The right destination if you want a plugin for everything and someone willing to own updates. Be clear-eyed about the import: WordPress.com's Wix importer skips blog posts entirely and falls back to the RSS plugin, which means the 20-post ceiling. Self-hosted, you are looking at a scraper or a CSV you assemble yourself, then a hosting bill, a security plugin and a maintenance routine on top.

3. Ghost

A fit if the blog is the whole product and a small team writes most of it. Ghost's importer takes a JSON file or a ZIP holding JSON plus your images, and there is no CSV path (Ghost's importer documentation, verified September 2026), so you still have to build that file from one of the four routes above. The other thing to model is the bill, which is set by list size rather than by how much you publish. As of September 2026, Ghost(Pro) charges $18 a month for Starter and $29 for Publisher billed yearly, both capped at 1,000 members, and the next step up is Business at $199 a month for 10,000. That is the pricing ladder you climb even if you never sell a subscription.

Questions people ask about exporting a Wix blog

Can I export Wix blog posts to WordPress?

Not through a Wix export file, because Wix does not produce one. WordPress.com's Wix importer moves pages, images, the site title and menus, and its own documentation says blog posts do not come with them. The practical routes are the RSS plugin for your 20 most recent posts, a third-party scraper, or manual re-entry.

Where is my Wix blog RSS feed?

At yoursite.com/blog-feed.xml. It returns up to 20 of the most recent posts, there is no per-category feed, and since March 2025 it has returned links rather than full post bodies.

Will my Wix blog images work after I move?

Only while the Wix site stays live. Images sit on static.wixstatic.com, so any post body that still points there breaks when you cancel. Move to a platform that downloads and re-hosts the files, or re-upload them yourself.

Can I keep my URLs when I leave Wix?

The slug, yes, on an import path that reads Wix's slug field directly. The /post/ prefix, no, because it is a Wix structure. Map /post/{slug} to your new /blog/{slug} with 301 redirects and keep the Wix domain pointed long enough for Google to process them.

Is it worth staying on Wix and working around this?

If the blog is a handful of posts a year next to a site you like, yes. If organic search is how you acquire customers, read our breakdown of Wix Blog and the Wix blog SEO guide before you invest another year of content into an archive you cannot take with you.

Before you write another post on Wix

Every post you publish on Wix is one more post you will move by hand later. If a move is already on the table, run the import first and write the next post on the other side. Superblog's Wix import pulls up to 500 posts per run through the API and keeps your slugs, and you re-run it if the archive is bigger. Start with the Wix alternative comparison for the feature-by-feature view, or start a trial and point the importer at your site.