Website Redesign Checklist: Everything to Do Before, During and After

Most website redesign problems do not come from bad design. They come from missing steps. Pages disappear without redirects. Forms break without anyone noticing. Rankings drop because nobody mapped the old URLs to the new ones. Tracking stops working because analytics was an afterthought. The new site looks great, but enquiries drop and nobody can explain why.

This checklist covers every stage: what to audit before you start, what to plan during design and development, what to test before launch, what to check on launch day and what to monitor afterwards. If you want the full picture of the website build process, our web design pillar guide covers everything. This article is the project checklist.

The Straight Answer: A Redesign Needs a Plan, Not Just a New Look

A successful website redesign should improve clarity, mobile usability, trust, conversion paths, speed, service page structure, SEO foundations, tracking, content management and long term maintainability.

It should not accidentally lose valuable pages, organic rankings, backlinks, enquiry tracking, forms, analytics data, customer trust, business email or working integrations.

The safest redesigns begin with an audit of what already works and finish with monitoring what changed after launch.

How to Use This Website Redesign Checklist

The checklist is divided into four stages: before the redesign, during design and development, before and during launch and after launch. For each task, assign an owner, a due date, an approval person and a status. Recommended status labels: Not Started, In Progress, Ready for Review, Approved, Blocked, Complete.

Use our website launch checklist tool alongside this guide to make sure nothing gets missed during the cutover.

Before the Redesign: Audit the Current Website

Do not begin by immediately designing a homepage. First understand what the current site is doing well, where it is failing and what needs to be protected.

1. Clarify why the website is being redesigned

Possible reasons include outdated design, poor mobile experience, low enquiry volume, difficult content management, unclear services, slow performance, weak SEO structure, business repositioning or platform limitations. Translate vague goals into measurable outcomes.

Weak goal: "Make the website more professional." Better goal: "Make the main services clear within 10 seconds and increase qualified quote requests from mobile visitors."

2. Define the primary website goal

Choose the main action the website should generate: phone calls, quote requests, consultation bookings, product sales or qualified project enquiries. Then define secondary actions like case study views, newsletter signups or service page clicks. The redesign should be structured around the primary conversion path, not the company's internal preferences.

3. Record current performance before changing anything

Capture a baseline: organic traffic, paid traffic, top landing pages, enquiry volume, phone clicks, form submissions, conversion rate, mobile vs desktop performance, top ranking queries, Core Web Vitals and revenue where trackable. Without baseline data, it becomes impossible to know whether the redesign improved performance or only changed the appearance. For help setting up analytics, see our guide to GA4 setup for small business.

4. Run a full content and URL inventory

Create a spreadsheet of every live URL with columns for current URL, page title, page type, traffic, conversions, ranking keywords, backlinks, content owner, keep/improve/merge/remove decision, proposed new URL, redirect required and notes. Include every page type: homepage, services, locations, articles, landing pages, case studies, contact, products, legal pages and thank you pages.

5. Decide what to keep, improve, merge or remove

Keep pages that rank, convert or attract backlinks. Improve pages with value that need clearer copy, better design or stronger CTAs. Merge pages that overlap or compete. Remove pages with no traffic, no backlinks and no strategic purpose. Even removed pages need a redirect decision. Do not let valuable old URLs simply disappear.

6. Review existing SEO performance

Identify top organic landing pages, important keywords, pages with backlinks and content gaps. Preserve valuable URLs, page topics, content depth, internal links and title tag intent. If SEO is a major driver for the redesign, our SEO guide for Melbourne businesses covers how site structure and content strategy fit into the bigger picture. Use our meta title and description checker to review existing metadata before deciding what to preserve.

7. Plan the new sitemap

The sitemap should reflect priority services, customer journeys, search demand, business growth and conversion paths. A typical small business structure includes Home, About, Services (with individual service pages), Industries or Service Areas, Projects or Case Studies, Articles or Resources, Contact and Legal pages. For a full framework, see our website planning guide.

8. Build the redirect map before development finishes

For every URL that will change, document the old URL, new URL, redirect type, relevance of destination, priority and implementation status. Avoid redirecting everything to the homepage, redirect chains, loops and unrelated destinations. For the full SEO migration process, see our website migration SEO checklist.

9. Gather content and brand assets

Collect logos, brand guidelines, service descriptions, team bios, testimonials, Google reviews, case studies, project photography, product images, videos, pricing guidance, FAQs, licences, downloads and legal policies. Content delays are one of the most common reasons redesign projects stall. Assign a content owner and due date for each item.

10. Audit website access and ownership

Confirm access to domain registrar, DNS, hosting, CMS, Google Analytics, Google Search Console, Google Tag Manager, Google Business Profile, Google Ads, CRM, email marketing, booking system, payment gateway, call tracking and third party integrations. The business should retain ownership and administrator access to its major accounts. The Australian Cyber Security Centre at cyber.gov.au recommends businesses maintain control of their own digital accounts and credentials.

During the Redesign: Plan the Customer Journey Before Polishing the Visuals

The design phase should focus on how visitors enter the site, understand the offer, compare services, build trust, find proof, overcome objections and take action.

11. Confirm page goals before designing each template

Every page needs a clear job. The homepage helps visitors understand the business and choose a path. Service pages explain and sell one specific service. Landing pages convert one campaign audience into one action. Articles answer questions and guide readers toward services. The contact page makes enquiring feel easy and predictable. For specific frameworks, see our guides on homepage conversion and service page structure.

12. Design mobile first, not desktop shrunk

Test the first mobile screen: can the visitor understand the service in 10 seconds, tap the main CTA easily, call or enquire quickly and use the menu with one thumb? Review tap targets, navigation, sticky CTA bars, phone links, form length, font size and popup behaviour. If you only review on desktop, you are missing what most visitors actually see.

13. Review copy before final design approval

The design should use realistic copy, not placeholder text. Check for a clear H1, specific service descriptions, customer first messaging, proof, FAQs, strong CTA wording and location details. Do not approve layouts before knowing final content length.

14. Build trust into every key page

Include reviews, testimonials, project examples, client logos, certifications, team photos, guarantees and process explanations. Place proof near the hero, near forms, near pricing, near objections and before the final CTA.

15. Plan forms and conversion paths

For each form, decide purpose, required fields, optional fields, confirmation message, notification recipient, CRM action, tracking event and spam protection. Test every form manually before launch. For detailed guidance, see our guide on forms people actually finish.

16. Plan analytics and tracking before launch

Define what should be tracked: form submissions, phone clicks, bookings, purchases, key CTA clicks and file downloads. Confirm GA4, Google Tag Manager, Search Console verification, Google Ads conversion tracking, consent setup and CRM attribution. Do not wait until after launch to decide what success looks like.

17. Build for speed from the start

Review hosting, image sizes, page builder weight, animations, video use, fonts, plugins, third party scripts, caching and CDN. Avoid giant hero media, sliders, unnecessary animation libraries and loading every script on every page. For specific speed guidance, see our guide on how to speed up your website. For hosting selection, see our Australian web hosting comparison.

18. Include accessibility basics

Review colour contrast, readable text sizes, keyboard navigation, form labels, button labels, image alt text, focus states, heading order and link clarity. Use our accessibility quick check tool for a fast review. The Australian Government's Digital Service Standard includes accessibility as a core requirement and the principles apply to good commercial web design too. This is a practical foundation, not a guarantee of full legal compliance. Get professional advice if accessibility is critical for your industry.

19. Review privacy, consent and legal content

Check privacy policy, cookie and consent setup, form consent wording, marketing opt ins, terms and conditions, refund and shipping policies (if relevant), tracking pixels and embedded third party tools. The OAIC's Australian Privacy Principles require businesses to handle personal information responsibly. Get legal advice if you are unsure about compliance requirements.

Website QA Checklist Before Launch

QA is not a quick glance before going live. It should cover content, design, functionality, SEO, performance, tracking, accessibility and cross browser testing.

Content QA

Check spelling, grammar, business name consistency, phone numbers, email addresses, addresses, opening hours, service areas, pricing, team details, testimonials, legal copy and placeholder content. Every page should be read by someone who did not write it.

Design and mobile QA

Check desktop, tablet and mobile layouts. Review spacing, typography, image cropping, button consistency, hover states, sticky elements, dropdowns, modals and footer. Test on Chrome, Safari, Firefox, Edge, iPhone, Android and the devices that appear most in your current analytics.

Functional QA

Test menus, links, buttons, forms, phone links, email links, bookings, payments, search, filters, downloads, logins, confirmation emails and CRM integrations. Submit every form manually and confirm the enquiry reaches the correct destination. A broken form on launch day is the most expensive silent bug a website can have.

SEO QA

Check title tags, meta descriptions, one clear H1 per page, heading hierarchy, canonical tags, indexability, robots.txt, XML sitemap, image alt text, internal links, structured data, redirect rules, the 404 page and any staging domain references that should not appear on the live site. For more on what these metrics mean, see our guide to Core Web Vitals explained.

Tracking QA

Confirm GA4 pageviews fire, form submission events track, phone click events fire, booking and purchase events work, Google Ads conversions record, thank you pages load and consent behaviour functions correctly. Avoid tracking button clicks as successful leads when the form may fail silently.

Website redesign risk register

Final Pre Launch Checklist

Before launch, confirm: all content approved, all design approved, redirects ready and tested, forms tested on desktop and mobile, tracking tested with real submissions, backups completed, DNS access confirmed, rollback plan documented, launch owner assigned, launch time agreed, support team available, old site archived, Search Console access confirmed, sitemap ready and staging restrictions documented for removal.

Website Launch Day Checklist

Before the switch

• Create final backup

• Freeze content changes

• Confirm DNS records and business email MX records

• Confirm redirect rules are loaded

• Notify stakeholders of launch timing

During the switch

• Deploy the production site

• Update DNS or hosting configuration

• Enable SSL and confirm HTTPS works across the site

• Remove staging passwords and noindex settings

• Enable production tracking (GA4, GTM, Google Ads)

• Activate redirect rules

• Clear all caches

Immediately after launch

• Test homepage, core service pages and contact page

• Test every form (submit a real enquiry to yourself)

• Test phone links on mobile

• Test bookings and payments if applicable

• Confirm analytics is recording

• Spot check key redirects

• Test mobile navigation

• Submit the XML sitemap in Search Console

• Check robots.txt and canonical tags

• Confirm HTTPS and www vs non www consistency

The launch is not complete when the homepage loads. It is complete when the main customer journeys, SEO settings, forms and tracking all work on the live domain.

What to Check After the Website Redesign Goes Live

First 24 hours

Check uptime, forms, phone links, payments, bookings, email delivery, analytics, critical redirects, mobile display, broken links, SSL and caching. Fix anything that blocks enquiries immediately.

First week

Monitor Search Console indexing, 404 errors, redirect issues, sitemap processing, organic landing pages, form submissions, enquiry quality, conversion tracking, mobile performance and customer feedback.

First month

Compare against the baseline: organic traffic, rankings, impressions, enquiries, phone calls, bookings, conversion rate, bounce and engagement rate, Core Web Vitals, top landing pages, lead quality and revenue where trackable. If your site is getting traffic but enquiries have dropped, our guide on why your website gets traffic but no enquiries can help diagnose whether the issue is messaging, trust, CTAs or something else.

Keep a post launch issue log

Track every issue with columns for issue, page, severity (Critical, High, Medium, Low), reported by, owner, status, fix date and retest result. Critical issues block enquiries or payments. High issues damage key pages. Medium issues affect usability. Low issues are cosmetic improvements.

Common Website Redesign Mistakes

• Starting with visual inspiration instead of goals. Pretty examples are useful, but only after the business problem is defined.

• Deleting pages without checking traffic or backlinks. A page with no visual appeal may still have organic value worth preserving.

• Rewriting ranking content too aggressively. Improve weak content, but do not gut pages that are already performing.

• Changing URLs for no meaningful reason. Every unnecessary URL change creates redirect complexity and SEO risk.

• Leaving redirect mapping until launch day. Redirects should be planned during development, not scrambled together at the last minute.

• Designing with placeholder copy. Approving layouts built around lorem ipsum leads to content that does not fit the design.

• Reviewing only on desktop. Mobile is where most visitors interact with the site. QA must include real devices.

• Forgetting forms and tracking. The most expensive launch day bugs are silent ones: broken forms and missing analytics.

• Launching with no rollback plan. If something critical breaks, you need a way to revert quickly.

• Leaving the live site set to noindex. Forgetting to remove staging restrictions makes the entire site invisible to Google.

• Treating launch as the end of the project. Post launch monitoring is part of the redesign. Rankings, enquiries and forms need active review for at least the first month.

What We Recommend at Elev8d

A website redesign should not erase the value built by the old site. It should preserve useful content, strong URLs, search visibility, backlinks, customer trust and working conversion paths. Then it should improve messaging, mobile usability, speed, proof, forms, page structure, tracking and maintainability.

A redesign is successful when the new website does a better job for both the business and its customers, not merely when it looks newer. If you are also considering a platform change as part of the redesign, our guides on Wix to WordPress migration and Squarespace to WordPress migration cover the platform specific steps. And our platform comparison guide can help you decide whether a platform switch is necessary at all.

FAQs

What should be included in a website redesign checklist?

A goal definition, performance baseline, content and URL inventory, sitemap plan, redirect map, design and copy review, mobile QA, forms and tracking setup, pre launch testing, launch day steps and post launch monitoring.

How long does a website redesign take?

A simple brochure site might take 3 to 6 weeks. A service business site with blog content might take 6 to 10 weeks. Complex sites with ecommerce, integrations or large content libraries can take 10 to 16+ weeks. For a realistic cost estimate, try our website cost estimator.

Will redesigning my website hurt SEO?

It can if URLs change without redirects, valuable content is removed or metadata is lost. A well planned redesign with URL preservation, redirect mapping and post launch monitoring should protect existing rankings.

Should I keep the same URLs during a redesign?

Yes, wherever the existing URLs are clear, relevant and performing well. Every URL change requires a redirect and introduces a small amount of SEO risk.

What should I test before launching a new website?

Content accuracy, mobile layouts, every form, phone links, tracking events, redirects, page speed, accessibility basics, browser compatibility and SEO elements like title tags, canonicals and indexability settings.

What should I monitor after a website relaunch?

Search Console indexing, 404 errors, redirect issues, organic traffic compared to baseline, enquiry volume, form submissions, phone clicks, conversion rate, Core Web Vitals and lead quality. Monitor actively for at least the first month.

Do I need a redirect map for a redesign?

Yes, for every URL that changes. A redirect map prevents rankings from dropping, backlinks from breaking and bookmarked pages from returning 404 errors.

How do I know whether the redesign was successful?

Compare the baseline data (captured before the redesign) with post launch performance. Look at enquiry volume, conversion rate, organic traffic, rankings, lead quality and revenue. Stakeholder opinions about the design are useful but should not be the only measure.

Should I redesign and migrate platforms at the same time?

You can, but it increases complexity and risk. If the platform change is necessary, combine it with the redesign and plan the migration carefully. If the current platform is fine, a redesign without a platform change is simpler and safer.

How often should a business redesign its website?

There is no fixed schedule. Redesign when the site has a measurable performance problem, the business has changed significantly or the structure no longer supports the customer journey. A well built site with ongoing maintenance can last 3 to 5 years or more before a full redesign is needed. Use our DIY website audit to check whether a redesign is genuinely needed.

Next Steps: Pick Your Path

• About to start a redesign? Begin with the audit checklist above. Record baseline data, inventory your URLs and build the redirect map before any design work starts.

• Already in the middle of a redesign? Jump to the QA and pre launch sections. Make sure forms, tracking, redirects and mobile testing are covered before launch.

• Just launched? Go straight to the post launch monitoring checklist. Check forms, redirects, indexing and analytics daily for the first week.

• Need help planning or executing? Talk to Elev8d about a website redesign in Melbourne that protects your existing SEO, improves the customer journey and includes proper QA and post launch monitoring.

Sources and Further Reading

• Google Search Central - Site Moves - Google's guidance on URL changes and permanent redirects during redesigns

• web.dev - Core Web Vitals - Google's documentation on loading, interactivity and visual stability metrics

• Australian Cyber Security Centre - Security basics including account access and credential management

• OAIC - Australian Privacy Principles - Privacy requirements for businesses collecting personal information

• Australian Government Digital Service Standard - Guidance on accessible, user centred digital services

General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you are unsure about compliance, get professional advice.