SchemaValid
ENDE

Person Schema Generator

Create valid Person JSON-LD structured data for an author, founder or expert — link their job, employer, education and social profiles so Google recognizes them as a real entity. Instant, in your browser, free.

Basic info

Work & education

Social profiles (sameAs)

Add the URLs of this person's official profiles (LinkedIn, X, GitHub, Wikipedia, personal site…). These become the sameAs array.

JSON-LD code

Fill in the required field (full name) to generate the JSON-LD code.

Person schema for authors and E-E-A-T

Person structured data describes a real individual — an author, founder, consultant or public figure — with their name, job title, employer, education and the profiles that represent them elsewhere via the sameAs property. It is one of the most practical ways to support E-E-A-T (Experience, Expertise, Authoritativeness, Trust): by marking up the author of an article or the expert behind a site, you give Google clear signals about who created the content and why they are qualified. Combined with a visible author bio and a consistent presence across the web, Person markup helps search engines connect content to a trusted, identifiable author rather than an anonymous page.

How to trigger a Knowledge Panel

A Knowledge Panel for a person is never guaranteed, but Person markup gives Google the structured facts it needs to build one. The most important property is sameAs: a list of authoritative URLs that unambiguously refer to the same individual, such as their LinkedIn, X, GitHub, Crunchbase or Wikipedia/Wikidata pages. The more consistent and reputable these references are, the more confident Google becomes that the person is a distinct entity worth a panel. Add a clear photo, a concise description, the job title and employer, and place the markup on a stable page about the person (an author or About page). Panels build over time as Google gathers corroborating signals across the web.

How to add the schema to your site

Copy the generated code and paste it into a script tag of type application/ld+json in the head section of the page about the person — typically an author page or About page. The details in the markup should match the visible bio on that page. A minimal example looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Miller",
  "jobTitle": "SEO Consultant",
  "url": "https://www.example.com",
  "sameAs": [
    "https://www.linkedin.com/in/janemiller",
    "https://x.com/janemiller"
  ]
}
</script>

Frequently asked questions

Which fields are required for Person schema?
Only the name is strictly required, and this tool enforces that. To be useful for E-E-A-T and Knowledge Panels, you should also add a job title, employer, a photo and — most importantly — sameAs links to the person's authoritative profiles.
What is the sameAs property for?
sameAs is a list of URLs that identify the same person elsewhere — their LinkedIn, X, GitHub, personal website, Wikipedia or Wikidata entries. Google uses these to connect your author to a single verified entity, which strengthens trust and can support a Knowledge Panel.
How does Person schema help with E-E-A-T?
E-E-A-T is about showing who created content and why they are credible. Person markup ties an article to a named, qualified author with a job title, employer and verifiable profiles, giving search engines explicit signals of expertise and authority behind the page.
Should I use Person or Organization?
Use Person for an individual — an author, founder or expert. Use Organization for a company or brand. For an author who writes for a company, mark up the author with Person and reference the company via worksFor, which this tool does automatically.
Where should the Person markup go?
Place it on a stable page about the individual, such as an author profile or About page, and reference that same person as the author of their articles. Keeping one canonical Person page helps Google consolidate the entity.

Related tools