A redesign can change your search traffic because it changes addresses, wording and structure. This checklist covers what to record first, what to keep and what to check after launch.
A redesign does not have to hurt your rankings, but it can if page addresses, titles or wording change without a plan. Record what ranks today, keep addresses where you can, send every changed address to its closest new page with a permanent redirect, keep the test site private, then check indexing and visits after launch.
Website redesign SEO checklist at a glance
A website redesign SEO checklist has one aim: change how the site looks without losing the pages, wording and links that bring visitors from search. Search engines judge pages, not styling. A redesign puts rankings at risk when it changes what a page says, where it lives or whether search engines can reach it. Google's own guidance says to expect temporary ranking changes after any significant change to a site, so the goal is to keep them short and small.
| Phase | Main tasks | What goes wrong if you skip it |
|---|---|---|
| Before the redesign | Record what ranks and what brings visits, list every page address, decide which addresses stay | You cannot tell what was lost, or which pages needed protecting |
| During the build | Map old addresses to new ones, carry over wording that earns visits, keep the test site private | Pages vanish from search, or the test copy gets indexed |
| Launch day | Turn on redirects, remove blocks, submit the new sitemap, test old addresses | Old links reach error pages, or the new site stays hidden from search |
| After launch | Watch indexing, errors and visits against your baseline | A fault runs for weeks before anyone notices |
Before the redesign: record what you have
Start with a list of every address on the current site that matters. You need it for three jobs later: deciding what stays, writing redirects and checking that nothing went missing. Build the list from several sources, because each one misses something.
- The sitemap file and the page list in your content management system.
- The Pages tab of the Performance report in Search Console, which shows the addresses that get clicks from Google.
- Landing pages in your analytics, which show where visitors enter the site.
- The Links report in Search Console, which shows pages that other sites link to.
- Images and downloads, such as PDF brochures, that get visits or links.
For each address, record the page title, the main heading, the searches it appears for, its clicks and whether other sites link to it. A spreadsheet is enough. Add the date at the top.
Then note the site-wide figures: total clicks and impressions from Search Console, the number of indexed pages, and the enquiries or orders the site produced. These are your baseline. The guide to running a basic SEO audit yourself shows where each figure lives.
Take a full backup of the old site, files and database, before any work starts. Also write down faults you already know about, such as duplicate titles or broken links, so that after launch you can tell old faults from new ones.
Should you keep the old page addresses?
Keep them wherever you can. A page whose address does not change needs no redirect, and nothing has to be learnt again by search engines or by the sites that link to it. A redesign changes the layout and wording of a page. It does not have to change the address.
Some addresses do have to change. The new platform may build addresses in a different pattern. Two pages may be merged. A service may have ended. Decide for every page in your list and write the decision next to it.
| If the page is... | Do this |
|---|---|
| Staying, with a new design | Keep the same address |
| Moving to a new address | Redirect the old address to the new one with a permanent redirect |
| Merged into another page | Redirect the old address to the merged page |
| Replaced by a close match elsewhere on the site | Redirect to that page, not to the home page |
| Gone with no replacement, such as an ended offer | Let it return a proper "not found" or "gone" response (404 or 410) and remove links to it |
Small differences count too. An address with a trailing slash and one without, or one in capitals and one in lower case, can be treated as separate pages. Pick one form and use it everywhere.
Why redirects matter when page addresses change
A redirect tells browsers and search engines that a page has moved and where it went. Without one, anyone who follows an old link, bookmark or search result lands on an error page. Search engines then drop the old address and meet the new one as a page with no history. Links from other sites to the old address stop helping you.
Google's documentation on moving a site gives the rules that matter most.
- Use server-side permanent redirects, such as 301 or 308, from each old address to its new one. Google says permanent redirects do not cause a loss in PageRank.
- Redirect each address to the most relevant new page. Sending many old pages to the home page can confuse visitors and may be treated as a soft 404 error.
- Send each old address straight to its final destination. If a chain cannot be avoided, keep it short, ideally no more than three redirects.
- Keep the redirects for as long as you can. Google's guidance is generally at least one year.
- Update your own internal links to the new addresses. A redirect works, but it adds a delay for every visitor.
Plan the redirects as a two-column table, old address on the left and new address on the right. Your developer can load it into the server settings or a redirect tool on the platform. Ask who owns this job, because it falls between design and development and is easy to forget.
Test before and after launch. The URL Inspection tool in Search Console checks single pages, and a crawler or script checks a long list.
Keep the wording and links that already earn visits
Design teams like to cut text for a cleaner look. On a page that ranks, that can remove the wording that made it rank. For every page on your list, check the searches it appears for and make sure the new version still answers them.
- Keep the page title and main heading close to the originals unless you have a reason to change them. If you rewrite them, keep the main phrase.
- Keep the body text that answers the search. Reorder it and shorten it if it helps, but do not strip a page down to a headline and a button.
- Keep internal links between related pages. Search engines use the links between your pages to judge which ones matter, so a new menu that buries a service page deep in the site can weaken it.
- Carry over image descriptions, structured data and meta descriptions. They are easy to lose when pages are rebuilt or a theme is swapped.
- Check that the new templates give each page one main heading, a unique title and a canonical tag that points to the page's own address.
A weak page can still be improved. The point is to change it on purpose and to know what you changed, so you can read the results afterwards.
During the build: keep the test site private
The new site is usually built on a separate test copy, often called staging. Search engines should never see it. A test site that gets indexed competes with the real one and puts unfinished pages in results.
Protect it with a password, because a request to stay out of search is easy to forget. Google's ecommerce documentation notes that a password blocks Google from the pages while still letting testers in.
The danger comes at launch. Many test sites carry a setting that tells search engines to stay away: a robots.txt rule that blocks everything, or a noindex tag on every page. If the test site goes live with that setting still on, the new site disappears from search. Write down each blocking setting as you add it, so every one is on the launch-day list.
Google also advises changing one major thing at a time. If a new domain name, a new platform and a new design all arrive in one release, a drop in visits has three possible causes. Where you can, separate them. Redesign first, or move the domain first, and let each settle.
The old site stays live while the new one is built. Anything you change on it in the meantime, such as a new product or a changed price, must be repeated on the new one, so keep a change log.
Launch day: the search steps in order
- Choose a quiet time. Google suggests timing a move for a period when your traffic is normally low.
- Switch on the redirects from the old addresses to the new ones.
- Remove the password and any noindex tags, and check that robots.txt does not block the site.
- Check that canonical tags use the live addresses, not test ones.
- Publish the sitemap with the new addresses, submit it in the Sitemaps report in Search Console and retire the old one.
- Test a sample of old addresses, starting with the ones that rank or have links. Each should reach the right new page in one step.
- Check that Search Console verification and analytics still work. A new theme can drop the verification tag or the tracking code.
- Test forms and the main enquiry or checkout path on a phone.
If the domain name changes, Search Console has a Change of Address tool for moving from one domain or subdomain to another. Google says you do not need it for a move from HTTP to HTTPS, a switch between www and non-www, or changed paths on the same domain. Most redesigns that keep the same domain do not need it.
This list covers only the search steps. The website launch checklist covers the wider pre-launch checks.
After launch: what to check and how long rankings take to settle
Rankings can move around for a while after any significant change. Google's documentation says it can take a few weeks for most pages of a small or medium site to move, and longer for large sites, and that visibility may fluctuate temporarily before settling. The exact period depends on how many pages you have, how fast your server responds and how well the redirects were done.
Use the table to read what you see in the first weeks.
| What you see | Likely cause | What to do |
|---|---|---|
| The whole site is missing from Google | A noindex tag, password or robots.txt block was left on | Check the page source, robots.txt and the URL Inspection tool, then remove the block |
| Old addresses show as "Not found" in the Page indexing report | Redirects are missing for those pages | Add a redirect to the closest new page |
| Visits to one section fell sharply but its pages are indexed | Titles, wording or internal links changed | Compare each page with the old version and restore wording that matched the searches |
| Old addresses still appear in results | Search engines process a move page by page | Check that each one redirects, then give it time |
| Old and new versions both appear as separate pages | Canonical tags or redirects are wrong | Point canonical tags to the live address and make the redirects permanent |
Look at the Page indexing, Sitemaps and Performance reports every few days at first, then weekly. Compare clicks, impressions and indexed pages with your baseline, and compare like with like. Run a crawl to find broken internal links and redirect chains. Keep the redirects in place for at least a year.
If visits have dropped sharply and these checks do not explain it, get a specialist review before making more changes. Liftup offers SEO, and the search engine optimisation page describes the service. Liftup also builds websites, and the website development page describes the websites Liftup builds.
If you are still deciding how far to go, website redesign vs rebuild and website maintenance vs redesign help you choose first.
Questions and answers
Will a website redesign hurt my search rankings?
It can, but it does not have to. Rankings are at risk when page addresses, titles or wording change without a plan, or when the new site is blocked from search by mistake. Google says to expect some temporary fluctuation after any significant change, so the aim is to keep it small and short.
What should I do before a redesign to protect SEO?
List every page address that matters, using your sitemap, Search Console and analytics. Record the title, the searches, the clicks and the incoming links for each, and note site-wide totals as a baseline. Decide which addresses stay and which need a redirect, and take a full backup of the old site.
Why do redirects matter when page addresses change?
A redirect sends visitors and search engines from the old address to the new one. Without it, old links, bookmarks and search results reach an error page, and links from other sites stop helping. Google recommends server-side permanent redirects, such as 301, from each old address to the closest new page.
How long do rankings take to settle after a relaunch?
Google's documentation says a small or medium site can take a few weeks for most pages to move, and larger sites take longer. Visibility may fluctuate in that time. The exact period depends on the size of the site, server speed and the quality of the redirects, so watch the trend in Search Console rather than waiting for a date.
Should I keep the old page addresses?
Yes, where you can. An address that does not change needs no redirect and loses nothing in the move. Change an address only when there is a reason, such as a merged page or a platform that builds addresses differently, and then redirect the old one to the new one.
What should I check straight after launch?
Check that the site is not blocked by a leftover noindex tag, password or robots.txt rule. Test a sample of old addresses, confirm the new sitemap is submitted, and make sure Search Console and analytics still work. Then test your forms or checkout on a phone.