How do you implement Person schema for an executive?

Implementing Person schema for an executive is mechanically straightforward; the value is in aligning every value with the rest of the entity stack. Place the markup on the executive’s bio page, ideally the entity home or a dedicated page on the corporate site, specify the core attributes, and keep every value consistent with the executive’s other authoritative references.

Where to place the markup

Add the Person schema to the executive’s bio page, the entity home or a dedicated page on the corporate site. This is the owned property that anchors the executive’s identity and links out to the rest of their footprint.

The fields to include

• name, the canonical name.
• jobTitle, the executive’s role.
• worksFor, pointing to the Organization the executive works for.
• image, the canonical photo.
• url, the canonical page for the executive.
• sameAs, links to the executive’s authoritative profiles, such as LinkedIn and, where they exist, Wikipedia and Wikidata.

The consistency discipline

The decisive discipline is consistency: every value should match Wikipedia, the Knowledge Panel, and the executive’s other profiles. The point of the markup is to raise confidence, and contradictory data does the opposite. Because the Knowledge Panel’s substantive facts are drawn from underlying sources such as Wikipedia and Wikidata rather than edited directly, your schema needs to agree with those sources rather than compete with them.

Why sameAs matters most

Of all the fields, the sameAs links matter most. They tie the executive’s identity to its authoritative anchors, the Wikipedia article, the Wikidata Q-ID, the LinkedIn profile, and drive resolution, telling search and AI engines that the scattered references all describe one person. We deploy and validate Person schema as part of building an executive’s entity layer, then confirm the effect by checking that the AI engines describe the executive accurately with AIQ.