Tara's Wonderworld makes DIY balloon sculptures, balloon garlands and party decorations from a workshop run by founder Britta and a small team. The business started on Etsy in 2018 and grew into a range of more than 1,000 products, with real demand behind it.
Its own website had not kept pace. It ran on WooCommerce, it was under-resourced, a plugin conflict had broken the homepage in some browsers, and it produced little commercial return compared with the products it was selling.
This case study covers what I found, how I planned the move to Shopify so the rankings the site had already earned were protected, and what was built.
At a glance
- Client: Tara's Wonderworld
- Sector: Party decorations, DIY balloon sculptures and balloon garlands
- Platform move: WooCommerce to Shopify
- Scale: more than 1,000 products, over 100 collections and around 4,000 URL redirects
- Work: Technical SEO audit, Search Console and order data analysis, redirect mapping, site structure, design, Shopify OS 2.0 theme build, full product migration and data clean-up, SEO foundations and training
The challenge
The products were proven. The website was the bottleneck.
I combined a full Screaming Frog crawl of the WooCommerce site with three months of Google Search Console data and the store's own order records. Together they showed a site with real search visibility that was not turning it into visits.
Visible in Google, but rarely clicked
Over three months the site appeared in Google searches hundreds of thousands of times, yet fewer than 1 in 100 of those searches led to a click. The average position was around 12, which puts most listings on page two. Of the roughly 1,000 pages showing in search, only a handful sat in the top three positions, where most clicks happen.
The visitors who did arrive bought at a reasonable rate. This was not a broken sales funnel. It was a site that Google could see but was not putting in front of enough people.
A platform working against itself
The April 2026 crawl, and the follow-up report in May, explained why:
- Products Google could not reach. More than a thousand paginated category pages had broken pagination sequences and could not be indexed, so products beyond the first page of a category had little chance of appearing in search.
- Slow on the devices that mattered. Server response times ran to more than 3 seconds. The large majority of search clicks came from mobile, where slow pages lose shoppers before products even load, and thousands of images were over 100 KB.
- Weak search listings. Hundreds of pages had no meta description, hundreds more had descriptions too long for Google to show in full, and dozens of page titles were duplicated.
- No structured data. None of the site's pages had schema markup, so Google had no product, price or review information to show in rich results.
- Messy URLs. Hundreds of URLs used underscores instead of hyphens, and the old category structure had produced competing pages, such as two separate pages both titled "Gender Reveal".
- Thin collection pages. Dozens of collection pages had no descriptive copy, leaving Google little to understand what each theme page was for.
- Broken pages. Internal links led to 404 and server errors, and the homepage itself was failing in some browsers because of a plugin conflict.
None of this is unusual for a WooCommerce site of this age and size. But together it explained why strong products were not translating into online sales.
The approach
A migration is the point where a site is most likely to lose the rankings it has spent years earning. So I planned this one around protecting what was already working, before building anything new.
Know exactly what to protect
I used the Search Console data to identify the pages and keywords carrying the site's search equity. A handful of pages were doing most of the work, including the Gender Reveal Box and the Gruffalo, Lightning McQueen, Paddington and Peter Rabbit ranges. Some held top-three positions for searches such as "gruffalo balloons" and "gender reveal box".
Those pages became the priority in the redirect map. Every old WooCommerce product and category URL was mapped to its closest Shopify equivalent with a permanent 301 redirect, so visitors and Google arrive at the right page instead of an error. The store now has around 4,000 redirects in place.
Plan in phases
The project ran in clear stages, each with something to sign off before the next began:
- Discovery and planning. Crawl and Search Console review, the redirect map, the new site structure and navigation, and the Shopify setup.
- Design. Mobile-first designs for the homepage, collection pages and product pages, approved before any build work started.
- Build and migration. A Shopify OS 2.0 theme built from the approved designs, every product moved across with its images, pricing, descriptions and categories, plus checkout, payments, shipping and order emails.
- SEO and analytics. Redirects implemented, titles, meta descriptions and structured data set up, the sitemap submitted to Google, and Google Analytics 4 conversion tracking configured.
- Testing, training and launch. Cross-browser and device testing, a full checkout test, and training and written guides so Britta's team can run the store themselves.
Build for the people running it
The store had to be something a small team could manage without a developer. Shopify's OS 2.0 editor lets them update products, collections, pages and images themselves, which matters as much as anything I built. A site the owner cannot maintain soon falls behind again.
What was built
The new store runs on a premium Shopify OS 2.0 theme, customised to the approved designs and connected to GitHub, so every change is version-controlled and can be rolled back.
Moving platform fixed a large share of the old problems on its own:
- Crawlable pagination. Collection pages use real page-two links that Google can follow, so products deep in a category can be found and indexed.
- Faster image delivery. Shopify's CDN compresses images and serves modern formats automatically, which matters on a site where most shoppers are on mobile.
- Clean URLs. Shopify uses hyphenated URLs as standard, replacing the hundreds of old URLs that used underscores.
- Structured data. Product pages now output schema markup, which the old site had none of.
- A clearer structure. More than 1,000 products now sit in over 100 collections, organised in the navigation by Characters, Occasions, the Balloon Boutique and Decorations, so shoppers can browse the way they plan a party. Collection pages now open with introductory copy instead of going straight into a product grid.
Moving the data was also the time to clean it. Product titles still carried leftover WordPress placeholders, images were missing alt text, meta descriptions were missing or duplicated, and some old links pointed nowhere. I fixed the missing and broken data as part of the migration, so the new store started clean rather than inheriting the old site's problems.
Results
The migration moved more than 1,000 products, over 100 collections and the full catalogue of images onto Shopify, with around 4,000 redirects in place so that existing rankings, backlinks and bookmarks carried across to the new URLs.
What the business has now:
- A store the team can run themselves. Products, collections, pages and menus are managed in Shopify's admin, without relying on WordPress plugins or a developer for everyday changes.
- A cleaner technical foundation. The issues the pre-migration crawl flagged, from underscore URLs and missing schema to missing alt text and duplicate meta descriptions, have been fixed rather than carried across.
- Search equity protected. Every old URL with traffic or links behind it has a permanent redirect to its closest match on the new site.
- A clear baseline to measure against. The pre-migration search report gives an honest picture of where the store started, so progress can be measured rather than guessed.
It is still early. Search engines take several months to fully re-crawl and settle after a platform change, so I am tracking impressions, click-through rate, average position and revenue from organic search against the pre-migration baseline. I will update this case study once there is enough data to report meaningful results.
What other retailers can take from this
- Audit before you move. A crawl of the old site tells you what to fix on the way across. Without it, the same problems move platforms with you.
- Protect what already ranks. Map every URL with traffic or backlinks to a sensible new destination. Redirects are the cheapest insurance in any migration.
- Use the move to fix the basics. Titles, meta descriptions, alt text and structured data are far easier to get right during a migration than after it.
- Check the data, not just the import. Imports carry old problems with them, such as leftover placeholders in titles and missing alt text. Checking the data on the new platform before launch stops them following you across.
- Build for the people who run the store. A platform the team can manage day to day is worth more than one that needs a developer for every change.
Frequently asked questions
How long does a WooCommerce to Shopify migration take?
It depends on the size of the catalogue and how much needs fixing along the way. For a store of around 1,000 products, a planned migration covering design, build, data import, redirects and SEO typically takes several weeks. Rushing the redirect mapping and testing is where most migrations lose traffic.
Will I lose my Google rankings if I move from WooCommerce to Shopify?
Not if the migration is done properly. Rankings are lost when old URLs disappear without a redirect, or when page titles and content are stripped out in the move. Mapping every important URL to its new equivalent with a 301 redirect, and carrying across the content that earned the rankings, protects most of the search value.
Can Shopify keep my WooCommerce URLs?
No. Shopify uses a fixed URL structure, such as /products/ and /collections/, so most WooCommerce URLs will change. That is why a full redirect map is essential. For this store, I set up around 4,000 redirects.
What should I fix during a migration rather than after?
Page titles, meta descriptions, image alt text, structured data, broken links and site structure. These are all easier to fix while the data is being prepared for import than to correct page by page once the new store is live.
Is Shopify better than WooCommerce for a growing retailer?
For many growing retailers, yes. Shopify removes the hosting, plugin and update overhead that comes with WordPress, and gives the team a simpler admin to work in. WooCommerce still suits businesses that need heavy custom functionality and have developer support on hand. The right choice depends on how the business operates, not on the platform's reputation.
Planning a migration?
If you are considering moving your store to Shopify, or you are worried about what a migration could do to your search traffic, I can help you plan it properly from the start. Read more about my WooCommerce to Shopify migration service, or email me at office@pinkdigital.co.uk with a little about your store and what you want to achieve.