Website Launch Checklist: What to Check Before Your New Site Goes Live

Why a Launch Checklist Matters More Than the Go-Live Date

Many Malaysian SME owners treat a website launch as a single moment: the day the developer points the domain at the new site and it goes live. In reality, that technical switch is the easy part. What actually determines whether the new site brings in enquiries is everything that happens in the days before and after: whether the forms work, whether Google can find the pages, whether the site loads properly on a mid-range phone in Shah Alam or Melaka, and whether anything important got left behind from the old site.

A proper checklist forces you to slow down at the exact point in the project where mistakes are cheapest to fix and most expensive to ignore. Skip it and you risk weeks of quietly lost leads: a contact form that silently fails, a missing redirect that drops your best-ranking page from Google overnight, or a WhatsApp button that dials the wrong number. None of these throw an error message. They just show up later as fewer calls and fewer enquiries, with no obvious cause.

• Contact form fails quietly and nobody is copied on the submission
• Old page URLs return a 404 instead of redirecting to the new equivalent page
• The new site is never submitted to Google Search Console, so indexing stalls for weeks
• The mobile menu, forms or checkout break on Android but nobody actually tested them

Content and Legal Pages Every Site Needs Before Go-Live

Before anything technical, walk through every page as a stranger would. You need a clear homepage, an about page that explains who you are and where you operate from, a services or products page, a working contact page, and a privacy policy that reflects how you actually collect and use customer data under Malaysia's PDPA. If the site takes online payments or bookings, add terms of service too. These are not optional extras; missing legal pages are one of the first things a cautious customer or a due-diligence-minded B2B buyer will look for.

Proofread every page for leftover placeholder text. It is surprisingly common for a site to go live with a stray paragraph of lorem ipsum, a template company name from a demo theme, or a phone number copied from a different client's project. Double-check your registered business name, SSM number if you display one, both office addresses if you operate from Shah Alam and Melaka, and your opening hours. Small factual errors like these undermine trust the moment a visitor notices them, and they often go unnoticed by the same team that has been staring at the draft for weeks.

On-Page SEO Basics Before You Launch

Every page should have a unique title tag and meta description written for the page's actual topic and Malaysian search intent, not a generic template repeated across the whole site. Each page needs exactly one H1 heading, a logical heading structure below it, and a URL that is short and descriptive rather than a string of numbers or parameters. If ranking on Google is the whole point of the new site, this is also the moment to line the page structure up with a proper keyword plan rather than bolting SEO on afterwards; our SEO and Google ranking service exists precisely because most sites are built first and optimised as an afterthought.

Check that internal links between related pages actually exist and use descriptive anchor text rather than generic 'click here' links. New sites launched from a template often end up with thin or missing internal linking, which makes it harder for both visitors and Google to understand how your pages relate to each other. A quick audit of every main page, confirming it links to at least two or three other relevant pages on the site, catches most of this before launch.

• Unique, keyword-relevant title tag and meta description on every page
• One H1 per page, with a logical H2 and H3 structure beneath it
• Short, descriptive URLs instead of default CMS slugs or query strings
• Working internal links between related service, product and blog pages

Site Speed and Core Web Vitals Testing

Run the finished site through Google PageSpeed Insights or a similar tool before you launch, not after a customer complains. Compress and convert large images to WebP, remove unused plugins or scripts that the developer forgot to strip out of the final build, and check that fonts and third-party embeds are not silently slowing the page down. A slow site does not just frustrate visitors; Core Web Vitals are a confirmed part of how Google evaluates page experience, so a sluggish launch can hold back rankings from day one.

Test on an actual mobile connection, not just office Wi-Fi. Malaysian mobile coverage varies a lot between a shoplot in central Shah Alam and an industrial area on the outskirts of Melaka, and a site that feels instant on fibre broadband can feel painfully slow on a patchy 4G connection. If speed testing turns up serious problems this late in the project, it usually means the build needs another pass rather than a quick patch, so budget a few days for this before the go-live date is locked in.

Mobile Responsiveness and Cross-Device Testing

The majority of traffic to most Malaysian SME websites now comes from mobile phones, so mobile is not a secondary check, it is the primary one. Open the site on a few different real devices, not just a browser's device-simulation mode, and check that menus open and close properly, tap targets are large enough for a thumb, and text is readable without pinching to zoom. Pay particular attention to tables, pricing grids and image galleries, which are the elements most likely to break or overflow on a smaller screen.

Forms deserve extra attention on mobile because that is where the most enquiries are lost. Test filling in every field with a phone keyboard, confirm dropdowns and date pickers work properly on both iOS and Android, and check that the confirmation message actually appears after submission instead of leaving the visitor unsure whether anything happened. A form that works perfectly on desktop but silently fails on mobile is one of the most common and most invisible launch mistakes.

Broken Links, 404s and Redirect Mapping

If the new site is replacing an existing one, this step alone can make or break months of previous SEO work. Every old URL that has earned backlinks, social shares or search rankings needs a 301 redirect to its closest equivalent page on the new site. Skipping this step during a redesign is one of the fastest ways to lose rankings overnight, which is exactly the mistake we cover in more detail in our guide to redesigning a website without losing your SEO rankings.

Run a link checker across the finished site before launch to catch broken internal links, missing images and dead outbound links to old partner or supplier pages. It only takes a few minutes and it catches problems that are otherwise very easy to miss when you have been looking at the same site in a staging environment for weeks.

Forms, Enquiries and Lead Capture Testing

Every form on the site, whether it is a contact form, a quote request, a newsletter signup or a job application form, needs to be tested as a real submission, not just glanced at in the page editor. Submit each one yourself and confirm that the notification email actually arrives, that any autoresponder fires correctly, and that the data lands in the right inbox or CRM rather than an account nobody checks. It is common for a form to be quietly misconfigured after a migration, sending enquiries into a spam folder or an inbox that was decommissioned months ago.

Also test every click-to-call and click-to-WhatsApp button to confirm they dial the correct number. These small details are the actual conversion points of the entire website, and a single wrong digit can silently cost you every enquiry that would have come through that channel until someone finally notices and reports it.

SSL, HTTPS and Basic Security Before Go-Live

Confirm the SSL certificate is installed correctly and that the entire site loads over HTTPS with no mixed-content warnings from old http image or script references. Decide on one consistent version of the domain, either www or non-www, and make sure every other variation redirects to it, rather than leaving both versions live and splitting your SEO signals between two addresses. Our guide to website maintenance for Malaysian SMEs covers the ongoing side of this once the site is live.

If the site runs on WordPress or another CMS, update the core software, theme and every plugin to their latest versions before launch, remove any unused plugins entirely, and set a strong, unique admin password rather than reusing one from another account. These basic steps close off the majority of the opportunistic attacks that hit small business websites, and they take far less time than recovering a hacked site after the fact.

Google Search Console and Sitemap Submission

Verify the domain in Google Search Console before or immediately after launch, submit the sitemap.xml file, and use the URL inspection tool to request indexing for your most important pages rather than waiting passively for Google to find them on its own schedule. Our full Google Search Console guide walks through property verification and submission in more detail if this is your first time setting it up.

Over the following days, check Search Console for coverage errors, mobile usability issues and any manual actions. Catching a crawl error or a blocked page in the first week is far easier to fix than discovering three months later that an entire section of the site was accidentally excluded from Google's index by a leftover staging-site setting.

Google Analytics 4 and Conversion Tracking

Install GA4 before the site goes live, not weeks afterwards, so that you have baseline traffic data from day one instead of a gap in your history right when it matters most. Set up key events for the actions that actually matter to the business: form submissions, WhatsApp clicks, phone number clicks and, if relevant, add-to-cart or purchase events. Our GA4 guide for Malaysian SMEs covers the setup process in full if analytics is new territory for your team.

Before trusting any of this data, use GA4's DebugView to confirm that events are actually firing correctly when you test them yourself. It is common for a tracking setup to look correct in the configuration screen but silently fail to fire in practice, which means weeks of decisions could end up based on incomplete data if nobody checks it at launch.

Google Business Profile and Local SEO Signals

Make sure your business name, address and phone number on the new website match your Google Business Profile exactly, down to the unit number and phone number format. Inconsistent details between your website and your Google listing are a well-documented drag on local search rankings, and they are easy to overlook when a new website goes live with slightly different formatting than what was on the old one.

Update the website link on your Google Business Profile to point to the new site as soon as it goes live, and if you operate from both a Shah Alam headquarters and a Melaka office, confirm both locations are represented correctly, whether that means two listings or a single listing with both addresses clearly stated on the contact page.

Schema Markup and Structured Data

Add Organization or LocalBusiness schema, breadcrumb schema, and FAQ schema on pages where you have genuine frequently asked questions, then validate all of it with a structured data testing tool before launch rather than after. Structured data will not fix a poorly built website, but it gives Google and AI-driven answer engines like ChatGPT, Gemini and Perplexity a much clearer, machine-readable picture of who you are, what you offer and where you operate, which increasingly matters for both traditional search results and AI-generated answers.

Keep the schema accurate and up to date after launch too. Stale structured data, such as an old address or an outdated phone number left in the schema markup even after the visible page content was updated, can actively confuse search engines rather than help them.

Backups and a Rollback Plan

Before touching DNS or pushing the new build to production, take a full backup of the old site, its database and its media files, and confirm you actually know how to restore from that backup if something goes wrong. This sounds obvious but it is one of the most commonly skipped steps under launch-day time pressure, and it is the single thing that turns a stressful launch mistake into a five-minute fix instead of a multi-day outage.

Schedule the actual DNS switch for a quieter period rather than the middle of your peak trading hours, and monitor uptime closely for the first 24 to 48 hours afterwards. If your team does not have the in-house capacity to manage this properly, our onsite IT support in Shah Alam team can handle the technical side of a launch window so you are not troubleshooting DNS propagation issues in the middle of a business day.

Browser, Email and Third-Party Integration Testing

Open the finished site in Chrome, Safari and Edge, and check it on both Android and iOS, since rendering quirks between browsers are still common enough to catch real bugs before customers do. If the site sends transactional emails, such as a booking confirmation or a quote request acknowledgement, send yourself a real test email and check that it lands in the inbox rather than the spam folder, since a misconfigured sender domain can quietly route every automated email straight into junk.

Test every third-party integration end to end: booking widgets, payment gateways, live chat plugins and WhatsApp click-to-chat buttons. Each of these depends on a script loading correctly and an API key being configured properly, and any one of them can silently fail after a migration even when the rest of the site looks completely normal.

The First 30 Days After Launch: What to Monitor

Expect a short-term dip in rankings for some pages in the first one to two weeks after a relaunch, especially if the site structure or URLs changed meaningfully. This is normal and usually recovers once Google finishes re-crawling and re-indexing the new site, provided the redirects and technical basics covered above were handled correctly. Resist the urge to make large, reactive changes in week one based on a few days of unusual data.

Instead, watch Search Console daily for the first two weeks for coverage errors or indexing issues, check GA4 for traffic and conversion patterns weekly, and fix problems as they surface rather than waiting for a monthly review. A website launch is the start of the site's working life, not the finish line of the project, and the businesses that keep improving it steadily tend to outrank the ones that launch once and never touch it again.

Key Takeaways

• Treat launch day as the middle of the project, not the end, with checks both before and after go-live
• Map every old URL to a 301 redirect if you are replacing an existing site, to protect existing rankings
• Test every form and click-to-call or WhatsApp button as a real submission, not just a visual check
• Install GA4 and submit to Google Search Console before or immediately at launch, not weeks later
• Keep monitoring for at least 30 days after launch instead of treating go-live as finished work