A good relaunch separates decisions into what exists, target state, migration, and control. If you only discuss URLs, forms, or tracking shortly before launch, you turn plannable tasks into unnecessary risks.
1. Goals and baseline
- Name business goals, audiences, and the most important user journeys.
- Secure organic entry pages, inquiries, and conversion events.
- Document the technical baseline with crawling, Search Console, and Lighthouse.
2. Content and information architecture
- Inventory all URLs and content.
- Decide what to keep, merge, revise, or remove.
- Derive navigation and page structure from user questions rather than internal departments.
3. Design and development
- Define components and states for mobile and desktop.
- Choose CMS, Shopify, WordPress, or custom based on requirements.
- Plan performance, accessibility, privacy, and maintainability from the start.
4. Migration
- Assign every important old URL to a fitting new URL.
- Update canonicals, hreflang, metadata, schema, and sitemap.
- Transfer forms, analytics, consent, feeds, and integrations.
5. Quality assurance and launch
- Check status codes, redirect chains, links, and the 404 page.
- Run test inquiries, orders, and emails end to end.
- Define backup, rollback responsibility, and launch window.
6. The first weeks
Search Console, server errors, 404 URLs, important rankings, and real user journeys are monitored. Not every fluctuation calls for an immediate new change; critical technical errors do. For the detailed work, see URL mapping and 301 redirects and custom web development.
Primary sources and documentation
As of: August 29, 2026. This article describes a professional decision framework and is not a guarantee of revenue, rankings, or results.