The short answer
Search engines know your site by its addresses and its content. A redesign that keeps both, or carefully tells search engines where each page has moved, carries its visibility across. A redesign that changes addresses without redirects, or deletes the pages people were finding, starts again from nothing.
That is the whole risk, and it is manageable. The steps below are in the order they should happen.
Why redesigns lose rankings
| Mistake | What happens | How to prevent it |
|---|---|---|
| Addresses change with no redirects | Old links and rankings lead to error pages | A redirect map, tested at launch |
| Everything redirected to the homepage | Search engines treat the old pages as gone | Redirect each page to its closest equivalent |
| Ranking content removed or cut back | The page no longer answers the search | Audit before deleting anything |
| Page titles and headings rewritten carelessly | Relevance signals change overnight | Carry over what works, improve deliberately |
| Staging settings left on | The live site tells search engines to stay away | Check for noindex and robots blocks at launch |
| Internal links lost | Important pages become harder to find | Review navigation and in-text links |
| Slower pages | A worse experience on phones | Test speed before launch |
Step 1: record what you have now
Before any design work, capture the current position. You need this both to protect what matters and to judge the result afterwards.
- The pages that receive the most search visitors.
- The searches you currently appear for, from Search Console.
- The pages other websites link to.
- Monthly enquiries and where they come from.
- A full list of every address on the site.
If Search Console has never been set up, do it now. Even a few weeks of data is better than none.
Step 2: decide what must survive
Mark every page as keep, improve, merge or retire. Anything that brings in visitors or enquiries is a keep or an improve. Be especially careful with older guides and location pages. They are often unglamorous and quietly responsible for a good share of enquiries.

Step 3: keep addresses where you can
The safest redirect is the one you never need. If a page is staying, keep its address exactly as it is. Only change addresses when there is a real reason, such as a clearer structure or a renamed service.
Step 4: build the redirect map
For every address that will change, record the old address and the closest matching new one. This is a simple spreadsheet, and it is the single most valuable document in the project.
| Old address | New address | Note |
|---|---|---|
| /our-services/boiler-repairs.html | /services/boiler-repair | Same topic, cleaner address |
| /news/2019-summer-offer | /services | Expired offer, nearest relevant page |
| /about-us | /about | Same page |
| /team/john | /about | Merged into the about page |
- Use permanent (301) redirects.
- Redirect page to page, not everything to the homepage.
- Avoid chains, where one redirect leads to another.
- Include addresses that other sites link to, even if they look unimportant.
This follows Google's site-move guidance, which is worth sharing with whoever is building the site.
Step 5: carry the content across
For pages that perform, bring over the substance: the topics covered, the questions answered, the page title and the main heading. Improve the writing by all means. Do not reduce a detailed page to three lines because the new design has less room.
Step 6: check the technical basics before launch
- The new site is not set to noindex and is not blocked in robots.txt.
- Every page has a unique title and description.
- There is one clear main heading per page.
- Images are compressed and have alt text.
- The site works and loads quickly on a phone.
- An up-to-date sitemap exists.
- Tracking is installed and consent is handled.
Step 7: launch, then watch
| When | What to check |
|---|---|
| Launch day | Test redirects for your top pages. Submit the new sitemap in Search Console. Send a test enquiry. |
| First week | Look for crawl errors and not-found pages. Fix any missed redirects. |
| Weeks two to four | Watch indexed pages, impressions and clicks. Compare top pages with the baseline. |
| Month two onwards | Review rankings and enquiries. Improve pages that slipped. |
What movement is normal?
Some fluctuation in the first few weeks is expected while search engines process the changes. A dip that recovers is not a cause for alarm. A sharp fall that does not recover within a few weeks usually points to missing redirects, blocked pages or removed content, and each of those can be found and fixed.
Use the redesign to improve, not only to preserve
Protecting what you have is the minimum. A rebuild is also the best moment to fix long-standing weaknesses, because every page is being touched anyway.
- Give each main service its own page if several currently share one.
- Rewrite thin pages so they answer the questions customers actually ask.
- Add clear facts search engines and AI assistants can quote: what you do, where, prices, how to start.
- Improve page speed, especially on phones.
- Tidy the structure so important pages are one or two clicks from the homepage.
- Add internal links between related pages.
What to ask whoever is building the site
- Will you produce a redirect map, and can we approve it before launch?
- Which existing pages are you proposing to remove, and why?
- How will you make sure the staging site settings do not go live?
- Who checks Search Console after launch, and for how long?
- What will you report at 30 days?
If the answers are vague, the risk is real. A supplier who does this routinely will answer without hesitation.
Common questions
How long should redirects stay in place?
Indefinitely is simplest. At minimum keep them for a year, and longer for any address that other sites link to.
Does changing the domain name make it riskier?
Yes. A new domain adds another layer of change. It can be done safely, but it needs the same redirect discipline plus a change-of-address notice in Search Console.
Is changing platform a risk?
Only because platforms often change address formats. If the addresses are kept or redirected properly, the platform itself matters less. See WordPress vs Webflow vs custom development.
Who should be responsible for this?
Whoever builds the site, in writing. It belongs on every website redesign checklist, and it should be in the quote, not an optional extra.
Can you check our current visibility before we redesign?
Yes. A free 24-hour audit can include what currently brings you visitors and what would need protecting.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See Website redesign.
