Website content preparation checklist

Before starting a website, prepare its business goal, service details, contact information, media permissions and the people who will approve the facts. You do not need polished copy for every page on day one. You do need to distinguish confirmed information from open questions and identify who can resolve them. This checklist helps you build a useful handover pack rather than prescribe the same page count for every business.

1. Define what the website should help people do

Explain who will visit, what decision they need to make and what should happen next: an enquiry, appointment or informed service choice. Choose the main goal before choosing pages.

The intended audience and questions heard in real sales conversations
The service or product visitors should understand first
The main action and the person responsible for following it up

2. Collect business and service facts

Gather the correct business name, service area and contact details. For each service, explain the audience, problem, process and scope. If pricing varies by project, describe the assessment criteria instead of publishing an unapproved figure.

Brand and legal names with agreed Thai and English spellings
Service scope, inclusions, exclusions and approved terms
Email, telephone, opening hours and the recipient of form enquiries
Reviewed customer questions and answers; no invented reviews or work

3. Organise images, logos and usage permissions

Supply usable source files and explain where each belongs. An unnamed picture forwarded from a chat gives the team little context. Check permission to use media on the website and any credit requirements.

Vector or transparent logos and existing brand colours or guidance
Product, team, location or project pictures with captions and filenames
Image ownership, licences or permissions and usage restrictions
The purpose of each image so alternative text can fit the page context

4. Assign languages, reviewers and missing information

Pair Thai and English content by page. Identify who approves names, prices and terms before translation. Mark missing information clearly and agree whether to wait, omit it or add it in a later release.

Matching page content across languages
A factual reviewer for each topic and a final approver
Missing items, their owners and their effect on delivery
The person who maintains content after launch and the update process

5. An example handover pack

The following is fictional, not a customer or completed project. “Good Day Gardens” wants homeowners to send their site size and requirements before a consultation. It prepares service content, authorised project images and an enquiry form. Package pricing stays out of the first release because it has not been approved.

Business folder: company facts, audience and enquiry goals
Service folder: garden-design scope, process and required customer information
Media folder: permitted pictures, filenames, captions and permissions
TH/EN page tracker: content, reviewer and ready or waiting status

6. Agree when delivery work can start

Complete information supports a realistic scope and delivery assessment; it does not guarantee a fixed turnaround for every project. Exploera scopes page count, presentation, modules and custom work before agreeing the delivery period. Review drafts and check contact routing with the responsible team before publication.

Files open correctly and the latest versions are identifiable
Names, prices, scope and both languages have been reviewed
Media permissions and contact recipients are confirmed
Commerce or other integrations have their own agreed scope

Useful next steps

Editorial references

Google Search Central: people-first content · W3C WAI: choosing image alternative text

Prepared by Exploera with AI-assisted drafting and source review. The business example is fictional; the illustration is AI-generated. Actual service scope follows the agreed proposal.