All articles
PlaybookJul 2026 · 6 min read

How to plan your website content before the build starts

Sort out your pages, words, and images before anyone touches code. It saves money, avoids rebuilds, and keeps the project from stalling halfway.

Why content comes first, not last

Plan the content before the build because the words decide the layout, not the other way round. A designer who has your real headlines, product descriptions, and photos can build pages that fit. Give them empty boxes and placeholder text, and you get a pretty shell that breaks the moment real content goes in.

Most Hong Kong small businesses hit this the hard way. The site looks finished in the demo, then launch stalls for weeks because nobody wrote the About page or gathered product shots. Writing content later almost always means paying for design changes twice.

Start with a simple page map

List every page the site needs before deciding how any of them look. A typical small-business site runs to five or six pages: Home, About, a Products or Services page, Contact, and maybe a blog or FAQ. Write each page name in a column, then note in one line what job that page does for the visitor.

This map catches problems early. If two pages do the same job, merge them. If a page has no clear purpose, cut it. Fewer, sharper pages beat a sprawling site that nobody finishes writing.

Answer the reader's question on every page

For each page, write down the one question a visitor arrives with. Someone landing on your Services page is asking "can you do the thing I need, and roughly what does it cost?" Put that answer in the first two lines, not buried at the bottom.

Draft the actual words in a plain document first. A short headline, two or three sentences, a clear next step. Do this in Chinese and English if your customers use both, and check the Chinese reads naturally to a Hong Kong reader rather than sounding translated.

Gather your images and proof before the deadline

Photos, logos, and any proof you have take longer to collect than people expect. Real product shots, a decent headshot, customer reviews, and licence or certification numbers all belong in a shared folder before the build. Stock images look generic and often clash with your brand.

Note the resolution and orientation you have for each image. A homepage banner needs a wide, high-resolution photo; a phone snapshot will look blurry stretched across a screen. Knowing the gaps early gives you time to reshoot instead of settling.

Write it down so the whole team works from one source

Put the page map, the words, and the image list in one shared document that the designer, developer, and you all read from. When everyone works from the same source, there is no guessing about what goes where, and revisions drop sharply.

Keep it as a living document through the build. Content always shifts once you see it on a real page, so expect edits. The point is not to freeze every word, but to start with something concrete instead of a blank screen.

Common questions

How much content do I need ready before the build starts?

Aim for a first draft of every page plus the key images. It does not have to be final. Having real headlines and roughly the right length of text lets the designer build accurate pages, and you refine the wording as the site takes shape.

Can't the web team just write the content for me?

They can help with structure and polish, but they cannot invent your prices, your story, or your proof. Those come from you. Handing over rough notes about your business is far more useful than waiting for someone else to guess it.

Should I write in Chinese, English, or both?

Match your customers. Many Hong Kong businesses serve both, so a bilingual site is common. If you go bilingual, write each language properly rather than running one through machine translation, which local readers spot instantly.

What if my content isn't ready but I need the site live soon?

Launch a smaller site done well rather than a big one full of placeholders. Ship the pages you have real content for, mark others as coming soon, and add them once written. A tight three-page site beats an eight-page site that looks half-finished.

Have a project in mind?

Tell us what you need — software, production, or both. We reply within one business day.

Start an enquiry