Key takeaways
- Tick an item after checking the live behaviour, and keep evidence and unresolved issues in a separate note.
- The 29 checks cover six groups; completion measures checked items, not launch risk or search performance.
- Progress is saved locally when browser storage is available, with no shared account or device synchronisation.
A website launch checklist turns the broad question “is the site ready?” into specific tests of content, forms, devices and ongoing responsibility. Use it before publishing a new website or replacing an existing one, especially when several people have worked on the project and assumptions about testing may differ.
Before you start
Choose the exact version and domain you are reviewing. A staging page, the public website and a cached preview can behave differently, so record the address and review date in your own notes. Have a phone, a desktop browser, keyboard access and the inbox that should receive test enquiries available.
Prepare a short list of important journeys: finding a service, submitting an enquiry, opening directions or reaching a confirmation page. For an Indian tuition centre, for example, test the admissions enquiry from a phone on mobile data and confirm that the actual receiving inbox gets it. Use clearly labelled test content rather than real applicant details.
Your checkbox choices stay in the browser and are not uploaded by CrizaTools. Unlike a temporary text field, the checklist attempts to save progress in local browser storage, so ticks can remain after closing the tab. It is a personal progress aid, not a shared sign-off record; keep your evidence and team decisions separately.
Step by step with CrizaTools
- Open the website launch checklist. Review the progress display and the count of 29 items. Previously saved ticks may appear when the tool loads in the same browser profile.
- Work through Content. Proofread representative pages, remove placeholders and compare the published contact information with the details the owner actually intends to use. Inspect the policy and asset-ownership prompts without treating the checklist as legal advice.
- Continue to Forms and conversions. Submit a test enquiry, check inbox delivery and failure messages, and try the relevant action links. Tick the corresponding checkbox only after the behaviour has been tested.
- Review Search and sharing, Speed and devices, and Accessibility. Check the public pages, actual mobile layouts and keyboard interactions; the tool lists tasks but does not run these tests for you.
- Use After launch to check secure addresses, recovery arrangements, account control and who handles problems. Record the responsible person and evidence outside the checklist because there are no note or assignment fields.
- Reopen the tool in the same browser when continuing the review. Untick an item if a later change invalidates its test, then retest it. Clear my progress resets all saved ticks when starting a fresh review.
Two worked examples
Example 1: progress after an initial review. Suppose you have genuinely completed all five Content checks, all five Forms and conversions checks, five of the six Search and sharing checks, and all four Speed and devices checks. Leave Accessibility and After launch unticked. The exact count is 5 + 5 + 5 + 4 = 19 completed items out of 29.
The percentage is round(19/29 × 100) = 66%, leaving 10 unchecked items. That number says how many boxes are ticked; it does not mean the website is 66% accessible or that the remaining work is 34% of the total effort. One unchecked form-delivery issue could matter more to the launch than several small copy corrections.
Keep a separate note such as “Admissions confirmation page tested on Android; inbox delivery checked at 14:00; second reviewer still needed for keyboard navigation.” The checklist remembers a yes/no choice, while that note explains what was actually tested and what remains uncertain.
Example 2: discovering a regression after almost finishing. Start with 28 checked items. CrizaTools shows round(28/29 × 100) = 97%. You discover that a newly deployed form no longer delivers messages, so untick the previously completed form-delivery item. The count drops to 27 and the display becomes round(27/29 × 100) = 93%.
Repair and retest that form, then complete the last originally outstanding check. The final count is 29 of 29 and the progress reaches 100%, with the completion message displayed. This is a record of your checks, not an automated certification. Save the review date and tested release separately, because a later content or configuration change can invalidate earlier evidence without changing the saved tick.
Limits and what to watch for
The checklist has no website-address input, crawler, automatic issue detector or report export. It does not inspect a page when you tick an item. There are also no separate “not applicable” choices; keep justified exceptions in your own notes instead of silently treating an irrelevant item as tested.
Storage is local to the browser environment. Another device or profile does not automatically receive your progress, and clearing site data can remove it. If browser storage is unavailable, the interface can still work during the current page session, but you should not rely on the ticks surviving a reload.
For search checks, distinguish discovery from indexing. Google explains that noindex can prevent an accessible page from appearing in its results, while a sitemap helps discovery but does not guarantee crawling or indexing. Verify the actual public configuration after launch; completing the checklist makes no promise about rankings. See Google’s noindex documentation and sitemap overview, checked 16 November 2026.
A short accessibility review can reveal obvious barriers but cannot establish comprehensive accessibility. W3C makes the same distinction in its Easy Checks guidance, checked 16 November 2026. Use the checklist to organise practical testing, and seek a fuller evaluation when the project needs one rather than treating four ticks as a conformance result.
Common mistakes
- Ticking from memory: rerun important journeys on the version you intend to publish.
- Seeing a form success message as delivery proof: confirm the test message reaches the receiving inbox.
- Reviewing only a desktop preview: try the important pages on an actual phone and mobile connection.
- Treating 100% as permanent approval: retest checks affected by later changes and record the reviewed version.
- Expecting progress on another device: keep a separate handover note for team use.
- Clearing progress before recording findings: save unresolved issues and evidence before starting a new review.
Questions and answers
What should I test before launching a website?
Test the visitor’s important tasks, including finding information, submitting forms and using the site on a phone. Then review content, public search settings, keyboard access and recovery responsibility rather than judging readiness from appearance alone.
Does the launch checklist scan my website automatically?
No, CrizaTools provides a list of manual checks and records your checkbox choices. Perform the actual tests yourself and keep evidence in a separate note or issue tracker.
Will my checklist progress be saved?
CrizaTools attempts to save it in local browser storage on the current device and profile. Storage restrictions or cleared site data can remove that progress, and it is not synchronised to a shared account.
Does a completed checklist guarantee search rankings?
No, the progress percentage describes checked items only. Google’s sitemap guidance also distinguishes helping discovery from guaranteeing indexing; checked 16 November 2026 in its official documentation.
How do I reset the checklist for another website?
Select Clear my progress after recording any findings you need to keep. The tool has one local progress set rather than separate named projects, so resetting removes the current saved ticks.
Sources
- Google Search Central: noindex — indexing controls; checked 16 November 2026.
- Google Search Central: sitemaps — discovery and limitations; checked 16 November 2026.
- W3C WAI: Easy Checks — first-review scope; checked 16 November 2026.
Run your review with the website launch checklist, or clarify unfinished scope first with the project brief builder.
Free tools for this
Business
Website Launch Checklist
An interactive pre-launch checklist for websites: content, forms, SEO, speed, accessibility and backups.
Business
Project Brief Builder
Answer seven quick questions to build a clear brief for your website, app or automation project.
PDF & image
Image Compressor
Compress and resize JPG, PNG and WebP images in your browser for websites, upload forms, email and WhatsApp.