Record the current site before changing it
List public pages, their purposes, important titles and headings, enquiry destinations and search or referral evidence. Include linked resources and pages people reach directly, not only the pages in the main menu.
Keep a recoverable copy of the current website and the information needed to restore it. Agree who is responsible for the launch and rollback. A backup file is more useful when someone understands what it contains and how it would be used.
Decide which URLs genuinely need to change
If the page still answers the same need, keeping its address can simplify the work. Where a change is justified, map the old destination to the most relevant replacement before launch.
Google’s migration guidance recommends appropriate permanent redirects when URLs move. Avoid sending unrelated old pages to the homepage simply to remove error messages. A customer following an old link should still reach a useful answer.
Preserve useful meaning as well as addresses
A redesign can unintentionally remove information while keeping the URL. Compare the actual service explanation, headings, pricing context, relevant proof and enquiry links. Do not replace useful detail with decorative headings alone.
Keep claims accurate and clearly distinguish customer work, your own projects and demonstrations. If you deliberately change a page’s purpose, record that choice rather than describing it as unchanged SEO preservation.
Test the functional journey
Check forms, phone links, confirmation messages, resource delivery and any booking or payment handoff. Test the route that a customer will actually use, with a controlled test account or inbox where appropriate.
Check mobile layouts, keyboard access and the behaviour of optional animations. Premium presentation should help someone understand the business. It should not make the essential service explanation or contact controls depend on a heavy visual effect.
Verify the public launch, then monitor
After launch, inspect normal public URLs rather than only an administrator preview. Check status codes, redirects, canonicals, internal links and sitemap content. Confirm important assets and enquiry routes are still available.
Keep the pre-launch baseline so later changes can be assessed in context. Search visibility may fluctuate, and a redesign does not come with a guarantee that rankings will remain identical. Investigate specific regressions rather than assuming either success or harm from the appearance alone.
PUT IT INTO PRACTICE
A launch handover everyone can sign off
Use these prompts in your own notes or when discussing the work. This is a reading checklist, with no submission or data collection.
| Item | Before launch | After launch |
|---|---|---|
| Important URLs | Inventory and change map | Public200 or intended redirect |
| Content and metadata | Recorded baseline and intentional edits | Correct headings, title, canonical and service meaning |
| Enquiries | Agreed routing and test inbox | Verified controlled delivery |
| Presentation | Desktop, phone and reduced-motion review | Public assets and essential controls work |
| Recovery | Protected backup and named owner | Rollback remains available |
Questions, answered
Can a redesign affect rankings?
Yes. Changes to access, URLs, content, links or performance can affect search. Careful planning reduces avoidable problems but cannot guarantee unchanged rankings.
Should every old URL redirect to the homepage?
No. Match changed URLs to relevant replacements. Blanket irrelevant redirects can leave both readers and search engines with an unhelpful destination.
Is a mobile screenshot enough to test launch?
No. Check navigation and important functions as well as appearance. A page can look correct while an enquiry or confirmation route fails.
Official guidance
For the platform rules and technical detail behind the relevant checks:
YOUR NEXT STEP
Make the next decision with a clearer brief.
Tell KSJ Growth what you offer, what is not working and what you want the website to help you achieve. We can discuss a suitable scope before you commit to further work.
Discuss your business