The developer says the site is ready. The owner looks at the home page on a laptop, likes it, and says go. A month later someone notices that the contact form has been sending enquiries to an address nobody reads. Launching is not the moment the design is approved. It is a short list of dull checks, and each one protects an enquiry.
Before launch: content
- Every page has its final text. No placeholder paragraphs, no sample names, no dummy phone number.
- Phone, WhatsApp number, email and address are the same on every page and match your Google listing.
- Photos are your own or licensed, compressed, and described in their alt text.
- Prices, timings and delivery areas, where shown, are current.
- Privacy and terms pages exist if the site collects personal details or takes orders.
- A not-found page offers the menu and a way to contact you.
Before launch: enquiries that arrive
This is the check that is skipped most and matters most. Send a real message through every form, from a phone, and confirm three things: the visitor sees a clear thank-you, the email lands in an inbox that someone opens daily, and it does not go to spam. Tap every WhatsApp button and phone link as well. On a site like Hadie's Crust, a Karachi bakery website whose online orders are sent by email, that email is the whole point of the site.
Before launch: phones and search
| Check | What to look for | Why it matters |
|---|---|---|
| Mobile layout | Every page on a small phone and a large one, with menus and buttons easy to tap | Phones are where customers will see it |
| Speed | Home and main service page tested on mobile data | A slow first page loses the visit |
| Titles and descriptions | A different title and description on every page | This is what shows in Google results |
| Main heading | One clear heading that says what the page is about | It helps readers and search engines alike |
| Sitemap and robots file | The sitemap lists the real pages; the robots file blocks nothing important | They tell Google what to read |
| Secure address | The padlock shows, and the non-secure address redirects to it | Browsers warn visitors otherwise |
| Analytics | Installed and recording your own test visit, behind a consent banner where needed | You cannot improve what you do not measure |
| Search Console | The domain verified under a company account | It is where Google reports problems with your pages |
Before launch: who owns what
Ask for this in writing before the last payment. The domain should be registered in your company's name, with a login you hold. The same goes for the hosting account, the site's admin panel, analytics and Search Console. Use a company email address for all of them, not a staff member's personal one. If the domain sits in a former developer's personal account, getting your own website back can become a long chase.
The website launch checklist for the day itself
Pick a quiet time
Launch on a working morning, when your developer is at a desk and can fix what appears. Avoid the night before a campaign.
Take a backup
Save the old site, if there is one, and the new one as it stands.
Point the domain and publish
Switch the domain to the new site and confirm the secure address works with and without www.
Open the site to Google
Remove any test-site password and noindex setting, then look at the page source to be sure.
Submit the sitemap
Add it in Search Console and inspect the home page there.
Test every form again
On the live domain, from a phone, including the WhatsApp and call buttons.
Check old addresses
If this replaces an older site, confirm that old pages redirect to their new ones.
Tell people
Update the link on your Google listing, social profiles, email signatures and printed material.
Replacing an existing site carries extra risk for rankings. Follow how to redesign a website without losing SEO alongside this list.
The first four weeks
| When | What to check | What to do with it |
|---|---|---|
| Week one | Enquiries arriving, Search Console errors, pages on different phones | Fix anything broken the same day |
| Week two | Which pages Google has indexed, and any it has skipped | Request indexing for important pages; fix thin or duplicate ones |
| Week three | Analytics: which pages people land on and where they leave | Rewrite the weakest opening paragraph; make the contact route more obvious |
| Week four | The searches that showed your site, speed on mobile, a working backup | Plan the next pages from real searches; set the maintenance routine |
After week four the site moves from launch to upkeep. Our guide to website maintenance after launch gives the weekly, monthly and quarterly routine, and website speed and sales explains the speed checks.
Every site Operix builds under web development is set up for Google from the first day, and ongoing SEO services are available separately. If you have a site waiting to go live and want a second pair of eyes on it, get in touch.
Questions people ask
What should I check before launching a website?
Final content on every page, forms that deliver to a monitored inbox, the layout on phones, page titles, a sitemap, analytics and Search Console. Also confirm that the domain and hosting are in your company's name.
How soon after launch will my site appear on Google?
It varies, and nobody controls it. Submitting the sitemap in Search Console and requesting indexing for key pages helps Google find them. Ranking for competitive searches takes longer than being indexed.
Do I need Google Search Console for a small site?
Yes. It is free, it reports indexing problems on your pages, and it shows the searches that lead people to your site.
What is the most common launch mistake?
Leaving the test site's noindex setting switched on, so Google is told to ignore the new site. The second is a contact form that sends to the wrong address.
Who should hold the domain and hosting logins?
Your company. Register them with a company email address and keep the logins where two senior people can reach them. The developer can be given access without owning the accounts.
