Published · 6 min read · By the Digiboy team
Before a website goes live, check ten areas: content, mobile, speed, SEO, analytics, forms, legal pages, security and backups, redirects from the old site, and a plan for the first week. The 25 checks below cover all of them. Most take a few minutes each, and a missed one, such as a contact form that sends enquiries nowhere, can cost weeks of business before anyone notices.
How to use this checklist
Go through it twice: once about a week before launch, so there is time to fix things, and once on launch day on the live address. Your developer should do the technical checks. You should do the visible ones yourself, on your own phone.
| Group | Checks | Who usually does it |
|---|---|---|
| Content | 1 to 3 | Owner |
| Mobile | 4 to 6 | Owner and developer |
| Speed | 7 to 8 | Developer |
| SEO | 9 to 12 | Developer |
| Analytics and Search Console | 13 to 14 | Developer |
| Forms | 15 to 16 | Owner and developer |
| Legal pages | 17 to 18 | Owner |
| Security and backups | 19 to 21 | Developer |
| Redirects | 22 to 23 | Developer |
| After launch | 24 to 25 | Both |
Content
- Read every page aloud. Look for spelling mistakes, old prices, and placeholder text such as “Lorem ipsum” or “Your text here”. Check Malayalam text separately if the site has it, because fonts and line breaks can go wrong.
- Confirm the contact details. Phone number, WhatsApp number, email, address and opening hours must be correct and must match your Google Business Profile exactly.
- Check the images. Use only photographs you own or have a licence for. Each important image should have alt text, a short written description that helps screen readers and search engines.
Mobile
- Test on a real mid-range phone on mobile data. Not only on the developer’s laptop or the office Wi-Fi. Most of your visitors in Kerala will arrive this way.
- Tap every button. The call button should open the dialler, the WhatsApp button should open a chat with the right number, and the map link should open directions.
- Look for layout problems. Text should be readable without zooming, nothing should scroll sideways, and menus should open and close with a thumb.
Speed
- Run the main pages through pagespeed.web.dev. Read the mobile result. Aim for the main content to appear within about 2.5 seconds, which is Google’s threshold for a good Largest Contentful Paint.
- Compress the images. Oversized photographs are the most common cause of a slow page. Our article on website speed in Kerala explains what else to fix.
SEO
- Give every page its own title and meta description. These are the headline and summary shown in Google results. No two pages should share them.
- Use one main heading per page. The main heading, called the H1, should say plainly what the page is about.
- Allow search engines in. Development sites are often set to “noindex”, which tells Google to stay away. Remove that setting, check that the robots.txt file is not blocking the site, and make sure a sitemap, a file listing all your pages, exists.
- Add structured data. This is a small block of code that labels your business name, address, hours and services for search engines and AI assistants.
Analytics and Search Console
- Install analytics and track the actions that matter. Page views alone say little. Record calls, WhatsApp taps, form submissions and purchases.
- Verify the site in Google Search Console and submit the sitemap. Search Console is Google’s free tool that shows how your site appears in search and reports problems. Set it up in an account you own.
Forms
- Submit every form yourself. Confirm the enquiry reaches the right inbox and has not landed in spam. Then reply to it, to check that the reply address works.
- Check what the visitor sees. There should be a clear thank-you message after submitting, sensible error messages for missing fields, and spam protection so the inbox is not flooded.
Legal pages
- Publish a privacy policy and terms. If the site collects names, phone numbers or emails, say what you collect and why. This checklist is not legal advice. Ask a lawyer if your business handles sensitive data such as health records.
- Add selling policies if you take payments. Refund, cancellation and shipping policies are expected by customers and required by payment gateways. See how to accept UPI and card payments.
Security and backups
- Turn on HTTPS everywhere. The address should show a padlock, and the plain “http” version should redirect to the secure one.
- Tidy the logins. Use strong, unique passwords and two-step verification on the website admin, hosting and domain accounts. Delete test accounts and any developer logins no longer needed.
- Set up automatic backups and test one. A backup that has never been restored is only a hope. More in website security basics for small businesses.
Redirects when replacing an old site
- Map every old address to a new one. List the old site’s pages and set a 301 redirect, a permanent forwarding instruction, from each to its closest match on the new site. Without this, old Google results and links lead to error pages and rankings can drop.
- Protect your email. If the domain’s settings change at launch, check that the mail records are carried over. Send and receive a test message on your business email right after the switch.
The first week after launch
- Watch for errors daily. Check Search Console for pages that cannot be indexed, look for “page not found” errors, and confirm that enquiries are arriving at the usual rate or better.
- Update every place that links to you. Google Business Profile, Instagram and Facebook bios, WhatsApp Business profile, email signatures, visiting cards and printed QR codes. Then ask two or three people outside the project to use the site and tell you where they got stuck.
What happens after the checklist?
A website needs regular care after launch: updates, backups, renewals and small content changes. Agree in writing who does this and what it costs. Our guide to website maintenance cost in India gives typical figures.
Where Digiboy fits
Every site we build goes through these checks before launch, including testing on mid-range phones and slow connections, and is followed by a short warranty period. See our web development service or read about our process.
Questions people ask
What should I check before launching a website?
Before launching a website, check that the content is final, the site works on a phone, pages load quickly, search engines are allowed to index it, analytics is recording, forms deliver enquiries, legal pages are present, HTTPS is on and backups are running.
What is a 301 redirect and why does it matter at launch?
A 301 redirect is a permanent instruction that sends visitors and search engines from an old page address to a new one. At launch, 301 redirects stop old links and Google results from leading to error pages when a new site replaces an old one.
How long after launch will my website appear on Google?
A new website can appear on Google within a few days to a few weeks after launch. Verifying the site in Google Search Console and submitting a sitemap helps Google find the pages sooner, though ranking well for competitive searches takes longer.
Which day is best to launch a website?
The best day to launch a website is early in a working week, in the morning, when the people who built it are available to fix problems. Avoid launching just before a weekend, a holiday or a major sale.
Who should run the website launch checklist, the agency or the owner?
The agency or developer should run the full website launch checklist, and the business owner should repeat the visible checks personally. The owner is the best person to spot a wrong phone number, an old price or a missing service.




