Person Schema for Webflow Websites

Person schema identifies an individual on the web. It powers author Knowledge Panels, team member profiles, and E-E-A-T authorship signals. For Webflow sites, Person schema is critical on About pages, team member pages, and author archive pages. It connects individuals to their published content, social profiles, and professional credentials.

Why Person Schema Matters

Person schema enables:

• Author Knowledge Panels in Google Search
• E-E-A-T authorship signals for content credibility
• AI answer engine author attribution ("According to [Person]...")
• Connection between author entities and their published content
• Team and founder visibility in company Knowledge Panels

Google's ProfilePage structured data documentation covers a limited set of Person properties (name, alternateName, description, identifier, image, sameAs, and interaction statistics). However, additional fields like jobTitle, worksFor, and knowsAbout are referenced in Google's article author guidance and contribute to entity understanding in AI systems.

JSON-LD Example

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Pavel Kurecka",
  "givenName": "Pavel",
  "familyName": "Kurecka",
  "jobTitle": "Founder & CRO Strategist",
  "description": "Founder of Karpi Studio. Builds Webflow sites that convert for Series A+ SaaS companies.",
  "image": "https://karpi.studio/team/pavel.jpg",
  "url": "https://karpi.studio/about",
  "worksFor": {
    "@type": "Organization",
    "name": "Karpi Studio",
    "url": "https://karpi.studio"
  },
  "alumniOf": {
    "@type": "CollegeOrUniversity",
    "name": "Czech Technical University"
  },
  "email": "pavel@karpi.studio",
  "sameAs": [
    "https://www.linkedin.com/in/pavelkurecka",
    "https://twitter.com/pavelkurecka"
  ],
  "knowsAbout": ["CRO", "Webflow", "Schema Markup", "AEO"]
}

Person-Specific Fields

These fields are defined exclusively for Person:

• givenName — First name (structured alternative to name)
• familyName — Last name (structured alternative to name)
• jobTitle — Professional title at current employer
• worksFor — Employer organization
• alumniOf — Educational institutions attended
• birthDate — Date of birth (ISO 8601)
• knowsAbout — Areas of expertise (also on Organization)

None of these fields are explicitly listed in Google's ProfilePage documentation, but jobTitle and worksFor are referenced in Google's article author markup guidance for E-E-A-T signals.

Shared Fields (Used Across Types)

These fields are common to multiple schema types but are frequently used with Person:

• name — Full name of the person
• description — Bio or summary text
• image — Headshot or profile photo
• url — Profile page URL
• email — Contact email address
• sameAs — Social profiles and external identifiers

Which Fields Should I Use?

Every team or about page needs:

• name, jobTitle, image, url
• worksFor linking to your Organization

For author E-E-A-T signals:

• sameAs with LinkedIn profile
• knowsAbout listing expertise areas
• url pointing to the author's profile or about page
• jobTitle and worksFor to establish professional credibility

For founder profiles:

• All of the above plus alumniOf and description
• givenName and familyName for name disambiguation

For biographical or encyclopedic content:

• birthDate for public figures with known dates
• givenName and familyName for structured name components

Webflow Implementation

Static about or team page

Add Person schema in Page Settings > Custom Code (before </head>):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Your Name",
  "jobTitle": "Your Title",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Company"
  },
  "image": "https://yoursite.com/headshot.jpg",
  "url": "https://yoursite.com/about",
  "sameAs": ["https://linkedin.com/in/yourprofile"]
}
</script>

CMS team member template

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "{{wf {"path":"name","type":"PlainText"} }}",
  "jobTitle": "{{wf {"path":"title","type":"PlainText"} }}",
  "image": "{{wf {"path":"headshot","type":"ImageRef"} }}",
  "url": "{{wf {"path":"slug","type":"URL"} }}",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Company"
  }
}
</script>

With Schema HQ

Schema HQ generates Person schema from your Webflow page data. It handles field mapping, JSON-LD formatting, and publishing to Webflow custom code. For CMS template pages, Schema HQ can map CMS fields to Person properties and publish per-page schema automatically.