Moving Retail Next's marketing site to WordPress without losing search rankings
We migrated Retail Next from a legacy CMS to headless-ready WordPress, kept every ranking URL, and gave marketing a page builder they can use without engineering.
Results
- ranking URLs lost in migration
- 0
- to launch a landing page, down from 2 weeks
- 2 days
- increase in demo requests from organic search
- 31%
The problem
Retail Next's marketing site ran on a legacy CMS that only two engineers could change. Launching a landing page took a sprint, the resource library was spread across three systems, and a previous migration attempt had stalled over fears of losing organic traffic.
Our approach
-
Crawled and inventoried more than 2,000 URLs, then ranked them by traffic, backlinks, and conversions to decide what to keep, merge, or retire.
-
Wrote a migration script that moved content, authors, taxonomy, and media into WordPress with structured fields instead of pasted HTML.
-
Built a library of approved Gutenberg blocks so marketing can assemble landing pages from tested patterns.
-
Mapped every retired URL to a 301 redirect and verified them in staging before cutover.
-
Ran the cutover on a weekday morning with rollback ready, then monitored Search Console and analytics daily for six weeks.
Project story
The risk everyone was worried about
Retail Next had tried to leave its old CMS once before. That project stopped when the team realized nobody could say for sure which pages drove pipeline. Losing those rankings was not an acceptable outcome, so the migration plan started with data, not design.
Inventory first
We crawled the full site and joined the crawl with analytics, backlink, and CRM data. Every URL got a decision: keep as is, merge into a stronger page, or retire with a redirect. About a third of the pages were thin or duplicate, which made the new information architecture simpler.
A builder marketing can actually use
Instead of a free-form page builder, we gave marketing a set of approved blocks: hero, proof bar, feature grid, comparison table, resource list, and form. Each block is accessible, fast, and on brand by default. Marketing can arrange them however they like without opening a ticket.
Cutover and after
Redirects were tested in staging against the full URL list before launch. After cutover we watched Search Console coverage, rankings, and demo requests daily. Rankings held, and organic demo requests grew over the following quarter as new landing pages went live.
“The migration was the quiet kind. Traffic held, redirects worked, and marketing started shipping pages the following week.”