Website Cost Calculator
Checklist • Website Planning
Website Redesign Checklist
A practical website redesign checklist covering strategy, UX, content, SEO, accessibility, development, migration, launch and measurement.
Use this Resource
How to use it
A redesign is easier to manage when the important decisions are visible before launch week.
Use this checklist as a working review across strategy, content, SEO, design and development. The point is not to create more documentation. It is to make ownership, risk and success criteria explicit before the project becomes expensive to change.
Business goals & measurement
- Write the business problem the redesign should improve in one sentence.
- Define the primary audiences and the highest-value website actions for each.
- Record the current baseline for enquiries, purchases, bookings or other key events.
- Decide which GA4 events and Search Console views will be reviewed after launch.
- Agree on the first 30-, 60- and 90-day post-launch review points.
Information architecture & UX
- Inventory the current pages before deciding the new sitemap.
- Identify journeys that are currently duplicated, confusing or unnecessarily long.
- Give every important page one dominant job and a clear next action.
- Confirm navigation labels use customer language rather than internal department language.
- Review mobile journeys independently instead of assuming desktop layouts simply stack.
Content & trust
- Assign an owner and approval deadline for each page's copy.
- Identify proof that supports each high-value decision: case studies, reviews, qualifications or data.
- Remove repeated company copy that can live on a more relevant page.
- Plan image ownership, alt text and any downloadable assets.
- Confirm legal, compliance or accessibility requirements that affect content.
SEO & URL migration
- Export the current URL list and identify organic landing pages worth protecting.
- Map every changed or removed URL to the most relevant new destination.
- Prepare permanent redirects before launch rather than after traffic drops.
- Review page titles, headings, internal links and crawlable navigation.
- Keep the XML sitemap aligned with the final canonical URLs.
Development & performance
- Define which content the internal team must be able to edit without a developer.
- Test forms, CRM connections, email notifications and third-party integrations.
- Review Core Web Vitals and the biggest performance bottlenecks on real templates.
- Avoid unnecessary scripts, oversized media and layout movement.
- Check keyboard navigation, focus states, labels and form feedback.
QA & launch
- Test priority templates across current mobile, tablet and desktop breakpoints.
- Crawl the staging site for broken internal links and missing metadata.
- Verify analytics, key events and consent behavior before opening the site to users.
- Test redirect mappings against a saved list of old URLs.
- Make sure development noindex or crawl-blocking rules are removed at launch.
Post-launch review
- Monitor Search Console coverage, clicks and priority landing pages after launch.
- Review forms and integrations using real submissions.
- Compare performance by device and template—not only the site-wide average.
- Log unexpected user behavior as hypotheses rather than immediately redesigning again.
- Build the first optimization backlog from real post-launch evidence.
Research references
Need help applying it?
Explore Antibe Services
Use the resource to get clearer. Use us when you are ready to turn the decisions into the actual website.
The resource should expose the important questions before the work becomes a list of disconnected tasks.
Ready to move from planning to execution?