Person Schema Generator — Clarify Profiles and Identity
Generate clean Person JSON‑LD for profile pages. Clarify name, image, job title, employer, and official profiles to improve entity understanding.
Why many profile pages underperform
Pain points we solve
- People with similar names are hard to disambiguate without structured cues.
- Official profiles and employer relationships aren’t linked, reducing clarity.
- Images are low‑quality or missing, hurting recognition and trust.
- Manual JSON‑LD drifts out of sync with on‑page profile content.
How SwiftSchema helps
Solution
The Person generator outputs clean JSON‑LD with the essentials: name, portrait image, jobTitle, worksFor, and `sameAs` links to official profiles.
It keeps markup consistent across team pages and author bios, and pairs well with Organization for the employer and Article for authored content.
How it works
How it works
- Choose Person in the generator below.
- Enter the person’s name and a high‑quality, crawlable image URL.
- Add current role details: jobTitle and worksFor (Organization).
- Link official profiles with `sameAs` (e.g., LinkedIn, X/Twitter, GitHub).
- Copy JSON or Script, paste on the profile page, and validate in the Rich Results Test.
Paste once per profile. Validate. Ship.
What is Person structured data?
Person structured data describes an individual’s identity for profile pages—name, image, job title, employer, education, expertise, and official profiles—so search engines can reliably understand who the page is about.
Why profile markup matters
- Disambiguation: Links to employers and verified profiles help differentiate people with the same name.
- Author/story mapping: Structured Person entities tie authored articles, talks, and podcasts back to the right person.
- Recruiting and PR: Accurate bios with awards and qualifications boost trust for prospective clients, donors, or hires.
- Governance: A consistent template keeps staff pages aligned when titles or headshots change.
Essential properties to include
- name(andalternateNamefor nickname/stage name).
- image: High-quality, crawlable portrait.
- url: Canonical profile page.
- jobTitleandworksFor(Organization).
- sameAs: Verified profiles (LinkedIn, GitHub, personal site, ORCID).
- alumniOf,knowsAbout,knowsLanguage: Expertise and background.
- description: Short bio matching on-page copy.
- Optional: contactPoint,award,honorificSuffix, pronoun info (in copy or additionalProperty).
Preparing profile content before generating schema
- Confirm bio details with the person (name spelling, pronouns, preferred title).
- Gather media: High-resolution headshots on a stable CDN.
- Document affiliations: Current employer, boards, notable projects.
- List profiles: Official social, portfolio, publication pages.
- Capture expertise: Degrees, certifications, focus areas; ensure they appear in page copy.
- Plan review cadence: Decide how often bios are audited (quarterly/annually).
Implementation workflow inside SwiftSchema
- Select Person in the generator.
- Enter name,image,url,jobTitle, andworksFor.
- Add sameAslinks and optionalalumniOf,knowsAbout,award.
- Include contactPointoremailif the person shares public contact info.
- Export JSON-LD, embed it on the profile template, and validate via the Rich Results Test.
Troubleshooting & QA
- Outdated roles: Update jobTitle/worksForwhen people change roles.
- Unofficial links: Include only verified profiles in sameAs.
- Low-quality images: Provide clear, crawlable portraits.
- Duplicate profiles: Ensure each person has one canonical URL referenced via mainEntityOfPage.
- Mismatch with page copy: Schema should mirror visible information; automated scripts can compare.
Maintenance and governance
- Audit bios regularly to keep titles, headshots, and contact info current.
- Update schema when someone joins/leaves; remove outdated entries promptly.
- Keep lastReviewedmetadata current and assign ownership (People Ops/Marketing).
- Store profile data in a CMS or HR system to regenerate schema automatically.
Required properties
name
Recommended properties
imageurljobTitleworksFor.namesameAs[]alumniOf.nameknowsAbout[]description
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Alex Rivera",
"image": "https://example.com/images/alex-rivera.jpg",
"jobTitle": "SEO Engineer",
"worksFor": {
"@type": "Organization",
"name": "SwiftSchema"
},
"url": "https://example.com/staff/alex-rivera",
"sameAs": [
"https://www.linkedin.com/in/alex-rivera/",
"https://twitter.com/alexrivera"
]
}