If you are commissioning a small-business website, an About page is an identity decision for a buyer: “Is this the team that will handle my request?” It should answer that question with facts a business owner can keep current. This guide checks the About page specifically. The sitewide content guide helps choose the pages to build, and the service-page acceptance guide checks what each offer promises.
The query is a research hypothesis, not measured search demand. The table and example below are editorial decision tools. They are not a Zendory customer study or a claim that a particular biography increases conversions.
Decide whether a separate page earns its place
Start with the buyer's uncertainty. A home-service customer may want to know who enters the property, what the team is qualified to do, and which area it serves. A buyer of a specialist service may need to know who reviews the work and how the process is supervised. If the homepage already answers these questions clearly, a separate About page may add little. Give the page its own URL when it can explain identity, people, process, and proof without repeating the homepage or a service page.
Ask the owner for a short source brief before accepting copy. Record the legal or public business name, locations and coverage, people approved to appear, current roles, process facts, credentials that can be checked, approved work photographs, and the contact route. A writer can make these facts readable; the writer should not invent a founding story, a number of years in business, a license, or a customer result to fill a layout. Google's people-first content guidance asks whether a page leaves a visitor with a satisfying answer. An unsupported origin story does not resolve the buyer's real question.
Use a six-row identity-to-proof acceptance table
For each row, keep the proposed wording, the business source, the person who approves it, and the next check date. A missing source is a hold, not permission to turn a guess into marketing copy.
| Claim | Accept when | Check before launch |
|---|---|---|
| Identity | The public name and location match the business's current customer-facing records | Compare the page with the contact page and operating record |
| Who helps | The relevant customers and work are specific without repeating every service page | Ask a new reader who the business serves |
| People | Names, roles, and photos are current and approved for publication | Confirm consent and a staff-change owner |
| Process | The described handoff reflects how a real request is handled now | Trace one inquiry to the right team |
| Proof | Credentials, work examples, and review claims support only what they actually show | Open each source and check its date and permission |
| Next step | The action leads to a working phone, form, booking, or quote route | Complete the route at phone width |
This is an acceptance record, not a required visual template. A two-person shop may need a concise owner introduction and one real work example. A larger practice may need team roles and a clear explanation of who handles the first inquiry. Reject claims that are broader than their evidence: a photo of one completed project does not prove every kind of job, and an old certificate does not establish a current license.
Match photographs and reviews to the claim
A genuine team photograph may help a visitor recognize who will arrive or reply, if the pictured people agree to that use. Do not label a stock image as the owner, and do not leave a former worker's portrait on the page after their role changes. The photo selection guide covers permission, relevance, crop, and alternative text. The W3C images tutorial explains that a text alternative depends on what the image does in context; an identity photo needs an accurate description when it conveys who is pictured.
Keep a review beside the claim it can fairly support. A comment about courteous scheduling is evidence of that customer's reported experience, not proof of a technical result or a guaranteed response time. Obtain permission and preserve context before republishing a customer image or quote. The FTC's endorsement and review resources address truthful presentation and material connections. If the owner cannot verify a credential, award, count, or testimonial, omit it until the evidence exists. A smaller accurate page is more useful than a fuller misleading one.
Rehearse a former-employee correction
Imagine a fictional appliance-repair shop that publishes a three-person team photograph and says “Mara personally reviews every quote.” Mara leaves, and a different technician begins triage. The shop, names, and sequence are invented to test the acceptance table; they are not a Zendory client. The page now fails the people and process rows even if the services and phone number are correct. A prospective customer could expect a person who no longer works there.
The owner confirms the new quote process, checks which photograph can still be used, approves revised names and roles, and updates the page. The website provider also checks homepage cards, service-page bios, image alt text, structured data if used, and social links that repeat the old claim. A tester submits a realistic question through the About page's contact route and confirms it reaches the current team. The record includes the old wording, approved replacement, source owner, publication time, and a later recheck. This exercise proves that one correction path works; it does not predict buyer behavior.
Accept the page with an update owner
Before sign-off, ask a person unfamiliar with the company to read the page and answer three questions: who does the relevant work, what evidence supports that claim, and how do I start? If the reader cannot answer, revise the words before polishing the design. Test the page on a phone and with keyboard focus. Check a short and long biography, a missing image, and an unavailable form state. The contact-page checklist provides the response-route test, while the launch guide covers sitewide acceptance.
Assign one business owner to review staff, location, service, credential, and contact facts after each operational change. Keep the approved source brief with the site handoff so the next editor can tell what must be rechecked. Check whether the site's navigation lets buyers reach this identity evidence and the right service. If a provider is preparing the page, compare the copy, photo preparation, revisions, and maintenance duties with Zendory's current website-build packages. After launch, keep page visits, qualified inquiries, booked work, and paid outcomes separate; no traffic count by itself proves this page answered a buyer's identity question.