WEMAIDE / WEBSITE REDESIGN CHECKLIST
Free editable checklist — 4 November 2026

Project / current URL:
Release owner:
Main visitor task:
Planned release:
For each item write: PASS / FAIL / PENDING / N/A, owner, evidence and date.
N/A needs a short reason. This is a project checklist, not a security or legal audit.

BEFORE DESIGN
[ ] Main audience, task and actual problem are written down.
[ ] Important existing URLs, downloads and useful content are inventoried.
[ ] Available search/analytics evidence is recorded with dates and limits.
[ ] Forms, business destinations, notifications and integration owners are listed.
[ ] Representative mobile pages and performance conditions are recorded.
[ ] Domain, hosting, content and editing ownership are clear.

SCOPE AND CONTENT
[ ] Refresh, redesign or rebuild is chosen for a specific reason.
[ ] Page map, representative layouts and one complete journey are approved.
[ ] Retained, changed, merged and removed material has an explicit decision.
[ ] Changed URLs have relevant destination mapping and redirect requirements.
[ ] Content, image and translation suppliers/approvers are named.
[ ] Editing workflow, first-release scope, exclusions and change process are agreed.

DESIGN AND IMPLEMENTATION
[ ] Real content works on representative desktop and narrow mobile layouts.
[ ] Important controls work with a keyboard and have visible focus and labels.
[ ] Essential information is available without hover or decorative images.
[ ] Forms have clear labels, validation and useful error/confirmation messages.
[ ] A valid test submission reaches the actual agreed business destination.
[ ] Invalid input, repeated clicks and interrupted/failed requests are checked.
[ ] Any in-scope booking/payment/account flow has its own final-state checks.
[ ] Representative pages have dated performance checks with device/network details.

PUBLIC RELEASE
[ ] Approved content/release, release owner and recovery steps are recorded.
[ ] Data/content changes during the transition have an owner and a plan.
[ ] Important public URLs return the intended pages and status codes.
[ ] Changed old URLs reach relevant new destinations without loops or error pages.
[ ] Canonicals, internal links, language alternates where applicable and sitemap agree.
[ ] Public pages have intended indexability; private pages remain restricted.
[ ] The live main journey is retested with clearly marked test data.
[ ] Notifications/records reach production destinations, not staging ones.
[ ] Analytics configuration and consent choices work as intended, without duplicate events.
[ ] Relevant Search Console/sitemap checks are performed where access is available.

AFTER LAUNCH
[ ] Early failures, missing content and redirect/indexing mistakes are reviewed.
[ ] Search/analytics comparisons use complete periods and acknowledge reporting delays.
[ ] Pending items have owners and dates; no unverified ranking gains are claimed.
[ ] Editing instructions, maintenance scope and incident contact are handed over.

ITEM RECORD — COPY AS NEEDED
Check:
Status:
Owner:
Evidence / test URL:
Test conditions and date:
Remaining action / due date:

Primary references:
https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
https://www.w3.org/WAI/tutorials/forms/
https://web.dev/articles/vitals

Full guide: https://wemaide.com/insights/website-redesign-checklist
Project brief: https://wemaide.com/resources/website-project-brief.txt
Website services: https://wemaide.com/services/website-redesign