03 / Migrate · URL to live check

Move off WordPress without losing what ranks.

Preview on a private URL, approve the look, then point the domain. A migration is a mapped inventory, a previewed cutover, and a live check of the same URLs. Unpushed shows what must survive, what failed, and the safe way back — not a redirect spreadsheet that ends at deploy.

Request access See how it works

relaypress.com · Migrate

/blog/*

unpushed

Legacy URLs broke after migration

8.6k clicks, last 28 days

Why this

Traffic still lands on old URLs that now 404 after CMS migration.

Proposed change

Live now

Legacy blog URLs return 404

After approval

Old URLs reach mapped article paths

What changes

Apply approved redirect map.

What stays

· URL history
· page topics
· internal links

Technical details

GET /blog/edge-caching → 404

GET /blog/edge-caching → 301 /articles/edge-caching

- GET /blog/edge-caching → 404
+ GET /blog/edge-caching → 301 /articles/edge-caching

Live check

Every old address is checkeda sample of the moved pages loads correctly
the change matches what you approvedold addresses reach their new pages
no detours or loopsvisitors go straight there
the previous version is keptthe old map can come back

Demonstration data — not a connected site.

Recognize the problem

A cutover is not done when DNS flips.

Staging can pass while production 404s the pages that already earned traffic. Migrate keeps the origin inventory attached to live verification.

01 / See the signal

Legacy blog paths 404 after the platform move.

312 addresses, 8.6k clicks in the last 28 days, still attach to the old blog tree. The signal is the inventory and the live response, not a hosting score.

Illustrative URL inventory

8.6k clicks· last 28 days

Old address	Where it should land
/blog/edge-caching	/articles/edge-caching
/blog/ssl-setup	/guides/ssl-setup
/blog/cache-keys	/guides/cache-keys

312 old addresses in total. Every one is checked on the real site after the move — anything still missing comes back as work.

Measure: 8.6k clicks, last 28 days
Live now: Legacy blog URLs return 404
Inventory: 312 addresses to map

02 / Run the loop

The job changes. The five moves do not.

Here is this job walking the same five moves.

01Find it8.6k monthly clicks depend on URLs that no longer work.
02Preview itEach old address beside the page it should reach.
03Approve itYou approve the map before anything moves.
04Push itThe map goes live at cutover.
05Check the real pageEvery old address is checked on the real site — anything still missing comes back as work.

03 / Watch the decision

Origin URL to destination to live check

Planned mapping, preview validation, production cutover, and the post-cutover live check stay visible as separate states. A missing destination becomes work.

Planned mapping
Preview validation
Production cutover
Live check

Origin URL

/blog/edge-caching

Destination

/articles/edge-caching

GET /blog/edge-caching → 404

Cutover left a traffic-bearing URL without a live destination. That returns as work, not a successful deploy.

relaypress.com · Migrate

/blog/*

pending

Legacy URLs broke after migration

8.6k clicks, last 28 days

Why this

Traffic still lands on old URLs that now 404 after CMS migration.

Proposed change

Live now

Legacy blog URLs return 404

After approval

Old URLs reach mapped article paths

What changes

Apply approved redirect map.

What stays

· URL history
· page topics
· internal links

Technical details

GET /blog/edge-caching → 404

GET /blog/edge-caching → 301 /articles/edge-caching

- GET /blog/edge-caching → 404
+ GET /blog/edge-caching → 301 /articles/edge-caching

Live check

Every old address is checkeda sample of the moved pages loads correctly
the change matches what you approvedold addresses reach their new pages
no detours or loopsvisitors go straight there
the previous version is keptthe old map can come back

A failed live check returns as work, with rollback recorded.

04 / What stays safe

A scoped change should stay scoped.

page intent: The destination still has to answer the same job unless the operator explicitly changes it.
URL history: Origin routes stay attached as preserved URLs or checked redirects rather than disappearing.
Content and internal links: The useful pages and the paths between them remain in the inventory that gets verified.
Tracking and revenue paths: Affiliate, checkout, and campaign URLs are reviewed before cutover and checked after.
Search history: Where search history exists, it stays attached to the surviving URL so Measure can continue.
The previous live state: The prior map stays recorded so a failed cutover can reopen or roll back instead of claiming success.

05 / Decide what to do

Move the useful site, then watch the same list.

Platform and structural transitions use the same inventory before and after cutover. This is traffic-safe migration and useful-site recovery, not a hosting comparison.

Observed signal	Question to answer	What to do
Same platform, new host	Do the origin URLs still resolve after DNS flips?	Preserve routes and live-check the inventory
New information architecture	Which origins become redirects, and which stay?	Map every traffic-bearing URL before preview
Tracking or revenue path	Does the destination keep the same measurement and payout path?	Review the high-value URL before cutover
Post-launch 404 or redirect chain	Did production disagree with the approved map?	Return the URL as work and keep the previous map available

The next job enters the same five moves

06 / Request access

Do not trust the deploy. Check the inventory.

See the origin list, the intended destinations, and what the live site actually returned.

Request access

Move off WordPress without losing what ranks.

Legacy URLs broke after migration

A cutover is not done when DNS flips.

Legacy blog paths 404 after the platform move.

The job changes. The five moves do not.

Origin URL to destination to live check

Legacy URLs broke after migration

A scoped change should stay scoped.

Move the useful site, then watch the same list.

Do not trust the deploy. Check the inventory.

Carry work to the real page.