Website launch checklist and review worksheet
Check the customer journey, records and handover before agreeing a launch. Choose a business website, online store or private portal, record your own evidence and download the review. No signup needed.
BringPak Editorial Team · Published 15 October 2026 · About this resource
Review one complete journey with the people who operate it
For a service website, follow a visitor from the service page to a received enquiry. For a store, follow a representative order through the agreed payment and dispatch states. For a private portal, review the customer's records, permissions and approval steps. Use permitted test activity and synthetic records for those checks.
Mark an item Reviewed when your team has examined it and record where the evidence lives. Use Needs follow-up for an unresolved issue, or Outside this scope with a reason when the capability is not part of the project. Unchecked work should remain visible in the handover discussion. These self-recorded states do not establish that a site is secure, accessible, indexed or ready to launch.
Record your launch review
Choose a project type, mark each check and note the evidence or next action. Use Outside this scope with a reason when a check does not apply.
Answers stay on this page and are lost on refresh. Download before leaving. Use brief references; keep credentials and customer records in your own systems.
Changing type keeps your notes. Downloads include only the selected type.
- Not checked
- 12
- Reviewed
- 0
- Needs follow-up
- 0
- Outside this scope
- 0
Use the checks below to record evidence and follow-up work.
Preview review
WEBSITE LAUNCH REVIEW Project type: Business website Planning worksheet from BringPak. Complete checks against your agreed scope. These are self-recorded review states, not an automated audit, launch approval or ranking score. Review states: 0 reviewed; 0 need follow-up; 12 not checked; 0 outside scope. Reviewed/outside-scope items without an evidence reference or reason: 0. Agreed scope and sign-off owner State: Not checked Evidence / next action: Not recorded Domain, hosting and staff account ownership State: Not checked Evidence / next action: Not recorded Approved content and contact details State: Not checked Evidence / next action: Not recorded Mobile navigation and readable pages State: Not checked Evidence / next action: Not recorded Enquiry delivery and error handling State: Not checked Evidence / next action: Not recorded Keyboard navigation and form labels State: Not checked Evidence / next action: Not recorded Public indexing and private access boundaries State: Not checked Evidence / next action: Not recorded Existing URLs, redirects and missing pages State: Not checked Evidence / next action: Not recorded Page titles and shared-link previews State: Not checked Evidence / next action: Not recorded Measurement and privacy choices State: Not checked Evidence / next action: Not recorded Recovery method and change ownership State: Not checked Evidence / next action: Not recorded Staff handover and support arrangements State: Not checked Evidence / next action: Not recorded Before agreeing launch: review unresolved work with the responsible team, record acceptance and identify the recovery owner. Keep credentials and private customer records in your own approved systems. https://www.bringpak.com/resources/website-launch-checklist
The checks and what to record
Checks for every project
Agreed scope and sign-off owner
Name the pages and customer journeys being accepted, the person reviewing each area and what is deferred. A business owner may accept content while an operations lead reviews order handling. Record those decisions separately and agree who authorises the launch.
Return to the review builderDomain, hosting and staff account ownership
Check who controls the domain, DNS, hosting, email and external provider accounts. Confirm the business can recover access and remove an old staff account. An invoice for development does not establish that these accounts are already in the intended owner's control.
Return to the review builderApproved content and contact details
Review service descriptions, product information, prices where shown, permitted photos and contact details. Follow a phone or email link on an actual device. Remove example business details and confirm who approves later changes. Generated draft copy still needs review against the actual offering.
Return to the review builderMobile navigation and readable pages
Walk through navigation, long headings, the main action and any tables at a narrow phone width. Check text is readable, controls are usable and content does not disappear behind a sticky header. Repeat with images unavailable and a slower connection where practical.
Return to the review builderEnquiry delivery and error handling
Use an agreed test enquiry and confirm the intended staff destination receives it with the correct service context. Check required fields, errors, duplicate clicks and the failure message when delivery is unavailable. An on-screen success message should correspond to the agreed receipt or storage outcome.
Return to the review builderKeyboard navigation and form labels
Use Tab and Shift+Tab to follow links and controls, see the focus position and operate the main action. Check field labels, useful error text and image alternatives. Automated accessibility checks can help find issues, but record manual journey checks as well.
Return to the review builderPublic indexing and private access boundaries
For public pages intended for search, review successful responses, canonical URLs, index settings, sitemap entries and visible content without JavaScript. Keep private records behind access controls. Robots exclusions guide cooperative crawlers; they are not a replacement for authentication or customer permissions.
Return to the review builderExisting URLs, redirects and missing pages
For a redesign, list useful old URLs and their relevant new destinations. Test permanent redirects, links and a genuinely missing page. Avoid redirecting every removed page to the homepage. If the site is new, mark old-URL migration outside scope with a reason while still checking navigation and missing-page behaviour.
Return to the review builderPage titles and shared-link previews
Open representative pages directly and check that the page title, description, canonical and preview image describe that page. Check a shared link using the intended platform's available preview tools. A correct preview does not establish that a search engine has indexed the page.
Return to the review builderMeasurement and privacy choices
Agree which events mean a valid enquiry, booking or completed order and distinguish them from page views and clicks. Test that controls for applicable privacy choices are respected. Use labelled test activity where measurement is required, and avoid counting your team's tests as customer outcomes.
Return to the review builderRecovery method and change ownership
Identify who can pause a change, restore a known deployment and recover the necessary records. Review the recovery method in a suitable environment, including access and the state it restores. Restoring code alone may not reverse a provider transaction or recover later data changes.
Return to the review builderStaff handover and support arrangements
Ask the staff who will operate the site to complete their regular tasks. Confirm instructions, content editing, exports where agreed, renewals, support hours and the route for reporting an issue. Record outstanding work and the owner of each item rather than relying on a broad 'all done' message.
Return to the review builderAdditional online-store checks
Variants, stock and final order details
Test a representative product with its size, colour, quantity and price. Check unavailable combinations, the last unit and the final order summary. Identify the authoritative stock record and what happens when shop and website activity overlap.
Return to the review builderVerified payment and COD states
Keep a COD order, an uploaded receipt and provider-verified payment distinct. Use the provider's permitted test process and review a failed or uncertain result before production. Confirm which verified event changes payment status and how staff handle a mismatch.
Return to the review builderDispatch, cancellation and returns
Follow the order reference through confirmation, packing, dispatch and a delivery exception. Check who can cancel, approve a return or change an address. Reconcile courier settlement separately from delivery where relevant. Use the business's approved policies and operating responsibilities.
Return to the review builderDuplicate orders and integration failures
Repeat a synthetic order event and simulate an unavailable downstream service. Confirm one intended transaction, a usable staff notice and a review route. When a provider may have accepted an action before timing out, check the recorded result before creating another request.
Return to the review builderAdditional private-portal checks
Customer-to-record access boundaries
With synthetic customers A and B, check record pages, direct file addresses, search and export access. Changing a reference must not reveal another customer's information. Review staff permissions separately and record the agreed access rules; a visible login screen alone is insufficient evidence.
Return to the review builderDocument versions and approval history
Approve a specific synthetic document version, revise it and check which approval remains recorded. Agree whether the new version needs another review and who can publish it. Keep a draft, a published update and a customer approval as separate states.
Return to the review builderRemoved users and exported files
Remove a synthetic user's access and check the agreed sign-in, session and file-access behaviour. Decide which staff can export records, how a downloaded copy is handled and what can actually be revoked. Access removal cannot recall copies a permitted user already downloaded.
Return to the review builderExisting record source and failed updates
Identify which system owns each displayed value and how stale or failed updates are shown. Check a repeated update, a missing record and an unavailable connection. Record how staff reconcile discrepancies and whether a migration is part of the launch scope.
Return to the review builderWorked example: a form message that has not reached staff
A synthetic review finds that the form shows a success message, but the receiving team cannot find the test enquiry. Record Enquiry delivery as Needs follow-up. A useful next action might be: “Developer to check the agreed receipt destination; staff member to confirm one labelled test arrives with its service context.” Keep a reference to the test and its outcome.
If a later test reaches the intended destination, the team can record Reviewed with that reference. The change does not establish that all future delivery is guaranteed or that other checklist items have passed. This is an illustrative workflow, not a report of a customer's launch.
Sources and next steps
For search moves, review Google's site-move guidance. The checks here also draw on W3C WAI preliminary accessibility checks and OWASP authorization guidance. This original AI-assisted planning resource is published by BringPak, which also offers development services. It is not a substitute for a scoped technical assessment.