The Website Launch Checklist: Before, During, and After

Website launches rarely fail in dramatic ways. They fail in small, dull ones: a contact form that emails nobody, analytics installed a month late, a domain registered under a freelancer's personal account. Every item on this checklist exists because somebody, somewhere, skipped it and paid for it.

The list runs in three phases: before you build, while you build, and launch plus the weeks after. It applies whether you are assembling the site yourself over a weekend or handing a full project to a development team. Work top to bottom; the ordering is most of the value.

Phase 1: Before you build

• Define the site's one job. Enquiries, orders, bookings, or something else: everything on this list serves that goal, so write it down first.
• Register the domain in your own account, in your own name. Never let a developer or platform hold it for you. Our guide to choosing a domain name helps if you are still deciding.
• Choose hosting sized to the site, not to your ambition. A standard business site runs happily on shared hosting; you can upgrade later in an afternoon.
• Map the pages and name who writes each one. Missing content delays more launches than missing code.
• Gather brand assets in one folder: logo files, colours, fonts, photos, and the exact spellings of names and addresses.
• Decide now who maintains the site after launch: you, a staff member, or a paid arrangement.

Get the boring infrastructure right early

Three pieces of plumbing deserve attention before any design work: the domain, DNS access, and email. Make sure you hold the login for the domain account and know where its DNS is managed, because launch day is a DNS change and you do not want to be hunting for passwords then. If DNS still feels like magic words, our explainer on DNS records covers the handful you will actually touch.

Set up business email on your domain early too, so the contact form has a proper destination from day one. SSL is no longer a purchase decision: hosts like ShrotiHost include free Let's Encrypt certificates, so the only thing to check is that HTTPS actually works when the site goes live.

Phase 2: While you build

• Build on a staging or temporary URL and keep it out of Google with a noindex tag until launch. Remember to remove that tag on launch day.
• Check every page on a real phone, not just a shrunken browser window. Most of your visitors will arrive on mobile.
• Compress and resize images as you add them. Oversized images are the single most common cause of slow pages.
• Build the contact form early and test where submissions land, including the spam folder.
• Write a unique title and meta description for every page while the content is fresh in your head.
• Create the legal pages: a privacy policy at minimum, plus terms and a refund policy if you sell anything.
• Turn on backups before launch, not after. Daily backups are included on ShrotiHost plans, but confirm rather than assume, whoever hosts you.

Phase 3: The week before launch

• Click through every page and submit every form, on desktop and phone. Fix what you find before adding anything new.
• Confirm SSL works and that the site forces HTTPS, so no visitor lands on an insecure version.
• Install analytics and verify the site in Google Search Console. You cannot improve what you never measured.
• If this replaces an old site, list its URLs and set up redirects to the new pages so you keep your search rankings and inbound links.
• Add the small trust details: favicon, social sharing image, and a useful 404 page.
• Do a speed pass. Test key pages on a throttled mobile connection; if the site runs on WordPress, our guide to speeding up WordPress is the deeper checklist.

Launch day

If you are starting from zero rather than replacing a site, the full path from empty hosting account to live site is walked step by step in our guide to hosting a website in India.

• Point DNS at the live server during a quiet hour for your business, and expect up to a day of propagation for stragglers.
• Remove the noindex tag and submit your sitemap in Search Console.
• Test the site from a phone on mobile data, not just the office Wi-Fi that has cached everything.
• Send a real test through every form, and place a small real order if you sell online. Payment flows behave differently in production.
• Confirm the first backup of the live site actually ran.

The first month after launch

• Check Search Console weekly for crawl errors and pages Google could not index.
• Read the analytics with one question: where do visitors give up? Fix that page first.
• Collect typos, broken links, and confusing wording from early visitors and fix them in batches.
• Switch on auto-renew for the domain and hosting, and check the payment card on file will not expire soon. Expired domains take good websites offline every day.
• Apply software updates promptly if the site runs a CMS: core, themes, and plugins.

What never comes off the list

A website is not a project that ends, it is a small system that runs. Keep applying updates, keep backups running, and once in a while actually restore one to prove it works. A backup you have never restored is a hope, not a plan.

Revisit the content twice a year: prices, team, services, and photos drift out of date quietly, and stale content costs trust exactly when a customer is deciding whether to call you. If the maintenance side is the part you dread, that is a normal thing to hand off, and a fair question to ask whoever builds your next site before they start.

Frequently asked questions