Get a Proposal
Business & IP Insights

Website Redesign Checklist: Evidence Before Launch

A DIFFERENT WAY TO EXPLORE

Summarize this page with AI

Opens your chosen AI service with this public page’s link. Sign-in may be required; summaries can contain errors.

A website redesign checklist should help a business decide whether a changed site is ready for use. A polished homepage is one review item; the release decision also needs a record of the content, journeys and operating responsibilities that have been checked. For a professional-services firm, start with the paths a prospective client and an existing client actually need.

Use the acceptance worksheet below to connect each requirement to a test, evidence and a decision owner. It is an original planning tool, not an official standard, a certification or a promise of search performance. Adapt it to the agreed project scope rather than assuming every redesign needs a platform migration.

1. Write the release question before approving the design

Describe the change in one sentence: for example, reorganise service information while retaining the current publishing platform. Identify the business owner, content reviewer and technical release owner. Give each person a decision to make and a dated version to review. Avoid an approval such as looks good that leaves everyone uncertain about whether forms, content and integrations were included.

Keep a short boundary list: included templates, required content, external systems, excluded changes and unresolved decisions. A fictional firm might include its service pages and enquiry form but defer its client portal. Recording that exclusion is clearer than presenting the portal as tested simply because the public website passed review.

2. Preserve the useful content and URL record

Build an inventory of important pages, documents and images before restructuring navigation. Record the current URL, intended destination, content owner and proposed action. Keep useful working URLs where the project permits; a new visual style is not, by itself, a reason to rename every page. Review merged or removed material individually rather than redirecting every old address to the homepage.

When URLs will change, Google’s site-move guidance describes preparing a URL mapping, testing the destination and redirecting old URLs to appropriate new ones. It also recommends separating major changes where practical and monitoring the move. Use the guidance for the actual change type: a design update with unchanged URLs is different from a domain move. Link: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

Give each changed destination an acceptance record: expected response, final address, relevant content and reviewer. Ask the technical owner to check internal links, canonical signals, indexing instructions and sitemap entries against the approved plan. Do not describe a migration as complete merely because the homepage loads.

3. Review journeys with real content and input methods

Select representative journeys rather than reviewing screenshots alone. For a fictional advisory firm, the journey might be service page to enquiry confirmation, followed by delivery to the designated test inbox. Include navigation, a long page, a document download and an error state if those are in scope. Use approved test data and a test route; do not send real customer records through a trial submission.

W3C’s Easy Checks covers an initial review of page titles, image alternatives, headings, contrast, text resizing, keyboard interaction and form labels, among other topics. W3C expressly describes these checks as a first review, not a comprehensive accessibility evaluation. Use them to identify issues and define any deeper assessment needed: https://www.w3.org/WAI/test-evaluate/preliminary/

On a narrow phone viewport, read the actual headings, button labels and form instructions. Check whether fixed bars or chat controls conceal important content. Record the viewport and browser used. Separately try keyboard navigation and visible focus on the desktop layout. A single passing device should not be recorded as proof that every browser and assistive technology works.

4. Use a six-field acceptance worksheet

Create one row for each meaningful requirement with six fields: requirement and owner; page or journey; expected result; test conditions; evidence and finding; release decision. The first field identifies who may accept the work. Test conditions should include the relevant device or viewport, account state and test-data arrangement so that another reviewer can repeat the check.

For example, a fictional row could say: marketing owner; mobile service enquiry; required fields have clear labels and a valid test enquiry reaches the agreed test inbox; narrow viewport and logged-out session; dated capture plus receipt reference; accepted by the named reviewer. The receipt is evidence of that controlled test, not a claim that every future message will arrive or become a qualified lead.

Another row could cover a renamed service URL: technical owner; old address to approved destination; expected redirect and relevant destination content; logged-out request; saved response and final URL; accepted or held. Keep this separate from a visual-design row so that an attractive page cannot conceal an unresolved destination problem. These examples illustrate the worksheet, not Menteso client work.

5. Make launch and recovery responsibilities explicit

Record who can release the site, who can stop the release and who owns each unresolved issue. Agree which failures must block launch and which may be accepted with a dated remedy. Keep the decision visible to the business owner; a developer’s completed task count is not the same as the owner’s release acceptance.

For a WordPress site, the official backup handbook distinguishes the database from the site’s files and explains that both are needed to restore a typical site. Ask the responsible operator to identify the backup set and recovery procedure appropriate to the environment: https://developer.wordpress.org/advanced-administration/security/backup/

Record where the recovery instructions are available to authorised operators and how a restore has been checked in an appropriate environment. Do not put passwords or confidential customer information in the public acceptance worksheet. For the launch window, name contacts for publishing, hosting, forms and connected systems instead of assuming the website supplier controls them all.

6. Close the release, then review the live result

At release, keep the accepted version, test evidence, outstanding issues and handover notes together. Repeat the agreed essential checks against the public site and record the time. Compare the result with the approved baseline, preserving any uncertainty rather than marking an untested integration complete. Continue with a short post-launch review of errors, enquiries and search reporting on consistent periods.

Google’s guidance warns that rankings can fluctuate during a site move. A short observation window is therefore not evidence of a guaranteed gain or permanent loss. Keep traffic measures separate from qualified enquiries and investigate unexpected changes before attributing them to the redesign.

Prepare a scoped redesign discussion

Use the worksheet to identify what you need to preserve, improve and verify. For service scope, see https://menteso.com/web-design-development/website-redesign/ ; for an actual platform or URL move, review https://menteso.com/web-design-development/website-migration/ . The delivery stages at https://menteso.com/web-design-development/our-process/ provide a separate process overview. Start a discussion with the current website, intended audience, priority journeys and known constraints; confirm responsibilities and acceptance evidence in the proposal.

MAKE THIS PRACTICAL

Bring these to your scoping conversation

  1. The business question and the decision you need to make
  2. Your existing information, priorities and constraints
  3. The scope and specialist support you want to discuss

A starting brief helps the right specialist understand your needs. Confirm the scope and professional review required for your project.

YOUR NEXT STEP

Put this guide to work.

Explore the wider business context. Bring your questions and project requirements to a focused discussion with our team.

Discuss your project → Explore services
TURN KNOWLEDGE INTO PROGRESS

Let’s move your project forward.

Explore the wider business context. Tell us your scope, priorities and timeline so we can discuss a practical next step.

Explore relevant services →
  • Discuss the support you need
  • Define scope and review responsibilities
  • Agree on a proposal before starting

Please keep the first message general. Ask us about a suitable channel before sharing confidential material.

Tell us about your project

LET’S GET STARTED

What can we help you achieve?

Share a few details. We’ll take it from here.

Your enquiry goes to the Menteso team. Privacy policy