Skip to main content
GullySystem
A practical guide

Website redesign checklist to keep your search traffic

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Treat a redesign as a move, not a repaint. Audit which pages earn visits, map every old address to a new one and install redirects. Keep analytics running, test on staging and watch search reports daily for a month. Most lost traffic comes from skipped steps, not from the design.

Audit before you touch a single page

Export every address the site has by combining a Screaming Frog crawl, the XML sitemap and the pages that received visits or links. Put them all in one sheet. Add columns for visits, inbound links and the purpose of each page.

Mark each page keep, merge, improve or remove. Pages that bring enquiries must survive in some form. Thin pages with no visits and no links can go, but decide that on purpose and write down the reason beside each one.

Save a snapshot of the current state as well. Keep the title tags, H1 headings, meta descriptions and schema markup. After launch you will compare against it.

  • Crawl export of all live addresses
  • Search console list of pages with clicks
  • Pages with backlinks from other sites
  • Title, heading and description for each page

Map every old address to a new one

The URL map is the heart of the project. Each old address needs a destination. A removed page should point to the closest relevant page, never blindly to the home page, because a blanket redirect reads as a soft 404.

Keep addresses unchanged wherever you can. A new design does not demand a new folder structure, and every address you keep is one 301 redirect that you never have to write, test, maintain or debug.

Watch the small things. Trailing slashes, uppercase letters, query strings, PDF downloads and old image files all create broken paths. Ask the developer to test the map against the full export, line by line, before launch.

Build on staging and test like a crawler

Run the new site on a private staging address behind a password and a noindex rule. Forgetting that block lets a duplicate copy get indexed, and the confusion between the two versions can last for weeks. Check it twice.

Crawl staging with a tool. Look for missing titles, duplicate headings, broken links, error pages and redirect chains longer than one hop. Then test the forms, the cookie banner, the Tag Manager container and the mobile layout on a real phone.

Compare words, not only looks. Designers shorten text to fit tidy layouts, and the cut copy often held the exact phrases that people typed into search before they found you. Restore it.

  • Titles and headings carried across
  • Canonical tags point to the live address
  • Sitemap and robots file updated
  • Forms send mail to the right inbox
  • Analytics and ad tags fire once

Launch day checks

Pick a quiet day, never Friday evening. Back up the old site, switch over, remove the noindex rule, load the redirect map and submit the new sitemap in Search Console and Bing Webmaster Tools. Announce nothing yet.

Then test as a visitor. Click twenty old links from your spreadsheet, search for the company name and submit the contact form. Open the live robots.txt file, because a leftover Disallow rule is the classic launch day disaster.

Keep the old site files and the old database export for a few weeks, so that a badly broken section can be restored in an afternoon. Delete nothing yet.

  • Robots file allows crawling
  • Redirects return a permanent status
  • Sitemap submitted
  • Contact form delivers a test message

What to watch in the first month

Check Search Console every day for the first fortnight and watch for indexing errors, pages dropped from the index and sudden falls in clicks. Expect a small dip. A cliff is not normal.

Review the list of addresses returning not found and fix each with a redirect. Compare rankings, impressions and visits for your top twenty pages against the pre-launch sheet. Look for patterns.

Fix problems in order of enquiries lost. At the end of the month, write down what changed and what the data said, then close the project.

Redesign URL map and launch sheet

A workbook with one line per existing address. Columns hold the old address, monthly visits, inbound links, the decision to keep, merge or remove, the new address, the redirect type and a tick for tested on staging. A second tab lists the launch day checks and the daily readings for the first month.

Open a blank worksheet to print

Questions owners ask

Will a redesign always lower my search traffic?

No. Traffic often holds steady when addresses, content and redirects are handled with care. Losses usually come from missing redirects, removed text or a blocked crawler.

Should I change my addresses during a redesign?

Only when there is a clear reason. Keeping the same addresses avoids redirects altogether and removes a whole category of risk.

How long do redirects need to stay?

Keep them for at least a year, and longer for pages with strong links. Removing them early breaks old bookmarks and links from other sites.

Can I redesign in stages instead?

Yes. Moving one section at a time makes problems easier to trace. It suits large sites where a single switch would hide the cause of any drop.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements