Most website launches go wrong in small, avoidable ways. A contact form that sends enquiries nowhere. A test setting that hides the whole site from Google. Old pages that vanish without redirects, taking years of rankings with them. None of these are hard to prevent, but they're easy to miss in the rush to go live. A checklist, worked through calmly the week before launch, catches nearly all of them. It covers the last two stages of the website development process.
The short version
- Test every form, button and link, on a phone as well as a computer.
- Make sure Google can index the new site, and that old page addresses redirect to the right new ones.
- Install analytics and set up key events before launch, not after.
- Check speed, security (HTTPS) and backups.
- Plan the launch for a quiet day, early in the week, with someone available to fix problems.
Content
- Every page has final copy: no placeholder text, "lorem ipsum" or notes left in.
- Spelling and grammar checked, ideally by someone who didn't write it.
- Phone numbers, email addresses, opening hours and prices (if shown) are correct everywhere.
- Images are final, licensed, compressed and have alt text.
- Copyright year in the footer is current.
- 404 page exists and helps people find their way.
Functionality
- Every form submits successfully, sends to the right inbox, and shows a confirmation message.
- Form notifications don't land in spam. Send test enquiries from a Gmail and an Outlook address.
- Phone numbers are tap-to-call on mobile, and email links open a new message.
- Every link works, including in the footer and menu. A link checker finds broken ones quickly.
- Booking tools, maps, videos and chat widgets work.
- For shops: test purchases with real payment, refunds, emails and tax calculation.
Mobile and browsers
- Every page works on a real phone, not just a resized desktop browser.
- Text is readable without zooming, and buttons are easy to tap.
- The menu opens and closes properly on mobile.
- Pages look right in Chrome, Safari, Edge and Firefox.
SEO
- Every page has a unique title and meta description. Our SERP preview tool helps.
- Each page has one main heading (H1).
- The site is not set to noindex, and robots.txt doesn't block crawlers. This is the most common launch disaster.
- An XML sitemap exists and lists only live pages.
- Every old page address has a 301 redirect to its closest new page. See our guide to redesigning without losing SEO.
- Structured data is added and tested where it fits.
- Social sharing images and titles are set for key pages.
Tracking
- Google Analytics 4 is installed on every page, once. See our GA4 setup guide.
- Key events fire for enquiries, calls and purchases. Submit a test and check.
- Google Search Console is verified, ideally as a domain property.
- Ad conversion tracking and remarketing tags are moved over, if you run ads.
Speed and security
- Key pages load quickly on mobile. Test them with our free website speed test.
- HTTPS works on every page, and HTTP and non-www addresses redirect to one version.
- Admin logins use strong passwords and two-factor authentication.
- Automatic backups are running and you know how to restore one. See our backups guide.
- Plugins, themes and software are up to date.
Legal and ownership
- Privacy policy is up to date and explains any tracking and forms.
- Terms are in place for shops or bookings.
- Any cookie consent you need is working.
- The business owns the domain, hosting, analytics and platform accounts, not just the agency. Our ownership check covers this.
Copy-ready checklist
Website launch checklist
WEBSITE LAUNCH CHECKLIST Website: ______________________ Launch date: __________ CONTENT [ ] No placeholder text; spelling checked [ ] Contact details and hours correct everywhere [ ] Images final, compressed, with alt text [ ] Helpful 404 page FUNCTIONALITY [ ] Every form tested, reaches the right inbox, not spam [ ] Tap-to-call phone, working email links [ ] No broken links (menu, footer, body) [ ] Bookings / maps / video / chat working [ ] Shop: test order, refund, emails, tax MOBILE [ ] Tested on a real phone; menu works [ ] Checked in Chrome, Safari, Edge, Firefox SEO [ ] Unique titles and descriptions [ ] One H1 per page [ ] NOT noindexed; robots.txt allows crawling [ ] Sitemap live [ ] 301 redirects from every old URL [ ] Structured data and share images TRACKING [ ] GA4 installed once; key events tested [ ] Search Console verified; sitemap submitted [ ] Ad tags moved over SPEED AND SECURITY [ ] Key pages fast on mobile [ ] HTTPS everywhere; one canonical domain [ ] Strong passwords + 2FA [ ] Backups running and tested LEGAL AND OWNERSHIP [ ] Privacy policy / terms [ ] Business owns domain, hosting and accounts AFTER LAUNCH (week 1) [ ] Submit sitemap; request indexing for key pages [ ] Check Search Console for errors [ ] Check forms and analytics daily [ ] Spot-check old URLs redirect
On launch day
- 1Launch early in the week, not on a Friday afternoon, so problems can be fixed while people are around.
- 2Take a full backup of the old site first, in case you need to roll back.
- 3Switch over, then immediately check the homepage, a few key pages and the contact form.
- 4Check that the site isn't noindexed and that redirects work, by visiting a handful of old addresses.
- 5Submit the sitemap in Search Console and request indexing for the most important pages.
In the first week
- Check Search Console every day or two for crawl errors and pages not found.
- Make sure enquiries are arriving and analytics key events are recording.
- Look for any old addresses still getting traffic that aren't redirected.
- Ask a few customers or friends to use the site and tell you what's confusing.
- Keep a list of small fixes and work through them, rather than leaving them for months.
Rankings sometimes wobble for a few weeks after a launch while Google processes the changes. If you've redirected properly, they usually settle. If traffic falls sharply and stays down, check redirects and indexing first.
Frequently asked questions
How long before launch should testing start?
Ideally a week or two, on a staging copy of the site. That gives time to fix issues without rushing the launch date.
Will a new website hurt my Google rankings?
Not if redirects, indexing and content are handled carefully. Most ranking losses after launches come from missing redirects or a site left on noindex.
Who should do the checks?
Your developer should handle the technical items, but someone from the business should check content, contact details and forms, as they know what's right.
What if something goes badly wrong?
That's why you take a backup first. If a serious problem can't be fixed quickly, restoring the old site while you sort it out is better than leaving a broken site live.
Want a launch that goes smoothly?
Our website design team works through every check on this list before and after launch. See our website redesign guide for the bigger picture, or book a call.
See it in practice · FinTech
FinTech KYC review cut from 5 days to 4 hours
Curious how your own site scores?
Run our free website audit. Simple report, about 10 seconds, no sign-up.



