Website Redesign Checklist: What to Do Before You Change Anything

Start With a Full Audit of What You Already Have

Before anything else, catalogue your existing site. You need to know what pages exist, which ones rank, and which ones bring in real visitors.

Export a full list of URLs using a crawler like Screaming Frog or a free tool like Google Search Console. Do not rely on memory or your navigation menu. Pages that never made it into the menu can still rank well.

Note which pages receive organic traffic, which have inbound links from other sites, and which convert visitors into enquiries or sales. These are your assets. They need protecting through the redesign.

Back Up Everything Before You Touch the Live Site

This sounds obvious, but it gets skipped more often than you would expect. Take a full backup of your database, your files, and your theme. Store it somewhere separate from your hosting account.

If your site runs on WordPress, a plugin like UpdraftPlus makes this straightforward. Download the backup locally rather than leaving it sitting only on the server.

Also screenshot or PDF your current design. When you are deep into a new build, it is easy to forget exactly what the old layout looked like. Having a visual record helps you spot what worked and what did not.

Record Your Current SEO Baseline

You cannot measure improvement if you do not know where you started. Before any redesign work begins, record your current position for every keyword that matters to your business.

Log your rankings, your organic traffic figures from Google Search Console, and your Core Web Vitals scores. Pull your top pages by impressions and clicks. Save this data somewhere safe.

Also note your current page titles, meta descriptions, and heading structure for your most important pages. These often get wiped during a redesign and rebuilt from scratch, which means you lose signals Google had already learned to trust.

Google's Quality Rater Guidelines, last updated in September 2025, still put real weight on experience and expertise signals. If your existing content demonstrates those qualities, you want to carry them forward rather than accidentally diluting them with thin replacement copy.

Map Out Your Redirects Before You Change Any URLs

Changing URLs without redirects is one of the most common and most damaging redesign mistakes. If a page ranked for a useful search term and you delete or rename it without a redirect, that ranking is gone.

Work through your URL list and flag every page that is changing address. For each one, decide where it should redirect. A 301 redirect tells search engines the page has moved permanently and passes the ranking signals to the new URL.

Build your redirect map in a spreadsheet. Old URL in one column, new URL in the other. Do not leave this until after launch. Doing it before means you can test it properly.

Also check for any URLs that appear in your Google Search Console sitemap but return a 404 already. A redesign is a good moment to clean those up too.

Agree on the Scope and Goals Before Design Work Starts

A redesign without a clear brief tends to grow. New features get added, old pages get deleted without proper thought, and the whole project runs over time and budget.

Write down what you actually want the redesign to achieve. Faster load times, a better mobile experience, a cleaner checkout flow, or a new brand look are all valid goals. Pick the ones that matter most and prioritise them.

Decide which pages are staying, which are being merged, and which are being removed. If pages are being removed, that feeds directly into your redirect map. Every decision made upfront saves you fixing problems after launch.

Also settle on your target audience and your main conversion actions before design work begins. A site redesigned around clear goals is always easier to measure than one redesigned purely on aesthetics.

Choose Your Technology Stack Carefully

The platform you build on shapes everything that follows. WordPress remains the most widely used CMS in the world for good reason. It is flexible, well-supported, and portable. If you ever need to move hosts or hand the site to a new developer, your content and structure go with you.

Proprietary builders can look attractive at the start. They often promise speed and simplicity. But your site lives inside their system, and if you ever want to leave, the migration is painful. WordPress sites can move cleanly because the data is yours.

Think carefully about SEO tooling too. A platform that handles your on-page SEO automatically, rather than leaving it as an afterthought, removes a lot of ongoing manual work. The difference between a site that runs its own SEO and one that relies entirely on you remembering to fill in every field is significant over the long term.

Test on a Staging Site, Not on the Live One

A staging environment is a private copy of your site where you can build and test without affecting your live traffic. Every reputable host offers this. If yours does not, that is worth noting.

Build the entire redesign on staging. Test every page, every form, every redirect. Check it on mobile as well as desktop. Run it through Google's PageSpeed Insights to catch performance issues before they go live.

Invite a small group of real users to click through it if you can. They will find things you missed because they have no expectations about how it is supposed to work.

Only push to live once you have signed off every item on your checklist. Launching half-finished and patching in public is stressful and bad for first impressions.

Plan Your Post-Launch Monitoring

The work does not stop at launch. The first two weeks after a redesign go live are the most important for catching problems quickly.

Watch Google Search Console daily for crawl errors, coverage issues, and any sudden drops in impressions. Check your analytics for traffic changes on your most important pages. If something drops sharply, you want to catch it in days, not months.

Resubmit your sitemap to Google Search Console after launch so the new structure gets crawled promptly. If you have changed a lot of URLs, this speeds up the process of Google discovering the redirects and updating its index.

Keep your old site backup for at least three months. If something goes badly wrong, having the ability to roll back is worth far more than the storage space it costs.