Person Schema

Person is a schema.org type for an individual. jobTitle and worksFor connect the person to a role and an organization. Profile URLs help tie the page to the same person elsewhere. Use the name readers see on the page.

What you get from Person Schema is concrete. Job title and organization are separate from the name. Profile URLs you add are included as links. The script describes one person. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on Person Schema looks like this. Start with real input, not a placeholder you do not understand. Enter the person’s name, job title, and organization. Then check the middle of the form, because that is where optional fields change the output. Add the personal site and other profile URLs shown on the page. Finish by reading the whole result, not only the first line. Copy the JSON-LD into that person’s page.

The limit is the part people skip on Person Schema. Match the output to the input you actually typed, then decide whether it belongs on the live site. No. Only the URLs you type are added. Profile URLs you add are included as links.

A second reading of Person Schema is worth it because the first pass is easy to rush. Say out loud what the output is claiming. Job title and organization are separate from the name. Profile URLs you add are included as links. The script describes one person. Then say what it is not claiming. An author or other person whose page shows the same name and role. No. Only the URLs you type are added. Yes. Copy it onto the person’s page. If those two speeches disagree, change the input or pick a different tool. Person Schema will not resolve the disagreement for you.

Read Person Schema once more as a single job. Part 1: Enter the person’s name, job title, and organization. Part 2: Add the personal site and other profile URLs shown on the page. Part 3: Copy the JSON-LD into that person’s page. You should be able to point at this in the result: Job title and organization are separate from the name. You should be able to point at this in the result: Profile URLs you add are included as links. You should be able to point at this in the result: The script describes one person. Who is this script for? An author or other person whose page shows the same name and role. Does it include profiles I did not enter? No. Only the URLs you type are added. Is the JSON-LD created locally? Yes. Copy it onto the person’s page. Who is Person Schema for? Person Schema is for someone already doing schema tools work who needs generate structured data representing authors and individuals. Person is a schema.org type for an individual. jobTitle and worksFor connect the person to a role and an organization. Profile URLs help tie the page to the same person elsewhere. Use the name readers see on the page. The first field was filled with a real value: Enter the person’s name, job title, and organization. The result was read: Job title and organization are separate from the name. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep Person Schema as this step only. When the job moves on, the Organization Schema is the next page: Organization Schema writes Organization JSON-LD from a name, URL, logo URL, description, and social profile links. The Article Schema Generator covers a different piece of the same work: Article Schema Generator writes Article, BlogPosting, or NewsArticle JSON-LD from a headline, image, author, and publisher.