
Case Study: A Multilingual Health-Tech Brand Moved to Shopify and Kept Writing in WordPress
Key takeaways: a two-month WordPress to Shopify move that kept the writers in WordPress
- The brand moved its storefront and its whole blog to Shopify in two months, in five languages and three blogs.
- Wash created 1,200 redirects from old WordPress addresses to the new Shopify pages, so existing links and search results kept working.
- The writers still work in WordPress. The WordPress site is now private, and readers only see the Shopify store.
- Six months on, the team has published about 2,000 new articles and edits through Wash.
- Organic clicks from searches that don't name the brand are several times the clicks from searches for the brand itself.
The brand is a health-tech company that sells a health device online in Europe, the UK, Australia and Canada, in English, German, French, Italian and Spanish. We've left its name out of this article.
Why did the brand move from WordPress to Shopify?
The brand moved from WordPress to Shopify because its checkout was failing and taking payments for its app subscriptions had become a problem. Shopify is now the storefront, the checkout and the subscription billing in every market, with Shopify Markets handling each region.
The decision came late, so the whole migration had two months. It also had to land alongside a new site, a new product and a launch in new countries, and all three launched successfully.
Why did the blog have to move too?
The blog had to move too because it brings in most of the brand's search traffic. Searches that don't include the brand name bring several times more organic clicks than searches for the brand itself, and the articles are what those searches find. That traffic depends on the old WordPress addresses still reaching the articles after the move.
What did the blog migration involve?
The blog migration moved every article in five languages into three Shopify blogs, with each WordPress category or language mapped to its Shopify blog. For each WordPress post, Wash created the Shopify article:
- with its translations, linked so each market shows the article in its own language;
- with its images uploaded to Shopify Files and served from the Shopify CDN;
- with its author, SEO title and meta description;
- with its custom fields, including each article's authors and reviewers, which the brand's new Shopify article template shows on the page.
Wash rewrote links between articles to the Shopify addresses and created 1,200 redirects from the old WordPress URLs, so bookmarks, backlinks and search results open the new pages. Today the Shopify blogs hold about 200 articles.
Why does the team still write in WordPress?
The team still writes in WordPress because its writers work in many locations and many languages, and WordPress already handled that. WordPress is still where every article is written, translated and published, so the move to Shopify didn't change how the writers work.
The WordPress site is now private. It only answers from approved regions, and it sits behind a login over HTTPS, so search engines and customers never see it. Readers find every article on the Shopify store.
How does publishing work day to day?
Publishing day to day starts in WordPress, and Wash is the link between that private site and the public store. A writer publishes or updates a post, and Wash creates or updates the matching Shopify article. A new translation in WordPress becomes the Shopify translation for that market. In six months that has added up to about 2,000 new articles and edits. The Wash log in Shopify is the record of every sync, so the team can see what went out and when.
What should a brand planning the same move decide first?
A brand planning the same move should first decide where its writers will work. If they stay in WordPress, the migration is simply Wash's first sync, and the old site can become a private editing tool once the store is live. Before that first sync:
- map each WordPress category or language to a Shopify blog;
- add the Shopify languages and markets, so translations have somewhere to go;
- turn on redirects before the domain moves, so old links work on launch day.