Insights / Business website guidance

Business website guide

How to Prepare Content for a New Business Website

Prepare the questions, service details, proof, actions, contact facts, images, approvals, page plan, and ownership that give a new business website a solid content foundation.

Quick answerClear source material gives a website a stronger starting point than a rush to fill a page.

Signal 01

Begin with customer questions, not a homepage headline

Evidence nodeBefore choosing layouts or writing a headline, collect the questions customers ask when they are deciding whether to contact the business. Canadian web-writing guidance notes that people commonly scan online for words and links connected to the task they want to complete. Use that behaviour as a prompt to make the most useful answers easy to find rather than burying them in company background.1

Create a working question bank from enquiries, calls, emails, proposals, and conversations with the people who deal with customers. Group questions by the moment they arise: understanding the service, checking fit, preparing to start, and getting in touch. Write short, direct answers from approved business facts; flag anything that still needs confirmation instead of guessing.

  • What problem does this service address?
  • Who is it for, and when is it not a fit?
  • What does the process look like from first contact onward?
  • What should a customer prepare before contacting the business?
  • What is the clearest next step if someone wants to proceed?

Signal 02

Describe services in usable detail and assemble proof

A service name alone is rarely enough source material for a page. Prepare a separate content sheet for every core service or offering. State what is included, what is outside the scope, who is involved, the usual sequence of work, and any details a customer needs before making an enquiry. Use the words customers use when they describe the need, then check that terminology with the people who deliver the work.

Gather proof as verified source material, not promotional filler. This can include approved qualifications, licences or memberships where relevant, years of operation when confirmed, named methods or products the business is authorized to identify, and concise examples that it is permitted to publish. Keep the underlying source, approval status, and date checked beside each item so a writer does not have to reconstruct it later.

  • Plain-language service name and what the service covers.
  • Who the service is intended to help and practical preparation requirements.
  • Verified supporting facts and their source.
  • Items that need internal confirmation before publication.

Signal 03

Map the pages, actions, and contact routes

Make a page inventory before design starts. For every proposed page, write its purpose, the customer question it answers, the source material needed, and the one primary action a visitor can take next. This avoids treating the home page as a container for every detail and gives each page a clear job.

Prepare calls to action as specific instructions, such as requesting an estimate, booking a conversation, sending an enquiry, or calling during business hours. Pair each action with the information required to complete it. Build one approved contact-facts sheet with the business name, phone number, email address, contact-form destination, hours, reply expectations if stated, and any instructions for visits or appointments. Review these facts together before they are used across pages.

  • Home: immediate explanation and primary next step.
  • Services: scope, fit, and supporting details.
  • About: business background and approved facts.
  • Process or FAQs: common questions and preparation.
  • Contact: routes, hours, and practical instructions.
  • Supporting pages only when useful content is ready.

Signal 04

Prepare images as content, not decoration

Choose images that clarify the business, work, people involved, or an important step in the customer journey. For each selected image, record what it shows, the page where it may be used, the owner or source, the date, and whether it has been approved for publication. A simple image brief gives the design process more useful material than a folder of unlabelled files.

Evidence nodeDecide what information an image contributes before it is placed on a page. W3C guidance distinguishes images that convey meaning, images that trigger an action, and images that are purely decorative. Meaningful images need a brief text alternative that conveys their purpose; a functional image’s text alternative should communicate the action; decorative images can use an empty alternative. Include that intent in the image brief so the content remains clear when it is implemented.2

  • Original filename and a descriptive label.
  • What the image contributes to the page.
  • Source or owner and publication approval status.
  • Preferred crop or focal point, if known.
  • Whether the image needs purpose-focused alternative text.

Signal 05

Make real-world context specific and set approvals

Evidence nodeWrite in plain, concrete language. The Canada.ca Content Style Guide recommends organizing web content around tasks, putting important information first, and using headings that accurately tell readers what follows. Apply the same discipline to business content: replace broad claims with the actual service, process, or condition a customer needs to understand.1

Evidence nodeInclude real-world details that affect how customers can work with the business. Explain whether services are provided at a business premises, at the customer’s location, remotely, or through a combination of these. State service boundaries, travel conditions, appointment requirements, or availability only when they are accurate and approved. If the business uses a Google Business Profile, Google’s guidance says that its address and/or service area should be accurate and precise. Use the same approved facts across the website and profile.3

Evidence nodeName the person who supplies facts, the subject reviewer who checks details, the final approver, and the person who can update the page later. Plan for content maintenance after launch: GOV.UK’s content guidance organizes information around the task people need to complete and says it should describe the current situation. For a business website, that means assigning ownership for information that changes and reviewing it when the underlying business information changes.4

  • Content contributor: supplies source material.
  • Subject reviewer: confirms accuracy.
  • Approver: authorizes publication.
  • Page owner: updates the information over time.
  • Review trigger: a change to a service, contact fact, team detail, or operating process.

Useful follow-ups

Questions, answered clearly.

Do I need final website wording before design begins?

No. Start with accurate source material, customer questions, a page plan, and approved facts. Clear source material gives the writing and design work a reliable basis.

How many pages should a new business website have?

Use the number of pages needed to answer distinct customer questions without forcing unrelated information together. Begin with core pages and add supporting pages only when their content is ready.

Can we use stock images?

Yes, when they are suitable for the page and their use has been confirmed. Label them clearly and do not let them replace images or details needed to explain the real business.

Who should approve the content?

Choose one final approver, with subject reviewers checking the facts they know best. This keeps decisions clear and prevents unverified changes from becoming final copy.

What should be kept after the website is published?

Keep approved fact sheets, image records, the page inventory, source files, and a named page owner. They make later updates easier to assess and prepare.

References

  1. Canada.ca, Content Style Guide ↗
  2. W3C Web Accessibility Initiative, An alt Decision Tree ↗
  3. Google Business Profile Help, Guidelines for representing your business on Google ↗
  4. GOV.UK, Plan new GOV.UK content ↗