Launch day is the worst time to find out a button goes nowhere. This checklist covers what customers hit most often. Go through it on a phone and on a laptop — they're different pages.
Buttons and links
- Every button and link goes where its words say
- The main button is on the first screen on a phone
- Nothing important only shows on hover
Forms
- Every field accepts normal answers (phone numbers with spaces, apartment numbers)
- Errors say what's wrong and keep what was typed
- Dropdowns can be picked on a phone
- Nothing asks for more than it needs right now
Prices and promises
- Every price matches from page to page
- Fees, tax and shipping show before the last step
- Promises like free returns or delivery dates appear where the shopper decides
- The page keeps whatever the ad or email that sent people here promised
Mobile
- Buttons are big enough to tap
- Sticky bars and pop-ups don't cover the content
- The keyboard doesn't hide the Continue button
Deeper guides
For the pages where the money is, see how to test your checkout before launch, how to test your website on mobile, and how to test a landing page before running ads.
Or run the whole list
A Run covers everything above. Paste a link — a live page or a Figma or Framer prototype — pick desktop or mobile, and say what matters. You get a Run Sheet in under an hour with each problem pinned to the spot and the change to make.
— FAQ
Questions people ask
- What should I check before launching a website?
- Every button and link, every form with one wrong answer, every price and promise from page to page, and the whole flow on a phone.
- How long does pre-launch testing take?
- By hand, a careful person needs most of a day for one flow. A Run takes under an hour.
- Can I test before the site is built?
- Yes. Run a Figma or Framer prototype.
- How much does it cost?
- Your first Run is free, with no card. After that, plans are on the pricing page.
Topicspre-launchchecklistwebsite launchQA