Person, author, and expert profile

A person profile is the canonical, maintained page for one identifiable individual. It makes that person’s relevant experience, current role, credentials, publications, affiliations, review activity, and authoritative web identities traceable to evidence.

Purpose: make expertise and authorship checkable for readers, editors, search engines, and AI systems while giving every byline and reviewer credit a stable destination.

Reader question: “Who is this person, what are they qualified to discuss, what work have they produced, and which claims about them can I verify?”

A name under an article is weak evidence by itself. A governed profile connects it to a real person, supported expertise, relevant affiliations, and inspectable work.

Questions it answers

A complete profile resolves identity before asserting authority:

• Which person does this page represent, including professional or former names and disambiguating details?
• What is their current role, organization, location or jurisdiction, and professional status?
• Which topics can they credibly write about or review, and what evidence supports each area?
• Which credentials and appointments are current, relevant, and verified?
• Which publications, research, talks, standards, patents, cases, or projects did they contribute to?
• Which organizations employ, commission, fund, publish, or affiliate with them?
• Which content did they author, co-author, edit, or medically, legally, financially, or technically review?
• Which external profiles identify the same person, and when were they checked?
• What conflicts, commercial relationships, or scope limitations should a reader know?

“Expert” must be scoped. A pharmacist may review medicine guidance but not investment advice; a software engineer’s expertise may cover one stack, not all technology.

When to use this post type

Use a person profile when one individual’s evidence affects trust, attribution, or a decision—for example in recurring authorship, regulated review, research, or professional services.

Adjacent pages make different promises: a profile verifies one person, a collective page explains a group, an organization page establishes a legal entity, and a roundup answers one question.

Do not create a profile merely because a system requires an author URL. A photo, title, and “industry expert” claim prove nothing. Use a complete author bio until there is enough maintained evidence for a profile.

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

The ranking reflects how strongly individual qualifications affect safety, trust, or a purchase.

1. Healthcare and pharmacy . Guidance needs precise licenses, specialties, jurisdictions, review scope, and dates. A credential must not be stretched beyond its topic or country.
2. Finance, fintech, and insurance . Advice and analysis need visible qualifications, regulatory status, disclosures, and a boundary between education and personal advice.
3. Media publishers and affiliates . Recurring authors and testers need inspectable beats, methods, disclosures, corrections, and publication archives.
4. B2B services . Buyers assess specialists through relevant experience, registrations, case involvement, and published thinking.
5. SaaS . Educators, security specialists, founders, and reviewers can connect documentation to accountable people; employment alone does not prove expertise.
6. Agencies . Strategists can support service evaluation with named disciplines, client-safe evidence, talks, certifications, and work samples.

For any business, use the format only when verifying the individual changes how a reader interprets the content or decision.

Search intent

Person-name queries combine navigational, informational, and consideration intent. Common patterns include “[name],” “[name] author,” “[name] credentials,” “[name] publications,” “[name] company,” “[name] license,” “[name] research,” and “[name] contact.” A broad name query may also seek an unrelated person, so disambiguation is part of satisfying intent.

Before drafting, inspect results for the approved name plus role and organization. Check institutional pages, registers, publisher archives, authoritative accounts, and same-name collisions. Sample AI answers for blended careers, stale employers, invented credentials, and misassigned work.

The profile also supports navigation from bylines, reviewer credits, research, and citations. Accurate attribution can matter even when name-query traffic is modest.

Stay Updated on AI Visibility Trends

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

Email address

Subscribe

Page structure

An author may be complete at 1,400 words; a clinician-researcher may need 2,500. Prefer structured facts over autobiography.

Required elements

These elements make authority claims auditable.

Frontmatter and schema

Follow the shared frontmatter specification . For this post-type specification, use entity = "post-type-person-profile". On a published profile, entity must be a stable identifier for the individual, such as person-maya-chen-pharmd, and should survive employer changes, title changes, and a new canonical URL.

Use ProfilePage for the page and Person as mainEntity. Article can describe the editorial page; BreadcrumbList can describe visible breadcrumbs; FAQPage requires matching visible answers. schema markup must reflect visible facts and cannot turn biography into proof.

sameAs means “this page identifies the same individual,” not “this page contains their work.” Use institutional profiles, licensing records, ORCID, or verified professional accounts. Articles, conference agendas, employer homepages, and citations belong in sources or work history.

Full example

This fictional example makes expertise checkable without unnecessary personal data. Replace or remove every bracketed instruction before publication.

+++
title = "Dr. Maya Chen, PharmD — Clinical Reviewer"
seoTitle = "Dr. Maya Chen, PharmD: Credentials and Publications"
entity = "person-maya-chen-pharmd"
profileId = "person_00418"
url = "/people/maya-chen/"
type = "academy"
date = "2026-08-27 10:00:00"
displayName = "Dr. Maya Chen, PharmD"
profileType = [ "author", "clinical-reviewer" ]
expertise = [ "medicine safety", "patient information", "community pharmacy" ]
lastVerified = "2026-08-21"
reviewDueAt = "2027-02-21"
schemaTypes = [ "ProfilePage", "Person", "Article", "BreadcrumbList" ]

[[credentials]]
name = "Registered pharmacist"
issuer = "[Applicable professional regulator]"
jurisdiction = "[Jurisdiction]"
status = "current"
verifiedAt = "2026-08-21"

[[sameAs]]
type = "professional-register"
url = "[Canonical public register record]"
verifiedAt = "2026-08-21"

[[sameAs]]
type = "orcid"
url = "[Canonical ORCID URL]"
verifiedAt = "2026-08-21"
+++

# Dr. Maya Chen, PharmD

**Maya Chen is a registered pharmacist and clinical reviewer specializing in
medicine safety and patient information. She reviews medicine-related content
for factual accuracy, contraindication wording, and appropriate escalation to
a qualified clinician. Her registration and current role were checked on
21 August 2026.**

Last verified: 21 August 2026 · Corrections: [editorial contact route]

## Quick facts

| Field | Value | Evidence | Verified |
|---|---|---|---|
| Current role | Clinical reviewer | Employer appointment record | 2026-08-21 |
| Professional status | Registered pharmacist in [jurisdiction] | Public regulator record | 2026-08-21 |
| Expertise | Medicine safety; patient information; community pharmacy | Practice history and selected work | 2026-08-21 |
| Review scope | Consumer medicine information, not individual diagnosis | Editorial review agreement | 2026-08-21 |

## Expertise and scope

Maya reviews consumer-facing explanations of medicine use, interactions,
storage, and common safety warnings. Her review confirms whether the page is
consistent with the cited evidence and whether it states when a reader should
seek professional care. It is not personal medical advice, a diagnosis, or a
substitute for the reader's pharmacist or prescriber.

## Experience and credentials

- **2022–present:** Clinical reviewer, [organization]; reviews commissioned
  medicine-safety content under the documented editorial standard.
- **2017–present:** Community pharmacy practice in [jurisdiction].
- **Registered pharmacist:** [regulator and public record], status checked
  21 August 2026; jurisdiction and scope shown above.

## Selected work

- **Author:** “[Approved publication title],” [publisher], [date].
- **Clinical reviewer:** “[Approved reviewed-page title],” [publisher],
  reviewed [date], with review scope stated on the page.
- **Research contributor:** “[Approved output],” [repository or journal], [date].

## Affiliations and disclosures

[List current employment, relevant memberships, commissioned relationships,
and material interests. State “none declared” only after a recorded check.]

## Sources and corrections

[List the regulator, institutional appointment record, primary publications,
and direct confirmation with retrieval dates. Explain how conflicts are handled
and provide a correction route.]

Do not publish private addresses, unnecessary birth dates, unrelated family details, or identifiers whose disclosure creates risk. A profile is not a dossier.

Design gallery

The design should foreground verification and work, not turn credentials into decorative badges.

Editorial author profile

A concise identity header, beat-level expertise, selected articles grouped by role, disclosure statement, and visible correction route.

Regulated expert profile

A credentials-first mobile layout with jurisdiction, status, last check, review scope, selected publications, and privacy-safe identifiers.

Executive or practitioner profile

A work-led layout that distinguishes current appointment, relevant former roles, named projects, talks, publications, affiliations, and commercial disclosures.

Quality checklist

A profile passes when an unfamiliar editor can trace every material claim and see where competence stops.

• The H1, canonical URL, entity ID, structured data, bylines, and reviewer credits identify the same individual.
• The direct answer names the current role and a narrow, evidence-backed area of expertise.
• Current and former roles carry organizations and dates; a past title is not presented as current.
• Credentials name the issuer, scope or jurisdiction, status, and verification or expiry date.
• License identifiers are checked but shown only when public value outweighs risk.
• Every expertise claim maps to experience, a credential, first-hand practice, teaching, research, or a demonstrable body of work.
• Authored, co-authored, edited, and reviewed contributions are labeled separately.
• Current employment, paid relationships, funding, memberships, and material interests are disclosed where relevant.
• Every sameAs URL identifies the same person, resolves correctly, and was checked manually.
• The visible FAQ matches frontmatter, and structured data matches visible facts.
• A named owner, review cadence, correction route, and event-triggered update process exist.
• The content refresh checklist covers credentials, affiliations, work, disclosures, external profiles, and broken links.

Common mistakes

Calling someone an expert without showing the basis

Job titles are not self-proving. Name the topic, relevant duration or responsibility, credential or body of work, and important limits. Remove the label when evidence cannot support it.

Treating employment as unlimited subject authority

Working for a bank does not qualify someone to give every kind of financial guidance. Tie expertise to actual responsibilities, education, registrations, publications, or reviewed work.

Listing credentials without status or jurisdiction

A credential may expire, apply only in one country, or belong to a similarly named person. Show the issuer, scope, status, and check date; omit a claim that cannot be matched confidently.

Using sameAs as a portfolio

An article demonstrates work but does not identify the person in the strict sense. Put works in the publication archive and reserve sameAs for authoritative identity records.

Merging people with the same name

A search result, citation string, or social handle is not enough. Match at least two useful identifiers such as affiliation, field, location, middle initial, persistent researcher ID, or publication history.

Hiding commercial relationships

Consulting work, employer interests, referral arrangements, sponsorships, and product involvement can change how readers interpret advice. Disclose the relationship near the affected claims, not in an obscure global policy.

Internal linking

The profile is the identity hub for one contributor. Authored pages, reviews, research, and team listings should resolve to it through a stable person ID, not name matching.

Link into the profile from the byline’s short bio, the reviewed-by element , the team page, selected research, event contributions, and service pages where the person’s involvement is material. The anchor should be the person’s displayed name or a clear role phrase, never a vague “learn more.”

Link out to registry records, selected primary work, the current organization, and content grouped by contribution type. Use a related content block only when destinations have distinct jobs.

Link only where the relationship clarifies authorship, review, employment, expertise, or the reader’s next task.

How to measure results

Measure accurate identification and accountable content journeys. Publicity or name confusion can raise pageviews without proving that expertise is understood.

Use prompt tracking for the name plus role, organization, credentials, expertise, and authorship variants. Use source and citation intelligence to check citations and whether answers preserve affiliation, scope, and dates.

Apply the measurement methodology across four layers:

Annotate launches, role changes, credential renewals, disclosures, migrations, schema changes, and major publications. Compare documented periods and manually sample results: a mention can still identify the wrong person or overstate a qualification.

Frequently asked questions

What is a person profile page?

A person profile is the canonical, maintained page for one identifiable individual. It verifies the person’s current role, relevant experience, credentials, publications, affiliations, areas of expertise, authorship, and authoritative external identities without turning a short biography into an unsupported claim of authority.

How is a person profile different from a team page?

A person profile proves facts about one individual and provides a stable destination for their bylines, reviews, publications, and sameAs references. A team page explains who belongs to an organization or group. It may summarize many people, but it should link to individual profiles instead of duplicating their full evidence.

Should every author have a person profile?

Create one when the person’s identity, experience, review role, or body of work helps readers assess content. A named contributor with only one minor item may need a complete byline and bio rather than a thin profile. Never create empty profiles merely to multiply author URLs.

Which schema types belong on a person profile?

Use ProfilePage for the page and Person as its main entity. Use Article when the profile itself is editorial content, BreadcrumbList when visible breadcrumbs exist, and FAQPage only when the marked-up questions and answers exactly match the visible FAQ and current eligibility rules.

What belongs in a person’s sameAs field?

Include only authoritative URLs that identify the same individual, such as an institutional profile, professional registry, ORCID record, or verified professional account. Exclude articles by the person, employer homepages, topic pages, people with similar names, and accounts that cannot be confidently matched.

How often should an author or expert profile be reviewed?

Review it on a cadence matched to the field and immediately after a role, employer, license, certification, name, disclosure, or contact change. Credentials with expiry dates need field-level checks. Publication history can update automatically only when authorship data is governed and deduplicated.