Website Redesign Checklist: Planning Your Project

A website redesign is more than a visual refresh: it can change how customers find information, contact you and complete important tasks. A clear checklist helps a small business make decisions in the right order, avoid losing useful content and spot risks before the new site goes live. Start by defining what is not working and what the redesigned website must help people do. Then review existing pages, traffic and search visibility; decide what to keep, improve, combine or retire; and agree the design, functionality, budget and responsibilities. Treat redirects, analytics, accessibility, mobile checks and backups as part of the project rather than last-minute extras. The right scope depends on your current website, business priorities and available time. A modest refresh may need careful content and usability work, while a rebuild can involve platform choices, integrations and a more detailed migration plan. Use the checklist below to guide discussions with your team or web partner. Record decisions, owners and approval dates so the project has a shared reference from planning through launch.

Content

Set project goals

Set project goals

A website redesign is easier to manage when the business knows what it needs the new site to do. Before discussing layouts or features, agree on the priorities the project must serve. These might include helping people understand your services, making it simpler to enquire, supporting online bookings, or making important information easier to find. Choose a small number of priorities so decisions stay focused when trade-offs arise.

Start by describing the problem, not the proposed solution. For example, “customers often call to ask what our service includes” identifies a communication issue; “we need a new home page” is one possible response, not yet a goal. Note who experiences the problem, where it occurs and what a better experience would look like. This gives your designer or developer useful context and leaves room to consider the right content, navigation or functionality.

Define priorities around real audience needs

Identify the main groups of people the site needs to serve. Keep this practical: consider existing customers, prospective customers, referral partners or job applicants, if those groups are relevant to your business. For each group, write down what they are trying to do, what information they need to decide or act, and what might prevent them from doing so. Use evidence you already have, such as questions staff hear, feedback from customers, common enquiry topics or support requests. Avoid relying only on assumptions about what visitors want.

Then rank needs against business importance. A redesign may have several worthwhile aims, but they will not all carry equal weight. Decide which user journeys are essential and which can be improved later. If a new feature is suggested, ask which goal it supports, who will use it and who will maintain its content or settings. This helps prevent the scope growing through additions that sound attractive but do not solve a clear business or audience problem.

Write each priority as an outcome that can guide a decision. “Make it easier for prospective clients to enquire about the right service” is more useful than “make the site modern”. You can still discuss visual direction later, but it should support the agreed outcome rather than replace it. Record any constraints alongside the priorities, such as staff capacity to update pages, approval processes, required accessibility considerations or a fixed launch deadline. These can affect what is realistic within the project.

Choose practical measures

For each goal, choose a measure that can help you assess progress. Depending on the goal, this could include completed enquiry forms, booking requests, visits to a key service page, use of a specified contact method, or feedback from staff about recurring customer questions. Measures should relate to the outcome, not simply be numbers that are easy to collect. A rise in overall visits, for instance, does not by itself show that the site is helping the right people take the right next step.

Before launch, record what information is available and how it is collected. If a measure depends on analytics or form tracking, confirm who will check it and whether the data is reliable enough for comparison. Where no useful baseline exists, note that plainly and begin collecting consistent information when appropriate. Set a review date after launch and treat early findings as guidance, not proof that the redesign alone caused a change. A shared goals document with priorities, audience needs, measures, constraints and an owner for each decision will give the project a clear reference point.

Audit the current site

Build an evidence-based picture of the site

Before deciding what the redesigned website should look like, work out what the current one already does well and where it creates problems. Set aside time to review the site as a business owner and as a customer. Keep a simple inventory of pages and features, and record a proposed action for each: retain, improve, combine or remove. Add a reason and, where possible, evidence to support each decision. This makes it easier to distinguish genuine priorities from personal preferences.

Start with the main pages: the homepage, service or product pages, about page, contact details, FAQs and any important landing pages. Check whether the information is accurate, current and easy to understand. Look for outdated prices or opening hours, duplicate explanations, unclear calls to action and pages that no longer reflect the business. Check images, downloadable documents and links too. If a page answers a common customer question or supports an important enquiry, note what should be preserved even if its wording or layout needs work.

Check how the site works and performs

Test the functionality that customers and staff rely on. Submit enquiry forms and confirm where submissions go; test phone and email links, booking steps, search, menus, account areas and payment flows if relevant. Check these tasks on a phone as well as a computer. Record the exact steps that fail or cause confusion, rather than writing only “the site is difficult to use”. Also ask the people who handle enquiries which website questions they repeatedly need to clarify. Their experience can reveal gaps that analytics will not show.

Review search visibility before removing or substantially changing pages. Note which pages appear for relevant searches, attract visits from search engines or earn links from other websites. Search Console can help identify queries, indexed pages and reported technical issues; an analytics platform can show traffic and what visitors do after arriving. Use the tools already available, and confirm that tracking is installed and collecting data before relying on it. A short or missing data history is not proof that a page has no value. Consider seasonality, campaign periods and changes in tracking when interpreting trends.

Look beyond total visits. Compare useful actions, such as completed enquiries or booking steps, with visits to the relevant pages. Check whether visitors reach key information, where they leave a process, and whether a page brings in relevant search traffic. Treat these figures as clues to investigate, not automatic instructions to delete or keep a page. If tracking is incomplete, note the limitation and use customer feedback, enquiry records or staff observations alongside it.

Finish the audit by grouping findings into decisions. Retain pages and features that remain accurate and useful; improve those with a clear purpose but weak content, usability or performance; combine overlapping material where it helps customers; and consider removing obsolete items only after checking their audience, search value and dependencies. Record questions that need further investigation and assign someone to resolve them. This audit gives the redesign team a practical starting point and helps ensure the new site carries forward valuable content and customer journeys instead of recreating the same problems.

Plan content and search

Plan content and search

Before approving new page designs, decide what the site needs to say and how visitors will find it. Use the current-site audit to build a content inventory: record each page’s URL, purpose, intended audience, key information, and whether it should be kept, updated, combined or removed. Include useful downloads, location pages and frequently asked questions, not just top-level pages. This makes gaps and duplication easier to spot and helps prevent valuable information from disappearing during the redesign.

Next, sketch the proposed page structure. Group related services and information under labels that make sense to customers, then check that important pages are reachable through clear navigation and relevant links from other pages. A small business may need a simpler structure than its current site, but do not merge pages just to reduce the page count if they answer different customer questions. For each planned page, note its main purpose, the information it must contain and the next useful action for a visitor. This brief gives the writer and designer a shared reference point.

Treat URL decisions as part of that structure, not as a task to leave until launch. Keep existing URLs where they remain suitable; where a URL must change, record the old and new addresses in a redirect map. Map each retired page to its closest relevant replacement rather than sending every old address to the homepage. Hypothetical: If /services/physio/ becomes /physiotherapy/, map the old URL to its closest replacement and update internal links. Check the map for missing pages, accidental loops and destinations that do not match the original page’s purpose. A redirect helps visitors and search engines reach the replacement, but it does not guarantee that search visibility will remain unchanged.

Review page titles and meta descriptions alongside the content plan. Give each important page a distinct, accurate title that describes its topic and, where useful, the business or service area. Write a concise description that reflects what the page actually offers; avoid repeating the same wording across the whole site or promising information the page does not provide. These details support clear presentation in search results, but search engines may choose how to display them. Also identify any page whose purpose or content is changing substantially so its title, description and on-page headings can be reviewed together rather than copied over by default.

Finally, plan internal links as part of the visitor journey. Link related pages using descriptive wording, and update links in menus, service pages, articles and calls to action when URLs change. Do not rely on redirects to compensate for links that still point to old addresses. Before launch, compare the finished page list with the inventory and redirect map, check that important pages are indexable as intended, and test links on the live site. Keep the documents shared with the project team, name an owner for each review, and revisit them if the scope changes. That preparation gives the launch team a practical way to catch omissions and preserve useful content and search signals where possible.

Agree design, features and budget

Turn priorities into an agreed scope

Before approving a redesign, agree which tasks the new website must make easier for visitors. Write down the main user journeys, such as finding a service, comparing options, booking an appointment or contacting your business. For each journey, note the pages and actions a person needs to complete it. This gives design and development decisions a practical purpose, rather than relying on preferences such as a particular colour or layout.

Next, separate requirements into “essential for launch”, “useful if budget allows” and “possible later”. Be specific about features: instead of requesting “better enquiries”, define whether visitors need a contact form, a phone number that works on mobile, or both. Record any rules that affect the feature, such as what information a form should collect, who receives submissions and what happens after someone sends one. This helps avoid misunderstandings and makes trade-offs easier.

Check that each proposed feature supports a user journey or a genuine business need. Consider the effort involved in adding and maintaining it, not only its initial appeal. A booking tool, searchable directory or connection to another business system may involve configuration, data handling or ongoing fees. Ask the project team to identify dependencies and explain what is included in the proposed work. If a requirement is uncertain, list it as an open decision rather than treating it as agreed.

Make platform, responsibilities and costs explicit

Confirm the platform and technical arrangements needed for the agreed scope. Review whether the current content management system, hosting setup and existing integrations can support the requirements, or whether a change needs investigating. Consider practical needs such as who will update pages, whether staff need training, and how the site will be maintained after launch. Ask for relevant limitations, assumptions and ongoing obligations to be documented; do not assume a proposed feature or integration is included until it is specified.

Name an owner for each part of the project. Your business may need to supply approved copy, images, service details, staff availability or access to existing tools. The project team may handle design, development, content migration or testing, but responsibilities vary, so confirm them in writing. Also identify who can make decisions and approve work, and how quickly they are expected to respond. Unclear ownership can delay decisions or leave essential launch tasks unfinished.

Ask for a cost breakdown that matches the scope, including any discovery or planning, design, development, content work, migration, testing and launch support that apply. Check which costs are one-off and which may recur, such as hosting, software licences or maintenance. Set a budget limit and discuss what would be removed or deferred if estimates exceed it. Avoid approving a total without understanding the assumptions behind it, what is excluded and how requests for additional work will be assessed.

Before work begins, capture the agreed pages, features, platform decisions, responsibilities, costs, exclusions and approval process in one scope document. Include how completion will be checked—for example, whether specified forms, navigation and page templates work as agreed. Review the document with everyone who needs to contribute, resolve outstanding decisions where possible, and record any that remain open with an owner and due date. Approve the scope only when the people responsible understand what they are committing to deliver or provide.

Prepare for migration and launch

Build a launch plan before migration

Treat launch as a controlled change, not simply the moment the new design goes live. Agree the migration date, who can approve it and how the team will communicate if something needs attention. Choose a quieter period for the business where practical, and allow time afterwards to check key pages and respond to issues. Document the current site’s important URLs, features and tracking arrangements before work begins; this gives you a reference for checking the new site.

Arrange a fresh backup of the existing website before migration, including its database and files, and confirm who can access it. Ask the person responsible for the website or hosting to explain how restoration would work and how long it may take. Where possible, verify that the backup can be restored in a safe environment rather than assuming that a completed backup is usable. Take another backup immediately before launch if the site has changed during the project. Keep access details secure and make sure the relevant owner knows where they are held.

Use a staging site to review the new website before it replaces the live one. Check that it is not publicly indexed or readily accessible to visitors while unfinished, using appropriate access controls and search-engine settings. Test the actual content and functions there, including navigation, forms, downloads, booking or payment steps if relevant. Record defects with the page address, what happened, the expected behaviour and a screenshot where useful. Agree which issues must be resolved before launch and which minor improvements can be scheduled afterwards.

Prepare a redirect map for every old URL that will change or disappear. Send each old address to its closest relevant replacement, not automatically to the home page, and update links within the new site so they point directly to the new addresses. Include important pages, campaign links and files, then test the redirects after launch for incorrect destinations, loops and errors. Keep the map as a project record so the team can investigate reports and refine it as needed.

Decide how tracking will be checked before launch. Record which analytics or measurement tools are currently in use, who has access and which key actions matter to the business, such as a form submission or completed booking. Confirm that the agreed tracking is present on the new site and test those actions without counting test activity as genuine business data where possible. If consent requirements apply to the site’s tracking, include the consent experience in the checks and involve the appropriate adviser if you are unsure what is required.

Test across common device sizes and more than one browser: use a phone, tablet and desktop where available, and check both narrow and wide screens. Prioritise practical tasks: can visitors read the text, open the menu, tap buttons, complete forms and reach contact details? Check images, page layouts, links, error messages and keyboard use as well. Do not rely only on a staging preview or a single person’s device; ask another team member to complete the main visitor journeys and report what is confusing or broken.

Name an owner for each launch check and for handling issues. For example, the business owner can approve content and confirm contact details, while the web professional can coordinate the migration and investigate technical faults; assign roles to the people actually involved. Set one reporting channel and a simple priority system: issues that prevent customers contacting or buying need immediate attention, while cosmetic defects can be logged for review. Agree who decides whether to pause or reverse a launch, and what evidence they need to make that call. After launch, check the live site, redirects, tracking and priority user journeys, then keep a dated issue log until outstanding work is resolved.

Conclusion: Keep the checklist live

Keep the checklist live

Treat the checklist as a working project record, not a document to file away once the scope is approved. Keep a shared decision log that records each important choice, who approved it, why it was made and whether it is still open. When priorities or requirements change, note the decision and its effect on timing, content or responsibilities so the team is working from the same version.

Give every outstanding task a named owner and a due date. Before launch, use the log to confirm that agreed checks have been completed and that unresolved issues have a clear next step. After launch, set a date for an initial review and assign someone to gather feedback, check key user journeys and compare the live site with the project’s original goals. Record what needs attention, who will handle it and when it will be revisited. This makes follow-through visible and helps prevent useful decisions from being lost during handover.

Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.

Let’s talk websites.

DIGITALON’s in-house team in Wurtulla on the Sunshine Coast designs, builds and supports WordPress and eCommerce websites for businesses across Australia. Tell us what you want your website to do, and we’ll help you work out the next step.

How may we assist you?

Contact

Or, call us now