The 27-Point Website Launch Checklist Every Business Needs

I’ve launched over 50 websites. The first few times, I missed things. Broken contact forms, missing favicon, analytics not tracking, 404 pages everywhere. Each launch taught me something new to check.

This is the checklist I actually use before every launch. Not a generic list — these are the 27 things that will bite you if you skip them.

Print it, bookmark it, share it with your developer. Going live without running through these is asking for trouble.

Pre-Launch: The Foundation (Points 1-8)

These are non-negotiable. If any of these fail, you’re not ready to launch.

1. SSL Certificate Is Active

Your site must load over HTTPS, not HTTP. Every page. No exceptions.

Check by visiting your site and looking for the padlock icon in the browser address bar. If you see “Not Secure,” stop everything and fix it. Google penalizes non-HTTPS sites, and visitors will bounce immediately.

Most modern hosts (Cloudflare, Netlify, Vercel) provide free SSL through Let’s Encrypt. There’s no excuse for launching without it in 2026.

2. Mobile Responsive on Real Devices

Don’t just check the mobile preview in your browser. Pull out your phone and actually browse the site.

Test on at least:

• An iPhone (Safari)
• An Android phone (Chrome)
• A tablet if your audience uses them

Check that text is readable without zooming, buttons are tappable with a thumb, forms are usable, and nothing overflows the screen horizontally. Google uses mobile-first indexing — your mobile experience is the one that determines your rankings. I covered why this matters in my mobile-first design guide.

3. Page Speed Passes Core Web Vitals

Run your site through Google PageSpeed Insights (pagespeed.web.dev). You want:

• LCP (Largest Contentful Paint): Under 2.5 seconds
• INP (Interaction to Next Paint): Under 200 milliseconds
• CLS (Cumulative Layout Shift): Under 0.1

Score below 90 on mobile? Optimize before launching. Common fixes: compress images, enable lazy loading, defer non-critical JavaScript, use a CDN. Page speed directly affects both rankings and conversions.

4. All Forms Submit and Deliver

Fill out every form on your site. Every single one. Verify:

• The form actually submits (no JavaScript errors)
• You receive the submission (check spam folders)
• The user sees a confirmation message or redirect
• Required field validation works
• The form doesn’t accept garbage data (empty submissions, invalid emails)

Broken contact forms are the number one post-launch issue I see. You could be losing leads for weeks before anyone notices. I’ve seen businesses lose thousands because a form silently stopped working after launch.

5. Analytics Are Installed and Tracking

Set up Google Analytics 4 (GA4) and verify it’s recording data before launch day. Install the tracking code, visit your site, and check the Real-Time report in GA4 to confirm your visit appears.

Also set up at least one conversion goal — typically your contact form submission or phone call click. Analytics without conversion tracking is like a dashboard with no speedometer.

If you’re new to analytics, my Google Analytics guide for small businesses walks through the full setup.

6. XML Sitemap Exists and Is Valid

Your sitemap tells search engines what pages exist on your site. Check that:

• It’s accessible at yourdomain.com/sitemap.xml
• It includes all important pages
• It doesn’t include pages you don’t want indexed (admin, staging, thank-you pages)
• The format is valid (use an XML sitemap validator)

Most CMS platforms and static site generators create sitemaps automatically, but verify it’s actually there and accurate.

7. Robots.txt Is Configured Correctly

Visit yourdomain.com/robots.txt. Make sure it’s not accidentally blocking search engines from your entire site. I’ve seen this happen more than once — a staging robots.txt that disallows all crawling gets pushed to production.

A basic robots.txt:

User-agent: *
Allow: /
Sitemap: https://yourdomain.com/sitemap.xml

8. Custom 404 Page Is Helpful

Visit a URL that doesn’t exist on your site (like yourdomain.com/thispagedoesnotexist). You should see a branded 404 page with:

• Your site navigation (so visitors can find their way)
• A search bar or links to popular pages
• A friendly message that isn’t the default server error

A generic “404 Not Found” page sends visitors straight to the back button.

Content: Get It Right Before Anyone Sees It (Points 9-15)

9. Every Page Is Proofread

Read every page out loud. Typos, grammatical errors, and placeholder text (“Lorem ipsum,” “Your text here”) destroy credibility faster than almost anything else.

Pay special attention to:

• Headlines and page titles (most visible)
• Contact information (wrong phone number is a disaster)
• Pricing (if listed)
• Team member names and titles

10. Images Are Optimized

Every image should be:

• Compressed (under 300KB for most images, under 100KB for thumbnails)
• Properly sized (don’t upload a 4000px image that displays at 800px)
• In modern format (WebP with JPG fallback)
• Named descriptively (team-photo-office.webp, not IMG_4392.webp)

Unoptimized images are the most common cause of slow page loads. One 5MB hero image can tank your entire PageSpeed score.

11. All Images Have Alt Tags

Every image needs a descriptive alt attribute. This isn’t optional — it’s required for accessibility and helps with SEO.

• Good: alt="Gustavo Vasquez working on laptop in home office"
• Bad: alt="image" or alt="" or missing entirely
• Over-optimized: alt="best web developer New York affordable web design services"

Describe what’s in the image naturally. Include keywords where they fit, but don’t force them.

12. Meta Descriptions Are Written for Every Page

Each page needs a unique meta description between 150-160 characters. This is what appears in Google search results below your page title.

• Include your primary keyword naturally
• Write it as a call to action (make people want to click)
• Don’t duplicate descriptions across pages

No meta description means Google writes one for you — and it’s usually terrible.

13. Page Titles Are Unique and Under 60 Characters

Every page needs a distinct title tag. Format: [Primary Keyword] - [Brand Name] or [Compelling Title] | [Brand Name].

Check that:

• No two pages share the same title
• Titles are under 60 characters (longer ones get truncated in search results)
• Your most important keyword appears near the beginning
• Titles accurately describe the page content

14. Internal Links Work

Click every link on every page. Seriously. Broken internal links create a terrible user experience and hurt your SEO.

Use a tool like Screaming Frog (free for up to 500 URLs) or Dead Link Checker to automate this. Fix broken links before anyone else finds them.

Make sure each page has 3-5 internal links to related content and that they point to actual, relevant destinations.

15. Social Sharing Previews Look Right

Share your homepage and a few key pages on Facebook, Twitter/X, and LinkedIn. Do the previews look correct?

Set up Open Graph tags (og:title, og:description, og:image) so your pages display with the right image and text when shared. Use Facebook’s Sharing Debugger and Twitter’s Card Validator to preview without posting publicly.

A sharing preview with no image or the wrong text means missed traffic from every social share.

SEO: Be Findable From Day One (Points 16-20)

16. Canonical URLs Are Set

Each page should have a <link rel="canonical"> tag pointing to its preferred URL. This prevents duplicate content issues from URLs like:

• yourdomain.com/about vs yourdomain.com/about/
• www.yourdomain.com/about vs yourdomain.com/about
• yourdomain.com/about?ref=social

Pick one URL format and stick with it site-wide.

17. Schema Markup Is Implemented

Structured data (Schema.org markup) helps Google understand your content and can earn rich snippets in search results.

At minimum, add:

• LocalBusiness schema (for local businesses) with name, address, phone, hours
• Organization schema with your logo and social profiles
• BreadcrumbList schema for navigation
• FAQ schema on FAQ pages (if you have them)

Test with Google’s Rich Results Test tool.

18. Heading Structure Is Logical

Each page should have exactly one H1 tag (the main heading), with H2s for sections and H3s for subsections. Don’t skip levels (H1 straight to H4) and don’t use heading tags just for styling.

Search engines use headings to understand page structure and content hierarchy.

19. URL Structure Is Clean

URLs should be:

• Lowercase
• Hyphenated (not underscored or camelCase)
• Descriptive (/services/web-development, not /page?id=47)
• Short (under 75 characters)

And once your site is live, never change URLs without setting up 301 redirects. Broken URLs mean lost traffic and lost link equity.

20. Redirect WWW to Non-WWW (or Vice Versa)

Pick www.yourdomain.com or yourdomain.com and redirect the other. Both versions being accessible means Google treats them as separate sites, splitting your ranking signals.

Most hosts let you configure this in their dashboard. Test by visiting both versions and confirming one redirects to the other.

Legal: Protect Yourself (Points 21-23)

21. Privacy Policy Is Published

If you collect any data — and you almost certainly do (analytics cookies, form submissions, email signups) — you need a privacy policy. It should disclose:

• What data you collect
• How you use it
• Who you share it with
• How users can request deletion

This isn’t just good practice. GDPR, CCPA, and similar regulations make it legally required in most jurisdictions.

22. Cookie Consent Banner Works

If your site uses cookies (Google Analytics alone qualifies), you need a consent mechanism for EU visitors. The banner should:

• Appear on first visit
• Explain what cookies are used
• Allow visitors to decline non-essential cookies
• Actually respect their choice (don’t fire analytics before consent)

23. Accessibility Basics Are Covered

At minimum:

• All images have alt text (covered in point 11)
• Color contrast meets WCAG AA standards (4.5:1 ratio for text)
• The site is navigable by keyboard (tab through all interactive elements)
• Form inputs have associated labels
• Font size is at least 16px for body text

Use WAVE (wave.webaim.org) for a quick accessibility audit. Full ADA compliance is deeper, but these basics cover the most common issues.

Performance: Make It Fast (Points 24-25)

24. CDN Is Active

A Content Delivery Network serves your site from servers geographically close to each visitor. If your hosting is in Virginia and your customer is in California, a CDN makes the site load as if it were hosted locally.

Cloudflare offers a free tier that handles most small business needs. If you’re on Vercel, Netlify, or similar platforms, CDN is built in.

25. Browser Caching Is Configured

Returning visitors should load your site faster than first-time visitors. Proper cache headers tell browsers to store static assets (images, CSS, JavaScript) locally.

Check your caching with PageSpeed Insights — it flags missing cache headers. Most hosting platforms and CDNs handle this by default, but verify it’s actually working.

Post-Launch: The First 30 Days (Points 26-27)

26. Submit to Google Search Console

Go to search.google.com/search-console, add your site, verify ownership, and submit your sitemap. This tells Google your site exists and gives you data on how it performs in search.

Monitor for:

• Indexing errors (pages Google can’t read)
• Mobile usability issues
• 404 errors from broken links elsewhere pointing to your site
• Security issues

Don’t just set it up and forget it. Check weekly for the first month, then monthly after that.

27. Set Up a Backup Schedule

Your site will be backed up. The question is whether it happens before or after something breaks.

• Hosted platforms (Shopify, Squarespace): Handled automatically, but export a copy anyway
• Self-hosted (WordPress, custom): Set up daily automated backups to an external location
• Static sites (Astro, Next.js): Your code is in Git, but back up any CMS content and databases separately

Test your backup restore process at least once. A backup you can’t restore isn’t a backup.

Bonus: The Launch Day Protocol

On the actual launch day:

1. Push your changes during low-traffic hours (early morning or late evening)
2. Clear all caches (CDN, server, browser)
3. Test the site immediately after going live — every page, every form
4. Monitor analytics real-time for the first hour
5. Have a rollback plan ready if something is fundamentally broken
6. Announce the launch once you’ve confirmed everything works

Don’t launch on Friday afternoon. If something breaks, you want business hours to fix it.

Save This Checklist

I use this exact list for every site I launch through my web development services. It’s evolved over dozens of projects and hundreds of “oh no, we forgot to check that” moments.

If you’re planning a launch and want a second pair of eyes on your site, reach out. A pre-launch review takes about an hour and can save you weeks of fixing things after the fact.

Your website only gets one first impression. Make it count.