A useful About page lets a buyer verify the basics: who is responsible for the work, who the business serves, where it operates and what evidence supports its claims. It should reduce uncertainty rather than turn the company biography into a collection of superlatives.
I would build the page around those buyer questions. Clear identity, scope and evidence help people assess a business and make the public record easier to interpret. They do not guarantee a ranking, citation or recommendation.
Name the business and the people responsible
Use the trading name customers recognise and explain any other company, product or project names that appear on the site. Name the people responsible for the work when that information helps a buyer understand accountability.
Avoid presenting several names without explaining the relationship. If a founder sets the strategy and a delivery partner builds the product, say which party does which job. Do not let a partnership imply that both parties supplied every service or achieved every reported result.
The page should answer three questions plainly:
- What does this business do now?
- Who is responsible for the service or product being described?
- How can a buyer contact the right person or team?
Google's guidance on helpful, reliable, people-first content asks creators to make authorship and the basis of content clear. That is a useful editorial test, not a formula for search visibility.
State who the work is for and where it is available
Describe the audience in terms a customer would use. A London SaaS consultancy might serve early-stage software teams that need an AI-search content audit. An e-commerce adviser might support sellers managing product information across Amazon and Shopify. These descriptions are more useful than saying the business serves "everyone".
Location also needs context. "Based in London" does not by itself say whether the business works only with London clients, serves the whole UK remotely or supports international accounts. Explain the practical boundary.
Keep the About, Services and Contact pages consistent. A reader should not find one audience on the About page, a different offer on the Services page and an unavailable contact route at the final step. A business-facts audit can provide the approved record for this check.
Connect experience to inspectable evidence
Experience should be relevant to the work being offered and supported at the right level. Link a qualification to the issuer's verification page where one exists. Link a project claim to a write-up that explains the problem, the business's role, the method and the limits of the result.
For example, a consultancy could publish an AI-search audit that shows the questions examined, the public sources checked and the factual errors found. A Shopify workflow specialist could document where a person reviews exceptions before product data is changed. Neither example needs an inflated outcome claim to be useful.
If a result is included, give the measure, period and scope. A testimonial describes one person's experience; it does not prove that every customer will receive the same outcome. A logo shows a relationship only when the business has permission to display it and can explain what the relationship was.
Give every important claim a route to verification
Before publishing, use a simple claim record:
| Claim | What the site says | Evidence or link | Last checked | Owner |
|---|---|---|---|---|
| Current role | The person's responsibility in the business | Official team page, current contract or approved company record | Date reviewed | Named owner |
| Qualification | Exact certificate or membership name | Issuer's verification page | Date reviewed | Credential holder |
| Project work | What the business actually delivered | Approved project record with role and scope | Date reviewed | Project owner |
| Service area | Where and how the service is available | Approved service record | Date reviewed | Operations owner |
| Contact route | How a buyer should enquire | Tested form, email or booking page | Date tested | Site owner |
The worksheet is not meant for publication in full. It is an internal control that helps the team remove unsupported wording and identify links that need maintenance.
Read the page as a buyer
Open the About, Services and Contact pages side by side. Ask someone unfamiliar with the business to answer:
- What does the business do?
- Who does it help?
- Where is the work available?
- Who is responsible?
- Which link would you open to check the claimed experience?
- What would you do next if the offer suited you?
Record their answers rather than coaching them. Confusion about a role, service boundary or proof link is a page problem worth fixing. The W3C's web accessibility writing tips also support clear headings, meaningful link text and plain language that help readers navigate content.
Keep transparency proportionate
Verifiability does not require publishing private addresses, personal phone numbers, confidential client material or unnecessary identity documents. Publish enough information to support the business claim, and keep sensitive evidence in an appropriate internal record.
Review the page when a role, offer, location, project status or verification link changes. A good About page is a maintained account of responsibility, not a historical collection of every ambition the business has expressed.
The strongest About page is not the most flattering one. It is the page that helps a buyer understand the business, inspect the relevant evidence and decide whether the offer fits.
About Samuel Anan
Samuel Anan is a London-based generative AI leader working across AI search, generative engine optimisation (GEO), answer engine optimisation (AEO), workflow automation and agentic AI. He writes for startups, SaaS teams, and e-commerce businesses selling through Amazon and Shopify.