Give a Website Prototype a Believable Content Hierarchy
A useful content map gives overview, service and detail pages different jobs. Varying their sample material then helps you inspect the proposed structure.

A prototype with ten equally polished pages can still feel strangely flat. Every page begins with the same headline shape, repeats the same benefit list and ends at the same button. The missing ingredient may be a hierarchy of information rather than more realistic filler.
Give the example business a bounded task
Imagine a fictional garden-maintenance business serving shared residential grounds. The prototype needs to help a property coordinator distinguish regular maintenance from a one-off clearance and understand what information is needed for an enquiry. No completed customer projects or verified service claims are being represented.
Write that task above your content map. It gives the sample pages a common purpose without making them identical. You are planning what the prototype should explain; the business owner will still need to confirm the actual services and their boundaries before final wording is approved.
Make an overview page choose between routes
The Services overview should help the reader recognise the available types of work and choose a relevant next page. Give it short, contrasting summaries. For the example, regular maintenance concerns ongoing grounds care, while clearance concerns an agreed one-off task. Those are illustrative distinctions to discuss with the client, not facts about a real provider.
Do not paste the whole service explanation into both the overview and each detail page. Instead, record the overview’s job: introduce the choice and explain the difference. Its sample content needs enough contrast to make that choice visible. Three cards with interchangeable descriptions cannot show whether the proposed grouping makes sense.
Let service pages answer a deeper question
The regular-maintenance page should explain what a prospective customer needs to know about that particular route: intended situation, included work to confirm, important limits and the enquiry information required. The clearance page may need a different emphasis, such as describing the site and material involved. Do not assume every service needs the same sections just because a template makes duplication easy.
For each page, add a short map entry: reader question; information needed; source of that information; next useful destination. Where the client has not supplied the answer, label it as an open question. This prevents the content map from quietly turning a plausible sample into a settled business description.
Place supporting detail where it earns a page
A separate preparation guide might explain how a coordinator gathers photographs and site details before enquiring. It earns a page if that explanation is substantial and useful beyond one service description. A sentence about sending a photograph probably does not require another page merely to make the navigation look complete.
Draw the relationship explicitly: service page points to preparation detail when relevant, and the preparation guide returns the reader to the appropriate enquiry route. A relationship can be a helpful contextual link rather than a parent-child item in the main navigation. Your map should describe the reason for the connection, not just its position in a tree.
Give headings a hierarchy inside each page
Page relationships and heading levels are different layers of organisation. Within a service page, mark the main topic, its sections and any subsections. W3C WAI’s headings guidance explains that headings communicate page organisation and should be nested by rank. Use that structure intentionally rather than choosing a heading level solely for its visual size.
For the maintenance page, the service title is the page topic; sections could cover the situation, proposed scope and enquiry preparation. A subsection belongs beneath the section it explains. This example is an information-organisation exercise, not a complete accessibility assessment or a requirement that every business use these headings.
Read the map before filling every page
Ask a colleague to follow the property coordinator’s task using only the page names, short purpose notes and drawn links. Where would they compare the services? Where would they learn what to send? Note any repeated explanation or missing transition. Revise the map before producing a large sample set. The result should be a small set of pages with recognisably different jobs, ready for content that exercises those jobs.
Choose the page relationships before filling the pages. Generated sample entries become more useful when they follow a deliberate content hierarchy.
If the real material is still missing, use the plan for designing while client copy is late. When it arrives, preserve the decisions behind each temporary content slot.




Discussion 0
What did this article make you think about?