What Content Does a Small Business Website Need Before a Build?

The content needed for a small-business website is not a folder of slogans and stock photos. It is a verified set of answers to the questions a real buyer asks: What do you do, is it for me, where do you work, why should I trust you, what will happen, what might it cost, and how do I start?

You can hire a provider to interview, write, edit, and structure those answers. The owner still needs to supply accurate facts, usable evidence, access to the right people and systems, and timely approval. If that division is unclear, the project can look busy while the launch date keeps moving.

This guide turns content preparation into a practical buying and delivery checklist. It complements the small-business web designer scorecard, which covers provider selection, and the website build timeline, which shows where content dependencies affect delivery.

Build a source packet before you build a sitemap

Start with raw, reliable material rather than forcing the owner to write finished marketing copy. Put the following in one shared, clearly labeled location:

• legal and customer-facing business name
• primary phone number, email, location, service area, and customer-facing hours
• the main service, product, or offer the website should sell first
• the buyers who are a fit and the requests the business does not accept
• service descriptions, process, pricing approach, availability, and important limitations
• approved reviews, case examples, credentials, memberships, warranties, and guarantees
• logo files, colors, type choices, photographs, video, and usage rights
• common customer questions, objections, and the answers staff already give
• existing page URLs, analytics, search data, and content worth preserving
• forms, booking, payment, email, CRM, and notification requirements
• privacy, terms, accessibility, refund, cancellation, and industry-specific policy needs
• one final approver and the people responsible for specialist review

The goal is not to make the packet pretty. The goal is traceability. A writer should be able to point from a statement on the website back to an owner-approved fact, document, interview note, customer permission, or authoritative source.

Google's current people-first content guidance asks whether content serves an intended audience, demonstrates first-hand expertise, has a clear purpose, and leaves the reader able to achieve a goal. A source packet helps a builder capture the business's real expertise instead of filling a template with generic industry claims.

Map each page to one buyer decision

Do not decide the page count by copying a competitor's navigation. List the decisions a buyer must make, then group decisions that can be answered clearly on the same page.

This method keeps the architecture proportional to the business. A one-off campaign may need one complete landing page. A local service company with several meaningfully different services may need separate pages. Use the small-business website page-planning guide to turn the decision map into the smallest sensible site.

Verify identity, contact, and local facts

Before anyone writes headings, create one approved business-facts record. Confirm spelling, abbreviations, phone routing, email destination, physical address, service area, hours, holiday handling, appointment rules, license or credential language, and whether customers visit the address.

These details should match the real operation. Google's Business Profile representation guidelines tell businesses to use the real-world business name, accurate address or service area, precise hours, and the fewest categories needed to describe the core business. The guidance also says the website and phone should represent the individual business location and remain under the business's control.

Consistency is not permission to copy an inaccurate listing onto the website. If the site preparation uncovers a wrong address, old phone number, invented category, or service area that no employee can actually cover, correct the source record and the affected profiles deliberately. Use the local SEO checklist for service businesses for the broader listing, review, and local-page work.

For structured data, provide the same accurate facts to the builder. Google's LocalBusiness structured-data documentation describes supported business properties and requires the markup to reflect visible page content. Schema is a technical expression of the truth on the page, not a place to add cities, ratings, services, or credentials the business cannot support.

Document the offer in operational language

A useful offer brief explains more than the service name. For each priority service or product, answer:

• Who is it for, and who is not a fit?
• What situation usually causes a customer to look for it?
• What is included, optional, or explicitly excluded?
• What does the process look like from first contact to completion?
• What affects price, timing, availability, or eligibility?
• What must the customer prepare or decide?
• What evidence helps a cautious buyer believe the claim?
• What should the visitor do next, and what happens after that action?

Use the words customers and staff actually use, then edit for clarity. A page should explain the service without inventing certainty. Replace vague claims such as “best quality” or “unmatched results” with specific, supportable details: response windows, process steps, materials, service boundaries, qualifications, guarantees, or representative outcomes.

If the business cannot explain one primary offer and one next action, more design will not solve the content problem. Consider a smaller launch or a focused offer workshop before paying for several pages. The landing page versus website guide helps decide whether one offer should ship on a single page or within a broader site.

Collect proof with context and permission

“Add testimonials” is not a complete content task. Build a proof register with the quotation or claim, source, date, relevant service, customer name or approved attribution, permission status, supporting asset, and any important limitation.

• Reviews: preserve the customer's actual meaning and do not combine separate comments into a stronger claim.
• Case examples: describe the starting condition, work performed, timeframe, and outcome without implying that one result is typical for everyone.
• Credentials: verify the exact title, issuing body, holder, expiration, and allowed logo usage.
• Statistics: record the source, population, date, and calculation so the number can be checked later.
• Guarantees: supply the actual conditions, exclusions, remedy, and owner authorized to approve the promise.

The Federal Trade Commission's endorsements, influencers, and reviews guidance points businesses to the Endorsement Guides, the Consumer Review Fairness Act, and the Consumer Reviews and Testimonials Rule. The FTC's advertising FAQ for small businesses also explains that endorsements must reflect honest experience and cannot make deceptive or unsupported representations.

Those rules have fact-specific legal implications, so obtain qualified advice when needed. Operationally, the website project should at least record where every testimonial came from, whether it can be used, whether a material connection requires disclosure, and who approved the final presentation.

Prepare images as evidence, not decoration

Real assets often answer trust questions faster than another paragraph. Gather original photographs of the location, team, process, equipment, finished work, packaging, or customer experience when they are relevant and safe to publish. For every asset, include:

• the original high-resolution file rather than a screenshot from social media
• who created it and what license, assignment, or permission allows website use
• who or what appears in it and whether a release is needed
• the date, location, service, and context needed for an accurate caption
• cropping restrictions, logo requirements, and whether details must be obscured
• what the image helps a visitor understand

The U.S. Copyright Office explains that website authorship can include writing, artwork, and photographs and that copyright protects original photographs rather than merely their subject. Its website and copyright FAQ is a useful reminder that finding an image online does not establish permission to publish it.

Ask the builder to define image preparation: crop sizes, compression, responsive variants, loading behavior, captions, and text alternatives. The W3C alternative-text decision tree distinguishes informative, functional, redundant, and decorative images. Google's image SEO guidance likewise recommends standard image elements, responsive delivery, descriptive context, and useful alt text without keyword stuffing.

Specify the complete conversion handoff

Content preparation does not end at button copy. For every call, form, booking, quote, payment, or signup path, document the complete handoff:

1. Name the visitor's goal and the minimum information needed to continue.
2. Decide which fields are required, optional, conditional, or inappropriate to collect.
3. Write labels, instructions, validation messages, consent language, and privacy context.
4. Name the business recipient, notification method, backup recipient, and system of record.
5. Define the confirmation page or message and the promised response window.
6. Provide a visible alternate contact path when the integration fails or is inaccessible.
7. Create valid and invalid test cases, then verify a real production-like submission.

A contact form is not complete because a button changes color. The business must know where the lead arrives, who responds, what the visitor sees, and how a failed delivery is detected. If the site needs payment, qualification, or a more involved intake, the content packet should also provide product names, prices, tax and refund rules, required acknowledgements, confirmation details, and the operational owner.

Zendory's website build packages separate a compact service website from a larger revenue website with checkout, booking, quote, or qualification flow. That distinction is useful when comparing any provider: price the actual handoff, not merely the number of pages surrounding it.

Write content that survives the real interface

Content and accessibility cannot be separated cleanly. Headings have to form a meaningful outline. Link text must explain its destination. Form labels and errors must remain understandable outside visual placement. Captions and text alternatives must carry the information a visitor needs. Instructions cannot depend only on color, shape, or position.

The W3C Web Content Accessibility Guidelines 2.2 is the current technical recommendation. It includes testable criteria for perceivable content, operable interfaces, understandable information, and robust implementation. A business should not accept an unsupported “accessible” or “compliant” promise. Ask which pages, components, content types, criteria, devices, and assistive technologies are included in review and what evidence is delivered.

Use the small-business website accessibility checklist to prepare headings, image alternatives, forms, video, error content, and acceptance testing. Specialist legal advice may still be needed for a particular business, jurisdiction, or obligation.

Identify policy and regulated-content owners early

A web designer should not silently invent a privacy policy, accessibility claim, medical disclaimer, financial disclosure, refund rule, shipping promise, warranty, consent statement, or regulated-service description. Create a policy inventory and assign an authorized owner or qualified adviser to each item.

For each policy, record the businesses and tools it covers, data collected, operational practice, governing location, effective date, update owner, and how a visitor can ask a question or exercise a right. The visible page and the real workflow must agree. A privacy page that says no information is shared while a form sends data into several vendors creates an operational problem, not merely a copy problem.

Flag sensitive workflows before the platform is chosen. Health information, financial details, children's data, employment applications, recurring billing, regulated goods, and location tracking can change the required architecture, vendors, consent, retention, security, and review. A fixed website package may be the wrong product when the underlying workflow needs specialist scoping.

Separate owner inputs from provider deliverables

A strong scope does not say only “content included.” It states who performs each part of the work.

This division makes quote comparison easier. One provider may include interviews and original copywriting; another may expect final copy in a document before design starts. Neither model is automatically wrong, but they are not equivalent offers. Normalize them with the small-business website cost guide.

Run a two-hour content readiness check

Before paying for a standard build, bring the owner, the person who handles new leads, and the final approver together for a focused review:

1. Twenty minutes: state the primary buyer, offer, and next action in plain language.
2. Twenty minutes: map the decisions that require a page or section.
3. Twenty minutes: verify business, location, pricing, timing, and contact facts.
4. Twenty minutes: inventory proof, images, credentials, and usage permission.
5. Twenty minutes: walk through every lead or revenue handoff from visitor action to staff response.
6. Twenty minutes: assign missing inputs, policy review, provider work, and final approval dates.

At the end, label each item ready, provider-owned, owner-owned, specialist review, or intentionally excluded. Do not label an item “later” without an owner and date.

If the primary offer, customer action, or operating process remains uncertain, reduce the build scope or choose a discovery path. If the facts and assets are mostly ready, compare the packet against the Zendory website-build process, review the website examples, and choose the smallest package that supports the mapped buyer decisions.

Primary guidance used for this content checklist

These first-party sources support the factual, search, accessibility, proof, and asset-handling parts of the checklist. They do not replace advice for a specific legal or regulated situation.

• Google Search guidance on helpful, reliable, people-first content, including audience, expertise, authorship, and purpose questions.
• Google guidelines for representing a business, covering real-world identity, location, service area, categories, hours, website, and phone.
• Google LocalBusiness structured-data documentation, for accurate visible business information and validation.
• Federal Trade Commission guidance on endorsements, influencers, and reviews, with links to current rules and plain-language compliance resources.
• Federal Trade Commission advertising FAQ for small businesses, including substantiation, endorsements, and testimonials.
• U.S. Copyright Office FAQ on protected website content and photographs, for understanding why asset rights must be confirmed.
• W3C alternative-text decision tree, for deciding whether an image needs informative, functional, or empty alternative text.
• W3C Web Content Accessibility Guidelines 2.2, the current technical recommendation for accessible web content.
• Google image SEO best practices, covering discoverability, responsive delivery, context, filenames, and alt text.