Check website relaunch without loss of visibility
Control URLs, content, redirects, measurement and technical approval before moving to a new website.
- For whom
- Marketing, editorial, development and SEO managers before a domain, CMS or structure change.
- When to use it
- During content migration, before technical release, and immediately after public transition.
A relaunch is ready to go when every relevant old URL has a conscious target, internal links and canonicals point to the final address, redirects are tested on the server side and indexing, measurement and error control have been prepared for the switchover day.
Download PDFInventory and target structure
The new navigation must not decide which old content is lost unnoticed.
Technical release
Forwarding and indexing must be reproducibly checked before switching.
Switching and control
The relaunch does not end with a successful deployment.
Result of the joint review
- A complete URL and destination registry
- Tested redirects without chains
- Shared indexing and speech signals
- A clear control plan for the weeks after launch
Sources and professional basis
This working aid translates general recommendations into a compact initial review. The primary sources and your specific context remain decisive.
Frequently asked questions
Does every old page have to be retained?
No. But every relevant old address needs a conscious decision and, with suitable follow-up content, a direct, permanent forwarding.
Can visibility fluctuate after a relaunch?
Yes. Search systems have to reprocess old and new URLs. Good preparation reduces avoidable errors and makes development observable.
Browser checkmarks are not stored or transmitted to sudo/PORT.