Want to redesign a website without losing SEO? You can reduce the risk, but nobody can promise that search rankings will stay the same. Protect the useful parts of your old site and plan every address change before launch.
SEO means helping search engines find and understand your pages. A redesign can change what they see. The steps below give you a clear list to share with your builder.
The short answer
- Save important URLs, useful content and search evidence before the redesign.
- Keep working addresses when possible and map each necessary move.
- Check content, redirects, page settings and the sitemap on the live site.
- Expect possible search changes and investigate clear faults before making more changes.
How this guide was made
Google site move, sitemap and SEO guidance informs this risk checklist. The five URL map and launch record are fictional planning tools. No search migration or traffic recovery was measured for this article, so it cannot promise a redesign without ranking loss.
Sources checked .
Save a record of the old site
List your current page addresses, also called URLs. Include service pages, useful guides and pages that other websites link to. Do not rely only on the main menu. It may leave out important pages.
Save recent search clicks and page visits if you have them. Note which pages lead to real enquiries. These records help you spot changes later. Compare similar time periods, since seasons and other marketing can affect traffic too.
Keep a copy of titles, main headings and page content. This is your reference if something useful gets lost. You do not need to freeze every word, but you should know why you are changing it.
Keep useful addresses and answers
Changing the look and moving the pages are separate decisions. Preserve useful answers even if the layout changes. A shorter page is not an improvement if it loses the details customers came to read.
The same page addresses
If the purpose stays the same, ask to keep the URL. Then compare old and new copy, titles and internal links. You still need a launch check even without redirects.
New page paths
If a page needs a new address, record the matching destination before the move. Ask whether the new page answers the same customer need. A working redirect to unrelated content is not a good replacement.
A new domain
Google advises separating major changes where practical. If you are also changing the domain, allow for ownership checks and the move process. Doing everything at once can make a fault harder to trace.
Source for this section: [1] Google guidance on site moves and redirects
Make a map for every changed address
A redirect sends an old URL to a new one. Google supports permanent redirects such as 301 or 308 for a lasting move. Go straight to the intended final page where possible.
This five URL map is fictional. It includes both a page retired on purpose and a page lost by mistake. Those cases need different decisions.
- Record the full old URL and final destination.
- Check the returned page content, not only the response code.
- Update internal links to the final addresses.
- Give someone responsibility for keeping the redirect map current.
| Old URL | Plan | Pass rule |
|---|---|---|
| /services | Keep the address | Current services remain available |
| /gardencare | Replace with /gardenmaintenance | Permanent redirect reaches the matching service |
| /pruning | Merge into /treecare | New page fully covers the useful pruning information |
| /oldoffer | Retire with no relevant replacement | Return a real 404 or 410 response |
| /hedgetrimming | Accidentally missing from the new build | Restore it or map to a genuinely equivalent page |
Source for this section: [1] Google guidance on site moves and redirects
Check the signals on each new page
Check the title and main heading against the page topic. Google recommends clear titles and useful links. Then ask the builder to check the separate settings below. One green result does not settle all of them.
Source for this section: [3] Google SEO starter guide
Crawl access
Can a search crawler reach the public page? Look for a login wall or a robots rule left over from the draft site. Do not remove protection from private pages as part of this check.
Index settings
A noindex instruction asks search engines to leave a page out of results. Check that it is not left on a page meant for search. A robots.txt crawl block is a different control and should not be treated as a reliable way to remove an indexed URL.
Canonical and sitemap
The canonical tag names the preferred address for a page. Confirm it points to the right public URL rather than a preview or old domain. It is a signal, not a promise that a search engine selects it.
The sitemap should list the current public URLs you want discovered. Google says a sitemap is a hint, not a guarantee that pages will be crawled or indexed.
Sources for this section: [2] Google guidance on building a sitemap; [3] Google SEO starter guide
Check the live site after launch
Use a launch record for the important pages. Fill it with actual results after release, not the expected result from a draft. The table describes what your reviewer should record.
Submit the updated sitemap through your search tools. For a supported domain move, follow the separate Change of Address process. An ordinary redesign on the same domain does not need that tool.
Google generally recommends keeping redirects for at least a year. Record who maintains them. Search traffic can fluctuate during a move even when the work is careful.
| Launch evidence | What the reviewer records |
|---|---|
| Old and final URL | Original address and actual destination |
| HTTP response | Expected live page or permanent redirect result |
| Correct content | Matching service and useful information retained |
| Canonical | Preferred public address in the page |
| Public index setting | No unintended restriction on a page meant for search |
| Reviewer and result | Name, date, pass or issue to fix |
Sources for this section: [1] Google guidance on site moves and redirects; [2] Google guidance on building a sitemap
Watch for problems and keep a change log
Review broken URLs, search performance and real inquiries after launch. Start with the pages most useful to the business. Compare similar periods and keep a note of other changes, since a traffic drop alone does not prove the redesign caused it.
A useful page is missing
Look up the old URL in the move map. If it was lost by mistake, restore the content or its proper replacement. Do not disguise the loss by sending every missing page to the homepage.
A redirect reaches the wrong page
Compare the destination with the original purpose. Fix the map and the internal links, then retest the old address. A 200 response only proves that some page was served.
Draft settings remain on public pages
Check crawl access, noindex and the canonical against the intended live settings. Correct an actual error, then review the URL in your search tools. An indexable page is not the same as a page confirmed in search results.
Sources and further reading
Numbered links beside each section point to the source used there. Our examples and checklists are guidance from SnapRebuild. They are not claims of test results. Product details can change.
SnapRebuild sells a website building service. These guides are published under our editorial team name and use AI for research and writing. This is not a claim of independent expert review. Read how we make and update our content. Found an error? Tell us.
Ready for a fresh start?
Bring your website or your business idea. Explore a SnapRebuild preview and decide what comes next.
Try your free preview