Website Launch Checklist: 30 Checks Before You Go Live (2026)

Launching a website feels exciting, but one missed check can turn launch day into a long fix-it session. A broken contact form, a page Google cannot index, or a missing backup can cost you visitors and sales in the first week. This website launch checklist walks you through 30 checks, grouped so you can work through them in order: content, design, speed, SEO, testing, security, backups, analytics, legal pages, launch day, and the weeks after launch.

Print it out or copy it into your own notes, and tick each item off as you go. Most checks take a few minutes each, and together they catch the problems that are painful to fix after launch.

1. Content Checks (1–5)

Visitors judge your site by its words first. Read every page out loud if you can — it catches mistakes your eyes skip over.

1. Proofread every page

Check spelling, grammar, and facts on your homepage, service pages, about page, and contact page. Look for placeholder text like “lorem ipsum” or “coming soon” that was never replaced. One unfinished page makes the whole site look unfinished.

2. Check titles and headings

Every page needs one clear title that says what the page is about, and headings that break the text into sections a reader can scan. If a heading promises something the text does not cover, rewrite one of them.

3. Fix or remove thin pages

Pages with only a sentence or two rarely help anyone. Either add useful detail or remove the page before launch. A small site with solid pages beats a big site full of empty ones.

4. Check images and alt text

Make sure every image loads, looks sharp, and is not stretched or squashed. Add short alt text that describes each image for visitors who use screen readers and for search engines. Compress large images so they do not slow the page down.

5. Set a favicon and social preview image

A favicon is the small icon in the browser tab. A social preview image is what shows when someone shares your link on Facebook, X, or LinkedIn. Without them, your site looks unfinished in tabs and in shared posts. Test a share on one social network before launch.

Source: Wikimedia Commons

2. Design and Mobile Checks (6–9)

More than half of web traffic now comes from phones, so test on real phones — not just by shrinking your desktop browser window.

6. Test on a real Android phone and a real iPhone

Open every key page on both. Check that text reads without zooming, buttons are big enough to tap with a thumb, and menus open and close cleanly. iOS Safari and Android Chrome handle some layouts differently, so one phone is not enough.

7. Test on a tablet and a desktop

Check at least one tablet size and one desktop size. Look for text that overlaps images, columns that collapse badly, and sections that look empty on wide screens.

8. Test on slow internet

Use your browser’s throttling tool, or simply test on a weak mobile connection. A site that feels fast on office Wi-Fi can feel broken on a slow train connection. If a page takes more than a few seconds to become usable, trim images or scripts.

9. Check accessibility basics

Make sure text has enough contrast against its background, every link and button works with a keyboard alone, and images have alt text. These checks help visitors with disabilities, and they usually improve the site for everyone else too.

3. Speed Checks (10–12)

Slow pages lose visitors. People leave, and Google notices.

10. Run a speed test on your key pages

Test your homepage and your most important service or product page with PageSpeed Insights. Note the score and the biggest problems it lists, then fix the top one or two before launch. You do not need a perfect score — you need pages that feel fast.

11. Check Core Web Vitals in plain terms

Google measures three things: how fast the main content appears, how quickly the page responds to a tap or click, and how much the layout jumps around while loading. Jumping layouts are a common fail — they happen when images load without set sizes or when ads and pop-ups push content down. Fix the jumps first, because they annoy real visitors the most.

12. Turn on caching and compression

Ask your host or check your site settings: caching should be on, and files should be compressed before they are sent to visitors. This is often one toggle in your hosting panel or caching plugin, and it can cut load times a lot.

4. SEO Checks (13–16)

SEO at launch is about making sure Google can find, read, and understand your site — not about ranking first on day one.

13. Write a title and meta description for every page

Each page needs a unique title (around 60 characters) and a meta description (around 155 characters) that describe what the page offers. Do not copy the same description across pages, and do not leave them blank — Google will pick text for you, and it usually picks badly.

14. Remove “noindex” and check robots.txt

Many sites are built with a setting that tells search engines not to index them. Before launch, turn that off. Check your robots.txt file too, and make sure it is not blocking pages you want found. This single check is the most common launch-day SEO mistake.

15. Submit your sitemap to Search Console

Set up Google Search Console, verify your site, and submit your sitemap. This tells Google your pages exist and shows you indexing problems, search queries, and errors after launch.

16. Fix broken links and plan redirects

Click through your navigation, footer, and buttons, and fix any link that leads to a “page not found” error. If you are replacing an old site, map each old URL to its new home with a 301 redirect, so visitors and search engines do not hit dead ends. Set up a friendly custom 404 page for the links you miss.

5. Forms, Links, and Checkout Testing (17–19)

Test like a visitor, not like the person who built the site. Log out first — logged-in users often see a different, working version of things that are broken for everyone else.

17. Test every form end to end

Fill in each contact form, quote form, and sign-up form yourself, and confirm the message arrives where it should. Check the confirmation message the visitor sees, and test what happens with a missing field or a bad email address. A form that looks fine but never delivers messages is worse than no form at all.

18. Test checkout if you sell anything

Place a real test order: add to cart, pay, and confirm the order email arrives with the right items, tax, and shipping details. Test a failed payment too, so you know what the customer sees. If you changed prices or shipping rules, test those exact cases.

19. Check email delivery

Make sure emails from your site actually reach inboxes, not spam folders. If your host’s default mail fails, use a proper sending service or SMTP setup. Ask your host or developer about SPF, DKIM, and DMARC records — these three domain settings tell email providers your mail is genuine, and they prevent a lot of lost order and contact emails.

Source: Wikimedia Commons

6. Security Checks (20–22)

Security is dull until the day you need it. These three checks cover most small-site problems.

20. Turn on SSL and force HTTPS

Your site should load over HTTPS with a valid certificate, and old HTTP links should redirect to the secure version. Browsers now warn visitors about non-secure sites, and many will leave before the page loads.

21. Clean up users and logins

Remove old admin accounts, test users, and unused plugins and themes. Turn on two-factor authentication for admin accounts, and make sure passwords are strong and unique. Most small-site hacks come through an old account or an abandoned plugin, not through clever attacks.

22. Update everything, then check it still works

Update your platform, theme, and plugins to their latest versions before launch, then click through key pages again. Updates sometimes break a layout or a form, and it is far better to find that out now than after launch.

7. Backups and a Rollback Plan (23–24)

This is the section most launch guides skip — and the one you will be grateful for if launch day goes wrong.

23. Set up backups — and test restoring one

A backup you have never restored is only a hope, not a plan. Set automatic backups that run at least daily, store a copy somewhere other than your web host, and keep several weeks of copies. Then actually restore one to a test location and confirm the site works. Write down how long a restore takes, so you can give honest answers on launch day.

24. Write a simple rollback plan

Before launch, decide in advance: what counts as “bad enough to roll back” (for example, checkout broken, homepage down, or forms not delivering), who makes the call, and what the steps are — restore the backup, point the domain back, or switch the site to a maintenance page while you fix it. Keep the old site or a full backup ready until the new site has run cleanly for a week. A plan written calmly today saves panic later.

8. Analytics and Tracking (25–26)

If you launch without tracking, your first month of data is gone for good.

25. Set up Google Analytics (GA4) before launch

Create a GA4 property, add the tracking code, and confirm visits show up in real-time reports. Set up at least one conversion event — a form submission, a purchase, or a key button click — so you can tell whether the site is working, not just whether it is visited. If you use a cookie consent banner, make sure tracking respects visitor choices.

26. Verify Search Console and check the first 48 hours

After launch, check Search Console daily for the first two days: indexing errors, pages Google could not crawl, and mobile usability problems. Early errors are usually quick fixes, but only if you see them. Add uptime monitoring too, so you get an alert if the site goes down instead of hearing about it from a customer.

9. Legal Pages (27)

27. Publish privacy, terms, and cookie pages

Most sites need a privacy policy that explains what data you collect and why, terms of use, and a cookie notice if you use analytics or advertising cookies. Do not copy another site’s legal text word for word — it may describe practices you do not follow, and that creates a bigger problem than a missing page. If you sell to visitors in California or Europe, check the rules that apply to you (CCPA and GDPR) or ask a lawyer for a short review before launch.

10. Launch Day (28)

28. Follow a launch-day order

On the day itself, work in this order: point the domain to the live site and allow time for DNS changes to spread; re-check SSL; turn indexing on; test the homepage, one service page, and one form on a real phone; submit the sitemap; and announce the site only after those checks pass. Tell one person on your team to watch for error reports for the rest of the day, and keep your rollback plan (check 24) within reach.

11. After Launch: Day 1, Week 1, Month 1 (29–30)

Launch is the start, not the finish. Competitors’ guides usually stop here, but the first month is when small problems show up.

29. Day 1 and week 1: watch, fix, listen

On day 1, re-test forms, checkout, and speed, and read every message visitors send. In week 1, fix broken links and errors Search Console reports, gather feedback from three to five real visitors, and fix the one complaint that comes up most. Small fixes in week 1 prevent bad first impressions from sticking.

30. Month 1: set a maintenance routine

By the end of the first month, set a simple routine: weekly updates and backups, a monthly check of speed and Search Console, and a monthly review of your most visited pages. Put it on a calendar. Sites that get a little regular care stay fast and safe; sites that get none slowly break.

Common Website Launch Mistakes

Three mistakes show up again and again. First, launching with the “do not index” setting still on — the site looks fine to visitors, but Google never sees it. Second, never testing a form while logged out — the owner thinks messages work because test messages arrived, while real visitors’ messages vanish. Third, skipping the backup restore test — the backup exists, but nobody knows it is broken until the day it is needed. This checklist exists to catch those three before they cost you.

Frequently Asked Questions

What are the steps to launch a website?

Build the site on a staging or private address, work through content, design, speed, SEO, security, and backup checks, then point your domain to the live site, turn indexing on, test on a real phone, and monitor errors for the first week.

How do I test a website before launching?

Test as a logged-out visitor on a real Android phone, a real iPhone, a tablet, and a desktop. Click every link, submit every form, and place a test order if you sell anything. Then run a speed test and check Search Console for crawl errors.

Should I do SEO before or after website launch?

Before. Titles, meta descriptions, sitemaps, and the noindex check all need to be right at launch, because Google starts forming its picture of your site in the first days. After launch, SEO becomes a routine: fix errors, publish useful content, and track what visitors actually search for.

What if something breaks right after launch?

Use your rollback plan: judge whether the problem is bad enough to revert, restore your tested backup or point the domain back, and put up a short maintenance message while you fix it. Fixing a broken launch calmly is normal — every large site has done it.

Last updated: November 2026