Website delivery checklist.

A clear checklist reduces confusion before launch and helps both sides understand what has been checked.

Launch discipline

Website delivery checklist before launch

A website should not be considered finished only because pages are visible. It must be checked for content, links, mobile layout, forms, SEO basics, speed and ownership details.

A professional handover reduces avoidable mistakes after upload and makes it clearer what the client receives, what is live and what still needs future improvement.

Delivery focus

Content
Links
Forms
SEO basics
Handover

Before launch

Checks before launch

These checks reduce basic mistakes before the site goes public.

Page titles checked

Each important page should have a proper title and clear purpose.

Mobile layout checked

The website should be reviewed on smaller screens before launch.

Navigation links checked

Menus, footer links and internal links should go to the right pages.

Forms tested

Lead and contact forms should be tested before relying on them.

CTA buttons tested

WhatsApp, call, email and enquiry buttons should open correctly.

Legal pages linked

Privacy, terms and support pages should be reachable where required.

Sitemap and robots checked

Basic crawl files should be present if the site is meant to be indexed.

Contact details verified

Phone, email, location and WhatsApp details should be correct.

After launch

Checks after launch

A launch still needs review after files go live.

Search Console submission

The site can be submitted for indexing if search visibility is needed.

Analytics or tracking

Tracking can be added if the client wants to measure actions.

Broken-link check

Live links should be tested again after upload.

Speed review

Heavy files and slow pages should be noticed early.

Backup copy

The final files should be kept safely.

Future update plan

The client should know how future edits will be handled.

Handover

Client handover items

A website handover should make ownership and future work clear.

Website files

The client should know what files are delivered.

Hosting details

Hosting access and setup notes should be documented where relevant.

Domain details

Domain ownership and DNS responsibility should be clear.

Admin/login details

Any admin access should be recorded safely if included.

Maintenance notes

The client should know what is included after launch and what is extra.

Pre-build

Business details collected
Page count confirmed
Features confirmed
Content responsibility understood

Design

Homepage structure
Inner page layout
Mobile spacing
Button hierarchy

Content

Service/product information
Contact details
Photos or work visuals
Legal text where needed

SEO basics

Page titles
Meta descriptions
Heading structure
Internal links

Technical

Sitemap.xml
Robots.txt
404 page
Favicon and OG image

Launch

Form/contact test
WhatsApp links
Mobile check
Handover notes