Own it
Assign one accountable owner
Name who collects the inputs, resolves missing information, records decisions and keeps the resource current after the first review.
CSV template / Free resource
Website launch checklist for SEO, accessibility and conversion readiness
Download a website launch checklist covering content, technical SEO, redirects, responsive UX, accessibility, analytics, forms, performance and post-launch validation.
Download the website launch checklistNo email gate · Editable CSV · No tracking claims
Purpose
Use the file to improve the decision, not complete paperwork.
Use this checklist before and after launch to protect discoverability, usability, measurement and conversion paths. Adapt it to the platform, migration risk and legal requirements of the project.
01Content and metadata readiness
02Redirects, canonicals, robots and sitemap
03Responsive design and browser checks
04Accessibility and keyboard review
05Forms, calls, WhatsApp and success states
06Analytics, consent and event validation
07Performance and image checks
08Post-launch crawling and monitoring
Operating context
Turn a free template into a repeatable marketing habit.
A planning file becomes useful when one owner maintains it, the inputs come from real evidence and the completed resource changes a priority, campaign, page or measurement decision.
Evidence
Separate facts from assumptions
Use platform exports, customer research, website evidence and approved business information. Mark estimates so they can be validated later.
Action
End with a priority and deadline
Translate the completed template into an owner, next action, success measure and review date. Documentation should create movement.
How to use it
Four steps from template to working system.
- 01
Assign owners before launch
Separate content, development, design, analytics, SEO and business approval responsibilities.
- 02
Record evidence
Add screenshots, crawl exports, test links and acceptance notes rather than relying on memory.
- 03
Test real journeys
Use mobile, keyboard and representative devices to complete navigation, contact and purchase or booking paths.
- 04
Repeat after release
Crawl the production site, confirm redirects and indexability, validate events and monitor important pages.
Working guidance
Use the template with context, evidence and ownership.
Open each note when that decision becomes relevant. The complete guidance remains available without turning the page into a wall of copy.
01Protect existing search equity
Inventory valuable URLs before migration, map changed paths to the closest relevant destination and preserve canonical intent, internal links and indexability. Avoid sending every removed page to the homepage or relying on a sitemap to replace redirects.
02Test complete user journeys
Check navigation, search, forms, calls, messaging links, checkout or booking flows and their success states on representative devices. Include error handling, keyboard use, zoom and slow-network conditions rather than reviewing screenshots alone.
03Validate measurement responsibly
Confirm the consent state, tag firing conditions, event names, duplicate controls and conversion definitions in production. Test whether the receiving analytics and advertising systems record the intended action without exposing secrets or personal information.
04Monitor after release
A successful deployment is the beginning of validation. Crawl the live site, inspect redirects and canonical tags, submit or confirm the sitemap, watch important templates and compare search, behaviour and conversion signals with the documented baseline. Keep the evidence with the release record so later changes can be compared against an agreed starting point.
Resource questions
Scope, use and validation, answered.
01When should launch QA begin?
Acceptance criteria should be defined during planning and checked throughout implementation. Leaving content, accessibility, search and analytics review until the final hour creates avoidable risk.
02Which screen sizes should be tested?
Test representative small mobile, large mobile, tablet, laptop and desktop widths, plus real devices when possible. Check wrapping, touch targets, navigation, image crops, forms and horizontal overflow.
03What should happen if a critical check fails?
Record the issue, affected journey, severity, owner and retest condition. Delay the release when the failure threatens access, payments, enquiries, indexability, security, privacy or reliable measurement.
04What should be checked immediately after deployment?
Confirm HTTPS and the canonical host, redirects, robots rules, sitemap, important pages, structured data, contact or purchase journeys, analytics events, console errors and monitoring before announcing the release.
Download and continue