Planning a website · guide 7 of 7
Website launch checklist: the checks before, during and after go-live
The small, avoidable things that go wrong when a website goes live (silent forms, lost email, a hidden “do not index” setting) and the checks that catch each one, from three weeks before launch to two months after.
29 min readUpdated 9 Nov 2026
- 10 questions to test yourself
- 1 calculator
- 37-item checklist
On this page12 sections
The launch bug that costs most is the one you never see
When owners imagine a launch going wrong, they picture the site crashing: a blank screen, an error, a panicked call to the developer. That does happen, and it is the good kind of failure. Everyone notices within minutes and someone fixes it.
The expensive problems are quiet. Nothing looks broken, so nobody looks. You just have a slow month and blame the season. Before reading on, test your instinct for which kind of problem hides longest.
Quick quiz
Your new site goes live on Monday. Which of these problems would you most likely notice last?
Pick one. Your first answer is the one that counts.
Almost every quiet launch failure comes down to one of three things: a hidden setting that keeps Google away, email that stops arriving, and a contact form whose messages go nowhere. This guide flags each one as you reach it, with a check that takes minutes, and walks you from three weeks before launch to two months after. At the end you score your own launch, and near the end is the cheapest check on the whole list.
First, put a number on “quiet”, using your own figures: what a silent form would cost you if nobody noticed for a few weeks.
Try the numbers
What a few silent weeks would cost you
Enquiries that would vanish
12 enquiries
Business lost over those weeks
about €900
What each unnoticed week costs
about €300 a week
Your own rough estimate, not a forecast. Compare the last line with the two minutes a test enquiry takes: that is the whole case for testing on launch day and once a month after.
Three weeks before: make sure you hold the keys
A launch depends on accounts that are often set up once, years ago, by someone who has since moved on. Find them now, while nothing is urgent. Discovering on launch day that a former designer registered your domain in their own name can stop everything for days.
There are three keys. The domain registrar is the company you rent your domain name from. The DNS host is where the records that point your domain at a website and at an email service are managed; it is often the registrar, but not always. The hosting is where the site itself lives. Write down who each one is, which login opens it, and whose name and card are on the account.
Ask one more question that owners often skip: where does your email live? If your email runs through your old host, a new site on new hosting can quietly cut it off. Your developer needs to know before launch, not after.
If you are earlier than this, with no developer chosen yet, the guide on writing a website brief is the better place to start: come back here once a launch date is on the table.
Checklist
The keys to have in hand
Saved on this device only
One week before: the content sweep
Test sites collect leftovers: placeholder text, demo products, a test phone number, the theme's sample blog post. They are invisible to the people who built the site because they have stopped seeing them. A fresh pair of eyes reading every page, on a phone, finds most of them in an hour.
Read the site the way a customer would, not the way you would review a design. Does every price match what you actually charge? Does the opening-hours table match your Google Business Profile? Does tapping the phone number on a phone actually start a call? Try your hand at it first: each card below describes something found on a real-looking test site. Spot the problem, then flip.
Test yourself
Think of your answer, then flip the card.0 of 6 flipped
Checklist
The content sweep
Saved on this device only
Silent failure 1: the setting that can hide your whole site from Google
While a site is being built, developers usually tell search engines to stay away, so a half-finished version does not end up in Google. That is sensible. The trouble is that the instruction sometimes survives the launch, and nothing on the screen tells you it is there.
It comes in two forms. A “noindex” tag on the pages asks Google not to show them in its results. A robots.txt file (a short text file at yoursite.com/robots.txt) with the line “Disallow: /” asks search engines not to crawl anything. In WordPress, the checkbox “Discourage search engines from indexing this site” under Settings, then Reading, does the first of these for the whole site.
Before the details, test your instincts. Some of these beliefs are true, and some are the reason sites go missing for weeks.
Myth or fact?
Five beliefs about getting a new site into Google
1.Blocking a page in robots.txt guarantees it will not appear in Google.
2.If a page has a noindex tag and is also blocked in robots.txt, Google may never see the noindex.
3.Submitting a sitemap tells Google to index every page in it.
4.Even after you ask Google to crawl a page, it can take from a few days to a few weeks.
5.Searching “site:yourdomain.com” shows every page Google has indexed.
Before and after
The robots.txt file: test site and live site
Left over from the test site
User-agent: *
Disallow: /
What a live site usually needs
User-agent: *
Disallow:
- The only difference is one slash. “Disallow: /” asks every search engine to crawl nothing; an empty “Disallow:” line blocks nothing.
- Checking takes 30 seconds: type your address followed by /robots.txt into a browser and read what comes back. If there is no file at all, that is fine too: it means nothing is blocked.
- The noindex tag does not show in the file. To check it, open a page, view its source (right-click, then View page source) and search for “noindex”, or use Search Console's URL Inspection after launch.
Speed: test the page people land on, on a phone
Most launch speed problems are not about the platform or the hosting. They are about what was added to the page: a camera-sized photo at the top, a background video, three web fonts, a chat widget, a booking widget and a social feed, each loading its own code.
Google measures how a page feels to real visitors with three numbers called Core Web Vitals. The first, Largest Contentful Paint, is how long it takes for the biggest thing on the screen (usually the hero photo or headline) to appear. Before you read the answer, guess the line Google draws.
Make a guess
Google calls Largest Contentful Paint “good” when the main content appears within how many seconds?
Anything within ±0.5 seconds counts as right.
Test before launch, so problems are fixed while it is cheap. Test the homepage and the two or three pages people most often arrive on (usually a main service or product page), and look at the mobile result, not the desktop one. Online speed tests, including the free speed test on this site (it runs Google PageSpeed Insights), need a public address, so they cannot reach a password-protected test site; before launch, ask your developer to run Lighthouse in Chrome's developer tools, which works behind a password.
Then run the free speed test on the same pages the day after launch, on the live address, because live sites gain extras such as analytics, cookie banners and chat widgets that the test site did not have. If a number puzzles you, the guide on Core Web Vitals explains each one without the jargon.
- Resize and compress the large photos first: it is usually the biggest, cheapest win.
- Question every widget: does the chat box or social feed earn the time it adds?
- Give images and embeds fixed space on the page so the layout does not jump while they load.
Launch day: the order matters
Launch day itself should be boring. Most of the work happened in the weeks before; today is about doing a short list of things in the right order, with your developer available to fix whatever turns up.
Pick the day with that in mind. A Tuesday morning beats a Friday evening, because if something breaks you want a full working day ahead and your developer at their desk. Avoid the week before your busiest season, and avoid the day you send a big newsletter or start an ad campaign.
One free shortcut for the day: the domain and email check on this site tests the padlock certificate, the http, https and www redirects, and the email records (MX, SPF, DKIM and DMARC) in one go. Run it once before the switch, so you have a picture of how things stood, and again after it, and compare the two.
Put it in order
Put the switch-over steps in the order they should happen
Use the arrows to move each item, then check.
- Point the domain at the new site
- Submit the sitemap in Google Search Console
- Send a test enquiry and a test email and check both arrive
- Back up the old site and copy every DNS record, including email
- Wait until the new site shows on your phone with Wi-Fi off
Checklist
Launch day
Saved on this device only
Silent failures 2 and 3: lost email and forms that go nowhere
Your website and your email are separate services that share one domain name. The DNS records decide where each goes: one set of records points the domain at the website, and the MX records point it at your email provider. When a launch involves moving DNS to a new provider, every record has to be copied across. Miss the MX records and email to your domain stops arriving. The sender may not get a bounce message for hours or days, and you see nothing at all.
Forms have their own trap. Many website forms send their notification email from the web server, pretending to come from your domain. Mail services increasingly reject or spam-folder messages like that unless the domain has proper authentication records: SPF, DKIM and DMARC, which tell the receiving server which senders are genuinely allowed to use your name. Google's sender guidelines for Gmail, tightened in 2024, require every sender to set up SPF or DKIM.
None of this needs to be understood in depth. It needs to be tested: a real test enquiry for the form, and the domain and email check from launch day for the records. Here is how it plays out, and how the quiz at the top of this guide ends.
What would you do?
A florist's quiet first week
An illustrative example: a made-up florist launches a new site on a Thursday. The old site brought in three or four order enquiries a week through its form. By the following Wednesday there has not been a single one. The site looks perfect and loads quickly.
What should the owner do first?
The first 48 hours: tell everyone where you live now
Once the site is live and the tests pass, it is time to make sure everything that points at your website points at the right place, and that you can see what happens next.
Google Search Console is Google's free dashboard for site owners. Add and verify the site if it is new, or check that your existing property still works if you kept the domain. Submit the sitemap, then use the URL Inspection tool on the homepage to confirm Google can fetch it and that it is not marked noindex. If you moved to a new domain, Search Console's Change of Address tool tells Google about the move. New to Search Console? The guide to Google Search Console for business owners is a 20-minute tour of the reports you will use here.
Then run the free broken link checker on the live site: it follows your links the way a visitor would and lists every one that leads nowhere, with the page it sits on. Old links pasted into new pages are the usual culprits. For the analytics item below, the guide on GA4 for SEO shows how to mark an enquiry as a key event and test it.
Checklist
The first two days
Saved on this device only
Weeks 1 to 8: what is normal and what is a warning
The weeks after launch are when owners worry most and can do least. Some wobble is normal, especially if the new site replaces an old one: Google has to recrawl your pages and work out what changed, and positions can move up and down for a while. What you are looking for is not perfection but things that stay broken.
Test yourself first: here are four things owners see in the weeks after a launch. Only one of them needs you today.
Quick quiz
Three weeks after launch, which of these should you act on today?
Pick one. Your first answer is the one that counts.
Timeline
An honest first two months
Day 1–2
Test everything that can fail silently
Forms, email, analytics, redirects and the noindex setting. These are the only checks that are truly urgent.
Week 1
Watch enquiries, not rankings
Compare enquiries, calls and bookings with a normal week. A sharp fall this early usually means something broke, so retest the forms and email before anything else.
Weeks 2–4
Read the Page indexing report
In Search Console, see which pages are indexed and why others are not. Sort the statuses the way the quiz did: “Discovered - currently not indexed” on a new site often clears on its own; “Crawled - currently not indexed” on a page you care about is Google's judgement, so strengthen the page and link to it; a noindex never clears by itself.
Weeks 4–8
Compare like with like
Compare visits and enquiries with the same weeks last year, or with the weeks just before launch, adjusting for season. Look at the pages that used to bring visits in particular: if one has dropped and not recovered, check its redirect and its content. If the whole site is still well down after two months, the guide on a Google traffic drop is a calm, step-by-step diagnosis.
Set up the alarms that catch the next problem
A launch is not the last time something can break silently. Set up the boring safeguards now, while the site is fresh in your mind. They take an afternoon once and then run by themselves.
Checklist
Set up once, then forget
Saved on this device only
That last item is the check promised at the start, and the cheapest insurance on this list. Forms do not only break at launch: a plugin update, a changed mailbox password or a new spam filter can silence them at any time, and the failure looks exactly the same as it did on day one. Nothing on the screen changes.
On the first working day of each month, fill in your own form and follow the message to the inbox you read. Two minutes, every month, for as long as the site exists. The calculator at the top tells you what each week it saves you is worth.
Score your own launch before you set the date
Answer for your launch as it stands today. Be strict with yourself: if you are not sure, choose “Not sure”, which scores less than a yes, because a check you have not done is exactly how silent failures survive.
Score yourself
How ready is your launch?
The domain account is in my name and I can log in to it myself
I have a copy of every DNS record, including the MX records for email
The test site is password-protected, or I know which “do not index” setting to switch off at launch
Someone who did not build the site has read every page on a phone
My main landing page has had a mobile speed test before launch, and the slow parts are fixed
Launch is on a weekday morning, with my developer available for the rest of the day
On launch day I will send a test enquiry through every form and follow it to the inbox I read
Search Console and analytics will be checked within 48 hours of launch
The old hosting stays until email and files are confirmed safe
0 of 9 answered. Answer them all to see your result.
Questions owners ask before going live
Questions people ask
Can I launch with some pages unfinished?
Yes, and it is often better than waiting months for everything to be perfect. Launch with the pages that matter (home, main services or products, contact) finished properly, and leave the rest out of the menu until they are ready. What you should not do is publish empty “coming soon” pages: they look abandoned to visitors and give Google nothing useful to show.
Do I need to tell Google my site has launched?
Google will usually find a site on its own, especially one that replaces an existing site on the same domain. Verifying it in Search Console and submitting a sitemap helps Google find your pages and, more importantly, lets you see what Google sees. It does not move you up the results.
How long until my new site appears in Google?
Google's own help pages say crawling can take anywhere from a few days to a few weeks. Being indexed is also not the same as ranking well for the searches you want; that depends on your content, your competition and your reputation, and nobody can guarantee a position.
Should the old and new site run side by side for a while?
Not on two public addresses with the same content: that splits visitors and gives Google two copies of the same pages. Keep the old site as a backup you can restore, not as a second live site. If you change domains, redirect the old address to the new one.
My developer says everything is done. What should I still check myself?
The things only you can judge, and the things that fail silently. Read every page on your own phone, check prices and details, send yourself a test enquiry through every form, and make sure the domain account is in your name. A good developer will welcome the second pair of eyes.
You reached the end
Your summary
This guide has 10 quick questions
Try them to see how much you already know. Your first answer is the one that counts.
Planning a website: 0 of 7 read
- 1. What a website brief should contain, and the gaps that stall projects: not read yet
- 2. Planning a website redesign: what to keep, what to change: not read yet
- 3. The homepage that turns visitors into enquiries: not read yet
- 4. Conversion basics: small changes that turn visits into leads: not read yet
- 5. WordPress, Shopify, Wix or custom? Choose once, not twice: not read yet
- 6. What a website really costs: the build, the bills and the extras nobody quotes: not read yet
- 7. Website launch checklist: the checks before, during and after go-live: this guide, not read yet
0 of 57 guides read · Saved on this device only
New guides by email when they are published.
Unsubscribe in one click.
What to do next
- Log in to your domain registrar today and confirm the account is in your name and set to renew automatically.
- Ask your developer for a copy of every DNS record, including MX, and whether the test site is password-protected or set to noindex.
- On launch day, send a test enquiry through every form and follow it to the inbox you actually read; then add a monthly calendar reminder to repeat it.
- Two to four weeks after launch, open Search Console's Page indexing report and check that your important pages are indexed.
Not sure which build fits?
Answer five questions and get a recommended build, add-ons and matching demos.
Open the plannerNext series: Measuring results
Measuring results
Google Search Console for business owners: the 20-minute tour
Search Console shows the exact words people typed before they found you, including the searches you are almost winning. It is free.
25 min readStart reading
Where we can help
See it on a real build
Every brand in the demos is fictional.


