Record what the current website does
List important pages, contact actions, products and integrations. Review available enquiries and analytics without assuming that a visual redesign alone will increase business. Identify the main problem: unclear services, slow images, mobile navigation, outdated information or a difficult enquiry journey. Set a practical acceptance check for each problem so the new version can be reviewed against a goal.
Keep a content and URL inventory
Save the current page URLs and note which content should remain, move or be retired. Review page titles and contact details while preparing the new structure. If URLs change, plan a mapping from each important old page to the relevant destination. Avoid redirecting unrelated pages to the homepage simply because it is convenient.
Plan the search transition
Google’s site-move documentation recommends preparing URL mappings and redirects when URLs change. Consult the official Google URL migration guide for the steps that apply to your project. A redesign is not a guarantee of stable rankings; monitoring after launch helps identify unexpected problems.
Review the journeys before launch
Test contact forms, phone links, WhatsApp links, menus and any checkout or login flow. Check headings, titles, descriptions, canonical URLs, image proportions and mobile overflow. Use actual devices alongside browser previews. Confirm who can approve the content and who handles hosting changes. Save a recoverable copy before replacing the site.
Agree support after launch
Monitor broken links, indexing and submitted enquiries where access is available. Define how problems are reported and which changes are included in support. Explore website redesign, SEO services and ongoing website care. Share your URL and main concern to begin a scoped review.
