The Website Content Checklist: What to Prepare Before You Brief a Developer

Here is a secret from the other side of the table: the thing that delays most website projects is not design, and it is not code. It is content — the words, photos and details only the business owner can provide. A build that should take three weeks stretches to three months because the About page text "is coming this weekend" for ten consecutive weekends. This checklist covers what to gather before you brief a developer, so your project moves at the speed you are paying for.

Your words: the copy for each page

Start with a simple page list — home, about, services, contact, whatever your business needs — and rough out what each page should say. It does not need to be polished prose; bullet points are fine, because a developer or copywriter can shape them. What nobody can do is invent your story, your process or your prices for you. Decide early who writes the final text: if it is you, block out real time for it; if you want it written for you, say so at the quoting stage, because copywriting affects both price and timeline.

Photos that are actually yours

Real photos of your team, premises and work build more trust than any stock library — we covered why in what makes a good business website. A modern phone camera in good light is genuinely enough. Two practical warnings: send the original files, not copies forwarded through WhatsApp, which compresses images until they look blurry on a big screen (send them as documents, or use a cloud drive link). And if you bought images anywhere, keep the receipts — your developer needs to know you have the right to use them.

Logo files in the right format

A screenshot of your logo cropped from your Facebook page will look fuzzy everywhere it is used. What your developer needs is the original vector file — usually ending in .ai, .svg, .eps or sometimes .pdf — from whoever designed the logo. If you cannot find it, ask the original designer; most keep archives. If the vector is truly lost and all that survives is a small blurry image, budget a modest fee to have the logo redrawn. It is a one-off cost that pays off across the website, signage and everything printed afterwards.

Testimonials and proof

Ask three to five happy customers for a short testimonial now, before the project starts — people are willing but slow, and this is the single most common piece of missing content on launch day. Get their permission to use a name or company name, which makes the quote far more convincing than "Anonymous, KL". While you are at it, gather the rest of your proof: certifications, licences, association memberships, awards, notable clients you are allowed to mention.

The business details nobody remembers until launch week

• ●Registered business name and SSM number, exactly as they should appear
• ●Full address, operating hours and service areas
• ●The phone number and WhatsApp number that will receive enquiries — and who answers them
• ●The email address for the site (ideally on your own domain, not a personal Gmail)
• ●Links to the social media accounts you actually keep updated
• ●Price lists, brochures or service menus, if you plan to publish them
• ●Your domain registrar login — see our domain name guide if you are not sure who holds it

How missing content actually delays a project

The pattern is always the same. The design is approved, the build finishes, and the site sits in staging full of placeholder text, waiting. Weeks pass, momentum dies, and eventually one of two bad things happens: the project stalls indefinitely, or the site launches half-empty — which, as we noted in our list of common SME website mistakes, looks worse than having no site at all. The fix is simple discipline: agree a content deadline alongside the development deadlines, and treat it as equally binding on you as the build dates are on the developer.

Do not let the checklist put you off

You do not need all of this to perfection before picking up the phone. A starter site needs only a fraction of it, and a good developer will tell you exactly what is required for your scope — we send every client a tailored version of this list at kickoff so nothing surprises anyone mid-project. If you are choosing who to work with, our guide to choosing a web developer in Malaysia covers the questions to ask. And when you are ready, request a free quote — bring whatever content you have, and we will tell you honestly what is still missing.