Website Redesign Checklist: Improve the Site Without Losing What Works
A successful website redesign starts with evidence about the current site, not a new colour palette. Audit the pages, customer journeys, enquiries and technical dependencies before changing the structure. Keep useful content and URLs where possible, map changes deliberately and test the main actions before launch. The aim is a clearer, more reliable website that solves identified problems while preserving the assets and information that already support the business.
Identify the reason for the redesign
Write down what the current website prevents customers or staff from doing. Visitors may struggle to compare services, the mobile menu may be awkward or the team may be unable to update basic information. A business may have changed its offer while the site still describes the old one. These are stronger starting points than a general feeling that the design looks dated.
Collect examples of the problem. Save the pages where users get confused, record common sales questions and review available enquiry data. If analytics are incomplete, acknowledge the gap rather than inventing a performance story. Staff observations and customer conversations can still reveal useful issues, provided they are treated as evidence to investigate rather than a complete explanation of every behaviour.
Agree the priorities with the people who operate the website. A marketing team may want clearer campaign pages while customer service needs accurate support information. A redesign can address both, but the project should name the main objective and the essential requirements. This keeps visual preferences from displacing the practical work that justified the project in the first place.
Inventory pages, files and external connections
Create a list of existing URLs before changing the site. Include core pages, articles, downloadable documents, campaign pages and any important product or category pages. Record what each page does, whether its content is current and what should happen to it. A small website may fit in a spreadsheet; a larger one may need a crawl and a more structured migration plan.
List the services connected to the site. Forms may send to several recipients. A booking widget may use a separate account. Analytics, search verification, email tools and payment systems may have settings that are not visible in the page design. Identify the owner and purpose of each connection so it is not accidentally removed or duplicated during the rebuild.
Check the domain, hosting and email arrangement as well. Website hosting changes can affect services beyond the visible site if records are edited without understanding their purpose. The redesign brief should distinguish moving website files from changing the domain registrar or business email. Document the existing setup and keep recoverable backups before making changes. This inventory is the foundation for a controlled launch rather than an urgent search for missing settings afterward.
Decide what to keep, improve, combine or retire
Review content page by page. Keep information that is accurate and useful. Improve pages that answer a real question but need clearer writing or updated details. Combine overlapping pages when customers would benefit from one complete explanation. Retire obsolete content deliberately, with an appropriate destination or response for old links where needed.
Do not rewrite every sentence simply because the design is changing. Existing language may reflect customer terminology or explain a specialised service accurately. Equally, do not preserve weak content out of habit. The test is whether a visitor can understand the offer and make a useful decision. Our service website copywriting guide provides a practical way to assess that clarity.
Record content decisions in the same inventory used for URLs. This gives the writer, designer and developer a shared reference. It also makes approvals easier because the business can see what is changing and why. Without this record, a redesign can quietly remove useful details, duplicate old problems in a new layout or create disagreements about whether an omitted page was intentionally retired.
Redesign the journeys before polishing the screens
Map a few important tasks from entry to outcome. A visitor might arrive on a service page, check the scope, view examples and request a quote. Another might open a campaign landing page and ask about one package. Identify the information and controls needed at each step, including what happens after the enquiry leaves the website.
Use a simple content outline or wireframe to review these journeys. It is easier to notice missing information before typography and imagery make a layout feel finished. Ask whether the page explains suitability, process, proof and the next action. Remove steps that require effort without helping the customer or the team respond.
Test the structure on a phone early. Navigation, long headings, fixed contact controls and forms can behave differently on a narrow screen. A design that looks balanced on a large monitor may hide the main action or force unnecessary scrolling. The mobile conversion checklist can guide this review. Resolve the important journey problems before spending time on decorative motion or secondary visual details.
Protect useful URLs and search information
Where an existing URL still represents the same useful page, consider keeping it. Changing every address creates migration work without necessarily improving the site. When a URL must change, map it to the most relevant new destination. Avoid sending all retired pages to the homepage, since that can leave visitors without the information they expected.
Preserve or improve descriptive page titles, headings and internal links. Check that the new site is accessible to crawlers and that important content is available as text. Google’s SEO starter guide is a useful reference for these fundamentals. A redesign is an opportunity to improve clarity, but it should not turn every page into a repetitive block of keywords.
Prepare the sitemap and canonical URLs for the final domain. Remove staging restrictions only when the public site is ready, while keeping private review environments appropriately controlled. Search visibility can fluctuate during a migration, so monitor the relevant pages after launch. The project should include checks and ownership for that monitoring rather than a promise that no search result will ever change.
Agree technical, content and accessibility checks
Define launch acceptance criteria before the final review. Test navigation, internal links, contact routes, forms, downloads and any transaction or booking flow. Check that the correct recipient receives an enquiry and that the visitor sees a clear next step. A form that appears to submit is not enough; the full route must work.
Review readability, keyboard access, visible focus and form instructions. Meaningful images need appropriate text alternatives, while decorative visuals should not create unnecessary noise for assistive technology. The W3C forms tutorial explains practical form considerations. Accessibility review is part of making the site usable, not a separate visual style.
Check representative pages for loading and interaction problems. Large media, third-party widgets and animation can affect the experience. Use measurements to identify issues, but also complete ordinary customer tasks on real devices where possible. Record failures and retest after fixing them. This is more reliable than repeatedly running broad checks without a clear list of unresolved problems and acceptance decisions.
Plan publication, backups and rollback
Choose a launch window that gives the team time to verify the result and respond to problems. Avoid switching the site just before everyone becomes unavailable. Keep a recoverable copy of the previous site and document what must be restored if the new version has a serious issue. A rollback plan is most useful when it has been considered before an urgent decision is needed.
Write the publication steps in order. They may include uploading files, changing hosting settings, applying redirects, checking the domain and verifying essential journeys. Identify which person has access to each system. If several suppliers are involved, agree who coordinates the launch so two people do not make conflicting changes at the same time.
Keep the old and new versions clearly separated during the process. Do not overwrite the only backup with unverified files. Once the new site is live, check the public domain rather than relying on the staging preview. Confirm key pages, images and enquiry links, then review any monitoring information available. Our website launch checklist gives a more detailed handover sequence.
Review the result after customers start using it
A redesign is not fully understood on launch day. Watch how real enquiries arrive and ask the team whether they contain the information needed to respond. Check whether customers still ask questions the site was meant to answer. These observations can identify small improvements without immediately starting another major redesign.
Compare evidence with the original problem statement. If the objective was clearer service selection, review the relevance of enquiries and the paths people use. If the objective was easier editing, ask the team to complete the tasks promised during handover. Use comparable periods and acknowledge changes in traffic, campaigns or seasonality when interpreting results.
Keep a short improvement list with an owner and priority for each item. Fix broken journeys promptly, then address smaller content and usability issues in a planned order. BrandNerds can help scope a redesign through our website design services. Bring the current URL, the problems you have observed and the content you want to preserve. A useful proposal should explain how the project will improve the site and how the result will be checked.
Common questions
Should I change every URL during a redesign?
No. Keep useful URLs when they still describe the same pages. Where changes are necessary, create a deliberate mapping to relevant new destinations and test important old links. A new design does not require a completely new address structure.
Can a redesign hurt search visibility?
Changes to content, URLs, internal links and crawl access can affect search visibility. Reduce avoidable disruption through an inventory, relevant redirects, accurate metadata and post-launch monitoring. No responsible supplier can guarantee that rankings will remain unchanged throughout a migration.
When should the old website be removed?
Keep a recoverable backup before switching. The live version can change once the new site passes agreed checks and the launch process is ready. Retain the backup according to the business’s operational needs and confirm that sensitive old files are not left publicly accessible.
