Websites: cost, hiring and build
Website redesign checklist: how to relaunch without losing your rankings
A new design rarely costs a site its traffic. Changed URLs with no redirects, deleted pages that used to rank, and a staging block left switched on do.
A redesign is the most common way a small business loses search traffic it spent years earning. Not because Google dislikes new designs, but because a relaunch quietly changes the things Google had attached your rankings to: the addresses of your pages, the words on them, and sometimes whether Google is allowed to see them at all.
This checklist is in the order the work should happen. Most of it is done before the new site exists, which is exactly why it gets skipped.
Step 1: record a baseline before anything changes
You cannot tell whether a relaunch hurt you if you never wrote down where you started. Before any design work begins:
- In Google Search Console, open the Performance report, set the longest date range available, and export it. Do this for queries and for pages. Search Console only keeps a limited window of history, so the export is your permanent record.
- In Google Analytics, note the landing pages that bring in the most visitors and the most enquiries over the last year.
- Write down how many pages Search Console reports as indexed.
- If you have no Search Console access at all, fix that first. It is free, and verifying a domain property through your DNS covers every version of the address at once.
Step 2: build a complete URL inventory
Google's own site move guidance starts here: list every URL on the old site, then decide where each one goes. Pull the list from several sources, because each one misses something:
- The current XML sitemap, usually at /sitemap.xml.
- The Pages report in Search Console, which shows what Google actually has.
- The landing pages report in Analytics, which catches old pages still getting visits.
- The Links report in Search Console, which shows which of your pages other sites link to. Those links are worth protecting.
- Your CMS, for blog posts, PDFs and image files that may not be in the sitemap.
Put it all in one spreadsheet, one row per old URL, and remove duplicates. This sheet becomes the redirect map.
Step 3: map every old URL to a new one
| Old page | What to do |
|---|---|
| Same page, same address on the new site | Nothing. Keeping a URL unchanged is always the safest choice |
| Same page, new address | Permanent redirect from the old address to the new one |
| Two old pages merged into one | Redirect both to the merged page |
| Page removed, with a close equivalent | Redirect to the closest equivalent, not to the home page |
| Page removed, nothing equivalent | Let it return a 404, or a 410 if it is gone for good |
Google specifically advises against sending lots of old URLs to one unrelated page such as the home page. If a page about brake repair used to rank, it should redirect to the new brake repair page.
Step 4: set up the redirects properly
- Use server side permanent redirects (301 or 308). Not JavaScript, not a meta refresh, not a plugin that only fires after the page loads.
- Redirect each old URL straight to its final destination. A chain of three hops is slower and wastes crawling.
- Update your own internal links, canonical tags and sitemap to the new URLs, so the site does not depend on its own redirects.
- Keep the redirects for at least a year. Google's guidance says generally at least one year, and keeping them indefinitely is reasonable. Old links in emails, directories and social posts keep arriving long after launch.
- If you are on a builder, check before you choose it how many redirects it supports and in what format.
Step 5: keep the content that ranks
Redesigns tend to trim text because a minimal layout looks better in a mockup. Go back to the baseline export. For every page that earns clicks, keep its title tag, its main heading and the substance of its body text, unless you have a clear reason to change them. You can rewrite and restructure later, one page at a time, and see the effect. Changing everything on launch day means that if traffic drops you will not know which change did it.
The same goes for your business name, address and phone number. They should match your Google Business Profile exactly on the new site.
Step 6: Search Console before and after launch
- If the domain stays the same and only paths change, you do not use the Change of Address tool. Google says it applies only when moving from one domain or subdomain to another.
- If you are moving to a new domain, verify both old and new in Search Console, then submit the Change of Address from the old property after the redirects are live.
- Submit the new sitemap on launch day. Warnings about redirecting URLs in the old sitemap are expected.
- Use the URL Inspection tool on your most important pages to confirm Google can fetch them.
Step 7: keep analytics continuous
Install the same Google Analytics 4 property on the new site, using the same measurement ID. A brand new property starts empty, and the history in the old one does not move across, so you lose the ability to compare before and after on one chart. Recreate every key event the old site tracked, such as form submissions and phone clicks, and test them in the Realtime report or DebugView before launch, not after. If you run ads, check that their conversion tracking still fires too.
Step 8: decide who owns the new accounts
A redesign is the moment new accounts get created: hosting, a new builder subscription, a new analytics tag, sometimes a new domain. Every one should be opened in an account your business controls, with your supplier added as a user. If a supplier opens them under their own login for convenience, you will be back where many owners start: a site you pay for but cannot move. If ownership of the design or code is written into the contract, that is a legal question, and worth having a lawyer read.
Launch day and the weeks after
- Check the robots.txt file and the page source for a noindex tag. Staging sites are usually blocked from search engines, and that block being carried over to the live site is one of the most common relaunch failures.
- Test a sample of old URLs from the inventory, including your top ranking pages, and confirm each returns a single 301 to the right page.
- Submit a test enquiry through every form and confirm it reaches a real person.
- Watch Search Console coverage and the Performance report weekly for the first two months.
- Expect some movement. Google says rankings can fluctuate temporarily during a move, and for a medium sized site it can take a few weeks or more for the new URLs to replace the old ones.
- Compare against the baseline export, page by page. A drop on one page usually points to one missing redirect or one deleted section of text.
What to do next
Do Step 1 today, even if the redesign is months away. The export takes ten minutes and cannot be recreated later. Then hand this checklist to whoever is building the site and ask them which steps are in their quote. If you would rather have someone run the whole migration, Corsa Media House does this work for Central Florida businesses, with every account opened in your name.
Questions
Will redesigning my website hurt my Google rankings?
It does not have to. Rankings usually drop because URLs change without redirects, pages that ranked are removed or stripped of text, or a staging noindex block is carried over to the live site. Google says some temporary fluctuation is normal during a move.
How long should I keep 301 redirects after a redesign?
Google advises keeping them for as long as possible, generally at least one year, and says keeping them indefinitely is reasonable. Old links in emails, directories and other sites keep arriving long after launch.
Do I need the Search Console Change of Address tool for a redesign?
Only if you are moving to a different domain or subdomain. If the domain stays the same and only page paths change, the tool does not apply. Redirects and a new sitemap do the work.
Should the new site use a new Google Analytics property?
No. Install the same GA4 property and measurement ID on the new site. A new property starts empty and the old history does not move across, so you lose the before and after comparison.
