Tool
What the Person Schema Generator does
Person Schema Generator: generates JSON-LD only from Full name, Job title and Organization. Example: full name Jane Doe, job title Head of Search and organization Example Ltd gives JSON-LD only { "@context": "https://schema.org", "@type": "Person", "name": "Jane Doe", "jobTitle": "Head of Search"….
This generator reads Full name, Job title, Organization and Profile URL and produces JSON-LD only. There is no submit step; the numbers move as you adjust them.
It is mostly used by anyone tuning a snippet. What Google displays is rarely exactly what you wrote, and the difference costs clicks.
Nothing is sent to a server, which means you can safely check drafts and staging content.
Each field is explained further down, along with the method and a worked example that uses the default values.
What do the Person Schema Generator fields mean?
The Person Schema Generator uses 5 inputs. The starting figures are ordinary, not edge cases, so they make a sensible baseline.
| Field | What to enter | Default |
|---|---|---|
| Full name | required | Jane Doe |
| Job title | optional | Head of Search |
| Organization | optional | Example Ltd |
| Profile URL | optional | https://example.com/team/jane |
| Social profiles, one per line | paste or type any amount of text | https://x.com/janedoe |
How does the Person Schema Generator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same generated output.
Inputs are validated before anything is computed, so a bad entry is reported rather than quietly producing a wrong answer.
Worked example
These are the values the Person Schema Generator loads by default, and the result it produces from them. The defaults produce the result shown here; change any of them and the answer moves.
| Full name | Jane Doe |
|---|---|
| Job title | Head of Search |
| Organization | Example Ltd |
| Profile URL | https://example.com/team/jane |
| Social profiles, one per line | https://x.com/janedoe |
| JSON-LD only | { "@context": "https://schema.org", "@type": "Person", "name": "Jane Doe", "jobTitle": "Head of Search"… |
|---|
name is the only requirement: everything else builds context
Person schema has a low bar to validate (name alone) and a much higher bar to be useful: it identifies an entity, it does not automatically create recognition for that entity.
Worth knowing
- Adding Person markup to a byline does not, by itself, produce a Knowledge Panel. That requires independent notability signals across the web that Google evaluates separately. Markup documents an identity, it does not manufacture one.
- jobTitle, worksFor and sameAs (linking to genuinely controlled profiles; a verified social account, a Wikipedia page, an ORCID ID for academic authors) all strengthen entity association, which feeds into the author-expertise signals increasingly emphasised for content quality, particularly on sites publishing in health, finance or other sensitive topics.
- This schema pairs naturally with Article schema’s author field: using the same name and identity details consistently across both is what lets Google connect "this person wrote this article" to "this person is this entity", rather than treating the two as separate, unconnected mentions.
How to use it
- Set Full name.
- Put Job title.
- Key in Organization.
- Fill in Profile URL.
- Paste your content into Social profiles, one per line.
- Because there is no round trip to a server, updating on every keystroke costs nothing.
- Check JSON-LD only on the right.
- If you need a record, Copy Link saves the inputs and Print produces a clean page.
What this tool does not do
- This inspects the markup you supply; it cannot see server headers or your live rankings.
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- The tool answers exactly the question it is given; it cannot know the context around your numbers.
Frequently asked questions
5 things: Full name, Job title, Organization, Profile URL and Social profiles, one per line. A starting value is in place for each, so you can change one value at a time and watch how the result responds.
With the values loaded when the page opens, JSON-LD only comes out as { "@context": "https://schema.org", "@type": "Person", "name": "Jane Doe", "jobTitle": "Head of Search"…. Edit any input and that figure moves with it.
No. There is no upload step, no database, and nothing to delete afterwards.
No cost and no account. Use it as often as you like.
It is exact within the stated method. Anything the method does not model is simply out of scope.