Website Launch Checklist: 12 Checks Before You Go Live

Launching a website is more than publishing a homepage. A few deliberate checks can catch broken links, missing pages, domain problems, forms that do not work, and configuration issues before visitors find them. Use this list before launch and again after major changes.

1. Confirm the domain and DNS

Check that the domain is registered to the right owner, that renewal information is current, and that DNS points to the intended hosting provider. Confirm any www and non-www versions are configured deliberately.

2. Verify HTTPS

Open the live site using HTTPS and check certificate coverage for the hostnames visitors will use. Make sure HTTP requests redirect to the preferred secure version.

3. Review redirects

Test the old URLs, www version, non-www version, and important campaign links. Avoid redirect chains and loops. Use permanent redirects for URLs that have truly moved permanently.

4. Check the homepage response

Make sure the public homepage returns the expected response and that important pages are reachable. A successful homepage does not guarantee every product, form, or checkout route works.

5. Write a unique page title and description

Give each important page a clear title and a useful description that reflects the visible content. Avoid repeating the same generic title across the whole website.

6. Review headings and page content

Make sure visitors can quickly understand what the page offers. Use clear section headings, helpful explanations, and obvious next steps. Avoid placeholder text and claims that the product cannot support.

7. Test the mobile layout

Check common phone-sized layouts. Try navigation, forms, tables, and buttons. Make sure content does not overflow horizontally and important controls are easy to use.

8. Test every form and conversion path

Submit contact forms, newsletter forms, quote requests, and checkout flows using safe test procedures. Confirm that success and error messages make sense and that submissions reach the intended destination.

9. Check links and images

Open primary navigation links and calls to action. Look for broken links, missing images, oversized assets, and images with useful alternative text when they convey information.

10. Review security and privacy configuration

Review the website's headers, cookies, access protections, privacy notice, and any third-party services. A public homepage check cannot verify every application route or private workflow.

11. Set up measurement

Use an analytics platform and Google Search Console where appropriate. Define useful events such as diagnostic starts, completed scans, quote requests, signups, and completed purchases. Respect consent and applicable privacy requirements.

12. Keep a backup and rollback plan

Before major updates, confirm that a recoverable copy exists and that someone knows how to restore the previous working version. Record what changed and who can approve production changes.

Common questions

Should I submit my sitemap to Google before launch?

Make sure the sitemap is accessible and contains canonical, indexable URLs. After launch, use Google Search Console to submit it and review indexing. Submission does not guarantee that every page will be indexed.

How often should I recheck a website?

Recheck after major releases, DNS or hosting changes, security configuration changes, and important checkout or form updates. The right cadence depends on how often the site changes and how important it is to the business.

Is a website diagnostic the same as a penetration test?

No. A configuration diagnostic checks selected signals. A penetration test is a separately scoped security assessment that requires explicit authorization and a defined test plan.