Prepare a website content plan by connecting each page to a reader task, the evidence needed to answer it and a named content owner. Prioritise useful decisions over a list of keywords. Give every proposed page a clear next step and a reason to exist alongside the pages already available.
A practical plan should help a writer decide what to include and help an owner decide whether the page remains accurate. Start with a visitor question that the business can answer. Then identify the records, documentation or people needed to support that answer before commissioning the draft.
What does the reader need to accomplish?
The GOV.UK user-needs guide offers a transferable research method. GOV.UK’s discovery guidance starts with likely users and their tasks. Its discovery questions include the channels people currently use. For a business website, adapt those questions to the visitor’s decision and the information already available elsewhere.
A service enquiry might begin with uncertainty about what information to send. An existing customer might instead need to find a support route. These are different tasks, even if both involve contacting the same company. Write each need in the visitor’s words before deciding whether it requires a separate page.
It recommends reviewing existing evidence such as analytics and search logs. It includes interviewing and observing actual or likely users. Use appropriate records you are authorised to review, and preserve the question that each record helps answer. A search phrase alone may leave the visitor’s actual intention unclear.
It treats opinions or suggestions that do not originate from users as assumptions to research. Label an internal preference accordingly: “We think visitors want a comparison table” is a proposition to investigate. Ask which decision that comparison would support and what would make its entries accurate and useful.
Its guidance asks teams to focus on problems rather than possible solutions. A reader who needs to understand project requirements does not necessarily need a downloadable brochure. Consider whether a clear page, an example brief or a contact instruction would resolve the need more directly. These are editorial options to assess through evidence.
How should evidence shape the page brief?
Separate three kinds of material in the brief: established business facts, publisher documentation and the original explanation you intend to contribute. Assign an owner to the business facts. Link the documentation that supports technical statements. Explain how the proposed worksheet, comparison or worked example helps the reader apply that information.
Google’s helpful-content guidance supplies useful review questions. Google asks whether content provides original information or analysis. Google asks whether the main heading gives a descriptive summary. Use these questions to challenge a brief that offers little beyond a broad topic label and a target phrase.
Google encourages accurate authorship information where readers expect it. Decide who will stand behind the published information and how contributors will be described. A named page owner in the planning sheet is an operational responsibility; the public byline should accurately describe the authorship arrangement.
Google suggests asking trusted people unaffiliated with the site for an honest assessment. When arranging a review, give the reader a task and ask what remained unresolved. Specific feedback about a missing requirement or confusing next step is easier to act on than a general request to make the copy more engaging.
Which fields make a content plan usable?
Use the following original planning sheet as a starting point. Complete a row for an actual proposed page, keeping unresolved questions visible until the responsible person supplies the evidence.
| Planning field | What to write | Review question |
|---|---|---|
| Reader task | The decision or action in the visitor’s words | Can a likely reader recognise it? |
| Existing answer | Current page or other available route | Would improving that answer be clearer? |
| Evidence | Approved records and primary documentation | Which assertion does each item support? |
| Original contribution | A useful explanation, worksheet or comparison | What can the reader do with it? |
| Owner | Person responsible for factual accuracy | Who resolves a disputed statement? |
| Next step | Relevant destination or information to prepare | Does it follow from the page’s answer? |
Add a short decision note beneath the row: create, improve, combine or investigate. The note should explain the reader benefit. If two proposed pages answer the same question, review them together before assigning separate drafts. If their tasks differ, make that difference explicit in both briefs.
Keep evidence close to the statement it supports. A source list at the end of a planning document can become difficult to interpret after several revisions. Record the intended assertion beside its source and identify any qualification that a writer must preserve, such as the product edition or configuration covered.
Original brief-preparation exercise
Consider a hypothetical business receiving enquiries that omit essential project information. Create a proposed page called “What to prepare before discussing your website”. Treat the problem as a research question first: ask the enquiry owner which missing details prevent a useful conversation and examine appropriate sample records.
Write the reader need as “I want to explain my project clearly so that the next conversation is useful”. Identify the information the business genuinely needs to begin. Keep later project decisions out of the first-contact checklist unless the owner can explain why the visitor needs them at that stage.
Next, map each checklist item to its purpose. Existing site address may help the team understand the current situation; an intended visitor action may clarify the desired outcome. Those are proposed planning prompts. The business owner should decide which belong in the actual process and confirm the wording before publication.
Draft an example using fictional details and ask a likely reader to use it to prepare a brief. Observe where they hesitate or supply information the team did not intend to request. Record the observation separately from the editor’s proposed correction, then revise the instruction and check the new wording.
Finally, compare the proposed page with the existing contact and service pages. Decide where the preparation checklist should be linked and whether another page already contains part of the answer. Assign responsibility for keeping the checklist aligned with the actual enquiry process when that process changes.
How should ownership continue after drafting?
Give the owner specific review triggers: a service change, revised documentation, an altered contact route or a reader report that the instructions no longer work. Set a review arrangement suitable for the material rather than inventing one universal interval for every page.
Keep the approved brief and its evidence with the draft. When an assertion changes, update the relevant source relationship and explain why. This makes it easier for the next editor to preserve useful detail while correcting information that has become outdated.
For related planning, see website development and SEO. Get started with your audience questions, existing pages and the evidence available to answer them.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.