Skip to content

Websites · 8 min read

The website launch checklist we use before going live

The pre-launch and post-launch checks our team runs on every site: content, redirects, technical SEO, Core Web Vitals, tracking, DNS and email.

Published · By Kumar, QuantumPlug Technologies LLP

Hand ticking off items on a handwritten checklist in a notebook with a pen

A safe website launch comes down to checking five areas in order — content and legal pages, technical SEO, performance, tracking, and the cut-over itself — then watching the site closely for the first month. Most launch disasters we are asked to fix come from a handful of avoidable mistakes: a staging ‘noindex’ left switched on, old URLs that no longer redirect, contact forms that silently fail, or email that stops working after a DNS change. This is the checklist our team works through before and after every launch, written so that you can use it whether we built your site or not.

Two weeks before launch: content, forms and legal pages

Start with what visitors will actually read. Every page should have final, proofread copy — no placeholder text, no ‘coming soon’ sections, no stock phrases left over from a template. Check that your business name, address, phone number, WhatsApp number and email are identical everywhere they appear, because inconsistencies confuse both customers and search engines.

Test every form and contact route end to end. Submit each form and confirm the message reaches the right inbox or CRM, that the autoresponder (if any) reads well, and that spam protection is not blocking real enquiries. Tap every phone and WhatsApp link on a real mobile phone.

Legal and accessibility basics belong in this phase too. You will usually need a privacy policy that reflects how you actually collect and use data — under India’s Digital Personal Data Protection Act, the GDPR in the UK and EU, or other local rules depending on your audience — plus cookie consent where the law requires it. Check that images have meaningful alt text, text has enough contrast, and the site can be navigated with a keyboard.

  • Final, proofread copy on every page
  • Consistent business name, address and contact details
  • Every form tested to a real inbox, with spam protection checked
  • Privacy policy, terms and cookie consent where required
  • Alt text, colour contrast and keyboard navigation checked
  • Favicon, social sharing images and 404 page in place

Technical SEO: the checks that protect your rankings

If you are replacing an existing site, the redirect map is the most important document in the whole launch. Export every URL the old site has — from its sitemap, a crawl, analytics and the top pages in Search Console — and map each one to its closest equivalent on the new site with a permanent (301) redirect. Avoid chains where one redirect points to another, and update internal links to point straight to final URLs.

Then check indexability. Staging sites are normally hidden from search engines with a noindex tag, a robots.txt rule or password protection, and forgetting to remove these at launch is one of the most common and most damaging mistakes. Equally, make sure pages you do want hidden — thank-you pages, internal search results, test pages — are set to noindex.

Every page should have a unique title and meta description, one clear main heading and a correct canonical tag. Generate an XML sitemap containing only live, indexable URLs and reference it in robots.txt. If you serve several countries or languages, check hreflang annotations carefully, and make sure any structured data matches what is visible on the page.

  • Complete 301 redirect map from every old URL
  • No leftover noindex tags, robots.txt blocks or password protection
  • Unique titles, meta descriptions and canonical tags
  • Clean XML sitemap referenced in robots.txt
  • HTTP and non-preferred hostname redirect to one HTTPS version

Performance and Core Web Vitals

Google’s Core Web Vitals measure loading, responsiveness and visual stability. Google’s published thresholds for a good experience are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, assessed at the 75th percentile of real visits. Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024, and it is the metric most often hurt by heavy scripts.

Before launch you only have lab data from tools such as Lighthouse and PageSpeed Insights. Use it to catch the usual culprits: oversized images, too many web fonts, render-blocking scripts, and third-party widgets such as chat tools, review badges and tracking tags. Test on a mid-range Android phone over a mobile connection, not just on a fast office laptop — that is how a large share of customers, particularly in India, will see your site.

After launch, real-user field data starts appearing in Search Console and PageSpeed Insights once enough visits have been recorded. That is the data that reflects actual experience, so plan a performance review a few weeks after go-live.

Tracking, analytics and consent

A launch without working measurement throws away the most useful data you will ever have about the new site. Set up Google Analytics 4 with the events that matter to your business — form submissions, calls, WhatsApp clicks, bookings or purchases — marked as key events, and verify each one fires correctly using the debug tools before go-live.

Verify the site in Google Search Console, ideally as a domain property using a DNS record so that every version of the site is covered, and in Bing Webmaster Tools. If you run ads, confirm that Google Ads conversion tracking and the Meta pixel, preferably with the Conversions API, are recording the right events with correct values.

Where consent rules apply, such as for visitors in the UK and EU, your consent banner must actually control whether tracking tags fire, and Google’s consent mode should be configured to match. Finally, note the launch date in your analytics so that future comparisons make sense, and save a copy of the old site’s key metrics as a baseline.

Launch day: the cut-over

Plan the switch for a quiet period in your business week, with the people who can fix problems available afterwards — which is why we avoid Friday evening launches. A day or two beforehand, lower the time-to-live on the DNS records you will change so the switch propagates quickly. Take full backups of the old site and its database, and freeze content changes on the old site.

The most overlooked risk on launch day is email. If your domain’s DNS is moving to a new provider, make sure your MX, SPF, DKIM and DMARC records are copied across exactly; otherwise email can stop arriving or start landing in spam, and nobody notices until a customer complains. Check any other records too, such as those used for domain verification by Google, Microsoft or Meta.

Once DNS has switched, confirm the SSL certificate is valid on every hostname, test the redirects from the old URLs, submit a form, place a test order if it is a store, and browse the site on a phone using mobile data.

  • Lower DNS time-to-live in advance
  • Back up the old site and database
  • Copy MX, SPF, DKIM, DMARC and verification records exactly
  • Confirm SSL on all hostnames
  • Test redirects, forms, checkout and key journeys on mobile
  • Keep the old site available privately until you are sure

The first 30 days after launch

Submit the new sitemap in Search Console and use URL Inspection to request indexing of your most important pages. Then check the Pages report regularly for the first few weeks, looking for unexpected exclusions, pages blocked by noindex, and spikes in not-found errors that point to missing redirects. Crawl the live site with an SEO crawler to catch broken links and redirect chains.

Some fluctuation in search traffic after a redesign or migration is normal while Google recrawls and reprocesses the site. A sharp, sustained drop usually has a specific cause — missing redirects, accidental noindex, removed content or changed internal linking — and is far easier to fix in week one than in month three.

Finally, update everything that points to your website from elsewhere: Google Business Profile, social media profiles, directory listings, email signatures and, where you can, important links from partner sites. Set up uptime monitoring so you hear about outages before your customers do.

Launching a website safely is less about heroics on the day and more about disciplined checking beforehand and close watching afterwards. Work through content, technical SEO, performance, tracking and the cut-over in order, protect your email and redirects, and give the new site a month of attention. Most of the problems that hurt businesses after a launch are ones a checklist like this would have caught.

Common questions

Will a website redesign hurt my SEO?

A redesign does not have to hurt SEO, but a careless one often does. The usual causes are missing redirects from old URLs, removed or thinner content, changed internal links and leftover noindex tags. With a complete redirect map and the same or better content, most sites settle after a period of normal fluctuation.

How long does it take Google to index a new website?

Important pages are often indexed within days to a few weeks, but there is no guaranteed timeline. Submitting a sitemap and requesting indexing for key pages in Search Console helps, as do links from your existing profiles and partner sites. Google states that indexing is never guaranteed.

Should I launch a website on a Friday?

It is best avoided. If something breaks — email, forms, redirects or checkout — you want the people who can fix it available the next day. A quiet weekday morning gives you a full working day to spot and fix problems.

Do I need an XML sitemap?

For most business websites, yes. Google says small, well-linked sites may not strictly need one, but a sitemap helps search engines discover pages and gives you a reference list to monitor in Search Console. Include only live, indexable URLs.

What should I do with my old website after launch?

Keep a full backup and, if possible, a private copy of the old site for a few weeks so you can check content or recover anything missed. Do not leave the old site publicly accessible on another domain or subdomain, as duplicate content can confuse search engines and visitors.

All insights