01/Launch checklist

21 checks

Before you share the link.

Twenty-one checks for a website or web app, in the order we run them before a link goes out. Tick each one off as you go.

0of 21 done

Your ticks stay in this browser, on this device. Nothing is sent anywhere.

01/It opens properly0/5

  • Most first visits come from a link tapped on a phone. Wi-Fi and a laptop hide slow images and layouts that break on a narrow screen.

  • No saved logins, no cache. You see what a stranger sees.

  • The title, description and image are the first thing anyone sees. Set og:title, og:description and a 1200 by 630 og:image on every page you'll share.

    metatags.io ↗
  • Tabs, bookmarks and phone home screens show it. Without one, a blank page stands in.

  • Your 404 page should lead back to the site, not to a dead end.

02/It's quick0/2

  • It loads the page on a simulated phone, times how long the main content takes to appear, and names what slows it down.

    pagespeed.web.dev ↗
  • The hero image is usually the heaviest thing on the page. Export it at the size it's shown, as WebP or AVIF.

    squoosh.app ↗

03/People can find it0/3

  • They're what a search result shows. One title shared by every page tells a search engine nothing.

  • A noindex tag, or a robots.txt that blocks everything, keeps the whole site out of search without a single error. Open /robots.txt and the page source to check.

  • It tells Google which pages exist, and shows you when one can't be indexed and why.

    search.google.com/search-console ↗

04/Everyone can use it0/2

  • Missing alt text, low contrast and form fields without labels take a minute to find, and shut people out until they're fixed.

    wave.webaim.org ↗
  • Tab through every page. If you can't see where you are, or can't reach a button, neither can someone who doesn't use a mouse.

05/Forms and email work0/2

  • Fill it in, submit it, and watch the result arrive where it should. A form that fails quietly looks like nobody's interested.

  • Set SPF, DKIM and DMARC for your domain, or sign-up and password emails go to spam. Your email provider's dashboard shows which are missing.

06/Payments are real0/2

  • Test keys take test cards and nothing else. Check every place one is set: the server, the app and the webhooks.

  • It's the only way to see the whole path: the charge, the receipt, the webhook, and what your app does next.

07/You'll know when it breaks0/2

  • The errors your users hit are errors you never see. A service such as Sentry sends each one to you with the page it happened on.

  • An uptime monitor, or a scheduled check of everything your site depends on, should email you before a user does.

08/The basics people look for0/3

  • UK and EU data protection law asks for one as soon as you collect personal data, even an email address. A careful customer opens it first.

  • Serve it over https, with www and the bare domain redirecting to the same one, so links and search results don't split between two.

  • A contact form or an email address that someone actually reads.