worksFor

worksFor · Not mentioned by Google

Appears in

Person

What is it?

worksFor connects a person to the organization they work for. It accepts an Organization object and supports arrays for people who work at multiple organizations. This field is one of the most important Person properties for establishing entity relationships between individuals and brands in the knowledge graph.

Why this matters for AEO

When a user asks "Who works at [Company]?" or "Where does [Person] work?", AI answer engines pull worksFor to connect people to organizations. This is critical for E-E-A-T author signals: pairing worksFor with jobTitle tells AI systems not just who the author is, but their professional context. An AI engine answering "Is [Author] credible on [topic]?" evaluates worksFor to assess whether their employer lends authority to their claims.

For company knowledge panels, worksFor on Person entities creates bidirectional links: the organization gains visible association with its key people, and those people gain association with the organization's authority.

What the specs say

Schema.org: Expects Organization. "Organizations that the person works for." Source

Google: Not listed in Google's ProfilePage structured data documentation. However, Google's article author markup guidance references worksFor as a property to include within Person markup for establishing author credibility. Source

How to find your value

• LinkedIn profile — Current employer under Experience
• Company website — Organization name from about page
• Email domain — Organization associated with the email
• Author byline — Company attribution under the author name
• Business registration — Legal entity name

Format and code

Single employer (most common):

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Patrick Coombe",
  "jobTitle": "CEO",
  "worksFor": {
    "@type": "Organization",
    "name": "Elite Strategies"
  }
}

With organization details:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jay Holtslander",
  "jobTitle": "Technical Director",
  "worksFor": {
    "@type": "Organization",
    "name": "Skunkworks Creative Group Inc.",
    "sameAs": [
      "https://twitter.com/skunkworks_ca",
      "https://www.facebook.com/skunkworks.ca"
    ]
  }
}

Multiple employers (array with @id references):

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Denver Prophit",
  "worksFor": [
    {
      "@id": "https://www.strikehawk.com/#organization",
      "name": "StrikeHawk eCommerce, Inc."
    },
    {
      "@id": "https://denverprophit.us/",
      "name": "DPCG, Co."
    }
  ]
}

Nested in article author (E-E-A-T pattern):

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Webflow SEO Guide",
  "author": {
    "@type": "Person",
    "name": "Pavel Kurecka",
    "jobTitle": "Founder & CRO Strategist",
    "worksFor": {
      "@type": "Organization",
      "name": "Karpi Studio",
      "url": "https://karpi.studio"
    }
  }
}

Always include at minimum the name property on the Organization object. Adding url, sameAs, or @id strengthens the entity connection. Use @id references when the organization has its own JSON-LD block elsewhere on the site to avoid duplication.

Webflow implementation

Static pages

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

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Pavel Kurecka",
  "jobTitle": "Founder & CRO Strategist",
  "worksFor": {
    "@type": "Organization",
    "name": "Karpi Studio",
    "url": "https://karpi.studio"
  }
}
</script>

CMS template pages

For team member pages with a reference to the company:

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

For multi-tenant CMS setups where the company varies per team member, use a plain text CMS field for the employer name.

In Schema HQ

The worksFor field pairs worksFor with jobTitle automatically in Person schema generation. Enter the organization name and URL, and Schema HQ outputs the full Organization object in the published JSON-LD. For sites with existing Organization schema, Schema HQ can cross-reference the @id to avoid duplication.

Real examples

Jay Holtslander on jay.holtslander.ca:

{
  "@context": "http://www.schema.org",
  "@type": "Person",
  "name": "Jay Holtslander",
  "jobTitle": "Technical Director",
  "worksFor": [
    {
      "@type": "Organization",
      "name": "Skunkworks Creative Group Inc.",
      "sameAs": [
        "https://twitter.com/skunkworks_ca",
        "https://www.facebook.com/skunkworks.ca"
      ]
    }
  ]
}

Denver Prophit on denverprophit.us:

{
  "@context": "http://schema.org/",
  "@type": "Person",
  "givenName": "Denver",
  "familyName": "Prophit",
  "worksFor": [
    {
      "@id": "https://www.strikehawk.com/#organization",
      "name": "StrikeHawk eCommerce, Inc."
    },
    {
      "@id": "https://denverprophit.us/",
      "name": "DPCG, Co. - Emperio Marketing"
    }
  ]
}

Related fields

• jobTitle — professional title at the employer
• alumniOf — former organizations (educational)
• memberOf — organizations the person belongs to (broader than employment)
• knowsAbout — expertise areas shaped by professional context
• name — full name of the person

FAQ

What is the difference between worksFor and memberOf?

worksFor specifically indicates an employment relationship. memberOf is broader and covers any type of organizational membership, including professional associations, boards, clubs, or volunteer organizations. Use worksFor for employers and memberOf for non-employment affiliations.

Should worksFor reference the same Organization as my site's Organization schema?

Yes. Use @id references to link the Person's worksFor to the Organization JSON-LD block on your site. This creates a linked data connection that strengthens both entities in the knowledge graph.

Can a person have multiple worksFor values?

Yes. Schema.org supports arrays for worksFor. Use this for people who hold positions at multiple organizations simultaneously, such as consultants, board members, or co-founders of multiple companies.