How to redesign a website without losing SEO
Prepare important old addresses, review language routes and ask the team to verify the live customer journey.
Before a redesign, collect the links customers already use: Google results, old emails, bookmarks and printed QR codes. A new design should still let those people reach the right answer.
Useful addresses can often stay the same. Where content genuinely moves, ask the team to show the old-to-new destination before launch.
Bring the links the team might miss
Send important page and download addresses, links used in campaigns and any printed material. Include each language. Tell the team what the customer expects at the destination.
| Existing customer entry | What to agree before launch |
|---|---|
| A QR code for a service page | The same service remains reachable and its inquiry route works |
| An old email linking to an estimate guide | The guide stays, or an appropriate replacement receives the visitor |
| A Chinese service page | The route reaches the corresponding Chinese answer |
| A discontinued service | A deliberate content decision; do not send every missing page to the homepage |
The examples are illustrative paths to review, not redirect instructions to deploy.
Ask for a before-and-after check
Please show how these old links reach the intended new content, including language versions. After launch, demonstrate the public destination and the actual customer action on a phone.
The team should check loops, unnecessary intermediate redirects, internal links, language switches and the sitemap. Opening a destination is not enough if its form or booking route fails. Agree who checks launch, who handles faults and who follows search status afterward.
Technical reference for the team
A permanent redirect sends visitors to the new address. A canonical signals the preferred address for equivalent content; it does not move visitors. Language annotations identify corresponding language versions; they do not translate pages. These settings have distinct jobs.
Translations should normally retain their own main URLs. Ask the maintainer to verify the actual language relationships and the relevant public pages. Google’s site-move guide describes migration work; search visibility can fluctuate during processing.
Use the provider-change guide for accounts and the wider handover, and the missing-page check for follow-up. SiteMonk rebuilds agree the necessary address work within project scope.
This guide explains URL, canonical, and redirect decisions. For how SiteMonk implements and checks these foundations in website projects, see Technical SEO Standards .
On websites we have built, SiteMonk Care includes monthly checks of canonical URLs, redirects, and duplicate-page signals. We report findings in the System report and handle covered website issues proactively. See Care plans and monthly scope if you want us to look after these foundations.
Official sources checked on October 27, 2026. Examples are illustrative, not client results.