Published 30 September 2026 · Updated 30 September 2026
What should I check before launching a website?
Work through five groups in order: the content is accurate and complete, every form and phone number actually works, the site behaves on a phone, search and analytics are set up correctly, and if you are replacing an old site, every old address redirects to its new home. Then check the legal pages, backups and security, and only then point the domain. Most launch failures are not dramatic. They are a contact form nobody tested, an old phone number on one page, or two hundred old URLs quietly returning 404.
Key takeaways
- Test the money path first. Whatever action earns you money, complete it yourself end to end, on a phone, before anything else on the list.
- Replacing a site is riskier than launching a new one. Old addresses need mapping and redirecting, or you hand back search visibility you already earned.
- Forms fail silently. A form that looks fine and sends nowhere is the single most expensive launch defect there is.
- Check the details that appear everywhere. Phone number, address, hours and email, on every page including the footer and the contact page.
- Launch early in the week. Wednesday morning gives you days to find problems. Friday afternoon gives you a weekend of them.
- The list does not end at launch. The first week is when real visitors find what testing missed, so keep watching rather than moving on.
What this guide covers
- Before you open the checklist
- Content: the pages that have to exist
- Read the copy once as a customer
- Details that must match everywhere
- Forms, phone numbers and enquiries
- Mobile and browsers
- Speed and images
- Search essentials
- If you are replacing an existing site
- Listings, profiles and social
- Analytics and tracking
- Legal, privacy and consent
- Accessibility
- Security, backups and updates
- Email, DNS and the domain
- The handover: what you should be given
- Launch day, in order
- If something goes badly wrong
- The first week after launch
- Mistakes that turn a launch into a rescue
- Frequently asked questions
Before you open the checklist
Two decisions save a great deal of confusion later. First, who signs off. One named person decides the site is ready, and that person is accountable for the list being completed rather than discussed. Launches drift when approval is diffuse, because everyone assumes someone else checked the forms.
Second, agree what launched means. A site can be live and unfinished, and that is often the right call for a small business: a working site earning enquiries beats a perfect one still in draft. Decide which items are genuinely blocking and which are improvements for the following month, and write that down so the distinction survives launch week.
The one non-negotiable Whatever action makes you money, book, buy, call or enquire, must work end to end on a real phone before you go live. Everything else on this list can be fixed after launch. That cannot.
Content: the pages that have to exist
Most small business sites need a small number of pages done properly rather than a large number half finished. Before launch, check that each of these exists, says something specific, and does not contain placeholder text.
The minimum set
- Home, which says what you do, who for, and where, in the first screenful.
- Services or products, one page per significant offering rather than a single page listing everything.
- About, with real people and real photographs, because it is one of the most visited pages on a small business site.
- Contact, with every way to reach you and a form that works.
- Pricing or an honest explanation of how pricing works, since the absence of any price information is the most common reason a visitor leaves.
- Privacy policy, required if you collect anything at all, including through a form or analytics.
- A 404 page, that helps rather than dead-ends, with links back to the main pages.
Then read every page once more looking only for placeholder text. Lorem ipsum in a footer, a template heading nobody replaced, or a stock testimonial from the theme demo. These survive to production more often than anyone admits, and they are the first thing a visitor notices.
Read the copy once as a customer
Everyone proofreads a new site for typos. Almost nobody reads it as a customer deciding whether to hire the business, which is the reading that matters.
Sit down with the homepage and the main service page and ask four questions in order. Is it obvious within a few seconds what you do and who for? Is it clear where you work, if location matters? Is there any indication of price, or at least of how pricing works? And is the next step obvious, with one clear action rather than five competing ones?
Then check the tone. Small business sites drift into describing themselves rather than the customer: our passion, our values, our journey. A visitor is trying to work out whether you solve their problem. The pages that convert say what the customer gets, in their words, and keep the company history to a short paragraph on the about page.
A five minute test worth doing Ask someone outside your business to read the homepage for thirty seconds, then close it and tell you what you do, who for, and what it would cost roughly. If they cannot, the words need work, not the design.
Details that must match everywhere
Business details appear in more places than people expect: the header, the footer, the contact page, structured data, the map embed, the email signature the form sends, and any social profiles you link to. They must all say the same thing, because inconsistency confuses visitors and undermines local search.
- Business name, written identically everywhere, including punctuation and any legal suffix.
- Phone number, in one consistent format, and clickable on mobile.
- Address, matching what appears on your Google Business Profile and any directory listings.
- Hours, including how holidays are handled, and consistent with anywhere else they are published.
- Email address, one that is monitored, not one that forwards somewhere nobody checks.
- Service area, if you travel to customers, stated plainly so people know whether you cover them.
Consistency between your website and your local listings is part of how search engines associate the two. Our guide to local SEO for small business covers what else to line up while you are at it.
Forms, phone numbers and enquiries
This is where the expensive failures live, and the test is not a glance at the page. It is submitting the form and confirming the message arrived, from a device that is not yours, on a connection that is not your office wifi.
Test each of these
- Submit every form, including the ones on inner pages that nobody remembers exist.
- Confirm arrival, in the inbox that will actually be watched, not a folder nobody opens.
- Check the spam folder, because new site emails frequently land there first and stay there.
- Read the confirmation the sender receives, since a blank or broken auto-reply looks worse than none.
- Tap the phone number on a phone, and make sure it dials the right number.
- Tap the email link, and check it opens with the correct address.
- Open the map, and confirm it lands on your actual door rather than a similar address.
- Check the booking or payment flow, all the way to a real confirmation, then cancel the test.
Form email is the most fragile part of a new site Website forms that send mail from the web server are frequently filtered as spam, especially when the address they send from does not match the domain properly. If enquiries matter to you, set up proper sending through an authenticated mail service and test it before launch rather than after the first missed lead.
Mobile and browsers
Check the site on a real phone, on mobile data, before launch. Not a simulator, and not only your own recent handset. Borrow an older Android if you can, because that is closer to what many visitors carry.
Look for the four failures that account for most mobile problems: text too small to read without zooming, the page scrolling sideways, buttons too small or too close together, and the page taking too long to become usable. Then open the menu, reach every page from it, and complete the enquiry path with a thumb rather than a careful fingertip. Our guide to checking whether a site is mobile friendly sets out the ten minute version of this test.
Then check one or two other browsers. You do not need a device lab. Safari on an iPhone and Chrome on Android cover most visitors, and a quick look on a laptop in a browser you do not normally use will catch anything badly broken.
Speed and images
New sites are usually slow for one reason: images uploaded at the size they came out of the camera. Before launch, check that every image is sized for the space it occupies, saved in a modern format, and loading lazily below the fold.
Run the homepage and one inner page through PageSpeed Insights and read the specific items rather than the score. Fix the largest contributors, which for most small business sites are images, an unnecessary slider, and scripts loading before anything is visible. Our guides to website images and speed for small business cover the fixes in order of effect.
Search essentials
You are not doing search optimisation at launch. You are making sure nothing prevents the site from being found, which is a much shorter list.
Check before going live
- The site is not blocked from indexing. Staging sites are usually blocked deliberately, and forgetting to unblock at launch is the most common single mistake in this whole list.
- Every page has its own title, describing that page, not the business name repeated.
- Every page has a meta description, written for a human deciding whether to click.
- One H1 per page, describing the page content.
- Images have alt text, which helps accessibility and image search together.
- URLs are readable and final, because changing them later means redirects.
- A sitemap exists, and is submitted in Search Console.
- Search Console and the domain are verified, so you can see what happens after launch.
The one that costs the most Launching with the staging block still in place. The site looks perfect, everything works, and search engines are being told to ignore it. Businesses have run for months like this before anyone noticed. Check it on launch day and again the day after.
If you are replacing an existing site
This is the part that separates a smooth relaunch from a drop in enquiries that takes months to recover. Your old site has addresses that search engines have indexed and other websites link to. If those addresses stop working, you lose both.
- List every URL on the old site. Export from the old system, from your sitemap, and from Search Console, then combine them.
- Map each one to its closest new page. Not everything to the homepage, which search engines treat as a soft failure and visitors find unhelpful.
- Set permanent redirects, so the new address inherits the value of the old one.
- Keep the ones with links or traffic alive, especially any page another website links to.
- Test the map before launch, and again immediately after, by requesting a sample of old addresses and confirming where they land.
- Watch for 404s in the weeks after, because the ones you missed show up in Search Console and in your analytics.
If the new site is on a different platform, this step is larger than it looks, and it is worth doing before launch rather than in response to the first complaint. Our piece on why a website is not showing on Google covers what to check when pages do go missing.
Listings, profiles and social
A launch is the natural moment to line up everything outside the website that points to it, because search engines and customers both check.
Update at launch
- Your Google Business Profile, with the new website address, correct hours and current photographs.
- Directory and association listings, anywhere your old URL appears, especially industry directories.
- Social profiles, with the new link in the bio and in any pinned post that mentions the site.
- Email signatures, for everyone in the business.
- Printed material, if the address changed, including invoices, cards and vehicle signage.
- Any advertising, including ad destination URLs, which silently 404 if a page was renamed.
Consistency across these is part of how a local business is identified, and it is also the cheapest work available in the week after a launch. If you run ads, check every destination URL specifically, because a redirect that works for a visitor can still break tracking.
Analytics and tracking
Set up measurement before launch, not after, because the first weeks are the ones you will most want to look back on.
At minimum: analytics installed and firing on every page, Search Console verified and the sitemap submitted, and a way to see which enquiries came from the site. Check that your tracking is not recording your own visits, and if you use any advertising, confirm the conversion tracking works on a real test submission rather than assuming the tag is enough. Our guide to website analytics for small business covers what is worth watching once data starts arriving.
Do not install more than you will use. Three scripts you never read cost speed and add privacy obligations for no return.
Legal, privacy and consent
If your site collects personal information in any form, including a contact form, a signup or analytics, you need a privacy policy that reflects what you actually do. In Canada, guidance for businesses is published by the Office of the Privacy Commissioner at priv.gc.ca, and we covered the practical version in our guide to a website privacy policy.
Also check the smaller items: terms of use if you sell or take bookings, a cookie or tracking notice if you use tracking that requires one, correct copyright year and business name in the footer, and any professional or licensing information your industry requires you to display. If you make claims about results, pricing or guarantees, make sure they are ones you can stand behind.
Accessibility
An accessible site reaches more customers and is usually a better site for everyone. At launch, the practical checks are contrast, real headings in order, alt text on images, form fields with visible labels, links that say where they go, and the ability to reach everything with a keyboard.
None of that requires specialist software to check at a basic level, and fixing it now is far cheaper than retrofitting it into a design later. Our guide to accessibility standards for small business sets out what applies and in what order to tackle it.
Security, backups and updates
A new site is the easiest time to get this right, because nothing has been improvised yet.
Before launch
- HTTPS working everywhere, with no mixed content warnings and http redirecting to https.
- Admin accounts cleaned up, with the developer’s test accounts removed and strong unique passwords on what remains.
- Two factor authentication enabled, on the site, the hosting account and the domain registrar.
- A backup that has been restored once, because an untested backup is a hope, not a backup.
- An update plan, naming who applies updates and how often.
- Login credentials recorded properly, in a password manager the business owns, not in one person’s notes.
Our guides to small business website security and website backups go further, and the short version is that the site you launch this week will need someone to look after it every month afterwards.
Email, DNS and the domain
The most disruptive launch failures are not on the website. They are in email, because the same DNS settings control both, and a careless change can stop a business receiving mail entirely.
Before you change anything, write down the current DNS records. Confirm which provider handles your email and that the records it needs will be preserved through the move. If your email is bundled with your old hosting, sort out where it is going before the site moves, not during. Then reduce the time to live on the records shortly before launch so changes propagate quickly, and keep a copy of the old settings in case you need to roll back. Our guide to domain names and business email covers how the two fit together.
Check the domain itself Confirm the domain is registered in the business name, that you control the registrar account, that auto-renew is on and the payment card is current, and that the contact email on the account is one you can still access. Expired domains and lost registrar logins cause more outages for small businesses than hacking does.
The handover: what you should be given
Whoever builds the site should hand over enough for someone else to take it on. This is the item most often skipped, and it is the reason so many small businesses cannot touch their own website.
Ask for all of it in writing
- Domain registrar account access, in your business name, with you as the registrant.
- Hosting account access, or the name of the plan and how it is billed.
- Website admin logins, with an administrator account in your own name.
- Analytics and Search Console ownership, with your account as an owner rather than a guest.
- A copy of the backup, and instructions for restoring it.
- A note of what was installed, including themes, plugins or apps and any that carry annual licences.
- A short guide to editing, covering the two or three things you will want to change yourself.
If a builder is unwilling to put ownership in your name, that is worth resolving before launch rather than during a dispute. The most common version of this problem is a domain registered inside a contractor’s account, which turns a simple move into a negotiation. Our comparison of WordPress, Wix and Squarespace covers how ownership differs by platform.
Launch day, in order
- Take a final backup of the old site, including its database and files, and keep it somewhere you can reach.
- Put the new site live, or point the domain, depending on how it was built.
- Remove the indexing block immediately, and confirm it is gone by checking the live site.
- Test the money path first, on a phone, for real.
- Spot check redirects, using a sample of old addresses across different sections.
- Submit the sitemap in Search Console, and request indexing for the most important pages.
- Check analytics is recording, by visiting the site yourself and watching real time.
- Walk the site once, slowly, reading every page as a visitor rather than as the person who built it.
Launch on a Tuesday or Wednesday morning. It gives you the rest of the week to find and fix whatever testing missed, with the people who can help still at their desks. A Friday afternoon launch means small problems sit live all weekend.
If something goes badly wrong
Occasionally a launch goes wrong in a way that cannot be fixed in ten minutes: the site is down, the payment flow is broken, or email has stopped. Decide in advance what you will do, because the decision is much harder while it is happening.
The rule of thumb is simple. If customers cannot contact you or cannot buy, roll back to the old site and fix the problem calmly. Pride is expensive here, and a day on the old site costs far less than a week of lost enquiries on a broken new one. That is why the final backup of the old site matters and why you should know how to restore it before you need to.
If the problem is smaller, put a temporary note on the affected page, give people another way to reach you, and fix it in order of what costs money. Most launch problems are in this category, and visitors are far more forgiving of an acknowledged issue than of a form that silently fails.
Have the two phone numbers ready Your host’s support line and whoever built the site, both reachable on launch day. Scrambling to find them while the site is down wastes the first and worst hour.
The first week after launch
Real visitors find things testing never will, so the week after launch is part of the launch.
Watch these
- Enquiries actually arriving, by checking with whoever answers them rather than assuming.
- 404 errors, in analytics and Search Console, which reveal the redirects you missed.
- Indexing, confirming pages are appearing in search rather than being ignored.
- Speed on mobile, once real traffic and real caching are involved.
- Anything people mention, including the offhand comment that something looked odd, which is usually a real defect.
- Your own inbox filters, in case form mail is arriving and being filed automatically.
Then schedule the first maintenance check for a month out. New sites drift fastest in the first quarter, as content is added by people who were not there for the build. Our piece on what website maintenance covers explains what that ongoing work actually involves.
Tell your existing customers the site is new, in whatever channel you already use, and ask two or three of them to look at it and say what is unclear. Customers notice different things from staff: a service they thought you offered that is not listed, a price they expected to see, a question the site does not answer. That feedback in the first fortnight is worth more than another round of internal review, and it costs one email.
Mistakes that turn a launch into a rescue
The recurring ones
- Launching with the staging block on. Invisible to search, sometimes for months.
- No redirect map on a rebuild. Handing back search visibility you already paid for.
- Never testing a form from outside. The lead that never arrived is the one you never knew about.
- Changing DNS without recording the old records. A website problem becomes an email outage.
- Placeholder content left in place. Lorem ipsum in the footer, demo testimonials on the homepage.
- Launching on a Friday. A weekend of live problems and nobody available.
- Treating launch as the finish line. The first week is when the real defects surface.
Launching or replacing a website soon?
We build and manage small business websites, including the unglamorous parts of a launch: redirects, forms, tracking and the checks that stop a rebuild costing you enquiries.
Frequently asked questions
What should I check before launching a website?
Content accuracy and no placeholder text, every form and phone number tested end to end, the site working properly on a phone, search basics including that indexing is not blocked, analytics installed, redirects mapped if you are replacing a site, and legal pages, backups and security in place.
What is the most common launch mistake?
Going live with the staging site’s indexing block still in place, so search engines are told to ignore the site. The second most common is launching a rebuild without redirecting the old addresses.
Do I need redirects if I am replacing my old website?
Yes, if the addresses change. Every old URL should redirect permanently to its closest equivalent, not all to the homepage. Without that you lose the search visibility and the inbound links the old pages had.
How do I know my contact form works?
Submit it yourself from a device that is not yours, on mobile data, and confirm the message arrives in the inbox someone actually watches. Check the spam folder too, and read the auto-reply the sender receives.
When is the best time to launch?
Tuesday or Wednesday morning, so the week is available for fixes with everyone still working. Avoid Friday afternoons and the day before you go away.
Should I launch a site that is not completely finished?
Usually yes, provided the money path works and nothing is misleading. A working site earning enquiries beats a perfect one still in draft, as long as you have listed what remains and set a date for it.
Will changing my website affect my email?
It can, because the same DNS settings control both. Record the current records before you change anything, confirm which provider handles your mail, and make sure those records survive the move.
What should I do in the first week after launch?
Watch that enquiries are arriving, check 404 errors and indexing, look at mobile speed with real traffic, and act on anything visitors mention. Then book the first maintenance check for a month later.