Building Your First Business Website: Launch Checklist

You have spent weeks planning, designing, and building your site. The go-live moment feels close enough to taste. But the week before launch is exactly when avoidable mistakes get shipped: a contact form that delivers nowhere, a robots.txt file that blocks Google, or a phone number that hasn’t been updated since the first draft. This checklist consolidates every cross-check so nothing slips through.

Work through it in order. Each section takes less than an hour on its own.

Before you start, confirm the groundwork from earlier in this series is in place: your security essentials (SSL certificate, hosting, backups) and your analytics configuration (GA4 and conversion events) should already be set up. This checklist verifies them, it does not set them up from scratch.

Content and copy checks

Placeholder text and outdated contact details are the most embarrassing things a visitor can find on launch day. Do a full read-through of every page before anything else.

Remove all placeholder text

Search every page for “lorem ipsum,” “coming soon,” “placeholder,” and “TBD.” Include footer boilerplate, form labels, email signature blocks, and any automated page templates. One orphaned placeholder on a service page will undermine everything else on the site.

Verify contact details

Test every phone number (call it), every email address (send a test), and every physical address (map it). If your business has multiple locations, check each one. A wrong phone number on a local service site in the Medical Center area, for example, means every call goes to a wrong number.

Confirm your legal pages are live and linked

A privacy policy and terms of service are required for most businesses running contact forms, collecting any user data, or using analytics. Both pages must be reachable from the footer on every page of the site. If you are using Google Analytics, your privacy policy must disclose that.

Technical checks

Test every form

Submit a test message through every form on the site: contact form, quote request, newsletter signup, checkout (if applicable). Confirm the submission delivers to the correct inbox or CRM. Check the confirmation message the user sees after submitting. A form that accepts input but delivers nowhere is worse than no form at all.

Configure your 404 page

Your 404 page is what visitors see when a URL doesn’t exist. A custom 404 page with a clear message, your navigation, and a link back to the homepage keeps visitors on your site instead of sending them back to Google.

Run a page speed test

Open Google PageSpeed Insights and test your homepage and at least one key service page on mobile. 53% of mobile visits are abandoned when a page takes more than three seconds to load, so address any flagged issues before launch, not after.

Confirm SSL is active and enforcing HTTPS

Your site should load at https:// by default. Type in http://yourdomain.com and confirm it redirects to the HTTPS version. Check for mixed-content warnings (a padlock icon with a warning or an “i” badge) which indicate some assets are still loading over HTTP.

SEO checks before go-live

Meta titles and descriptions on every page

Every page of the site needs a unique meta title (under 60 characters) and meta description (under 160 characters) that accurately describe the page’s content. These are what appear in Google search results. A page without a meta description gets a randomly excerpted sentence, which almost never represents the page well.

For a deeper treatment of on-page SEO items before you go live, see our guide to on-page optimization.

Submit your sitemap to Google Search Console

Google Search Console is a free tool from Google that lets you monitor search performance, submit your sitemap, and request indexing for new pages. After connecting your site as a property, navigate to the Sitemaps section and submit your sitemap URL (typically yourdomain.com/sitemap.xml). This tells Google the full structure of your site and accelerates initial indexing.

Review your robots.txt file

Your robots.txt file tells search engines which pages they can and cannot crawl. The most common pre-launch error is a site still running a “Disallow: /” instruction left over from the staging or development environment, which blocks Google from indexing anything. Open yourdomain.com/robots.txt and confirm it is not blocking your production pages.

Analytics and tracking confirmation

Verify GA4 is firing on all pages

Open your site in a browser, open Google Analytics in another tab, and check the Realtime report. Navigate through three or four pages on your site. Each page view should appear in Realtime. If you see nothing, your tracking code is either missing or incorrectly configured.

Confirm conversion events are tracking

Every form submission, phone number click, or purchase (if applicable) should fire a conversion event in GA4. Test each one and confirm the events appear. A site that goes live without conversion tracking is a site you cannot measure or improve.

Cross-device and cross-browser testing

Load the site on at least two physical devices: a desktop and a smartphone. Check that text is readable without zooming, buttons are tappable, navigation works, and images load at the right size. Then open the site in Chrome, Safari, Firefox, and Edge. Each browser renders CSS slightly differently.

Pay particular attention to your contact form on mobile. It is the highest-stakes interactive element on most small business sites, and the one most often broken on a small screen.

Domain and DNS: pointing correctly

If your domain was registered separately from your hosting, confirm DNS is fully propagated before you announce launch. Use a tool like whatsmydns.net to confirm your domain resolves correctly from multiple global locations. If DNS was recently changed, allow up to 48 hours for full propagation.

Using your website launch checklist on go-live day

When every item above is checked, publish the site. Then immediately:

1. Open your site and do a final walkthrough as a visitor would.
2. Confirm GA4 Realtime shows activity.
3. Submit your sitemap in Google Search Console if you have not already done so.
4. Test your contact form from a personal email address and confirm the submission arrives.
5. Check that your 404 page loads when you visit a nonsense URL on your domain.

For the next 48 hours, revisit Google Search Console daily for crawl errors and check your inbox for form submissions. Most problems surface within the first two days of real traffic.

The Monarch Patio and Outdoors site launched on a fixed timeline with every item on this list cleared in advance. The Naran Group real estate site went live without delays for the same reason. A checklist is not caution, it is process.

What comes next

A live site is a starting point, not a finish line. Part 10 covers the work that begins after launch: growing organic traffic, building your content strategy, and turning a new site into a reliable lead channel.

Up next: growing traffic after launch

When you’re ready to hand off the launch process entirely, our web design service covers every item on this checklist as part of how we deliver sites. Get in touch to talk through your project.

Frequently asked questions

What should be included in a website launch checklist?

A complete website launch checklist covers five areas: content (no placeholder text, accurate contact details, legal pages), technical (forms tested, SSL active, 404 page configured, page speed verified), SEO (meta titles and descriptions on every page, sitemap submitted, robots.txt not blocking search engines), analytics (GA4 firing on all pages, conversion events confirmed), and cross-device testing. Checking all five areas before go-live prevents problems that cost time and credibility to fix after the site is live.

How do I submit my website to Google?

Submit your website to Google using Google Search Console, a free tool from Google that lets you monitor search performance, submit your sitemap, and request indexing for new pages. Add your site as a property, verify ownership via a DNS record or HTML file, then navigate to the Sitemaps section and submit your sitemap URL. Google will typically begin crawling your site within a few days of submission.

How long does it take to launch a website?

The go-live process itself takes anywhere from a few minutes (flipping a staging site to production) to a few hours (if DNS propagation is involved). DNS changes can take up to 48 hours to fully propagate, though most updates resolve within a few hours. Budget the week before launch for working through the checklist systematically so there is no rush on go-live day.

What should I monitor in the first 48 hours after launch?

In the first 48 hours, check that GA4 is recording sessions, confirm contact forms are delivering to the right inbox, verify Google Search Console shows no crawl errors, and test the site on a phone. If you made any URL changes during the build, confirm your redirects are working correctly so visitors and search engines land on the right pages.