Skip to content
Antoine Le LouëtIndependent senior developer (Home)
A free tool · No account needed

The right things to check before launch.

Prepare your website or SaaS launch with a checklist tailored to your project.

Your progress stays in this browser.
Export it at any time.

What are you launching?
Your project includes…

Options are suggested based on the profile. Adjust them to your project.

0 / 26 applicable checks completed0 %

26 to do · 0 not applicable checks excluded from the calculation

Domain & launch

0 / 3 applicable checks completed

The website must be accessible on the chosen domain, with a valid certificate.

How to check? Check the domain and HTTPS certificate

Open the final domain in a private window. Check the certificate in the browser and also try an http:// URL: it should redirect to the HTTPS version.

Visitors must find the right content after an address changes.

How to check? Redirect old URLs and domain variants

Test important old URLs and variants with and without www. Check the HTTP status, destination and absence of redirect loops.

Staging keeps its own access and indexing rules.

How to check? Separate production from test environments

Compare variables and keys in each environment. Check that production uses the intended services and that private environments are protected by access control.

Search & sharing

0 / 3 applicable checks completed

Each main page should clearly describe its content, including when shared as a link.

How to check? Review titles, descriptions and sharing previews

Inspect the initial HTML of the main pages: title, description, canonical URL and Open Graph. Open sharing images and check their text.

Google: SEO starter guide (new tab)

Public pages should be discoverable according to your indexing policy. A robots.txt file does not protect a private page.

How to check? Check indexing directives and the sitemap

Check robots.txt, the sitemap and robots tags on several pages. Remove staging directives only on the relevant public website and test private access separately.

Google: block indexing with noindex (new tab)

Visitors must be able to continue their journey and contact you.

How to check? Test links, the 404 page and contact actions

Go through the menu and footer links, open a nonexistent URL and try contact buttons with test data.

Performance & accessibility

0 / 3 applicable checks completed

Loading, interactions and visual stability matter throughout the journey.

How to check? Test main pages on mobile and a slow network

Test several pages with browser tools and a throttled connection. Look for late-loading main content, layout shifts and slow actions; supplement with real data when available.

web.dev: Web Vitals (new tab)

Focus must remain visible and menus and forms must be usable.

How to check? Navigate essential actions with the keyboard

Navigate links and controls with Tab, Shift + Tab, Enter and Escape. Check focus order, menu opening and closing, and access to every action.

W3C WAI: initial checks (new tab)

Content and errors must remain understandable on small screens and when zoomed in.

How to check? Check labels, contrast and enlarged content

Check field labels, useful image alternatives and contrast. Zoom the page to 200% and test a width of 320 px, in each available theme.

W3C WAI: initial checks (new tab)

Security & access

0 / 4 applicable checks completed

Private keys and service credentials must remain in authorised environments.

How to check? Check that no secret is exposed to the browser

Inspect public files, network responses and logs. If a secret has been exposed, revoke or replace it before fixing its configuration.

OWASP: secrets management (new tab)

Delivered components and HTTP protections need checking on the deployed version.

How to check? Review dependencies and security headers

Run the audit provided by your ecosystem, review alerts and check HTTP headers. Test real journeys with the protections applied, particularly the CSP.

OWASP: HTTP headers (new tab)

Each account must access only the resources it is authorised to use, with server-side checks.

How to check? Test sign-in and access rights

With two test accounts and a signed-out session, try another account’s URLs and resource identifiers, including through the API. Check that unauthorised access is denied.

OWASP: access control (new tab)

Users must be able to end their session and recover access using the provided mechanism.

How to check? Test sign-out and account recovery

Test sign-out, expired or already-used recovery links and error messages. Check that sessions no longer grant access to resources after revocation.

OWASP: password recovery (new tab)

Backup & restore

0 / 3 applicable checks completed

Code alone is not always enough: files, configuration and content may be required.

How to check? Keep what is needed to restore the website and its content

Identify what needs backing up, where it is stored and the access needed. Restore a copy in an isolated environment and check representative pages.

A backup must be readable and usable to resume a business workflow.

How to check? Restore a backup of the application data

Restore a test backup in a separate environment. Check the data and a representative workflow; document the procedure and who can run it.

A faulty deployment needs a recovery procedure suited to the project.

How to check? Prepare rollback to the previous version

Try the rollback outside production. For an application, check migration and data compatibility with the restored version.

Transactional emails

0 / 2 applicable checks completed

Confirmations and access messages must arrive with usable content and links.

How to check? Test receipt of transactional emails

Trigger each message with test addresses at several providers. Check the sender, delivery, links and outcome from another device.

Sender configuration and sending errors must be verifiable.

How to check? Check the sending domain and failure tracking

Check the DNS records requested by your email provider. Simulate a failure and check its reporting, planned retries and the absence of secrets in logs.

Payment

0 / 2 applicable checks completed

Each payment outcome must produce a consistent state without creating duplicate purchases.

How to check? Test successful, declined and cancelled payments

In your provider’s sandbox, simulate success, decline, cancellation and retry. Check confirmation, amounts and the state of the order or subscription.

Sandbox example: Stripe (new tab)

A browser redirect is not enough to confirm a payment.

How to check? Check server-side payment notifications

Using the provider’s test tools, verify notification authenticity. Replay a notification and test a different arrival order: the business outcome must remain consistent.

Notification example: Stripe (new tab)

Errors & monitoring

0 / 2 applicable checks completed

An important error must be detectable after launch.

How to check? Trigger a test error and check its reporting

Trigger a controlled error without real data. Check that it appears in monitoring and that the expected alert arrives, with useful context and without unnecessary sensitive data.

An outage must be visible and someone must know how to respond.

How to check? Plan availability monitoring and responsibilities

Test your availability check outside production. Verify the alert recipient, access to logs and the diagnosis procedure.

Measurement & privacy

0 / 4 applicable checks completed

Each tracked event should serve a specific need, with limited data collection.

How to check? Decide which measurements are useful at launch

List the chosen measurements and inspect requests throughout a complete journey. Check the data sent, providers and behaviour when measurement is refused or unavailable.

CNIL: cookies and trackers (new tab)

Trackers requiring consent must respect visitors’ choices; exemptions depend on their use and configuration.

How to check? Review trackers and consent choices

Inventory trackers and examine the rules applicable to each. In a fresh session, test before a choice, after refusal, after acceptance and after withdrawal. If no tracker is used, select “Not applicable”.

CNIL: cookies and trackers (new tab)

Information must be accessible and match the processing actually carried out.

How to check? Inform people when collecting their data

Inventory the data, purposes, recipients and retention periods. Check information near forms, useful contact details and how to exercise rights against CNIL recommendations.

CNIL: informing individuals (new tab)

Collected data must have defined retention periods and recipients suited to your context.

How to check? Check retention periods and access to data

Check team and provider access, planned deletion and retention periods applied to data and logs. Examine the relevant rules for your activity and document your choices.

CNIL: informing individuals (new tab)

Keep a record of your launch.

The profile, options and status of every check, in Markdown format.

This checklist guides your checks. It is not an audit or a security or compliance certification.

Something blocking you?

I can help you prepare for launch.

Let’s discuss your launch