Free tools

A launch checklist you can use without handing over your email.

Launch preparation is more useful when responsibilities and unresolved questions are visible. A checklist can help a business and its development team notice gaps before release, but ticking a box is not proof that the underlying work was done correctly. Use each item as a prompt to check the actual site and record any follow-up with the person responsible.

Illustrative toolbox: project scoping and launch preparation.

Use this tool in your browser.

Use the checklist as a review prompt

Launch preparation is more useful when responsibilities and unresolved questions are visible. A checklist can help a business and its development team notice gaps before release, but ticking a box is not proof that the underlying work was done correctly. Use each item as a prompt to check the actual site and record any follow-up with the person responsible.

Start with the General tab and then choose the platform closest to your build. Each platform tab carries the shared checks alongside an additional platform-specific prompt in each category. A hybrid site may need more than one perspective: a WordPress backend with a separate storefront, for example, has publishing and frontend responsibilities that should both be reviewed.

The checklist is free to use in the browser without email. Your ticked items stay in this browser's local storage where available, so you can return to the same device and continue. Different browsers and private sessions may not share that state. Reset removes the saved ticks; copying or printing creates a separate record that you control.

Progress indicates how many prompts you marked complete, not a technical quality score. Some checks may not apply to your project, and a team should agree how those decisions are recorded. Keep outstanding risks, access needs and ownership questions in the project documentation rather than hiding them behind a complete progress ring.

General launch preparation

Begin with the goal of the site and the actions a visitor should be able to complete. Verify navigation, forms, public contact details and the release domain. Confirm who approves content and who can revert the deployment if something goes wrong. A short, shared record of those decisions is more useful than assuming that every launch uses the same workflow.

Shopify launch notes

Review the theme and apps as parts of the same buying journey. Product variants, cart behavior, delivery information and the handoff into checkout should be checked with supported settings and approved tests. Theme changes can also affect analytics and content presentation, so ownership of those areas should be clear. Record the published theme and the recovery route before switching the live storefront.

WooCommerce launch notes

A store can depend on custom PHP, plugins, product data and external payment or courier systems. Check how those responsibilities meet rather than reviewing only the visible template. An approved test order can help verify expected order transitions and notification behavior. Backups need to consider both files and the database, and access to logs or admin settings should follow an agreed boundary.

WordPress launch notes

Review the templates that editors actually use, including navigation, archives and reusable content. Check the published version rather than relying solely on an editor preview. A page builder and custom components can coexist, but someone still needs to understand updates, roles and the path to restore the site. Enquiry forms deserve an end-to-end delivery check as well as a visible success state.

Next.js and headless launch notes

A separate frontend depends on deployment settings, generated routes and backend connections. Check what happens when content is published, an external service fails or a route does not exist. Keep private credentials out of the client bundle and document which system owns each cache or publishing action. Client navigation, metadata and focus behavior should be reviewed on the production build as well as direct page loads.

Questions about this tool

Do I need an email to use the checklist?

No. The checklist is usable without a form. Any optional copy-by-email feature must remain separate and is disabled by default.

Where are my ticks stored?

They are kept in this browser's local storage where available. If storage is blocked, the checklist still works for the current visit.

Does complete progress mean the site is safe to launch?

No. Progress reflects your selections, not an independent audit or certification. The actual checks, exceptions and release decision remain with the responsible team.

Can I export a copy?

Use Copy as text or Download as PDF. The PDF option opens the browser's print interface, where saving to PDF depends on the browser and device.

Can someone review these areas for me?

The free audit page accepts a public site or a planned build. It offers written recommendations, with any implementation scope discussed separately.

08 / Start a project

Let’s build something dependable.

Send a short brief about what needs to work better and get a direct reply from Abdullah.

  • Direct response from Abdullah
  • NDA-friendly
  • No-obligation first conversation