Website launch checklist: 40 checks before you go live

A comprehensive pre-launch checklist covering content, design, functionality, SEO, performance, accessibility, security, analytics and the launch itself.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Before launching a website, check content accuracy, design on every device, forms and integrations, SEO settings and redirects, speed, accessibility, security, analytics and legal pages. Remove staging blocks that hide the site from search engines, plan DNS changes carefully, and keep a rollback plan. After launch, monitor errors, forms, search indexing and performance closely for the first few weeks.

Launch day is exciting and nerve-wracking. A missed detail, like a form sending emails nowhere or a setting blocking search engines, can undo months of work. Use this checklist in the week before launch.

Content

  1. All placeholder text and images replaced.
  2. Spelling and grammar checked.
  3. Contact details, addresses and phone numbers correct.
  4. Prices, services and product details accurate.
  5. Links point to the right pages; no broken links.
  6. Images have descriptive alt text.
  7. Legal pages in place: privacy policy, terms and cookie information where relevant.

Design and devices

  1. Tested on recent iPhone and Android phones.
  2. Tested on tablets.
  3. Tested on major desktop browsers.
  4. Text readable and buttons easy to tap on mobile.
  5. Favicon and app icons set.
  6. Social sharing images and previews look right.

Functionality

  1. Every form submits, validates and delivers to the right inbox. If not, see our guide to fixing a contact form that isn't sending email.
  2. Confirmation messages and emails work.
  3. Spam protection active on forms.
  4. Search, filters and interactive features work.
  5. Payments and checkout tested with real transactions and refunds, if applicable.
  6. Third-party integrations, such as CRM and booking tools, connected to live accounts.
  7. Custom 404 page in place.

SEO

  1. Unique titles and meta descriptions on every page.
  2. One H1 per page with logical headings.
  3. "Noindex" settings from staging removed.
  4. robots.txt allows crawling of important pages.
  5. XML sitemap generated.
  6. Canonical tags correct.
  7. Structured data added and validated.
  8. 301 redirects from old URLs if replacing an existing site.

Performance

  1. Images compressed and properly sized.
  2. Caching and a CDN configured. See our CDN guide.
  3. Core Web Vitals checked on key pages.

Accessibility

  1. Keyboard navigation works throughout.
  2. Colour contrast meets WCAG AA.
  3. Forms labelled with clear error messages.

Security

  1. HTTPS on every page, with HTTP redirecting.
  2. Security headers configured.
  3. Admin accounts limited, with strong passwords and two-factor authentication.
  4. Backups configured and tested.

Analytics and tracking

  1. Analytics installed, with goals and conversions set up, and consent handled where required. Our guide to privacy-friendly analytics covers options.
  2. Search Console and other webmaster tools verified, with the sitemap submitted.

Launch day

  • Choose a quiet time, avoiding Fridays and busy trading periods.
  • Lower DNS TTLs in advance. Our guide to DNS records explains how.
  • Make sure the team knows the plan and who does what.
  • Switch DNS or deploy.
  • Check SSL certificates issue correctly.
  • Test the live site: homepage, key pages, forms and checkout.
  • Keep the old site available for rollback if needed.

After launch

  • Monitor error logs and uptime.
  • Check form submissions arrive for several days.
  • Watch Search Console for crawl errors and indexing.
  • Check analytics is recording traffic and conversions.
  • Test redirects from old URLs.
  • Gather feedback from staff and customers.
  • Fix issues quickly.

Who should sign off

Agree in advance who approves the launch: usually a business owner for content, a developer for technical checks and someone responsible for legal and privacy pages. A short sign-off meeting the day before launch catches last-minute issues and makes sure everyone knows the plan, the timing and who to contact if something goes wrong.

Rollback plan

Decide in advance what would make you roll back, such as broken checkout or forms, and how you'd do it. Keep the previous version deployable and DNS changes documented so you can revert quickly if needed.

Keep a launch document

Record what was launched, settings changed, accounts and access, and known issues. It's invaluable for future updates and troubleshooting.

Launch checklists for different site types

Some sites need extra checks. A SaaS marketing site should confirm sign-up flows and trial emails work end to end; see our guide to SaaS website design. A charity site should test donation journeys, receipts and recurring giving; our nonprofit website guide covers those details. Online stores need full checkout, tax and shipping tests.

Turn this list into a shared document or project board, assign an owner to each item and tick items off together in a pre-launch meeting. A shared checklist stops tasks falling between people.

How we help

Every site our web development team launches goes through a checklist like this. Our CMS development team makes sure editors are trained before launch, and our maintenance plans provide monitoring and support afterwards.

Frequently asked questions

What's the most common website launch mistake?

Leaving a noindex setting from staging, which hides the site from search engines. Forms not delivering email is a close second.

When is the best time to launch a website?

During a quiet period early in the week, when the team is available to fix problems.

How long after launch should I monitor closely?

At least two to four weeks, checking forms, errors, indexing and performance.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All websites & web design guides