Website Redesign Requirements Checklist

A website redesign requirements checklist captures the design you want, the information customers need and the actions the website should support. Use it to turn your business goals into a clear brief you can build and review.

Use this checklist for your own website or a client project. Mark each item as confirmed, open or planned for later.

Business and visitor needs

Name the main audiences and what each needs from the website.
Choose the important actions: enquire, book, buy, join, apply or another clear outcome.
Record what works on the existing site and should stay.
Explain what visitors currently struggle to find or complete.
Separate essential launch needs from later improvements.

Pages and content

List existing pages and the intended action for each: keep, update, combine or remove.
List genuinely missing pages and their purpose.
Record the address each page should use.
Identify who supplies and approves service details, prices, images and customer evidence.
Include required languages and who checks translated content.
Include navigation, footer links and relevant policy pages.

Use the content inventory template to keep these decisions in one place.

Design and editing

Provide the brand materials you want to retain.
Attach reference images or websites and explain what you like about them.
Describe the visual qualities you want, such as spacious layouts, prominent photography or a more refined use of color.
Identify everyday edits you want to make yourself, such as changing a service description or replacing a photograph.
Identify the pages and journeys to review on a phone.
Decide who gives consolidated feedback and final approval.
Agree on the intended direction before extending it to the remaining pages.

In Revamp, you can refine the design through conversation or direct visual editing. Your requirements should describe the result, not require the customer to choose technical implementation details.

Working features

Define the steps for each booking, purchase, enquiry or application.
Specify what information is needed at each step.
Explain which customers or team members need accounts and what they can do.
Identify confirmation messages and emails.
Describe the management area the business needs on its website.
Include how to handle unavailable appointments, incomplete submissions or cancelled actions.

A booking requirement might read:

Visitors choose one of our three locations, see the services available there and book a time. The location team can review and manage its bookings.

Existing information and connected tools

List where existing content and business information live.
Confirm permission to import the files or connect the accounts.
Identify which information is a one-time import and which should stay connected.
Record the business tools involved and the result expected from each connection.
Decide which system remains the source of current information.
Identify sensitive information that needs a specific handling review.

Bring existing files, images or source code into Revamp, and connect the tools that hold your business information. Specify what should appear publicly and what belongs in a private area, using authorized access for information beyond the public website.

Search and launch

Review useful existing URLs before changing them.
Record relevant redirects for moved or combined pages.
Check titles, descriptions, headings and important internal links.
Review SEO issues and planned fixes.
Confirm who can connect the domain and who approves publishing.
Test the important visitor journeys in preview.
Agree on who checks the website after publication.

Turn requirements into acceptance checks

Requirement	How to check it
Visitors can request a consultation	Complete a test request and check it reaches the intended destination
Customers can book by location	Try the flow for each location and confirm the correct service choices
Important old pages remain reachable	Visit the retained addresses and any planned redirects
The team can update service content	Make a change in preview, review it and confirm the publishing process
The website supports two languages	Review navigation and representative pages in both languages

Build from the checklist in Revamp

Start from your URL, refine the first design and ask Revamp to build the pages and working features in your checklist. Import relevant information and share the preview for review.

Publish when the agreed requirements are met. Later additions stay in preview until ready; you can keep evolving the website in the same project.

Start a redesign or explore Revamp for agencies for client delivery.

Frequently asked questions

Does everything need to be decided before starting?

No. Confirm the important goals and constraints first, then record open decisions as you work. A preview often makes design and workflow decisions easier.

Does every new idea need to wait for another redesign?

No. You can add pages and features later in the same Revamp project. For client work, agree whether an addition belongs to the current service scope or a later phase.

Is this a technical specification?

It is an outcome-focused requirements checklist. It helps people agree on what the website needs without requiring the business owner to write technical instructions.