Ten questions before you press publish
- Has someone who never saw the site completed a full order on their phone?
- Did a test payment succeed, and was another declined with a clear message?
- Do confirmation messages really arrive by email or text?
- Is Arabic right to left, and English free of leftover text?
- Is every placeholder text and temporary image gone?
- Do all menu and footer links open real pages?
- Are the privacy, terms and contact pages in place?
- Does the site run on your domain with the padlock in the address bar?
- Do you have a backup and know how to return to the previous version?
- Do you know who answers customers during the first week?
What blocks a launch and what can wait?
| Blocks the launch | Can wait |
|---|---|
| A customer cannot finish an order or pay | An animation or color you dislike |
| One customer's data shows to another | An 'about us' page that needs nicer wording |
| The site is broken on phones | An extra report in the admin panel |
| Confirmation messages do not arrive | An unfinished minor feature, which you can hide for now |
Does a checklist guarantee no bugs?
No. No checklist or tool guarantees a bug-free site. The aim is that no customer meets a bug that blocks a purchase or touches their data, and that you find the rest quickly and fix it. The full list is in the website testing checklist.