# Website launch checks

Site / version:
Reviewer:
Date:

For every check below, record the URL, device/browser, expected result, observed result and evidence. Mark untested items as untested; a loading homepage is not a completed launch check.

## Content
- [ ] Each page answers a distinct visitor question.
- [ ] Services, location, hours and contact details match the business.
- [ ] Portfolio examples distinguish completed work, concepts and sample data.
- [ ] Image and testimonial permissions are recorded.
- [ ] Prices and exclusions match the approved offer.

## Navigation and access
- [ ] Primary actions work from homepage and service pages.
- [ ] Menu works with keyboard and at narrow widths.
- [ ] Focus stays visible; content remains usable when zoomed.
- [ ] Old URLs resolve or have an appropriate redirect.
- [ ] Unknown URLs return a genuine not-found response.

## Enquiry path
- [ ] Labels and required fields are clear.
- [ ] Invalid input gives a specific recoverable error.
- [ ] A permitted test submission reaches its intended destination.
- [ ] Confirmation describes the actual receipt state.
- [ ] Delivery failure leaves a usable contact alternative.
- [ ] Repeated attempts do not silently create duplicate work.

## Search and sharing
- [ ] Titles and descriptions describe their own page.
- [ ] Canonical URLs use the public domain.
- [ ] Published pages are reachable from useful internal links and sitemap.
- [ ] Private, test and editor routes remain excluded.
- [ ] Article share images and image alt text are appropriate.

## Ownership and recovery
- [ ] Domain, hosting and email owners are recorded.
- [ ] Renewal notices reach the agreed owner.
- [ ] Access is stored in an appropriate password manager.
- [ ] A known recovery version exists and the owner knows how to restore it.
- [ ] Remaining issues and final launch approval are recorded.

araNET Studio — https://www.aranetsolutions.com/blog/service-business-website-launch-checklist