Guide
Website launch checklist: what to check before you go live
Before you launch a website, check that every page reads correctly, every link and form works, the site loads over HTTPS on a phone, search engines are allowed in, backups exist, and your contact and legal details are present. Work through the checks below in order, tick each one, and launch only when the list is clear.
Why bother
A launch is easy to get wrong in small ways
Most launch problems are not dramatic. A contact form that sends mail to the old email address. A menu link that points at the test site. A page still saying "lorem ipsum". A search engine instruction left over from development that tells Google to ignore the whole site. Each is a five-minute fix, but only if you find it before your customers do.
A checklist works because it replaces memory with a routine. You are excited and tired on launch day, which is exactly when you overlook things. Print this page or copy it into a note, and tick items off as you verify them rather than as you assume them.
Do the checks on the real domain, not only on a preview address. Some problems, such as mixed content warnings or email delivery, only appear once the live domain, SSL and DNS are in place.
Group 1
Content and design
- Proofread every page. Read it aloud, and have someone else read it too.
- No placeholder text. Search for "lorem", "test" and "coming soon".
- Prices, hours and addresses are current. Check against your own records.
- Images have alt text. Describe what the image shows in a short phrase.
- Images are compressed. A hero image of several megabytes needs resizing.
- Every page has one clear heading and a next step. Visitors should know what to do.
Group 2
Links, forms and functions
- Click every menu and footer link. Check none lead to a test address.
- Submit every form. Confirm the message arrives at the right inbox and the visitor sees a thank-you.
- Check phone and email links. On a phone, tapping the number should offer to call.
- Test any shop, booking or login feature end to end. Use a real small transaction where you can.
- Look for broken links and 404 errors. Fix or redirect them. See setting up 301 redirects.
- Add a helpful 404 page. Offer a link home and a search or contact option.
Everything you need to go live
Free SSL, backups and live chat open 24/7 on every plan.
Group 3
Technical checks and how to do them
| Check | How to do it | What good looks like |
|---|---|---|
| HTTPS works | Visit the site and look for the padlock | No browser warnings on any page |
| Mixed content | Open pages and check the browser console | No insecure images or scripts |
| www and non-www | Type both versions | One redirects to the other |
| Domain resolves | Load the site from a device on mobile data | Live site, not the old one |
| Mobile layout | Open on a real phone | Readable text, tappable buttons, no sideways scroll |
| Page speed | Run a speed test on key pages | Main content appears quickly |
| Favicon | Look at the browser tab | Your icon, not a default |
If you are moving from another site, also work through the website migration checklist.
Search engines
Make sure search engines are allowed in
Many website tools have a setting called "discourage search engines" or a "noindex" tag, used while the site is being built so that half-finished pages do not appear in results. It is the single most common reason a new site never shows up. On launch day, find that setting and turn it off. In WordPress it sits in the Reading settings, and some SEO plugins add their own.
Then check three more things. Every page should have a unique title tag and meta description that reads naturally. Your site should have an XML sitemap, which most SEO plugins create for you. And your robots.txt file should not block the whole site. Open yourdomain.co.uk/robots.txt in a browser and make sure it does not contain a line that says "Disallow: /" under all user agents.
Set up Google Search Console and submit your sitemap. It is free, it tells you if Google has trouble reading your pages and it shows which searches bring people to you. If you serve a local area, create or claim a Google Business Profile with the same name, address and phone number as your website.
Group 4
Security and backups
- Strong, unique passwords. For hosting, WordPress, the database and email.
- Two-factor login where offered. Especially on the WordPress administrator account.
- Default "admin" user removed. Create a differently named administrator.
- Everything updated. WordPress core, themes and plugins.
- Unused plugins and themes deleted. Fewer parts, fewer weak points.
- Backup taken just before launch. Keep a copy away from the server. See how to back up a website.
Check that your email works
If you launch a new domain, email is the thing most likely to be forgotten. Create your mailboxes, send a message to a personal address, reply to it, and send one from the website form. Check that nothing lands in spam. If it does, look at your SPF, DKIM and DMARC records, explained in our guide to SPF, DKIM and DMARC.
If you are moving an existing site and keeping mailboxes elsewhere, be careful not to change the mail records by accident when you change DNS. A wrong MX record sends your incoming mail into the void. Send yourself a test from outside the domain before and after you switch.
Soft or hard launch
Two ways to go live
Soft launch
- Publish quietly and tell a few friendly customers
- Collect feedback and fix rough edges
- Good for shops and booking systems
- Lower pressure if something breaks
- Announce widely a week later
Big-bang launch
- Announce on the day it goes live
- Good for events and campaigns with fixed dates
- Needs a longer, stricter checklist
- Have someone on hand to fix issues
- Prepare social posts and emails in advance
Group 5
Legal and trust
- Business name, address and contact details shown
- Company number and registered office, if a company
- Privacy notice that matches what you collect
- Cookie notice if you use non-essential cookies
- Terms or delivery and returns pages for shops
- Photos and text you have the right to use
- Accessible text sizes and colour contrast
- Prices clearly shown with what they include
After launch
The first week after going live
Check the site daily for the first week. Look at your enquiries, your search console messages and your uptime. Fix typos the moment you spot them. Ask two or three real customers what they thought, and watch for pages where nobody clicks anything, which often means the next step is unclear.
Put a recurring reminder in your calendar to review the site every month: updates, backups, broken links and out-of-date text. Legal and price details drift, and a site that says the wrong thing is worse than a smaller site that is right. The legal pointers here are general guidance, not legal advice. Check the ICO and gov.uk for current rules.
FAQ
Common questions
How long should a launch check take?
For a small site, allow two to three hours to work through the list carefully, plus time to fix what you find.
What is the most common launch mistake?
Leaving a "discourage search engines" setting switched on, so the site never appears in Google. Check it first.
Do I need a backup before launching?
Yes. Take one just before launch, and store a copy away from the server. We also keep weekly remote backups for about a month.
Should I launch on a Friday?
It is wiser to launch early in the week, when you can fix problems quickly and ask for help during working hours. Our live chat is open 24/7 either way.
Can I launch and improve later?
Yes. A correct, simple site beats a perfect one that never goes live. Fix the checklist items first, and improve the design afterwards.
Keep reading
Related pages
Launch on hosting built for UK sites
UK servers in London, free SSL and weekly remote backups on every plan.