21+ years in hosting · Jaipur, India · INR billing with 18% GST · 24/7 email support
Blog · WebJi® India

Website Launch Checklist

Quick answer

Run a website launch checklist twice: once on staging, once on the live domain after DNS moves. It covers DNS TTL, SSL on the hostname you publish, working forms and mail, 301 redirects for old URLs, a phone-width layout, analytics, and a backup you have restored once. What is left unchecked is what breaks publicly.

For site owners and agencies shipping a site in India: what to verify on staging, on launch day, and in the first week after the domain moves.

✓ In business since 2005
✓ INR + GST billing
✓ 24/7 Email Support — avg reply < 60 min
GuideWebJi®
knowledge
Read time
3 min
Sections
6
Updated
14 Nov 2026
Written by
WebJi® team

What must be true before launch day?

Before launch day, the site must pass seven checks on staging: a phone-width layout, a tested contact form, working 301 redirects, no noindex tag or staging password, a backup restored once, SSL on both hostnames, and DNS TTL already lowered. Lowering the TTL to 300 seconds a day early is the one preparation most teams skip — it turns a rollback from a waiting game into a five-minute fix.

  • Mobile layout: menu, form and gallery work on a phone over mobile data, not only on office Wi-Fi.
  • Contact form: a test message arrives in a mailbox someone opens, with a usable reply-to.
  • Old URLs: every promised old path returns exactly one 301 to its replacement — test each with a redirect checker.
  • noindex and staging password: gone from the page source and the response headers.
  • Backup: files and database captured, and restored once on a staging copy. A backup never restored is a file, not a plan.
  • SSL: the padlock shows on both www and non-www; the www choice itself is explained in www versus non-www.
  • DNS TTL: dropped to 300 seconds at least a day before the switch.

Certificate problems caught here are cheap; the same problems on launch evening are not. If SSL misbehaves on staging, the SSL not-working guide walks the usual causes before they become public.

What do you do on launch day, in order?

Launch day runs in one order: move DNS, wait for the new host to answer, remove the noindex tag and staging password, submit the sitemap, verify analytics, then test the form from a phone on mobile data. Doing these out of order is how a staging hostname gets indexed or an analytics-less day gets lost.

  1. Switch the record: point the A record (or CNAME) at the new host; keep the old record until the new IP answers from two networks.
  2. Verify resolution: check the site from two connections — phone data and a second network — not one office line.
  3. Open the site: remove the noindex tag and the staging password so the public page is the live page.
  4. Submit the sitemap: in Search Console, once; the full sequence is in how to submit your website to Google.
  5. Confirm analytics: the real-time report shows your own visit on the live domain — a tag installed only on staging sees nothing.
  6. Test the form: send one real message from the phone over mobile data and reply to it.

Propagation usually settles within a few hours once the TTL is low, but a resolver that cached the old record can hold it for up to 48 hours. Keep the old host alive for those 48 hours, and do not schedule the launch promotion for launch evening.

What do you watch in the first week?

In the first week, four signals tell you the launch held: the 404 log, uptime alerts, form mail arriving, and real traffic in analytics. Search Console's coverage and security reports settle within days rather than hours, so read them once at the end of the week instead of refreshing them hourly.

  • 404 log: no inbound link should land on a missing page — every one is a redirect you forgot.
  • Uptime: the monitor should show no downtime alert since the switch.
  • Form mail: real enquiries reach the inbox, not just your test message.
  • Indexing: the homepage and key pages move from Discovered to Indexed; the security report stays empty.

After the first week the work turns into routine upkeep — updates, backups, content — whose INR budget is covered in website maintenance cost in India. The recurring hardening list for WordPress specifically sits in the WordPress security checklist.

The full website launch checklist by stage

The complete list runs in three stages — before launch, launch day, first week — and every row names the evidence that proves it passed, so nothing is ticked from memory. Print it or paste it into the project ticket; a row without evidence is a row not done.

Website launch checklist by stage, with the evidence for each check
StageCheckHow you know it passed
Before launchMobile layoutMenu, form and gallery work on a phone over mobile data
Before launchContact formTest message arrives with one usable reply-to
Before launchOld URLsEach old path returns one 301 to the replacement
Before launchnoindex and staging passwordNeither appears in page source or headers
Before launchBackupFiles and database restored once on a staging copy
Before launchSSLPadlock on both www and non-www hostnames
Before launchDNS TTLTTL at 300 seconds at least a day before the switch
Launch dayDNS switchNew IP answers from two networks
Launch daySitemapSubmitted in Search Console, fetched without error
Launch dayAnalyticsReal-time report shows your own visit on the live domain
Launch dayForm retestOne message sent from mobile data arrives
First week404 logNo inbound link lands on a missing page
First weekUptimeNo downtime alert since the switch
First weekIndexingKey pages Indexed; security report empty

Which launch mistakes cost the most?

The expensive launch mistakes are the ones that burn money or index the wrong page: promoting before DNS settles, cancelling the old host too early, and leaving a staging copy indexable. Each is a five-minute check that becomes a week of cleanup when skipped.

  • Promoting on launch evening: ads and email go out while some resolvers still show the old host or nothing.
  • www left unredirected: both hostnames resolve, so ranking signals and analytics split in two.
  • Forms to an unread mailbox: the form works, the enquiry dies in an inbox nobody opens.
  • Old host cancelled on day one: resolvers holding the old record for up to 48 hours serve errors.
  • Indexed staging hostname: the staging copy competes with the real launch page until it is deindexed.

If the build itself is still on paper, website design services is the commercial page, and the boundary between this content product and a logged-in tool is drawn in website versus web application. For a handover to an agency, ask for this checklist completed — with evidence — as part of the delivery.

FAQ

Frequently asked questions

Should the staging site stay noindex until launch?

Yes. Keep the staging copy noindex and password-protected until the live domain answers, then remove both on launch day. An indexed staging hostname competes with the real page and can keep both out of results until it is cleaned up.

How long does DNS propagation take after a launch?

Usually a few hours once the TTL is already at 300 seconds. Resolvers that cached the old record can legally hold it for up to 48 hours, so keep the old host serving for two days and delay paid promotion until the new IP answers from two networks.

When should analytics be installed?

Before launch, but verified after it. A tag installed only on staging never sees a public visitor, so the launch-day step is confirming the real-time report shows your own visit on the live domain — not installing the tag from scratch.

What if an old URL has no replacement page?

Redirect it to the closest living page — usually the category or the homepage — rather than leaving a 404. A 301 to something relevant keeps the link working; a 404 throws the visitor and any link value away.

Can we launch on a weekend?

Technically yes — DNS does not keep office hours — but avoid Friday-evening switches. Launch when the people who can fix a form or a certificate are reachable, and hold the promotion until the 48-hour resolver window has passed.

Last editorial update: 15 November 2026.

WebJi® since 2005

Ready to get started with WebJi®?

Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.