TL;DR
A website launch checklist prevents the errors that tank your SEO, break your forms, and scare off visitors on day one. This guide covers 40 steps across seven categories -- content, SEO, performance, security, analytics, accessibility, and post-launch monitoring. Start working through it two to four weeks before go-live, not the night before. The biggest launch-day disasters (lost rankings, broken redirects, staging noindex tags going live) are all preventable with a systematic pre-launch process.
A website launch checklist is the difference between a smooth go-live and a week of scrambling to fix broken pages, missing redirects, and tanked search rankings. Every launch mistake costs real money -- either in lost traffic, lost leads, or emergency developer hours.
I run Verlua, a web design and development agency that has launched over 80 websites for small businesses, contractors, and professional firms. Every project runs through a standardized checklist before the DNS switch. This post is that checklist -- the same one we use internally, written for business owners and developers who want to launch without the usual fires.
According to HTTP Archive, the median website in 2025 loads 2.2 MB of resources and takes 4.7 seconds to become interactive on mobile. Most of those sites launched without a proper checklist. A structured pre-launch process catches the performance, SEO, and usability issues that separate sites that rank and convert from sites that just... exist.
Why Does a Website Launch Checklist Matter?
A website launch is a one-shot event with compounding consequences. Get it right, and Google starts indexing clean pages with proper schema and fast load times from day one. Get it wrong, and you spend weeks cleaning up 404 errors, resubmitting sitemaps, and explaining to the client why their phone stopped ringing.
The most expensive launch mistakes are not the ones you notice immediately. A missing 301 redirect from an old URL with 200 inbound links does not trigger an error page for you -- it triggers a 404 for every visitor clicking those links. A staging noindex tag that ships to production does not look broken in the browser. It just silently tells Google to ignore your entire site.
What a Missed Checklist Costs
- Lost rankings: Broken redirects can drop organic traffic 30 to 60% overnight, according to Google's redirect documentation
- Lost leads: A broken contact form on launch day means every visitor who tried to reach you bounced instead
- Emergency dev costs: Fixing launch issues under pressure costs two to three times more than catching them in staging
- Brand damage: Placeholder text, broken images, and Lorem Ipsum on a live site tells visitors you do not care about details
- Delayed indexing: Missing sitemaps and misconfigured robots.txt can delay Google indexing by weeks
If you are redesigning an existing site, the stakes are even higher. See our website redesign checklist for the full migration-specific process and our website migration SEO checklist for preserving search equity during the transition.
Content Quality Checklist (7 Items)
Content issues are the easiest to miss and the most embarrassing when visitors find them. Placeholder text, broken images, and inconsistent messaging tell Google and your visitors that the site is not finished -- even if technically everything works.
| # | Check | Why It Matters |
|---|---|---|
| 1 | Remove all placeholder text | Lorem Ipsum on a live site destroys credibility instantly |
| 2 | Spell-check and proofread every page | Typos erode trust, especially on service and pricing pages |
| 3 | Verify all images load correctly | Broken images return 404s that waste crawl budget |
| 4 | Test every form submission | A broken contact form means zero leads from day one |
| 5 | Click every internal link | Broken internal links hurt SEO and frustrate visitors |
| 6 | Verify phone numbers and email addresses | Wrong contact info sends leads to a dead end or a competitor |
| 7 | Check CTAs on every page | Every page needs a clear next step -- call, form, or click |
A good rule of thumb: if you would not hand a printed copy of the page to a prospective client, it is not ready to go live. For a deeper dive into writing pages that actually convert, see our website copywriting guide and the service page copywriting guide.
SEO and Metadata Checklist (8 Items)
SEO mistakes at launch are expensive because they compound. A missing title tag does not just cost you one day of traffic -- it costs you every day until someone catches it. These eight items protect the organic visibility you have been building (or will build) through content and link acquisition.
The 8 SEO Items to Verify Before Launch
- Unique title tags on every page. Each page needs its own title under 60 characters with the primary keyword front-loaded. Duplicate titles confuse Google about which page to rank. Use our on-page SEO checklist as a reference.
- Meta descriptions written for click-through. Under 160 characters, include the primary keyword, and give searchers a reason to click. Pages without meta descriptions let Google auto-generate one -- and Google usually picks the wrong text.
- XML sitemap generated and accessible. Your sitemap should live at
/sitemap.xmland include every indexable page. Exclude staging URLs, admin pages, and anything behind authentication. - Robots.txt configured correctly. Confirm it allows crawling of all public pages and blocks only what should be hidden (admin, staging, API endpoints). A single misplaced
Disallow: /blocks your entire site. - Canonical URLs set on every page. Self-referencing canonical tags prevent duplicate content issues when URLs have query parameters, trailing slashes, or www/non-www variants.
- 301 redirects mapped for every old URL. If this is a redesign or migration, every old URL with traffic or inbound links needs a redirect to its new equivalent. See our website redesign SEO guide for the full redirect mapping process.
- Schema markup implemented. At minimum, add Organization, LocalBusiness (if applicable), and BreadcrumbList schema. Blog posts need Article schema. Our schema markup guide walks through every type.
- Remove noindex tags from production. This is the single most common catastrophic launch error. Staging environments often have
<meta name="robots" content="noindex">to prevent Google from indexing test pages. If that tag ships to production, Google will deindex your entire site within days.
Pro Tip
After launch, open Google Search Console and submit your sitemap URL within the first hour. Then use the URL Inspection tool to manually request indexing of your homepage and top five service pages. This cuts the time to first indexing from days down to hours. Our Google Search Console guide covers the full setup process.
How Fast Is Fast Enough? Performance Checklist (6 Items)
Page speed directly affects both rankings and conversions. Google uses Core Web Vitals as a ranking signal, and according to Google Web.dev, pages that pass all three Core Web Vitals thresholds rank higher in mobile search results. Slow pages also lose visitors: a site that loads in 1 second converts three times better than one that loads in 5 seconds, per Portent's load time study.
6 Performance Checks Before Launch
- Run Google PageSpeed Insights on mobile. Target 90+ on mobile for every key page. Desktop scores are less important because Google uses mobile-first indexing.
- Optimize all images. Compress to WebP or AVIF format, set explicit width and height attributes to prevent layout shift, and lazy-load below-the-fold images.
- Verify Largest Contentful Paint under 2.5 seconds. LCP is usually your hero image or main heading. Preload the LCP resource and use a CDN to serve it fast.
- Check Interaction to Next Paint under 200ms. INP replaced First Input Delay in March 2024. Heavy JavaScript, unoptimized event handlers, and third-party scripts are the usual culprits.
- Confirm Cumulative Layout Shift under 0.1. Set dimensions on images and embeds, avoid inserting content above the fold after page load, and use font-display: swap for web fonts.
- Test on a real mobile device over cellular. Lab tools like Lighthouse simulate throttled connections, but nothing replaces loading your site on an actual phone over 4G. Emulators miss real-world bottlenecks like DNS resolution delays and carrier-level compression.
For the full technical breakdown of Core Web Vitals, see our Core Web Vitals guide. For image-specific optimization, the website speed optimization guide covers compression, lazy loading, and CDN configuration in detail.
Is Your Site Secure Before Launch? (5 Items)
Security at launch is not just about preventing hacks -- it is about trust signals that affect both rankings and conversions. Google has used HTTPS as a ranking signal since 2014, and browsers now show "Not Secure" warnings on any page served over HTTP. A missing SSL certificate on launch day tells every visitor your site is not safe.
5 Security Checks Before Go-Live
- 1.SSL certificate installed and forcing HTTPS. Every page should redirect HTTP to HTTPS automatically. Check for mixed content warnings where HTTPS pages load HTTP resources (images, scripts, fonts).
- 2.Remove staging credentials and test accounts. Default admin passwords, test user accounts, and exposed API keys get found by automated scanners within hours of going live.
- 3.Set security headers. At minimum, configure Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security headers. These prevent cross-site scripting, clickjacking, and MIME type attacks.
- 4.Verify form spam protection. Add reCAPTCHA, hCaptcha, or honeypot fields to every form. Without protection, your inbox will fill with spam within the first week and real leads will get buried.
- 5.Back up everything before DNS switch. Take a complete backup of the old site (files, database, DNS records) before changing anything. If the launch goes wrong, you need a rollback plan that takes minutes, not hours.
For a complete security baseline, see our website security essentials guide, which covers ongoing monitoring, automatic updates, and incident response plans for small business sites.
Planning a website launch and want a professional team to handle the checklist? Verlua runs every project through a 40-point quality assurance process before go-live. We catch the SEO, speed, and security issues that most agencies skip.
Get a Free Launch ReviewAnalytics and Tracking Checklist (5 Items)
Analytics set up after launch means lost data from your most critical period -- the first days when you need to identify what is working and what is not. Configure tracking before launch so you capture day-one behavior.
5 Analytics Items to Configure Pre-Launch
- Google Analytics 4 installed and verified. Confirm the GA4 tag fires on every page, not just the homepage. Use the Real-Time report to verify. Our GA4 guide covers setup from scratch.
- Conversion events configured. Set up event tracking for form submissions, phone number clicks (tel: links), and any other actions that represent a lead or sale. Without conversion tracking, you are flying blind on ROI.
- Google Search Console verified. Add your domain in Search Console before launch. Submit the sitemap immediately after the DNS switch. This is how you monitor indexing status, keyword rankings, and crawl errors.
- Heatmap tool installed. Microsoft Clarity is free and takes five minutes to set up. Heatmaps show you where visitors actually click, how far they scroll, and where they drop off -- data that analytics alone cannot provide.
- UTM parameter strategy documented. If you run paid ads, email campaigns, or social media traffic, set up UTM parameters before launch so you can attribute leads to the correct channel from day one.
For measuring the business impact of your site, our website ROI measurement guide walks through the formulas and KPIs that actually matter for small businesses.
Accessibility Checklist (5 Items)
Web accessibility is not optional in 2026. The Department of Justice has confirmed that the ADA applies to websites, and ADA-related lawsuits topped 4,000 in 2024 according to UsableNet. Beyond legal risk, accessible sites serve more visitors and rank better because Google rewards clean, semantic HTML.
5 Accessibility Checks for Launch
- Alt text on every image. Descriptive alt text helps screen readers and boosts image SEO. Decorative images get empty alt attributes (
alt=""). - Keyboard navigation works on every page. Tab through the entire site without a mouse. Every link, button, and form field should be reachable and operable with keyboard alone.
- Color contrast meets WCAG AA standards. Text must have a contrast ratio of at least 4.5:1 against its background. Use the WebAIM contrast checker to verify.
- Heading hierarchy is logical. One H1 per page, H2s for main sections, H3s for subsections. Never skip heading levels (H2 followed by H4). Screen readers use headings to navigate page structure.
- Form labels are associated with inputs. Every form field needs a visible
<label>element connected with theforattribute. Placeholder text is not a substitute for labels.
For the complete accessibility picture including WCAG 2.2 compliance, see our web accessibility guide and the ADA website compliance 2026 guide for legal requirements.
Pro Tip
Run a quick automated scan with the free WAVE Web Accessibility Evaluation Tool on every page before launch. It catches low-hanging issues like missing alt text, empty links, and contrast failures in seconds. Automated tools catch about 30% of accessibility issues -- the other 70% requires manual testing with a keyboard and screen reader.
What Should You Monitor After Launch? (4 Items)
Launching is not the finish line. The first two weeks after go-live are when most hidden problems surface. Real users behave differently than test users, and search engines take time to crawl and index your new pages. Active monitoring during this window catches issues before they compound.
4 Post-Launch Monitoring Tasks
- Monitor Google Search Console daily for the first two weeks. Watch for crawl errors, indexing issues, and any pages flagged as "Excluded." The Coverage report shows exactly which pages Google is and is not indexing.
- Check GA4 for traffic anomalies. Compare day-one traffic to pre-launch baselines. A sudden drop signals a redirect issue or indexing problem. A sudden spike on a 404 page means a broken link is getting hit.
- Test forms and CTAs again with real traffic. Some form issues only appear under production conditions -- email deliverability failures, CORS errors on API endpoints, rate limiting on your hosting provider. Send yourself a test submission every day for the first week.
- Monitor page speed with real user data. Lab scores (Lighthouse) are synthetic. Once real visitors hit your site, check the Core Web Vitals Experience report in Search Console for field data. This typically takes 28 days to accumulate enough data points.
For ongoing website health, our website maintenance guide covers the weekly, monthly, and quarterly checks that keep a site performing after the launch excitement fades.
What Does the Launch Day Protocol Look Like?
Launch day is about execution, not discovery. If you have been working through the checklist for two to four weeks, launch day itself should feel anticlimactic. Here is the sequence we follow at Verlua for every client launch.
Launch Day Sequence (In Order)
- Take a final backup of the old site (files, database, DNS snapshot)
- Verify the staging environment one last time -- run through all seven checklist categories
- Switch DNS records to point to the new hosting
- Verify SSL certificate is active on the production domain
- Test the live site on mobile and desktop (different browser, incognito mode)
- Submit the XML sitemap to Google Search Console
- Request indexing of the homepage, top service pages, and contact page
- Verify GA4 Real-Time report shows active sessions
- Submit a test form and call the phone number on the site
- Share the launch with your team and start post-launch monitoring
DNS propagation typically takes 15 minutes to 48 hours depending on the registrar and TTL settings. Set your DNS TTL to 300 seconds (5 minutes) at least 24 hours before launch to speed up propagation. If you are migrating from an old site, see the website build timeline guide for how launch day fits into the overall project schedule.
Real Scenario: The Noindex Disaster
A roofing contractor came to us after launching a new WordPress site with a different agency. Traffic dropped 80% within two weeks. The previous agency had left the WordPress "Discourage search engines from indexing this site" checkbox active from their staging setup. Every page on the site had a noindex meta tag.
It took three weeks for Google to fully re-index the site after the tag was removed. During that time, the contractor estimated losing 15 to 20 phone leads -- roughly $12,000 to $16,000 in potential revenue for a roofing company. A single checkbox on a launch checklist would have prevented it.
What Are the Best Tools for Pre-Launch Quality Assurance?
You do not need expensive software to run a thorough pre-launch check. These free and low-cost tools cover 90% of what a professional QA process requires.
| Tool | Category | Cost | What It Checks |
|---|---|---|---|
| Google PageSpeed Insights | Performance | Free | Core Web Vitals, load time, optimization suggestions |
| Google Search Console | SEO | Free | Indexing, crawl errors, sitemap submission, keyword data |
| WAVE | Accessibility | Free | WCAG compliance, contrast, alt text, ARIA labels |
| Screaming Frog | Technical SEO | Free (500 URLs) | Broken links, duplicate titles, missing meta, redirects |
| Microsoft Clarity | Analytics | Free | Heatmaps, session recordings, scroll depth, rage clicks |
| SSL Labs | Security | Free | SSL certificate validation, protocol configuration, grade |
Screaming Frog is the single most useful tool on this list for a pre-launch crawl. Point it at your staging URL and it will find every broken link, missing title tag, duplicate meta description, and redirect chain on the site in minutes. The free version covers up to 500 URLs, which is enough for most small business websites. For a full guide on technical SEO auditing, see our technical SEO audit and fix plan.
Frequently Asked Questions
How long before launch should I start a website launch checklist?
Start the pre-launch checklist two to four weeks before your planned go-live date. Technical items like SSL setup, redirect mapping, and analytics configuration need time to test. Rushing through a checklist in a single afternoon virtually guarantees you will miss something that hurts SEO or breaks the user experience on day one.
What is the most common mistake during a website launch?
Forgetting to set up 301 redirects from old URLs to new ones. This single mistake can wipe out months or years of accumulated search rankings overnight. Every URL that existed on your old site and has inbound links or organic traffic needs a redirect to the equivalent page on the new site. The second most common mistake is launching with a noindex tag still active from the staging environment.
Do I need to notify Google when I launch a new website?
Yes. Submit your XML sitemap through Google Search Console immediately after launch. You should also use the URL Inspection tool to request indexing of your most important pages -- homepage, service pages, and contact page. Google will discover your site eventually through links and crawling, but manual submission speeds the process from days or weeks down to hours.
Should I launch my website on a Friday?
No. Launch on a Tuesday or Wednesday morning. If something breaks, your development team is available to fix it the same day. A Friday launch means bugs discovered over the weekend sit unfixed for two to three days while potential customers hit errors. Tuesday also gives you a full work week to monitor analytics, fix edge cases, and handle the initial wave of real user traffic.
What analytics should I set up before launching a website?
At minimum, set up Google Analytics 4 with conversion events for form submissions and phone clicks, Google Search Console for indexing and keyword monitoring, and a heatmap tool like Microsoft Clarity for user behavior insights. Configure these at least one week before launch so you can verify data is flowing correctly in the staging environment before real traffic arrives.
How do I check if my website is ready for launch?
Run through four categories: technical (SSL, redirects, sitemap, robots.txt, Core Web Vitals), content (spell check, placeholder text removed, images optimized with alt text), SEO (title tags, meta descriptions, schema markup, canonical URLs), and legal (privacy policy, cookie consent, terms of service). Test every form, button, and link on both desktop and mobile. Load the site on a real phone over cellular data, not just your office WiFi.
Need Help Launching Your Website the Right Way?
Verlua builds custom websites for small businesses, contractors, and professional firms -- and every project goes through our full 40-point launch checklist before go-live. We handle the SEO, speed optimization, security, and analytics setup so nothing slips through the cracks. Based in Sacramento, serving clients nationwide.
Founder & Technical Director
Mark Shvaya runs Verlua, a Sacramento web design and development studio. He builds Next.js lead-generation sites for contractors, home service businesses, and professional firms across the Sacramento metro area.
California real estate broker, property manager, and founder of Verlua.
Stay Updated
Get the latest insights on web development, AI, and digital strategy delivered to your inbox.
No spam, unsubscribe anytime. We respect your privacy.