Before launching a business website, make sure the important customer journey works, the business information is correct, the domain is under control and search engines can actually discover the site. The launch checklist matters more than squeezing in one final animation.
Most launch problems are mundane.
The phone number is wrong.
The contact form sends nowhere.
The site looks good on a laptop but the main button disappears on a phone.
The new domain works, but Google still sees the temporary address.
Those are the things worth finding before customers do.
Read the site like a customer
Do not begin the final review by inspecting margins.
Begin by pretending you know nothing about the company.
Can you understand what the business does within a few seconds?
Can you find the main service?
Can you tell where the business operates?
Can you contact it without hunting?
If the answer to any of those is no, the website is not ready simply because the design is finished.
Check every business detail
A wrong phone number is more damaging than a slightly imperfect layout.
Read the site for factual accuracy: business name, phone, email, address or service area, opening hours, prices, service descriptions and any claims about qualifications or experience.
If the website and Google Business Profile disagree, fix that too.
Your website should reinforce your other business information, not create a second version of reality.
Test the actual enquiry journey
Submit the contact form yourself.
Do not just look at it.
Make sure the message arrives at the right inbox and that the confirmation shown to the customer makes sense.
Test phone links on a phone. Test WhatsApp buttons. Test booking links. If there is a payment route, go through it as far as practical.
A call-to-action that looks beautiful but does not work is decoration.
Look at the site on a real phone
Responsive design is not a box to tick.
Use the site with your thumb.
Read the text.
Open the menu.
Tap the buttons.
Check that images are not cutting off important details and that forms are not painful to complete.
For many local businesses, the phone version is the website most customers will actually experience.
Worth knowing
Domain ownership is one of those boring details that only becomes interesting when something goes wrong. I think the business should know where its domain is registered, whose account it sits in and how it would regain access if the designer disappeared. Launch day is the right time to make sure that is clear — not two years later when someone needs to move the site.
Make sure you control the domain
Know where the domain is registered and who has access to the account.
The business should ideally own and control it.
If somebody else registered it for you, confirm the arrangement before launch rather than when you eventually want to move provider.
A normal domain is usually a modest annual cost; the more important issue is ownership. I explain both in my guide to domain name costs in Ireland.
Search setup should be part of launch, not an afterthought
A new site should have clear page titles, sensible headings, crawlable links and a canonical version of each important page.
The XML sitemap should contain the URLs you actually want indexed, and the robots configuration should not accidentally block the site.
Google Search Console should be set up so you can monitor indexing and search performance.
None of that guarantees rankings.
It simply makes sure you are not launching with avoidable technical obstacles.
I have separate guides planned on getting a business website on Google, XML sitemaps and Google Search Console. Those links should only become live once the relevant guides are published.
Check the final domain, not only the preview
Development URLs are useful during the build.
They should not become the main address search engines and customers continue to find after launch.
Make sure internal links, canonical URLs, social-sharing metadata and sitemap URLs refer to the real production domain where appropriate.
If both www and non-www versions exist, choose the intended canonical version and redirect consistently.
The same principle applies to HTTP versus HTTPS.
One business. One clear primary web address.
Analytics: measure something useful
If you want to know whether the site is working, install analytics before you begin sending traffic.
Page views are useful, but the better question is whether people do the things the website exists to encourage.
That could be a contact-form submission, a phone click, a WhatsApp click or a booking action.
You do not need a giant analytics implementation for a five-page local-business site.
You do need enough measurement to distinguish "people visited" from "the site generated interest".
What about privacy and cookies?
The website should reflect the tools it actually uses.
If you collect personal information through forms, use analytics, embed third-party services or set non-essential cookies, the privacy/cookie setup needs to match reality and applicable requirements.
Do not copy a random privacy policy from another business and assume the job is done.
For legal specifics, use appropriate legal or data-protection guidance rather than relying on a web designer to invent legal advice.
Check how the site looks when shared
Paste the homepage into the places customers might actually encounter it.
A good social preview should have an appropriate title, description and image where the platform supports them.
This is particularly useful when you plan to share the site on Facebook, LinkedIn, WhatsApp or local groups.
A broken preview can make a polished launch look unfinished.
Gavin's take
I do not treat launch as the moment a website becomes "finished forever". It is the point where we finally get real evidence: what people search for, which pages they visit, what questions still come up and whether the enquiry route works. I would much rather launch a strong, focused site and improve it from real behaviour than delay indefinitely trying to predict every future requirement.
Launch is the start of the evidence
Do not expect Google rankings to appear instantly.
Do not assume the first version of every headline is perfect.
Once the site is live you can see:
- which pages receive impressions,
- which searches bring visitors,
- what people click,
- which questions customers still ask,
- which content is worth adding.
That evidence should guide the next improvements.
This is much healthier than endlessly delaying launch while trying to predict everything in advance.
How I think about launch at Built by Gavin
I want the site technically tidy, easy to understand and ready to measure.
I do not want launch turned into a months-long ceremony.
A custom small-business website should go live when the important pieces are right. We can improve and expand it as the business produces real information.
That includes adding useful Guides, local pages or service pages later when there is a genuine reason to do so.
A practical final check
A short checklist is useful here because this is one of the few places where a list genuinely earns its keep:
- the main phone/email/form works;
- mobile navigation and calls to action work;
- business details are correct;
- the production domain and HTTPS work;
- canonical URLs and sitemap use the intended domain;
- Search Console and analytics are connected where required;
- privacy/cookie handling matches the site's actual tools;
- key pages have useful titles and descriptions;
- there are no obvious broken links;
- somebody other than the person who built it has tried to use it.
Then launch.
Ready to put the business online?
You can see my website options and pricing or tell me what you need to launch.
A good launch should feel organised, not mysterious.
---