Skip to content
All articles
Web Development9 min read

Website launch checklist: what to check before go-live

A website launch checklist for business owners: forms, redirects from old URLs, noindex left on staging, sitemaps, previews, speed on a real phone and rollback.

EK

EK Ra Sunya team

EK Ra Sunya Inc.

A website launch checklist is short, and it runs in a set order. Check that every form submits and its email arrives. Redirect the old site's URLs with 301s. Remove the staging noindex. Verify Search Console and submit the sitemap. Then check titles, share previews, analytics, speed on a real phone, backups, admin access, the 404 page and a rollback plan.

None of this is design work. It's the plumbing that decides whether the new site keeps the old one's enquiries and search traffic. You don't need to run the checks yourself, but you should see each one done.

This list assumes the site has already been through user acceptance testing and you've signed off on how it looks and works. If you haven't, do that first; our UAT checklist before sign-off covers it. Launch checks come after.

Does every form work, end to end?

A form that looks fine and sends nothing is one of the costliest launch bugs, because it can go unnoticed for weeks. Test each form on the live domain, not on staging, because email settings often change between the two.

For every form (contact, quote request, booking, newsletter, careers):

  • Submit it with real-looking data and confirm the email reaches the inbox it should. Check spam too.
  • Confirm the person filling it in sees a thank-you page or message, not a blank screen or the same form again.
  • If the form saves to a database or CRM, check the entry is there.
  • Submit it once from a phone on mobile data, not office Wi-Fi.

Then tap every phone number and email link.

Have the old site's URLs been redirected?

If you're replacing an existing site, this check protects your search traffic. Old pages have links from Google, other sites and customers' bookmarks. If the new site uses different addresses, those visitors hit a 404.

Google's guidance on moving a site with URL changes is plain about what to do. Make a map of old URLs to new ones, starting with your most important pages, and set up server-side permanent (301) redirects from each old URL to its new one. It also warns against sending lots of old URLs to one unrelated page such as the home page, and says to keep the redirects for at least a year.

Ask for the redirect map as a spreadsheet, then test ten old URLs yourself. Each should land on the matching new page in one hop. Google also says to expect rankings to move around for a while after a move, so a dip in the first weeks isn't by itself a sign something broke.

While you're on addresses, check the site loads on HTTPS with a valid padlock, and that the http:// and www versions redirect to the one address you've chosen. The domain switch itself is a DNS change; plan when it happens and who makes it.

Is the staging noindex gone?

Staging sites are usually hidden from Google with a noindex rule, and that rule can travel to production with everything else. The site launches, works perfectly, and never appears in search.

Google's page on blocking indexing with noindex describes the two places it lives: a <meta name="robots" content="noindex"> tag in the page head, or an X-Robots-Tag HTTP header. Your developer should confirm both are gone from public pages. You can check the first one yourself: open a page, view the source and search for "noindex".

Check robots.txt too (yourdomain/robots.txt). A staging line like Disallow: / blocks crawling of the whole site. And note Google's warning: if robots.txt blocks a page, Google never sees its noindex tag. On a live site, public pages should be crawlable and indexable, full stop.

Is Search Console set up and the sitemap submitted?

Search Console is how you'll find out later that something went wrong. Set it up at launch.

  1. Verify the property. Google offers several methods, including an HTML tag, an uploaded file and a DNS record. A Domain property covers http, https and every subdomain, but needs the DNS record, and Google says not to remove that record after verification. If you're moving from an old site, verify both.
  2. Submit the sitemap. Most platforms generate one at /sitemap.xml. Google's sitemap guide says to submit it in the Sitemaps report, or add a Sitemap: line to robots.txt. Do both. Google calls a sitemap a hint, so it speeds discovery but doesn't guarantee indexing.
  3. Make sure the account is yours. Search Console should be owned by a company Google account, with the developer added as a user. Not the other way round.

Does each page have a title, a description and a share preview?

Open a few pages and look at the browser tab. Each page needs its own title, not "Home" or the theme's default on every tab. Then check the meta description in the page source. Google says it uses the description only sometimes, and that identical descriptions on every page aren't helpful, so write one per important page.

Then share a page link in WhatsApp, Facebook Messenger or LinkedIn and look at the card. That card comes from Open Graph tags. The Open Graph protocol lists four required properties: og:title, og:type, og:image and og:url. A missing image gives a blank card. Test the home page, a service page and a blog post.

If the site is in English and Nepali, check both language versions have their own titles and previews. Our post on building a Nepali-language website covers the bilingual setup.

Open the site in a private window, click around, and check your visits appear in the analytics real-time view. If the old site had analytics, note the switch date so you can compare before and after.

If the site shows a cookie or consent banner, test that it does what it says. Decline, then check in the browser's developer tools (or ask your developer to show you) that tracking scripts didn't load. Whether you need a banner at all depends on your visitors and what you collect, and that's a question for whoever advises you on privacy. The developer's job is making the banner work.

How fast is it on a real phone?

Test on an ordinary phone on mobile data, not the developer's laptop. Google's Core Web Vitals give the targets: web.dev sets "good" thresholds of a Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads.

At launch you won't have real-user data yet, so lab tools like Lighthouse are a starting point. web.dev notes lab results aren't a substitute for field data, so look again in Search Console's Core Web Vitals report once real visitors arrive. Meanwhile, the phone test catches the obvious: a slow hero image, a menu that won't open, buttons that jump. Run the accessibility checks in the same sitting.

Who has admin access, and where are the backups?

Before launch day, write down:

ItemWhat to confirm
CMS adminWho has an admin login, and that your company holds at least one
Developer accountsWhich ones will be removed or downgraded after launch
BackupsTaken automatically, stored off the server, and restored once as a test
Search Console, analyticsOwned by a company account, not a personal one
404 pageExists, helps people find their way, and returns a real 404 status

The status matters. Google drops pages returning 404 from its index, which is right for pages that are gone, while error pages returning a success code show up as "soft 404" errors in Search Console. Type a made-up address on your domain and see what happens.

What is the rollback plan?

Decide before launch what happens if the new site breaks badly on day one. Keep the old site and its files intact, somewhere you can switch back to, until the new one has run cleanly for a while. Know who makes the switch, how long it takes, and who decides to pull it. Launch on a day when that person is reachable, which usually rules out a Friday evening.

A rollback plan you never use is cheap. Discovering you have none while customers see an error page is not.

Frequently asked questions

How long before a new website appears in Google?

There's no fixed time. Submitting the sitemap and verifying Search Console help Google find the pages, but Google calls a sitemap a hint, not a guarantee. Use the URL Inspection tool in Search Console to see whether a given page is indexed.

Do I need a new sitemap if I only changed the design?

If URLs didn't change, just confirm the sitemap loads and lists only live pages. If URLs changed, submit the new sitemap in Search Console.

Can launch checks happen after go-live?

Some can, such as Core Web Vitals field data. Forms, redirects and the noindex check can't wait, because each one fails silently and costs enquiries or traffic every day it's wrong.

Launching a new site

Our web development team builds business websites and web apps for clients in Nepal and Australia. If your site is close to go-live, or you want a second pair of eyes on the launch, tell us where it stands.

Have a project in mind?

Let us help you build something scalable, fast, and built to last.

Start a conversation