A successful website launch is more than publishing files or changing nameservers. This website launch checklist helps you verify the domain, DNS, hosting, security, email, analytics, accessibility, performance, backups, and monitoring before and after go-live. Use it for a new site, redesign, staging-to-production release, domain change, or recurring launch audit.
Overview
A launch is a controlled change to a system that visitors, customers, search engines, and internal teams rely on. The work is easier to manage when it is divided into checkpoints rather than treated as one final publish button.
Assign an owner and deadline to every important task. A simple tracker can include these columns: item, owner, environment, status, evidence, deadline, and rollback action. “Complete” should mean that someone has tested the item and recorded what they found, not merely that a setting appears to be enabled.
For small teams, keep one launch document with the production domain, hosting account, DNS provider, registrar, deployment method, email provider, analytics property, backup location, and emergency contacts. Store credentials in an appropriate password manager rather than in the checklist. If the project includes a domain transfer, review the domain transfer checklist separately because registrar changes can affect DNS, renewal, and email dependencies.
What to track
1. Domain, DNS, and hosting readiness
- Confirm the intended production domain, preferred hostname, and redirect policy. Decide whether both the root domain and
wwwshould work, and make the chosen version canonical. - Verify that the domain is registered to the correct account, has current contact information, and is set to renew according to the organization’s documented policy.
- Record the authoritative nameservers and DNS provider. Check A, AAAA, CNAME, MX, TXT, and any required verification records against the approved zone plan.
- Confirm that the hosting environment has the correct application version, environment variables, database connection, storage permissions, and resource allocation.
- Verify that the production deployment does not rely on staging URLs, test API keys, debug settings, temporary redirects, or blocked assets.
- Confirm that a rollback package or previous deployment is available and that someone knows how to use it.
Use a DNS record reference when checking the zone rather than editing records from memory. The DNS records cheat sheet can help organize website, application, and email entries. DNS changes may not appear everywhere immediately, so record the change time and allow for resolver caching while testing.
2. Content and functional checks
- Review page titles, headings, navigation labels, contact details, pricing or service descriptions, and calls to action.
- Test every important form, including validation, success messages, email notifications, spam controls, and storage of submissions.
- Test account creation, sign-in, password recovery, checkout, search, filters, downloads, and other workflows that matter to the site’s purpose.
- Check internal links, redirects, images, videos, PDFs, favicons, social previews, and error pages.
- Confirm that staging-only content, placeholder copy, sample users, comments, and test orders are removed from production.
- Test with realistic permissions: anonymous visitor, standard user, editor, administrator, and any relevant API client.
Run these checks on the production URL or a production-like environment. A page that works on a developer’s machine may still fail because of DNS, TLS, caching, permissions, build configuration, or third-party settings.
3. Accessibility, compatibility, and performance
Check keyboard navigation, visible focus, form labels, heading order, link purpose, color contrast, alternative text, and useful error messages. Confirm that the site remains understandable when images are unavailable and that interactive controls are usable without a mouse.
Test current, commonly used browsers and representative mobile and desktop screen sizes. Focus on the workflows that generate value, not only the homepage. For performance, check server response, large images, font loading, scripts, caching, layout movement, and slow network conditions. Treat automated audits as evidence for investigation, not as a substitute for manual testing.
4. SSL, privacy, analytics, and email
- Open HTTP and HTTPS versions and confirm the intended redirect behavior. Check the certificate, hostname coverage, mixed content, and renewal ownership.
- Verify that analytics loads only as intended, records the correct property or data stream, and does not count internal testing as ordinary traffic.
- Test important conversion events, campaign parameters, consent behavior where applicable, and the privacy notice or preference controls used by the site.
- Confirm that transactional and business email can send and receive. Check MX, SPF, DKIM, DMARC, and any provider-specific verification records.
- Test forms from an external mailbox and confirm that replies go to a monitored address. Do not assume that website email works merely because DNS looks complete.
For a deeper email review, use the email DNS setup guide. For HTTPS checks and renewal ownership, see the SSL certificate renewal and HTTPS audit guide.
5. Search visibility and recovery
- Confirm that production pages do not carry accidental
noindexdirectives or staging-only robots rules. - Check the XML sitemap, canonical URLs, redirects, structured content where used, and links to the preferred domain version.
- Verify the search property or webmaster account and record who can access it.
- Confirm that backups run, complete, and can be located. A backup is more useful when the team knows what it contains, how long it is retained, and how restoration would be requested or performed.
- Document the rollback path, DNS rollback plan, hosting access, and escalation contacts.
Cadence and checkpoints
Use a staged schedule to reduce last-minute decisions.
Before the release
Several days before launch, freeze major content and code changes where practical. Complete the domain and hosting inventory, test the release candidate, confirm backups, check integrations, and assign a go-live owner. Lowering DNS TTL before a planned cutover may be considered when appropriate, but record the previous value and understand that resolver behavior can vary.
At DNS cutover or deployment
Record the exact time of the deployment and any DNS edits. Publish the approved build, apply migrations carefully, verify the health check, and test the production domain from more than one network. Check both the preferred hostname and its redirects. Watch logs for application errors, failed requests, authentication problems, and unexpected traffic patterns.
Immediately after launch
Repeat the critical visitor journeys: open the homepage, browse key pages, submit a form, complete a representative transaction, send and receive email, and confirm analytics activity. Check the status page or monitoring panel, hosting resource use, certificate status, and error logs. Keep the old environment available until the team has enough evidence that rollback is unlikely to be needed.
After one day and one week
Review broken links, search crawl reports, form delivery, analytics events, support questions, uptime alerts, server capacity, and backup completion. Compare results with the expected baseline rather than relying on a single metric. Record defects and decide whether each requires an immediate fix, a scheduled task, or no action.
Monthly or quarterly
Run a lighter operational audit. Check domain renewal settings, DNS records, certificate renewal, administrator access, software updates, backups, monitoring alerts, email authentication, analytics configuration, and the accuracy of the launch documentation. A small domain portfolio may need a quarterly review; a frequently changing application may justify monthly checks or automated monitoring.
How to interpret changes
Not every change indicates a launch failure. First identify what changed and when: deployment, DNS edit, certificate renewal, analytics release, content update, provider change, or traffic variation. Then separate the symptom from the affected path. A drop in analytics may be tracking-related, while a drop in completed forms may indicate an application, email, or user-experience problem.
Compare several signals together. For example, rising server errors plus failed checkout requests is more urgent than a small change in page views alone. A domain that resolves from one network but not another may involve caching or propagation rather than an incorrect application build. An email delivery problem should be checked against MX, SPF, DKIM, DMARC, provider logs, and the recipient’s bounce message.
Use severity categories to make decisions:
- Blocker: visitors cannot reach the site, a critical workflow fails, data is at risk, or the rollback path is unclear.
- High priority: an important audience, device, form, integration, or email flow is impaired.
- Routine: a non-critical layout issue, content correction, documentation gap, or optimization opportunity.
Preserve evidence before changing several variables at once. Save timestamps, screenshots, request IDs, DNS results, error messages, and deployment identifiers. This makes the next diagnosis faster and prevents a temporary fix from becoming an undocumented dependency.
When to revisit
Reopen this website launch checklist whenever a new domain is registered, nameservers change, hosting is migrated, a major redesign ships, a staging environment becomes production, or an email or analytics provider is replaced. Also revisit it after a security incident, failed deployment, unexpected traffic increase, certificate problem, or backup restoration.
For a recurring review, schedule a monthly or quarterly calendar task with these actions:
- Confirm the domain, registrar, DNS provider, hosting account, and responsible owners.
- Check DNS records, HTTPS, redirects, forms, email authentication, analytics, and monitoring.
- Verify recent backup completion and document a restoration test or evidence of recovery readiness.
- Review errors, performance trends, search visibility, accessibility issues, and support feedback.
- Update the launch document, remove obsolete instructions, and assign deadlines for unresolved work.
Keep the checklist versioned so the team can see what changed between audits. For related operational reviews, consult the domain portfolio management checklist, the domain renewal guide, or the cloud server deployment checklist. The practical goal is not to create paperwork around a launch; it is to make ownership, evidence, recovery, and follow-up visible every time the website changes.