01A launch sequence that protects what already works
Inventory pages, search data and inbound links first. Preserve useful URLs and content, clarify navigation and the offer, then improve mobile layouts, proof and calls to action. Only redirect a changed URL to its genuine replacement. Before launch, compare the page inventory, canonicals and sitemap; after launch, verify forms, analytics and URL Inspection. Unrelated deleted pages should return a useful 404, not redirect to the homepage.
02Signs the current site needs a redesign
A dated appearance is only one signal. The stronger reasons are unclear services, slow mobile pages, weak calls to action, missing location context, broken forms, confusing navigation or pages that search engines cannot interpret well.
03Protect useful search equity
Existing URLs, indexed pages and inbound links should be reviewed before launch. When a URL must change, a redirect plan helps preserve signals and prevents customers from landing on dead pages.
04Redesign scope
The project can include positioning, content architecture, copy restructuring, responsive design, technical cleanup, analytics preparation and launch support.
- Current-site and competitor review
- Page and keyword mapping
- Mobile-first redesign
- Metadata and structured data
- Redirect and launch checklist
- Post-launch support options
05Platform judgment
A rebuild is not automatically required. If the current platform is stable and supports the needed changes, improving it may be the better investment. If it creates security, speed or ownership problems, the proposal will explain why moving is justified.