Website redesign checklist: how to rebuild without losing rankings

A redesign is supposed to bring in more work. Sometimes it does the opposite. The new site looks better than the old one, and a few weeks after launch the phone is quieter. Pages that used to come up for “water heater repair” or “roof leak repair” have gone missing.

That usually isn’t bad luck. A redesign changes what Google relies on: page addresses, the words on each page and the settings behind them. This checklist can’t guarantee nothing moves. Google’s own site move guide says to expect some temporary fluctuation. The goal is to keep any dip small and short, and to catch real problems early.

Why do redesigns lose traffic?

Most traffic lost after a redesign traces back to a short list of mistakes:

• URLs changed without redirects. The drain cleaning page moved to a new address. Google, and every site that linked to the old page, now hits a dead end.
• Pages that ranked got dropped. The new menu needs fewer items, so a few service pages quietly disappear, including some that brought in calls.
• Content got cut for looks. A long, plain service page becomes a big photo and three lines of text. It looks cleaner, but Google reads words, and most of them are gone.
• Noindex was left on from staging. The new site was hidden from Google while it was built, as it should be, and the setting came along to the live domain.
• Tracking was forgotten. The analytics tag, call tracking script or form events didn’t make it onto the new site. Leads may be fine, but you can’t tell a real drop from a broken report.

All of these are preventable, mostly before anyone designs a page.

What should you record before you start?

Take a snapshot of the old site before it changes. Once it’s gone, much of this is hard to get back.

• Every URL with traffic, calls or links. Export the Pages tab of Search Console’s Performance report as far back as it goes, since it only keeps a limited window of history. Export landing pages from your analytics, check Search Console’s Links report for pages other sites link to, and if you use call tracking, note which pages produce calls. Combine it all into one list.
• A crawl of the old site. A crawler tool, such as Screaming Frog, lists every URL it can find with its title, headings and status. Save the old sitemap file too. The crawl catches what the exports miss, like a PDF price sheet a supplier links to.
• The searches you care about. Write down the searches that matter, like “AC repair Brandon” or “panel upgrade electrician”, and which of your pages shows up for each. Search Console’s Queries tab shows what people actually typed.
• A Search Console baseline. Clicks and impressions for the last few months, and how many pages the Pages report lists as indexed, saved with a date.
• A lead baseline. Calls and form submissions per week for the last few months, and the same weeks last year if you have them. Service work is seasonal, so last July is a better comparison for this July than last April.
• Screenshots or a copy of key pages. Save your top pages in full: words, headings, title tags and FAQs. If a page that ranked gets rewritten and slips, you’ll want to see what changed.

How do you plan redirects?

A redirect sends anyone who asks for an old address to the new one, people and Google alike, and helps carry the old page’s standing over to its replacement. The plan is a spreadsheet, usually called a redirect map, with one row per old URL and a column for the new one.

• Map one to one. Each old URL points to the single new page that best replaces it. The old water heater repair page goes to the new water heater repair page, not to a general services page.
• Use permanent 301 redirects. A 301 tells Google the move is permanent, so it shows the new address in results. A temporary redirect, like a 302, tells Google to keep showing the old one.
• Don’t send everything to the homepage. Google’s guide warns against it: it confuses visitors, and Google may treat those redirects as missing pages anyway. If an old page has no close replacement, send it to the nearest relevant page. If it had no traffic, no links and no calls, letting it return a 404 is fine.
• Avoid chains. If the old site already has redirects from an earlier redesign, update them to point straight at the final page. Each hop adds delay, and Google recommends going straight to the final address.
• Keep URLs that don’t need to change. The best redirect is the one you don’t need.
• Leave the redirects in place. Google’s guide recommends keeping them for at least a year. In our experience, there’s rarely a good reason to remove them at all.

The http, https, www and non-www versions of your site need the same care. Our guide to how sites accidentally hide from Google covers those, along with redirect loops, in more detail.

What content should you keep?

Content that earns calls stays, even if it looks dated. That’s hard in a redesign, because everyone wants the new site to feel new.

Here’s a made-up example of a pattern we see. An electrician has a panel upgrade page written years ago: long, plain and a bit clunky. It also brings in panel upgrade calls, because it answers what homeowners search for, like whether the work needs a permit and how long the power is off. The redesign swaps it for a short blurb and a stock photo, and those calls fall off.

• Rewrite and improve rather than delete. Keep the substance: the questions answered, the towns named, the specifics. Then improve it with current details, real job photos and a clearer layout.
• Keep titles and headings that work. If a page shows up for “sewer line repair”, don’t retitle it “Underground Solutions”.
• Merge carefully. Combining several thin pages into one stronger page is fine, as long as each old page redirects to the new one.
• Delete only what does nothing. A page with no traffic, no links, no calls and no job to do can go.

What should you check on launch day?

Launch day is when the settings that hid the staging site either get switched off or don’t. Check these on the live domain, not on staging:

• robots.txt. Open yourdomain.com/robots.txt and make sure it doesn’t block the whole site.
• Noindex. Check the site-wide setting in your platform, then view the source of the homepage and a few service pages and search for “noindex”.
• Canonicals. Each page’s canonical tag should point at its own live address, not at the staging domain or the homepage.
• Sitemap. The new sitemap should list only live, final URLs. Submit it in Search Console and remove the old one.
• The redirect map, tested. Run every old URL on your list through a redirect checker. Each should return a single 301 straight to the right page.
• URL Inspection. Run Search Console’s live test on the homepage and your top service pages.
• Tracking. Confirm the analytics tag is firing, form and booking events are recording, and the call tracking script is swapping numbers. Keep your existing analytics property rather than starting a new one, so before and after sit side by side.
• Forms. Submit every form and confirm each one reaches the right inbox or CRM.
• Phone links. Tap every click-to-call button on a real phone.
• Your Business Profile website link. If it pointed at a page whose address changed, update it. Do the same for ad landing pages and directory listings that link to a specific page.

Moving to a new domain as well? Use Search Console’s Change of Address tool. For what each setting above does, see noindex, robots.txt and other ways sites hide from Google.

What should you watch in the first eight weeks?

Check once a week, not every morning. Positions for any one search move around daily, and watching them mostly produces worry. Look at these instead:

• The Pages report in Search Console. Old URLs listed as “Page with redirect” is expected. Your new service and town pages should move into the indexed list over the following weeks.
• 404s. Any old URL under “Not found (404)” that used to get traffic or links needs a redirect. Add it and move on.
• Clicks by page. Compare the Performance report against your baseline, page by page, so if there is a drop you can see where it is.
• Calls and forms against your baseline. This is the number that matters. Compare with the weeks before launch, and with last year’s if the season has changed.

Some wobble is normal. Positions may bounce for a few weeks while Google recrawls the site and processes the redirects. Old addresses may still show in results for a while. Impressions may dip and then come back.

Signs of a real problem:

• Your homepage or key service pages aren’t indexed, or URL Inspection says “Excluded by ‘noindex’ tag”
• The 404 list keeps growing with pages that used to bring traffic
• A whole section, like all your town pages, drops and stays down week after week
• Calls and forms stay below your baseline after you’ve confirmed the tracking works

When leads drop right after launch, check the tracking first. In your reports, a missing call tracking script or a broken form looks exactly like a drop in business. Our call tracking guide explains how the pieces fit together.

If the redesign also starts new SEO work, like adding town pages, that work runs on its own clock. For local search, months one to three are usually foundations, and the map tends to move in months four to six. More on that in how long local SEO takes. Nobody can promise a position or a date.

Who should own what during a rebuild?

A rebuild is when access gets lost. The old developer leaves, the new one starts, and the accounts holding your history fall in between. Before work starts, make sure these are in your name, under your email, and that you can log in:

• The domain, at the registrar
• Hosting, for the old site and the new one
• Google Search Console, with you as a verified owner
• Analytics, and Tag Manager if you use it
• Your Google Business Profile
• Call tracking, plus the site’s admin login or code repository

Then add your developer as a user and remove them when the job is done. If a former agency owns your Search Console or analytics, getting access back takes time, and you need that history for your baseline. If they own the domain, you have a bigger problem. Our developer ownership checklist lists every account and what a proper handoff includes.

Planning a redesign?

On our website builds, we map every existing URL to its new page and set up permanent redirects, keep the content that already ranks, submit the new sitemap to Search Console and watch it for crawl errors after launch. Everything sits in accounts in your name. If you want to know where your current site stands before you change it, our free website review checks whether Google can find, read and index your pages, and sends back the three changes we’d make first.