The useful answer first.
Before launch, confirm your business details, domain access, essential content, and the action visitors should take. Then test the website on real phones, check enquiries reach your team, and assign responsibility for updates. Treat this as a website checklist, separate from business registration or licensing.
What affects the answer?
What needs to be ready, and when
| When | Practical checks |
|---|---|
| Before design | Confirm the name, audience, offer, page list, domain, and main contact route. |
| Before the build is finished | Supply approved text, images, prices, translations, and integration access. |
| Before publishing | Review mobile pages, forms, booking links, page titles, privacy information, and account ownership. |
| On launch day | Check the live domain, delivery of enquiries, map links, and the information customers will use. |
| After opening | Review real questions, update hours and availability, and fix anything that is confusing visitors. |
Your business is opening before the full site is ready
Publish a focused page with a clear opening date, what you offer, the location, and a tested contact route. Mark anything that is not yet available honestly. A menu or price list should reflect what customers can actually buy. Add the fuller site when its content and functions have been checked.
Put important accounts in the right hands
Keep control of the domain registration, business email, website access, and any booking or payment accounts. Record who owns each account, who can administer it, and when it renews. Use appropriate account security and a recovery method the business can access.
An agency can manage services for you without becoming the only person who can recover them. Ask for a handover document that explains responsibilities. Keep credentials in a password manager rather than scattering them through chat messages.
Build a small content folder
Collect the approved business name, logo files, contact details, address, opening hours, service descriptions, and original photographs. Note which images you have permission to use. Provide clear filenames and captions when the subject is not obvious.
If you serve Thai and English readers, decide which pages need both languages and who approves each version. Check prices, dates, units, and booking conditions carefully across translations. Avoid putting essential text inside images where it becomes difficult to update or read on a small screen.
Walk through the website as a new customer
Open the site on a phone and try the most important task without using your own knowledge of the business. Can you find the address, understand the offer, and send an enquiry? Are buttons large enough to tap, and can the form be completed without guessing what went wrong?
Check the real destination of every contact, map, booking, and payment link. Test a successful form submission and an invalid one. Confirm the staff notification arrives, and remove sample text, placeholder prices, and test contact details before the site is made public.
Prepare discovery and ongoing care
Give each important page a clear title and description. Ask your developer to check indexing settings, canonical URLs, and the sitemap. After launch, use Search Console to inspect the main pages and submit the sitemap. Submission helps discovery; it does not promise that Google will index every page or rank it immediately.
For eligible local businesses, keep your Google Business Profile consistent with the website. Assign someone to update holiday hours, respond to enquiries, and review service information. Agree how backups, software updates, and urgent problems are handled rather than leaving them until something breaks.
- 01Information
Accurate and approved
- 02Customer journey
Tested on a real phone
- 03Ownership
Accounts and support ready
What should be included?
- Domain and recovery access confirmed
- Opening details and prices approved
- Image permissions checked
- Both languages reviewed where needed
- Forms and external links tested
- Search settings and sitemap checked
- Privacy information reflects the site
- Update and support owners named
When a simpler option may be enough
You can open with a small site when its information is useful and accurate. Leave unfinished features out of the navigation, and keep a written list of what will follow.
Questions worth asking
- 01Which details are still likely to change before opening?
- 02Who owns the domain and can recover the accounts?
- 03Has someone outside the project tested an enquiry?
- 04Who is responsible for updates after launch?
How we approach it
We include launch checks and handover in the website project. The aim is to leave the business with a working site and a clear understanding of what needs attention afterwards.
See selected workShort answers
Do I need every page ready before opening?
No. Publish the essential information and customer actions first, as long as the page accurately describes what is available.
Should we submit a sitemap to Google?
Yes, it is a useful discovery signal. You can submit it through Search Console, but Google decides when to crawl and index pages.
Is this a business registration checklist?
No. This guide covers the website. Registration, permits, tax, and other business requirements need separate advice appropriate to your operation.
What should we check after the first week?
Confirm enquiries are arriving, review questions customers still ask, and check hours, prices, and booking information against actual operations.