Home / Questions / What content do I need to give my web developer?
What content do I need to give my web developer?
Before your project starts, give your developer your logo, brand colours and fonts, text for each page, photos, contact details, service and price information, examples of sites you like, logins for domain and hosting, and legal pages such as privacy policy. A complete website content checklist saves weeks.
The fastest website projects are the ones where content arrives on day one. A website content checklist helps you gather everything your developer needs before design starts, so nobody waits and nothing is forgotten.
Use the checklist below and tick items off as you collect them.
Website content checklist: brand
- Logo in high quality, ideally vector (SVG or PDF) plus PNG.
- Brand colours and fonts, if you have them.
- Any brand guidelines or existing printed materials.
Ready to act on this?
Get a written review of your site, or send us your question and we will reply within 24 hours.
Website content checklist: pages and text
| Page | What to provide |
|---|---|
| Home | Main message, who you help, key services, call to action |
| Services | One section or page per service: what it is, who it is for, benefits, price if shown |
| About | Your story, team members, experience, photos |
| Contact | Address, phone, email, map, opening hours |
| Reviews | Testimonials with names and permission |
| FAQ | Questions customers often ask |
Images and media
- Photos of your team, premises, products or work.
- Videos, if you plan to use them.
- Stock images you have licensed, with proof of licence.
Technical and account details
- Domain registrar and hosting logins, or permission to buy them in your name.
- Email addresses that forms should send to.
- Google Analytics, Search Console and Business Profile access.
- Payment gateway account if you sell online.
Legal and policy pages
- Privacy policy.
- Terms of service.
- Refund, shipping and cancellation policies for stores.
- Cookie notice if you use tracking.
Examples and preferences
Share two or three websites you like and say what you like about each: layout, colours, tone or features. This is often more useful than long descriptions. Our web developer brief guide shows how to write it up.
Example: a project that started on time
A law firm used a website content checklist and sent a shared folder on day one: logo files, lawyer photos and profiles, text for each practice area, office details, three example sites and the privacy policy. Design began the same week, and the site launched a week ahead of plan. A website content checklist is simple, but it turns a vague project into a clear one. It also helps you spot gaps early, such as missing team photos, so you can arrange them before they cause delays.
Tips for writing your content
- Write how customers speak, not in internal jargon.
- Use short paragraphs and clear headings.
- Answer the questions customers ask most.
- Google’s guidance on helpful content is a useful reference.
How to organise your files
Create one shared folder with sub-folders for brand, pages, images and accounts. Name files clearly, for example “services-tax-returns.docx” or “team-priya.jpg”. Keep one document listing who will approve content and by when. Share the folder link with your developer at the start. A tidy folder built from a website content checklist removes most back-and-forth emails and makes it easy to see what is still missing.
Frequently asked questions
What if I do not have all the content yet?
Start with what you have. Read building a website without content for options.
Can my developer write the content?
Many offer copywriting as an extra. Agree this in the scope.
In what format should I send text?
A shared document per page is easiest, with headings marked clearly.
Do I need professional photos?
Real photos of your business build more trust than stock images, even if taken on a good phone.
Should my website content checklist include prices?
If customers compare prices, showing a starting price or range usually brings better enquiries. Decide before the build starts.
How much text does each page need?
Enough to answer the main questions clearly. Service pages often need a few hundred words; the home page can be shorter.
Not sure where your site stands?
Send us the details and we will reply within 24 hours with a clear next step.