New Website Launch Checklist: 30 Practical Points
Launching a new website without a checklist is how small mistakes become expensive problems. In SEO, analytics, and site performance, the costly errors are often boring ones: a missed redirect, a stray noindex, a broken form, a missing measurement tag.
This checklist is built for real teams with limited time. Not enterprise launch squads. Not perfect theoretical workflows. Just the practical checks that stop a good launch from turning into a cleanup project.
How to use this checklist
Treat it as a pre-launch and post-launch sequence.
If time is tight, the bare minimum is:
- indexation,
- canonical setup,
- forms and conversions,
- analytics,
- and mobile performance.
Pre-launch checks
1. Confirm the canonical domain
Pick the main version of the domain from day one.
You do not want Google seeing mixed versions of:
- HTTP and HTTPS,
wwwand non-www,- or old domains left half alive.
2. Check HTTPS properly
Make sure the certificate is valid and the site is free from mixed-content issues.
If you want a fast check, use the SSL certificate checker.
3. Validate redirects
Confirm that old URLs, preferred domain versions, and legacy paths resolve cleanly. Redirection mistakes are one of the fastest ways to waste authority after a relaunch.
4. Review robots.txt
This is where staging leftovers still break real launches.
If your team is not comfortable reading the file, use this guide on how to read robots.txt for SEO.
5. Check meta robots
Important pages should not be carrying noindex or nofollow accidentally.
6. Validate the XML sitemap
The sitemap should include useful indexable URLs, not redirects, 404s, or pages you do not want indexed.
7. Review canonical tags
Every important page should point to its correct final version.
8. Review titles and H1s
You do not need poetic copy. You need clarity, relevance, and consistent hierarchy.
9. Check navigation and internal linking
Key pages should be easy to reach for both users and crawlers.
10. Test the main form
Do not just look at it. Submit it and verify that the lead or message actually arrives.
11. Review mobile speed
Staging can hide performance problems that become obvious in production. Run critical pages through the performance checker.
12. Optimise key images
Oversized hero images are still one of the simplest ways to damage launch-day performance.
13. Check legal and trust pages
Privacy, cookies, contact details, and basic business information all matter for trust, not just compliance.
14. Review analytics setup
Make sure GA4 is implemented before launch, not as a "we will do it later" task.
15. Connect Search Console
You want visibility from day one, especially if the new launch affects indexation or traffic.
Post-launch checks
16. Submit the sitemap
Do it immediately. Small tasks get postponed for weeks surprisingly often.
17. Request indexing for priority pages
Start with:
- homepage,
- service pages,
- and top commercial sections.
18. Re-check status codes
Launches often create unexpected 404s, redirect chains, or soft errors.
19. Confirm the live canonical version
Sometimes the launch environment differs slightly from staging and changes how canonical logic resolves.
20. Test forms again on production
It worked in staging is not the same as it works live.
21. Check tracking and conversions
Make sure sessions, events, and important actions are actually being recorded.
22. Review real mobile behaviour
Lab tools are useful, but live devices often reveal issues faster. If performance matters commercially, read more on Core Web Vitals in plain English.
23. Inspect the homepage in Google
Check whether Google can discover the site and whether the brand starts appearing correctly.
24. Monitor server and site stability
New launches often trigger resource or cache issues that never showed up in testing.
25. Review internal links one more time
Menus, buttons, and contextual links can break quietly during last-minute edits.
26. Check images, scripts, and visual assets
Look for broken media, missing fonts, odd layout shifts, or delayed interactive elements.
27. Confirm contact details and trust copy
This sounds basic, but it affects conversion more than most teams expect.
28. Review international or multilingual links
If the site is multilingual, check that users and search engines are sent to the right versions.
29. Watch for indexing anomalies in the first days
If pages stay invisible, go straight to indexation checks instead of waiting passively. This article on why a website may not show up on Google covers the most common reasons.
30. Keep monitoring after the launch week
A smooth launch day does not mean a stable month. Template changes, scripts, and integrations can still create problems later.
That is where Monitoring becomes valuable. It helps you catch regressions after the adrenaline of launch has already passed.
The practical mindset
The point of a launch checklist is not perfection. It is preventing avoidable mistakes.
Most post-launch SEO problems are not advanced. They are neglected basics.
Next steps
- Use the free analyzer on the live site once it is public.
- Confirm indexation and redirects before worrying about secondary optimisations.
- Re-test forms, analytics, and mobile speed on production.
- Keep an eye on the site after launch instead of assuming the job is finished.
FAQ
What is the biggest SEO mistake on a new website launch?
Accidentally blocking indexation with noindex, bad canonicals, or a staging robots.txt rule.
Should I submit every page for indexing?
No. Start with the pages that matter most commercially and structurally.
How soon should I connect Search Console?
Before or immediately at launch. Waiting means losing visibility when you need it most.
Is launch-day speed really that important?
Yes. If the site launches heavy, unstable, or slow on mobile, the damage starts immediately.