Why a redesign can make rankings drop
Google ranks specific pages, identified by their address (URL) and their content. When a redesign changes addresses, removes text that attracted visits or breaks internal links, Google has to understand the site again from scratch.
The mistakes that do the most damage tend to be the same ones: new URLs with no redirect, content cut down to look “cleaner”, headlines and page titles rewritten without judgement, and a test environment that gets indexed by mistake.
Google warns that during a migration, rankings and visibility can fluctuate while it crawls and indexes again. Good preparation minimises this, but does not eliminate it.
Before you start: the inventory
A good part of the risk is avoided before anything is designed, with information. Gather:
- All current URLs. You can get them from the sitemap, a site crawler, analytics and the Search Console performance report.
- The pages that bring visits, enquiries or external links. Those are the ones you cannot lose.
- The current titles, descriptions and headlines of the important pages.
- A full copy of the website and the database, in case you need to go back.
- The starting figures: organic visits, most frequent queries and positions, so you can compare afterwards.
Deciding what changes and what is kept
The safest rule is the one that seems least creative: keep the URLs of the pages that already work whenever you can. A visual redesign does not oblige you to change addresses.
If a page’s content ranks, do not delete or trim it for aesthetic reasons. You can improve it, reorder it and make it clearer, but keep the topic and the answers it gave. If a page has no traffic and no purpose, you can retire it: return a 404 or 410, or redirect it to a page that is genuinely equivalent.
Watch the titles
Google recommends descriptive, unique titles that are not repeated across pages. If the redesign turns them all into “Home | Brand”, you will be losing information Google used to understand each page.
301 redirects: the critical piece
If any URL changes, every old address must redirect to the new one that replaces it. Google explains this in its site-move guide: draw up a URL-by-URL mapping and use permanent server-side redirects (301 or 308) straight to the final destination, with no chains.
- Do not send lots of old pages to the home page. Google expressly advises against it when it is not a real equivalence.
- Update internal links, canonical URLs and the sitemap so they already point to the new ones.
- Check that they work with the URL inspection tool or a script, before and after launch.
- Keep the redirects for at least a year, according to Google’s documentation; keeping them indefinitely is reasonable.
Permanent redirects tell Google that the new address is the definitive one. Temporary ones (302, 307) leave the old address in the results, so use them only if the change is genuinely provisional.
The test environment: keep it out of the index
Working on a copy of the website (staging) is the right approach, but that copy must not appear on Google. There is a common trap: blocking it with robots.txt alone does not prevent indexing. Google explains that if a page is blocked in robots.txt, the crawler will never see the noindex tag, and the page can still appear in results if others link to it.
- Protect the test environment with a password, or use `noindex` on crawlable pages.
- When you launch the final website, remove the noindex and check it has not been carried over to the live site. It is a classic oversight that makes a website vanish from Google.
- Also check that the new site’s robots.txt file blocks only what you want blocked.
Launch and the first few weeks
Switch on the redirects and check that canonicals and robots tags point to the right places.
Submit the new sitemap in Search Console and remove the old one.
If you change domain, use the change-of-address tool for each verified variant.
Review internal links and ask profiles, directories and campaigns to use the new addresses.
Keep an eye on Search Console: indexing coverage, sitemap, errors and performance.
Compare visits and queries with your starting figures and fix any errors that appear.
Google says that on medium-sized sites new results can take weeks to show. Do not be alarmed by the first fluctuations, but do be alarmed by sustained drops on particular pages: they usually point to a broken redirect or to content that has been trimmed.
To check afterwards how your website stands for crawling and indexing, the guide Why your website is not on Google lists the usual causes.
Frequently asked questions
How long does Google take to recognise the new website?
It depends on the size of the site. Google says that on medium-sized sites new results can take weeks or longer to show, and longer still on large sites. During that time it is normal for rankings to fluctuate.
Do I lose rankings if I only change the design and keep the URLs?
The risk is lower, but it still exists if the content, titles or speed change noticeably. Keep the copy, heading structure and internal links, and check performance in Search Console carefully after launch.
Does a 301 redirect lose strength?
Google states that permanent redirects do not lose PageRank. What does harm is redirecting many pages to a single unrelated one, chaining redirects, or removing them too soon, so plan the mapping carefully.
Can I use the redesign to change domain as well?
It is better not to combine two big changes at once. A domain change brings its own procedure (verifying both sites and using the change-of-address tool). If you can, separate the two projects in time.
Sources4
- Google Search Central — Site move with URL changesdevelopers.google.com (opens in a new tab)
- Google Search Central — Redirects and Google Searchdevelopers.google.com (opens in a new tab)
- Google Search Central — Block Search indexing with noindexdevelopers.google.com (opens in a new tab)
- Google Search Central — Title linksdevelopers.google.com (opens in a new tab)
