Before You Go Live: The Website Launch Checklist We Use Every Time
Topic: website launch checklist
A practical pre-launch checklist covering content, forms, mobile, speed, SEO and backups, so your new website goes live without avoidable surprises.
Launch day should be quiet. When a new website goes live and the phone number is wrong, the contact form sends enquiries nowhere, or pages break on a phone, the problem is rarely the design — it is the final checks skipped in the rush to publish.
We run the same pre-launch routine on every site we build, from a five-page local site to a larger store. Here is that checklist in plain terms, so you can use it before your own site goes live.
1. Read every page like a first-time visitor
Start with the words. Read each page start to finish and look for placeholder text, unfinished sections, spelling mistakes, and details copied from an old site — old addresses, hours, prices, and services you no longer offer are the most common launch-day errors we see.
Check the facts a customer will act on: phone numbers, email addresses, opening hours, service areas, and directions. Then click every internal link. A visitor who lands on a broken page rarely complains — they simply leave and call the next business.
2. Test every form, button, and phone number
Never assume a form works because it looks right. Submit every form on the site yourself — contact, quote request, booking, checkout — and confirm three things: the message arrives in the right inbox, the visitor sees a clear confirmation, and any automatic reply says what happens next and how quickly.
Tap every phone number on a mobile phone to confirm it dials correctly, and test buttons in the header, content, and footer. If your site takes payments or bookings, run one complete real transaction and then refund or cancel it, so you know the whole path works.
3. Check the site on real phones and tablets
Most visitors will meet your site on a phone first, so that is where final testing matters most. Open every main page on at least one real phone and one tablet, in both portrait and landscape. Menus should open and close cleanly, text should be readable without pinching, and buttons should be easy to tap without hitting the one beside them.
Watch for content designed on a wide screen: tables that overflow, images that cover text, pop-ups that cannot be closed, and forms where the keyboard hides the submit button. Small faults like these make a new site feel unfinished in seconds.
4. Measure speed before your visitors do
A new site should launch fast, because it will only get slower as you add content. Run the homepage and your busiest service page through a speed test, on a mobile connection rather than office Wi-Fi, and fix the obvious problems first: oversized images, unnecessary sliders and videos that load before the page does.
You do not need a perfect score. You need pages that appear quickly and stay stable while they load. If a page feels slow on your own phone, it will feel slower to a customer on a weaker signal — deal with it before launch, not after.
5. Set the SEO and sharing basics
Search engines and social platforms need a few basics in place from day one. Every page should have a unique title and a short description written for people, not a copy of the same text everywhere. Check that your business name, address, and phone number match exactly what appears on your Google Business Profile and other listings.
Confirm the foundations too: the site should be reachable at one clear address, old pages should redirect to their new equivalents, and a sitemap should be in place so search engines can find every page. Finally, share your homepage link in a message to yourself and check how it looks — that image and text are what customers will pass on.
6. Confirm security, backups, and who has access
Before launch, confirm the site opens securely over HTTPS on every page, with no browser warnings. Check that automatic backups are running and — this is the part most people skip — that a backup can actually be restored. A backup nobody has tested is a hope, not a plan.
Then review access. Everyone who updates the site should have their own login, stored safely, and anyone who no longer works on the site should be removed. Note where the domain is registered, where the site is hosted, and when each renews — launch day is the easiest time to record this.
7. Plan the first week after launch
Going live is the start of testing, not the end. In the first week, check your enquiry inbox and analytics daily, watch for pages visitors leave immediately, and ask a few real customers to find key information on the site while you listen — where they hesitate is where the next improvement belongs.
Keep a short list of anything you spot, fix genuine problems quickly, and resist redesigning on day three based on one opinion. You can see how we design, build, and look after business websites at webpronc.com — and if you have a launch coming up and would like a second pair of eyes on the final checks, we are happy to help.