Development
Website planning: what to prepare before design
Prepare a page list, one complete content example and the journeys the website needs to support. Assign responsibilities and agree how the finished website will be checked before discussing design and development.
Before design begins, prepare a few concrete materials: a page list, the content for those pages and the ways people will use the website. These make it easier to estimate the project, choose functions and agree on the finished result.
This is a practical preparation pack for a business owner. You can assemble it in a shared folder and spreadsheet, then use it with your designer and developer. The examples describe an imaginary coffee machine repair business.
Define what your website needs to achieve
Picture a typical enquiry. A customer wants to know whether you repair their model, how to bring it in and what information is needed for an estimate. The website should answer those questions and help them contact the workshop.
Write down three common journeys. For each, identify the starting point, information needed and final action. For example: find repair support for a model, read the diagnostic process and fees, then submit the model and fault description. This gives you a basis for a page and a form.
Also describe what the team does after receiving the message. Your reception or support team needs the right details to handle it. If a specialist prepares the estimate, explain to the customer how the response process works.
Plan the pages your website needs
Start with the actual services you provide. You do not need to design every screen yet. Identify the distinct offers and useful information sections the website will contain.
| Page | Content | Visitor action |
|---|---|---|
| Coffee-machine repairs | Supported equipment, drop-off, diagnosis and repair conditions. | Submit the model and problem. |
| Office equipment servicing | Service arrangement, visits, scope and estimate inputs. | Discuss servicing requirements. |
| Drop-off location | Address, opening hours, directions and contact. | Get directions or call. |
| Preparing equipment for drop-off | What to bring and what information to provide. | Prepare for the visit. |
Add four working columns: content owner, current readiness, proposed page address and source-file links. The team can then see which sections are ready for design and which need more material.
Plan for SEO before design begins
For each service or product page, list the language customers use to describe the service. Compare it with the actual offer. A repair page and an equipment-cleaning guide address different needs; they may require different information and next steps.
Plan navigation alongside the pages. Important services should be accessible from a clear section of the website. Google's link documentation explains how links using an a element with an href address help search engines discover pages. The link wording should describe its destination.
Reserve fields for the page title and a short description in your inventory. Finalise them once the content is ready, so the search presentation matches what visitors will find on the page.
Gather and organise your content
Group files by page and use understandable filenames. Create one location for current versions instead of relying on several message attachments. Label each photograph with its subject and intended placement.
- Copy: service descriptions, conditions, contact details and answers to common questions.
- Photographs: source files at a suitable resolution, including portrait and landscape options.
- Brand materials: logo, available font weights, colours and presentation references.
- Data: services or products, specifications, prices and update rules.
- Messages: submission confirmation, staff notification and any planned customer response.
Prepare one complete example for each important page type. A catalogue item needs its specifications and photographs; a service page needs the actual conditions. A complete example makes missing information elsewhere easier to identify.
Define features through real user journeys
A form can mean very different things. Specify the required fields, message destination, attachment support and the response the visitor sees. Apply the same approach to booking, catalogue search, payments and customer accounts.
| Function | Questions for the brief | Acceptance check |
|---|---|---|
| Enquiry with a photo | File types and sizes, required fields, recipient. | The message and image arrive; the visitor receives confirmation. |
| Appointment booking | Source of available times and confirmation process. | The chosen time appears correctly for customer and booking team. |
| Price editing | Who edits the price and where it is repeated. | A staff member updates it using the instructions; related pages show the new value. |
Select the content management system after making this list. Focus on everyday operations: adding a service, replacing a photo, changing a price and reviewing an enquiry. Ask for a demonstration using your content.
Agree what needs to be ready for launch
Create an acceptance list around visitor actions. Include reading the conditions on a phone, navigating between pages, submitting forms and receiving messages. For a redesign, also map old page addresses to their new equivalents for the technical transition.
Review contrast, text resizing and keyboard operation. Form fields need understandable labels: the W3C guide explains how to associate labels with controls so visitors can identify their purpose.
Open the finished website on a phone and computer. Check image sizing, text clipping, accessible buttons and clear form errors. Include loading performance in acceptance criteria instead of leaving it until a campaign is ready.
Plan the website handover
Keep domain, hosting, content management and analytics access with an appointed business representative. Add content-update instructions and a list of configured integrations. Assign responsibility for maintaining prices, contact details and service conditions.
Your preparation pack now contains journeys, a page inventory, materials, functional requirements and acceptance criteria. It provides a concrete basis for discussing website development. Our service page plan helps with the content of individual sections.
Common website planning questions
Can we begin before all the copy is ready?
Yes. Prepare one complete example of each important page type and assign the remaining materials. The launch plan should account for content readiness.
Do we need a large website immediately?
The initial scope depends on business needs. You can start with essential services and contact information while planning a clear expansion path. Keep deferred sections in a separate list.
How should we brief a designer using reference websites?
Identify what you like: heading scale, navigation, cards, photography or the presentation of conditions. Specific notes are more useful than a general request for a similar website.
When should an SEO specialist join?
When the team discusses pages, addresses, content and navigation. These decisions affect later search work, so it is useful to review them before final layouts.
Share this article