About and team page

An About and team page is the organization-controlled record of who the business is, why it exists, who is responsible for its work, and what evidence supports its claims. It turns a vague brand into an identifiable organization with real people, a specific history, and accountable expertise.

Purpose: help a consideration-stage visitor decide whether the organization is legitimate, relevant, and competent enough to trust with the next action.

Reader question: “Who is behind this organization, why should I believe it can do what it says, and who will be accountable if I engage?”

Prospects often check this page after a homepage, product page, or article creates interest. Its job is to connect identity, people, experience, and verifiable proof—not call the company “passionate” or “leading.”

Questions it answers

A useful About page resolves four layers of uncertainty: identity, purpose, competence, and accountability.

• What is the organization’s current name, legal or trading relationship, location, and area of work?
• Why was it created, which problem does it choose to solve, and for whom?
• What makes its approach materially different from an interchangeable competitor’s?
• Who founded, owns, leads, or governs it?
• Which real people deliver, review, or stand behind the work?
• Which experience, qualifications, methods, outcomes, or milestones demonstrate competence, and how can the visitor verify them?
• How current are the team, leadership, location, and credential details?
• What is the sensible next page for a buyer, candidate, journalist, partner, or researcher?

When to use this post type

Use this post type for an organization’s own account of its identity, purpose, people, and competence. It can combine About and team content on one URL or govern two connected URLs when the team requires a directory. The distinction from adjacent formats matters because each makes a different promise: an About page may persuade with supported facts, an editorial profile must remain independent, and a person page must give one individual enough depth to stand alone.

Split a team page only when the list needs departments, filters, offices, individual profile routes, or its own maintenance owner. Otherwise, one strong About page keeps the story and people connected.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Best for these business types

Every organization benefits from clear identity. This ranking reflects how strongly a purchase depends on the people, expertise, governance, or continuity behind the offer.

1. B2B services . Buyers assess judgment and delivery risk before they can inspect the work. Name accountable leaders, experts, roles, sector experience, and evidence.
2. Agencies . Distinguish founders, leadership, client teams, and specialist partners so prospects know who sells, strategizes, creates, and manages the account.
3. SaaS . A product may be self-serve, but enterprise buyers, partners, and candidates still evaluate leadership, ownership, security responsibility, product history, and organizational stability.
4. Healthcare and pharmacy . State who provides care, who reviews content, which jurisdiction applies, and what each qualification permits; do not turn the page into medical advice.
5. Finance, fintech, and insurance . Licensed entities, leadership accountability, regulatory status, risk ownership, and professional experience can affect whether a visitor proceeds. Keep regulated claims specific to the entity and jurisdiction they cover.
6. Manufacturers and industrial businesses . Connect engineering competence, facilities, quality systems, and responsible contacts to technical evidence rather than an anniversary slogan.

Search intent

The dominant search intent is navigational investigation: “[brand] about,” “[brand] team,” “[brand] founders,” “[brand] owner,” “[brand] leadership,” and “[brand] legitimate.” Prospects also arrive indirectly from service, pricing, author, job, media, and partnership journeys. They are rarely looking for a long corporate history; they are looking for enough evidence to reduce risk.

Search engines and answer systems may use the page to reconcile the brand, organization, founders, leaders, locations, and linked people. Make relationships explicit: “Avery Chen founded Northstar Analytics in Bristol in 2019” is clearer than “Avery — Founder.” Explain former names once and distinguish the legal entity from a product brand.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Page structure

The page should move from a fast identity answer to evidence, then people, then the next step. Word bands control focus rather than set a target: a five-person studio may be complete at 1,300 words, while a regulated multi-office organization may need 2,500 plus individual profiles.

Required elements

Each element exists to prevent a recognizable failure: vague identity, unsupported confidence, anonymous expertise, or a dead end after trust has been earned.

Frontmatter

Follow the frontmatter specification . For this playbook specification, use entity = "post-type-about-team-page". For a produced page, use a stable organization-scoped value such as northstar-analytics-about rather than a generic value such as about; this prevents similarly named pages from collapsing into one internal entity.

Use schemaTypes = [ "AboutPage", "Organization" ] as the baseline: AboutPage describes the page and Organization the subject. Add Person only for visibly named people with supported facts and a stable @id; add BreadcrumbList for visible breadcrumbs and FAQPage only when the rendered questions match. Organization schema should confirm visible identity through supported properties such as name, legalName, url, logo, foundingDate, founder, address, sameAs, and organization relationships. Treat all structured data as maintained claims, not a hidden place to add unsupported facts.

Full example

The illustrative example below shows a concise organization-controlled specification.

+++
title = "About Northstar Analytics: Team and Approach"
seoTitle = "About Northstar Analytics | Team, Experience, Approach"
entity = "northstar-analytics-about"
url = "/about/"
keywords = [ "Northstar Analytics", "Northstar Analytics team", "analytics consultancy", "data strategy team", "Bristol analytics", "analytics experts" ]
description = "Meet the Northstar Analytics team, learn why the consultancy was founded, see how it works, and review the experience behind its data strategy services."
type = "about"
date = "2026-08-27 10:00:00"
lastReviewed = "2026-08-27"
contentOwner = "Head of Marketing"
entityReviewedBy = "Managing Director"
schemaTypes = [ "AboutPage", "Organization", "Person", "BreadcrumbList", "FAQPage" ]
businessTypes = [ "b2b-services" ]

[[people]]
name = "Avery Chen"
role = "Founder and Managing Director"
profile = "/people/avery-chen/"
personEntity = "person-avery-chen"

[[people]]
name = "Sam Okafor"
role = "Director of Data Strategy"
profile = "/people/sam-okafor/"
personEntity = "person-sam-okafor"

[[faq]]
question = "Where is Northstar Analytics based?"
answer = "Northstar Analytics is based in Bristol and works with clients across the United Kingdom."
+++

# About Northstar Analytics

Northstar Analytics is a Bristol-based data consultancy that helps operations teams turn fragmented reporting into dependable decisions. Founded in 2019, the company combines data strategy, analytics engineering, and team enablement for growing UK businesses.

## Why we exist

Our founders repeatedly saw capable operations teams lose time reconciling dashboards that measured the same business differently. Northstar was created to fix the definitions, ownership, and workflows behind the reports—not simply add another dashboard.

## Evidence of competence

- Read the approved case study showing how a distributor replaced five conflicting weekly reports with one governed operating view.
- Review our current analytics platform certifications and verify each credential with its issuer.
- Meet the named strategist and engineer responsible for each engagement before work begins.

## Leadership

### Avery Chen — Founder and Managing Director

Avery leads delivery standards and commercial accountability. Her profile documents her relevant operating and analytics experience, published work, and current role.

### Sam Okafor — Director of Data Strategy

Sam leads discovery and measurement design. His profile documents his experience in metric governance, analytics implementation, and team training.

## What to do next

Review our services and case studies, or contact the team to discuss a defined reporting problem.

The example makes a limited promise, supplies verification routes, names accountable people, and avoids numbers that cannot be audited.

Design gallery

Editorial organization story

Use an identity statement, restrained origin, evidence cluster, and portraits beside the work those people lead. This suits smaller consultancies, studios, and SaaS teams.

Team directory with profile routes

Use filters only when they help visitors find someone. Keep names, roles, image treatment, and profile links consistent.

Regulated trust layout

Put licensed entity, jurisdiction, governance, professional roles, and verification routes ahead of brand history.

Avoid carousel-only team lists. Important people and claims should remain available without interaction, with every profile and CTA keyboard-accessible.

Quality checklist

• The first 70 words name the organization, what it does, who it serves, and its geographic or operational scope.
• The legal entity, trading brand, parent, subsidiary, and product relationships are distinguished wherever confusion is plausible.
• The origin story explains a real problem or responsibility rather than presenting chronology as proof.
• Every competence claim has adjacent evidence: a case, credential, method, publication, customer permission, or accountable expert.
• Logos are approved, current, explained, and do not imply an endorsement that was not granted.
• Every named person has a current role, relevant context, consistent name, and approved photograph or deliberate no-photo treatment.
• Individual profile links exist only where the destination contains useful, maintained evidence.
• Credentials show issuer, scope, status, and verification route.
• Milestones have dates and explain why the event matters to identity or capability.
• Locations distinguish registered office, headquarters, workplace, facility, and service area.
• Claims in page copy, metadata, and schema agree.
• The page identifies a content owner and a reviewer for organization facts.
• Review triggers cover leadership, ownership, location, name, credential, and positioning changes.
• The mobile layout preserves names, roles, evidence, and profile links without hiding them behind hover behavior.
• The final CTA follows the established trust and routes non-buyers to careers, media, or partnership pages where relevant.

Common mistakes

Writing a founder memoir before identifying the company

Lead with current identity and capability. Use history only to explain a meaningful choice in the organization’s approach.

Replacing evidence with adjectives

Adjectives such as “world-class” and “innovative” are conclusions. State the practice, qualification, case, or responsibility that supports them.

Publishing an anonymous team

Group photography can show culture but not accountability. Name relevant leaders and explain who owns delivery, review, safety, or governance.

Creating thin profiles for everyone

A card that links to duplicate text adds no knowledge. Create a profile only when meaningful expertise, work, credentials, media, or contact information can support it.

Treating headcount as a trust metric

Headcount changes and rarely explains fit. If scale matters, state relevant capacity with a date and definition; otherwise, show responsible people and the delivery model.

Using an unexplained logo wall

Group logos by relationship, get permission, label the set, and link to evidence. Never make visitors guess whether a logo means customer, partner, integration, or press mention.

Leaving former staff and expired credentials live

Connect staff and credential changes to content review, while handling departures respectfully and preserving necessary authorship records.

Hiding the organization behind a product brand

State the contracting organization and responsible team visibly; footer legal text or schema alone will not resolve the relationship.

Internal linking

An About page sits between discovery and action. Link into it from the footer, contact area, careers and media navigation, high-consideration commercial pages, author information, and anywhere organizational accountability matters. Use descriptive anchors such as “About [organization]” or “Meet the team.”

Links out of the About page should follow four routes:

1. Proof: connect an outcome claim to the relevant case study, research, certification record, or documented method.
2. People: connect named founders, leaders, authors, practitioners, and reviewers to substantive person profiles.
3. Offer: connect broad statements about work to the exact product, service, solution, or use-case page.
4. Action: connect buyers to contact, demo, booking, or enquiry; candidates to careers; journalists to media resources; and partners to the appropriate route.

Place each link where the question occurs. A case beside a result claim is more credible than a generic block at the bottom.

How to measure results

Measure whether the page reduces uncertainty and supports action, not whether it attracts large unbranded traffic. Follow the measurement methodology : record a baseline, annotate edits, and compare like-for-like periods.

Track:

• Qualified entrances: branded and referral visits landing on the page, segmented from employee and recruitment traffic.
• Assisted conversions: visitors who view the page before a qualified enquiry, demo, booking, application, donation, or partnership action. Treat this as contribution, not proof that the page caused the outcome.
• Evidence engagement: clicks from claims to case studies, credentials, research, customer proof, and methods.
• People engagement: profile clicks, profile depth, and returns to a commercial or contact route.
• Next-step rate: clicks from the About page to services, products, contact, careers, media, or partner destinations, reported separately by route.
• Branded visibility: impressions and clicks for organization-plus-team, founder, owner, leadership, location, and legitimacy queries.
• Entity accuracy: whether search results and sampled AI answers correctly identify the organization, founders, current leaders, location, and relationship to parent or product brands.
• Content integrity: stale people, expired credentials, broken verification links, conflicting titles, and correction time.

Review quality as well as quantity. A lower generic CTA rate may be healthy if candidates are routed away from sales and buyers get stronger evidence. For AI checks, repeat dated prompts such as “Who founded [brand]?” and “Who leads [brand]?” Record the engine, date, answer, citations, and factual errors. Success means correct, supported relationships—not merely a citation.

FAQ

The following questions cover implementation choices that often remain after the page has been scoped.

Should an About page and a team page be separate?

Keep one page when the organization is small and the same reader needs its purpose, history, proof, and people in one visit. Split them when the team directory is large, has filters or departments, or changes much more often than the company story. Link both ways and keep organization facts canonical on the About page.

Which schema type should an About page use?

Use AboutPage for the page, Organization for the organization it describes, and Person for people who are visibly presented with supported facts. Connect the entities with valid relationships rather than nesting every employee under the organization. Add FAQPage only when the same questions and answers are visibly rendered.

Does every team member need a person profile?

No. Create a person profile when that person’s expertise, authorship, leadership, public role, or contact route supports a real user journey. A name, role, and accurate photo can be enough in a team grid. Empty profiles with duplicated biographies create maintenance work without adding evidence.

What proof belongs on an About page?

Use proof that supports the claims next to it: named customers with permission, linked case studies, current certifications, verifiable awards, operating locations, leadership experience, published research, or concrete milestones. Avoid unexplained logo walls, vanity numbers, and awards that cannot be checked.

How often should an About or team page be updated?

Review it at least quarterly when staff, leadership, offices, certifications, or ownership change often, and at least twice a year for a stable organization. Also trigger a review after a rebrand, acquisition, executive change, office move, certification expiry, or major positioning change.

Should the About page target the phrase “about us”?

Write primarily for branded and trust-oriented investigation, not for a generic “about us” ranking. Use a clear title and snippet that name the organization and its value, then answer who runs it, why it exists, what it can prove, and where readers should go next.

Turn identity into measurable trust

An About page should make the organization easier to identify, its claims easier to verify, and its people easier to hold accountable. Start with one organization statement, one evidence register, and one owner for changes; then connect the page to the journeys where trust matters.

Measure how your brand appears in AI answers and use the factual errors you find to prioritize clearer organization, leadership, and profile relationships.