Keep your URLs the same wherever you can. For every page whose address has to change, set up a server-side permanent redirect (301) to the most relevant new page, and keep the pages and titles that already bring searches. Then watch Search Console after launch. Google says a move can cause temporary ranking swings, and that permanent redirects do not cause a loss in PageRank.
Last checked November 6, 2026Why redesigns lose rankings
Google ranks pages, and each page is known by its address. When a redesign changes an address, deletes a page or hides the site from Google, a page that earned its place can drop out. Google's guide to debugging traffic drops names the technical causes: server problems, pages that return "page not found", and a misplaced noindex tag, which tells Google to leave a page out.
- Pages moved to new addresses with no redirect, so old links and old search results land on an error page.
- Pages deleted because they did not fit the new design, even though they brought in searches.
- A noindex tag or a robots.txt block left over from the build. Google notes that some owners block all crawling while a site is in development, and tells you to plan what the file should look like at launch.
- Titles rewritten into vague text. Google says to avoid descriptors such as "Home" and to give every page a distinct, descriptive title.
- Several big changes at once. Google advises changing one thing at a time, so a new domain, a new platform and a new layout do not all land on the same day.
Google says small shifts in position happen at any time, and also recommends avoiding radical changes to a page that already performs well. So change what needs changing and protect the rest.
Before you start: write down what you have
You cannot protect pages you have not listed. Before any design work, build a list of every address on the current site and mark the ones that matter. Google suggests these places to look:
| Where to look | What it tells you |
|---|---|
| Your sitemaps | Your most important addresses are likely listed, because they were probably submitted to Search Console |
| Server logs or analytics | Which addresses get the most visits |
| The Links report in Search Console | Which pages have links pointing at them, from your own site and from others |
| Your content management system | A full list of every address that holds content |
Include the images, PDFs and videos you host. Google says they need to be moved the same way as pages.
Then save each important page's title, headings and text, and check that every version of the old site (www, non-www, http, https) is verified in Search Console.
Keep addresses and the pages that rank
The best redirect is the one you never need. If the new site can use the same addresses, a page keeps its place. Google's guide to changing hosting, where addresses stay the same, shows how much simpler that is: no redirect map to build.
- Keep the address of any page that brings search visits, even if you redesign everything on it.
- Keep the page's topic and main text. Improve it, but do not swap it for something unrelated.
- Keep titles that describe the page. Google calls the title link often the main thing people use to decide which result to click.
- Do not merge or delete pages that bring visits unless there is a clearly better page to send people to.
Map old addresses to new ones and redirect
For every old address that will not exist on the new site, choose the one best new page and write the pair down. Google calls this a URL mapping. Then set up permanent redirects on the server so visitors and Google follow each old address to its new home.
- List the old addresses, using the sources in the table above.
- Next to each one, write the most relevant new page. A service page goes to its new service page, a post to its new post.
- Set up server-side permanent redirects, 301 or 308. Google recommends them over other types, and says permanent redirects do not cause a loss in PageRank.
- Redirect straight to the final page. Google advises against chains, and says that if one is unavoidable you should keep it short.
- Test them. Google's URL Inspection tool checks single addresses, and a script can check many.
| Situation | What to do |
|---|---|
| A page moved to a new address | Permanent redirect from the old address to the new one |
| Several old pages merged into one | Redirect each old address to the new combined page |
| A page removed, with nothing like it on the new site | Let the old address return a 404 or 410 error, not a redirect to an unrelated page |
| Many old pages sent to one unrelated page, such as the home page | Avoid it. Google says it can confuse visitors and may be treated as a soft 404 error |
| A move to a new domain | Redirect every address, then submit a Change of Address in Search Console for the old site |
Keep the redirects as long as you can. Google says generally at least one year, and suggests keeping them indefinitely for visitors.
Launch day checklist
Before and at launch
- Remove the build blocks. Take the noindex rules and the robots.txt block off the new site, or Google cannot index the new pages.
- Check that each page has a canonical tag pointing at its own new address.
- Update internal links and the sitemap to the new addresses, then submit the new sitemap in Search Console.
- Make sure Search Console verification still works. If you verify with an HTML file or a tag, it has to be in the new copy of the site.
- Test the redirects, forms and phone links, on mobile too.
- Check that the server can take extra load. Google says it crawls more heavily than usual after a move.
A Change of Address is only for moving from one domain or subdomain to another. Google says you do not need it for http to https, www to non-www, or moving paths within the same domain.
What to check after launch
Expect some movement. Google says rankings can fluctuate while it recrawls and reindexes, and that for medium-sized sites it can take a few weeks or more for new addresses to replace old ones. That is Google's general rule, not a promise for your site.
- Sitemaps report: pages indexed from the new sitemap should rise as pages from the old one fall.
- Page indexing report: look for new "not found" errors and pages excluded by a noindex tag.
- Performance report: compare clicks and impressions for the pages you listed before the redesign.
- Your own analytics: traffic to old addresses should fall as traffic to new ones rises.
If traffic drops, check the technical causes first: the site being down, "not found" errors, a stray noindex tag. Google also advises waiting a few weeks before judging any fix.
Getting help with a redesign
Google's own advice is that a redesign is a good time to bring in an SEO, the earlier the better, so the new site is search friendly from the start. Our custom websites start at $999 with 3 months of support included, and every site is set up for Google with titles, descriptions, a sitemap and structured data. For help watching results after launch, our SEO starts at $799 a month. Every project starts with a free call and a written plan and price.
Where we can help
- Website design: Custom websites that load fast on mobile and are built to show up on Google.
- SEO: Monthly work to get you found: new pages, fixes and a report you can actually read.
Sources
- Google Search Central: Site moves with URL changes
- Google Search Central: Changing your hosting and SEO
- Google Search Central: Redirects and Google Search
- Google Search Central: Debugging drops in Google Search traffic
- Google Search Central: Influencing your title links in search results
- Google Search Central: Do you need an SEO?