A practical guide

Before buying a domain, brief one page your readers need

Use a worked content brief to define your readers, check available evidence and plan a useful website before buying a domain.

Before buying a domain for a new publication or business website, write the brief for one page that somebody would use. It should answer a specific question using information you can obtain and maintain. A name can wait until you know what the website will do.

This is a small test of the publishing idea. If you cannot describe the reader’s task, the evidence behind the answer or the next useful step, a larger list of article titles will not resolve the gap.

Describe a task rather than a topic

“A website about local venues” is a topic. “Help an organiser shortlist rooms for a twelve-person workshop” is a task. The latter identifies a person, a situation and a decision.

The GOV.UK Service Manual’s guidance on learning user needs starts with understanding what people need to do. For a small independent site, you can apply that approach by speaking to intended readers, reviewing the questions you already receive or observing how someone currently completes the task. Keep evidence from those conversations separate from your own guesses.

Do not invent research to make the brief sound established. “We think organisers struggle to compare room layouts” is a hypothesis until you have checked it. Write down how you will investigate it and whether the result could change the idea.

Give neighbouring pages different jobs

Consider a fictional meeting-room directory. Its three proposed pages could have these distinct purposes:

  • A shortlist page helps the organiser identify rooms that may fit the date, location and intended layout.
  • A quote-comparison worksheet helps them compare what each venue includes and what remains uncertain.
  • A pre-booking checklist helps them confirm access, equipment and cancellation terms directly with the chosen venue.

Those pages support different decisions. Publishing three variations on “best meeting rooms” would give the reader less help, particularly if each one repeated the same unsupported descriptions.

Choose the first useful output before commissioning the whole site. You may discover that a clear comparison sheet is more valuable than ten introductions to the subject.

Work through one page brief

Here is an illustrative brief for the directory’s quote-comparison page. No actual venues or facilities are implied.

Reader and situation: an organiser has responses from three venues for the same workshop date.

Decision: which quote should they pursue, and what must they clarify first?

Information required: room layout and stated capacity for that layout, hire period, included equipment, additional charges, access arrangements, payment dates and cancellation terms.

Evidence plan: retain each venue’s written response and record when it was received. Mark unanswered questions as unknown. Confirm any requirement that matters to a participant with the venue rather than inferring it from a photograph.

Original contribution: a blank comparison worksheet, plus one clearly fictional completed row showing how an excluded projector charge changes the comparison.

Next step: send the remaining questions to the shortlisted venues. The worksheet does not make a booking or guarantee that a venue will meet an individual’s access needs.

Maintenance: review the page when the worksheet changes or a reader identifies a missing comparison field. If the site later publishes venue-specific facts, assign someone to check those facts with the provider and show the relevant date.

That brief is specific enough for an editor to reject an attractive but irrelevant draft. A general history of meetings would not help the reader compare those quotes.

Check that the evidence is affordable to maintain

For every important claim, ask who can verify it and what happens when it changes. A directory of live prices and availability creates a different workload from an evergreen worksheet that readers complete themselves.

Budget for research, permissions, editing and updates as well as design and hosting. If the proposed site depends on photographs or documents you do not own, resolve the permission question before building pages around them. Public availability does not by itself tell you what reuse is permitted.

The W3C’s writing tips provide useful checks for headings, link wording and instructions. Apply those to the worksheet too: “Enter the quoted hire period” tells the reader more than an unexplained box labelled “Details”. Test the draft with someone unfamiliar with your plan and watch where they need clarification.

Choose the address after the purpose is clear

Now assess a possible domain against the actual brief. Is it understandable when spoken aloud? Does it suggest a service or affiliation the site will not provide? Would a reader reasonably expect to make a booking when your site only supplies guidance?

Put a short address decision beside the page brief. For the fictional room directory, record: the proposed name, an acceptable alternative, the person who will manage it, the confirmed acquisition route and the deadline. If the publication can use a suitable name it already controls, record that option too. This keeps a preferred name from becoming an unexamined dependency for the useful worksheet.

If a new UK address is needed, DomainSabre explains the different preparation questions for a new registration and acquiring a name already held by someone else. Content Charlie and DomainSabre are published by Serallo Domains Ltd. The guide is a related planning resource, not independent evidence that a proposed name is available or a recommendation to buy it. Use the route to identify work and uncertainty in your brief: who confirms the registration, which ongoing charges need checking, and whether the project can still launch if that name cannot be obtained.

Check registration, renewal and any purchase charges separately from the editorial budget. Buying a previously used name does not establish rights to its former content or a relationship with its former operator. Avoid making history, rankings or assumed visitors the substitute for a publishing plan.

Keep the first page brief with the project record. Before approving another article, identify the distinct reader task and the evidence it adds. If it merely repeats the first page with different keywords, improve the existing resource or choose a different question.

Sources

  1. GOV.UK Service Manual: Start by learning user needs
  2. W3C WAI: Writing for web accessibility
  3. GOV.UK: How copyright protects your work