A website redesign changes more than the visual layer. It can affect how people find information, where existing links lead and how inquiries reach your team. Treat the project as a controlled change to a working business system, with clear reasons for replacing what already exists.
Record what the current site does well
Inventory important pages, customer tasks, lead forms and connected systems. Review available search and business data to identify pages that bring suitable visitors or answer frequent questions. Ask staff which links customers commonly use.
Keep a reference copy of the current content and design before editing. A redesign can unintentionally remove helpful details simply because the old layout looks dated. Document what should remain, what needs improvement and what can be retired.
Decide the new structure before building
Organize pages around customer needs and the services or products you actually provide. Name an owner for content approval. If you can keep a useful existing URL, changing it purely for appearance may create unnecessary migration work.
Where URLs must change, build an old-to-new mapping with the closest relevant destination. Google's site-move guidance recommends preparing mappings and redirects and expects possible visibility fluctuations while pages are processed. A migration plan reduces avoidable mistakes; it cannot guarantee unchanged rankings.
Test the business journey and technical handoff
Review navigation, internal links, mobile readability, accessibility basics, images and search metadata. Test forms through delivery and confirmation. Check redirects and avoid sending every removed page to the homepage regardless of relevance.
Confirm that the production site can be indexed as intended and that temporary staging restrictions do not remain by accident. Verify the preferred domain, canonical links and sitemap behavior. Assign responsibility for these checks rather than leaving them as assumptions between providers.
Launch with an owner and a recovery plan
Choose a release window that your team can support. Keep a recoverable backup and document how to restore service if a critical function fails. Agree on what would trigger a rollback and who can make that decision.
After launch, inspect priority pages and inquiry delivery immediately, then monitor errors, search visibility and customer feedback. Google recommends retaining migration redirects for as long as possible, generally at least a year. Keep internal links current so visitors do not have to pass through avoidable redirect chains.
Measure improvement against the original brief
Compare the redesigned experience with the problems that justified the project. A fresh appearance is useful only when the important tasks remain dependable and become clearer. AGM can connect strategy, creative design and technical delivery in a redesign scope with documented launch checks and ongoing responsibilities.
Explore AGM capabilities, review our service investment guide, or start a conversation.
Sources and further reading
Google: Site moves with URL changes
Prepared with AI assistance for AGM Insights. Examples are illustrative and are not reported client results. Illustration created with AI.
