Domain Migration Case Study: WooCommerce.com to Woo.com and Back Again
Case study: how WooCommerce migrated from woocommerce.com to woo.com and back. Key SEO lessons on domain history, migration challenges, and what not to do.
On October 31, 2023, WooCommerce switched its primary domain from WooCommerce.com to Woo.com. On April 9, 2024, it switched back. In between, organic traffic dropped hard enough that the company publicly named the domain change as a contributing cause, on top of a Google core update that landed mid-migration and made the damage harder to isolate.
This is what a real domain migration setback looks like from the outside, with the actual dates, the stated cause, and what's worth taking from it before you consider changing your own domain.
The timeline
- ~April 2021: Automattic quietly acquires Woo.com. The domain previously belonged to an unrelated registrant with the surname Woo. For over two years it just forwards to WooCommerce.com, doing nothing.
- October 31, 2023: WooCommerce rebrands to “Woo” and flips the primary domain to Woo.com. WooCommerce.com now redirects the other way.
- March 2024: a Google core update lands while the new domain is still settling. Organic traffic, already soft from the migration, drops further.
- April 9, 2024: WooCommerce reverts the domain back to WooCommerce.com. The developer team's own advisory states directly that the domain change was a contributing factor to the traffic decline, on top of the core update's impact.
From the October migration to the April reversal is roughly five months. WooCommerce announced the reversion about a week before executing it, and framed the goal plainly: regain normal traffic levels.

Why it went wrong
Bad timing compounded the reset. A domain migration already resets some trust and relevance signals while search engines re-crawl and re-evaluate the new URLs. That reset landed right before a core update reshuffled rankings sitewide across the web, so WooCommerce couldn't cleanly separate normal core-update noise from its own migration's redirect chain settling in. Two unrelated ranking disruptions stacked on top of each other at the same time.
The new domain carried baggage of its own. Woo.com wasn't a fresh registration. It had an unrelated owner and history stretching back years before WooCommerce ever touched it, then sat forwarding quietly for over two years before going live as the primary domain. A domain's history is itself a signal search engines weigh. Picking up a domain with an unrelated past and expecting it to instantly inherit the authority of the old one doesn't work that way, even when the redirects are technically clean.
What's stayed the same since
As of 2026, there's been no further domain change. WooCommerce.com is still the live domain, and it has been since April 2024. What didn't revert is the brand name: the company kept calling itself “Woo” even after moving the domain back. Domain and brand name turned out to be two separate decisions, and only one of them needed fixing. That's worth remembering if you're weighing a rebrand: you don't have to bundle a name change and a domain migration into a single risk.
What to take from this if you're planning a migration
- Separate the rebrand from the domain move. If the migration goes badly, you want the option to revert the domain without also unwinding a new name, logo, and messaging.
- Check the domain's history before you commit to it. A previously-owned or long-dormant domain isn't a blank slate. Pull its Wayback Machine history and back-link profile before you plan a migration around it.
- Don't schedule around a known volatile window if you can avoid it. You can't predict every core update, but you can avoid launching a migration right as one is rumored or already rolling out.
- Watch the first few weeks closely, and be willing to reverse course. WooCommerce's decision to revert wasn't instant, but it also wasn't dragged out for a year. Set a real checkpoint for when you'll call a migration a loss. The Google Search Console MCP's
traffic_dropsandcheck_alertstools are built for exactly this kind of monitoring window — ask for a diagnosis instead of eyeballing the Performance report every morning. - Audit what a migration leaves behind, on either side of it. Old and new URLs both staying indexed at once is one of the most common side effects, and it's easy to miss. Check which old URLs are still indexed with a Google index checker, and watch for keyword cannibalization between old and new URLs, which shows up on almost every migration I've looked at.
Frequently asked questions
Is woocommerce.com still WooCommerce's domain in 2026?
Yes. There's been no further domain change since the April 9, 2024 reversion.
Why did WooCommerce migrate to Woo.com in the first place?
The company rebranded to the shorter “Woo” name, which customers already used informally, and moved the domain to match as part of that rebrand.
Why didn't WooCommerce revert the brand name too?
The traffic problem was tied to the domain and its history, not the name. Reverting only the domain fixed the actual issue without also unwinding a rebrand customers had already absorbed.
Was the core update or the domain change the real cause of the traffic drop?
WooCommerce's own advisory names both as contributing factors, without splitting out how much each one cost. That's realistic. When a migration and a core update overlap, isolating the exact share each one caused is rarely possible from the outside.
What's the single biggest lesson from this case?
A domain migration isn't just a technical redirect exercise. The domain's own history and the timing relative to Google's update cycle both matter as much as getting the 301s right.
Where this leaves you
A well-known brand with real SEO resources still lost meaningful traffic on a domain change, and it took roughly five months to decide the trade wasn't worth it. If you're considering a domain migration, treat the domain's own history as a real input, not a footnote, keep the rebrand and the domain move as separable decisions, and set a concrete checkpoint for when you'll call it and reverse course. The technical side of a migration is the easy part to get right. Domain history and timing are the parts that actually decide the outcome.