Inventory before editing
List the current pages, navigation, forms, assets and external integrations. Record which URLs are linked from outside the website. Keep a backup of the original files and note any hosting configuration that is not part of the visible design. This makes the scope of the change easier to control and review.
Separate the problem from the appearance
Identify the actual issues: unclear content, mobile overflow, slow media or an awkward enquiry flow. Some problems need a small layout or code repair rather than a new template. Agree which parts should change and which should remain. That prevents a visual update from unintentionally removing useful content or functionality.
Preserve meaningful URLs
Keep existing URLs where practical. If a page must move, plan an appropriate redirect and update internal links. Review canonical references and the sitemap after the change. Avoid launching a redesign with old links pointing to empty placeholders or every retired page redirected to an unrelated homepage.
Test the real visitor journeys
Check navigation, service links, forms, phone links and the mobile menu. Review multiple screen sizes and inspect error or fallback states. Compare the redesigned page against the agreed scope rather than relying only on a screenshot. Report what was actually tested and where device or account access was unavailable.
Launch with a rollback plan
Keep the previous version and a clear list of changed files. Confirm the intended domain and clear relevant caches after deployment. Review the live pages, not just a local preview, when access is available. A controlled launch makes it easier to distinguish a code problem from a stale cache or hosting issue.
A quick checklist
- Back up and inventory first.
- Preserve or deliberately redirect URLs.
- Test journeys and keep a rollback copy.
Further reading: Google Search Central: SEO Starter Guide. Search outcomes are not guaranteed.