WEBSITE STRATEGY GUIDE
Website Redesign Checklist: What to Prepare Before Launch Day
By Websites In A Day editorial team ยท Updated 6 August 2026
Before a website redesign launch day, confirm goals, audience, page structure, approved copy, brand assets, image rights, domain and hosting access, form routing, legal drafts, analytics decisions and one authorised approver. Preparation is the main protection against delay.
Business direction
Write down the primary audience, priority offer, geographic market, main conversion action and objections the site must answer. Decide what success will be measured after launch.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Content inventory
Approve the six-page mix, headings, service facts, biographies, contact details and genuine proof. Mark claims that require evidence. Do not carry inaccurate old copy into a new design.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Brand and imagery
Supply usable logo files, colours, existing guidelines and licensed images. Confirm who owns each asset and whether people shown have given the necessary permission.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Technical access
Test access to the domain registrar, DNS, current hosting, email routing, analytics, Search Console and any integrated provider before launch day. Use secure credential sharing.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Compliance decisions
Provide final legal entity details, privacy contacts, processor list, retention decisions, cookie categories and tax wording for professional review.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Approval and contingency
Name one authorised decision-maker, reserve checkpoint times and agree what happens if a dependency is unavailable. Keep a tested rollback or DNS recovery plan for migrations.
The practical test is whether this decision improves clarity for the customer and can be maintained after launch. Record assumptions, confirm ownership and avoid claims that cannot be evidenced.
Next step
Explore the six-page sprint, review regional pricing, or discuss your launch day.