When people move a Wix blog, they redirect the posts: /post/my-title to wherever the post lives now. That covers the URLs you think of. Google has indexed more than that, and every one you don't map turns into a 404 the day the domain moves.
Here is what a real Wix site exposes, using one we checked this week: a design studio's blog with 356 posts, a shop and some dynamic pages. The patterns are the same on any Wix site.
1. Start from the sitemap, not the feed
/sitemap.xml on a Wix site is an index that points to one sitemap per content type. On this site there were nine:
blog-posts-sitemap.xml 356 posts at /post/<slug>
blog-categories-sitemap.xml /blog/categories/<slug>
pages-sitemap.xml /blog, /portfolio, /about…
store-products-sitemap.xml /product-page/<slug>
store-categories-sitemap.xml
pricing-plans-sitemap.xml /pricing-plans/list
member-profiles_…-sitemap.xml
dynamic-…-sitemap.xml (two CMS collections)
The RSS feed (/blog-feed.xml) on the same site lists 20 posts. It's a feed of recent items, not an inventory, so a redirect list built from it misses 336 posts here. Large blogs also split the posts sitemap into pages, so follow the nested index too.
2. Category archives
Every blog category has its own URL, /blog/categories/<slug>, and Wix lists them in the sitemap, so they get indexed and collect links. The slug is Wix's, not necessarily the category name: a category called "Women in Business" can live at /blog/categories/womeninbusiness.
Point each one at the matching archive on the new platform: /category/women-in-business/ on WordPress, /tag/women-in-business/ on Ghost, or the blog index where the platform has no category pages.
3. Paginated blog pages
/blog/page/2, /blog/page/3 and so on answer with a 200 and a canonical tag pointing at themselves, so Google can keep them. Their numbering won't match the new blog, so send them all to the blog index with one pattern rule:
# Netlify / Cloudflare Pages (_redirects)
/blog/page/* /blog/ 301
# Apache (.htaccess)
RedirectMatch 301 ^/blog/page/[0-9]+/?$ /blog/
# Nginx
location ~ ^/blog/page/[0-9]+/?$ { return 301 /blog/; }
4. The old /single-post/ links
Older Wix blogs served posts at /single-post/… before the switch to /post/. Links from that era are still out there in old articles, forum threads and newsletters. On the site we checked, /single-post/<slug> already returns a 404 on Wix itself, so those visitors are being lost today. A move is a chance to win them back: map /single-post/<slug> to the new post as well.
5. Exact paths: slashes and capitals
Wix answers /post/my-title/ with a 301 to the version without the trailing slash, and /Post/my-title with a 404: paths are case-sensitive. WordPress and Ghost add trailing slashes. Keep the old side of each redirect exactly as Wix wrote it, and the new side exactly as the new platform does, or the redirect chains through an extra hop or misses.
6. Things that aren't posts
-
Products live at
/product-page/<slug>. If the shop moves to Shopify or WooCommerce, map them to the new product URLs; if it closes, to the most relevant page. - Pricing plans, member profiles and dynamic CMS pages each have their own sitemap. Decide per collection: rebuild, redirect to a parent page, or let them go.
-
Images are served from
static.wixstatic.com, a Wix domain you can't redirect. Image search traffic only survives if the images are re-hosted on the new site with their alt text, before the Wix plan ends. -
Free addresses (
name.wixsite.com/site) can't carry redirects at all. Only a custom domain can, which is one more reason to connect the domain to the new host rather than start fresh.
Check it after the switch
Once the domain points at the new host, run the old URLs through a checker and look for anything that isn't a single 301 to a 200. A free redirect checker does that for a pasted list, and the Wix redirect map tool builds the list from a live Wix sitemap.
Disclosure: I build Decamp, which exports Wix sites and writes these redirect files (category archives and the old /single-post/ links included).
Top comments (0)