The project I started the role with in 2019: the full rebrand from CustomSpace to ReadySpaces. New brand, new templates, new URLs, one cutover. Organic grew through the migration instead of dropping.
Site migrations are where organic traffic usually goes to die. The folklore is grim and mostly accurate: change your URLs and expect a dip. Change your templates and expect another. Change your brand name and plan on months of teaching Google who you are all over again. The company was doing all three at once: rebranding CustomSpace to ReadySpaces. New name, new brand identity, new page templates, new URL structure, one cutover, shipped across 2019 and 2020.
I led the whole rebrand, not just the SEO of it: the brand, the site, and the migration underneath. And organic wasn’t a channel we could afford to gamble with. The pages that ranked were the ones that drove real leads for real facilities. Every one of them was about to have its URL, its markup, and its brand context changed on the same day. Nothing broke, and the playbook below is why.
Nothing in the playbook is exotic. Migrations fail on discipline.
Redirect mapping first. Every existing URL got a destination before anything shipped: one-to-one, to the closest equivalent page on the new site, served at the edge through Cloudflare so redirects were fast and could be changed in minutes.
Content parity audits. New templates were checked against old pages for the things rankings are actually made of: headings, body copy, internal links, canonicals, structured data. A redesign that quietly drops half the content of a page is a rankings loss dressed up as a visual refresh.
Pre and post crawl comparisons. A full crawl of the old site became the baseline. After cutover, the new site was crawled and diffed against it: status codes, redirect chains, titles, internal link coverage. Anything that changed without a reason got a reason or got fixed.
A fixed Search Console cadence. Daily during the launch window, watching index coverage, redirect pickup, and impressions by page group. Weekly once things settled. The cadence mattered more than any single check.
Staged rollout. Where the plan allowed it, sections moved in stages, so a mistake surfaced small instead of everywhere at once.
A migration is a thousand small risks, and almost every one of them can be checked before launch.
Traffic didn’t dip and recover. It grew through the migration rather than falling into the usual post-cutover trough, and the footprint the rebrand created kept compounding: a coherent brand, cleaner templates, and a URL structure built for the content strategy gave every new page a stronger site to land on. The organic system the rebrand set the foundation for now runs at roughly 149,000 organic sessions in the past 12 months (GA4, Jul 2025 to Jun 2026), and 2026 is the highest organic has ever been, holding around 15,000 sessions a month across the second quarter.
The current scale is verifiable in Google Search Console: 110,894 organic clicks and 7.24M impressions in the past 12 months, with average position improving from roughly 21 to roughly 13 over the last 16 months. GA4 replaced Universal Analytics in July 2023, so the earliest comparable measurement window starts well after the 2019 to 2020 cutover. The numbers here reflect the system the rebrand built, not the migration-era jump itself.
The second-order effect matters just as much. Organic became the demand source the whole engine leans on. The ads budget engine reallocates paid spend nightly against demand each market already has, and a large organic base is what makes that reallocation worth doing. Paid fills the gaps; organic is the floor.
Redirect mapping is content work. The map only works if every old URL points at the page that answers the same intent. Blanket redirects to the homepage tell Google the old page’s topic no longer exists. Mapping to the nearest true equivalent is slower, and it’s the entire point of doing it.
Baseline everything before you touch anything. The pre-migration crawl and the Search Console benchmarks felt like busywork until launch week. Then they were the only way to tell a real problem from normal turbulence. You can’t diagnose a drop against a baseline you never captured.
The monitoring cadence is part of the migration. Most migration damage comes in the quiet weeks after cutover, when a bad canonical or a missed redirect sits unnoticed. A fixed daily review of Search Console during the launch window turns silent decay into a same-day fix.
Metro, location, and property pages plus market reports for ReadySpaces and WareCRE: hand-authored content on a templated architecture, with live inventory from an API.