What is sameAs for, exactly?

sameAs is a list of URLs that identify the same real-world person elsewhere on the web, typically social profiles (LinkedIn, Twitter/X, GitHub) or a Wikipedia page. Listing them helps search engines confirm identity and can contribute to a Knowledge Panel; each line in this generator's sameAs box becomes one URL in that array.

Should I use Person schema or Organization schema for an author bio?

Person, when the byline is an individual - a writer, a team member, a speaker. Organization is for the company or publication itself. Many pages need both: an Article's author as a nested Person, and its publisher as a nested Organization; this generator produces the standalone Person object you'd nest into other schema or use directly on an author profile page.

Is worksFor required?

No, it's entirely optional. Leave it out for a personal blog or portfolio where there's no single employer to name; fill it in for staff/author bio pages where linking the person to their organization is useful context for search engines.

Why does the generator skip the address object if I only fill in some fields?

It doesn't skip it for partial input - address is included as soon as at least one field (street, city, region, postal code, or country) is filled in, with only the fields you actually entered included in the nested PostalAddress. It's only omitted entirely when every address field is left blank.

Person Schema Generator - Person JSON-LD with Social Profiles

Overview

Introduction

Person schema is what ties a name on a page to a verifiable identity elsewhere on the web, through the sameAs property's list of social and professional profile links. It's the building block behind author bylines, team pages, and speaker profiles, and it's also what gets nested inside other schema types (Article's author, Event's organizer) when the entity involved is an individual rather than an organization.

This generator collects the fields that matter for a standalone Person page or byline (name, title, image, employer, social links) and outputs a complete, correctly-shaped JSON-LD block.

What Is Person Schema Generator?

A form-driven generator for Person JSON-LD: name, job title, image, personal URL, a list of social profile links, an optional employer, contact email, and an optional address.

sameAs is built as an array from one URL per line, and worksFor and address are each nested as their own typed objects (Organization and PostalAddress) rather than flattened strings.

How Person Schema Generator Works

Name, jobTitle, image, url, and email map directly to their Person properties; the sameAs box takes one profile URL per line and turns each line into an array entry.

worksFor is only included when an employer name is entered, nested as an Organization object; address is only included when at least one address field is filled in, nested as a PostalAddress with just the fields you provided.

When To Use Person Schema Generator

Building an author bio page or byline block for a blog, publication, or documentation site.

Adding a team or speaker profile page and wanting search engines to associate it with the person's real social and professional presence.

Often used alongside Structured Data Validator, Organization Schema Generator and Article Schema Generator.

Features

Advantages

Builds the sameAs array from a simple line-per-URL list, rather than requiring manual JSON array formatting.
Nests worksFor and address as their correctly-typed objects (Organization, PostalAddress) automatically.
Produces valid minimal Person markup from just a name, with every other field genuinely optional.

Limitations

Doesn't verify that sameAs URLs actually belong to the person or that the profiles are still active.
Covers a single employer via worksFor; someone with multiple current roles needs a manually merged array, which this generator's single-object field doesn't produce.
Doesn't expose every schema.org Person property (like birthDate or alumniOf), focusing instead on the fields most commonly used for author/team bio pages.

Examples

A staff author bio with social links

Input

Name: Jamie Lee
Job title: Senior Developer Advocate
URL: https://example.com/authors/jamie-lee
Same As:
https://twitter.com/jamielee
https://github.com/jamielee
https://linkedin.com/in/jamielee
Works for: Acme Devtools

Output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jamie Lee",
  "jobTitle": "Senior Developer Advocate",
  "url": "https://example.com/authors/jamie-lee",
  "sameAs": [
    "https://twitter.com/jamielee",
    "https://github.com/jamielee",
    "https://linkedin.com/in/jamielee"
  ],
  "worksFor": {
    "@type": "Organization",
    "name": "Acme Devtools"
  }
}
</script>

Each sameAs line becomes its own array entry, and worksFor is nested as an Organization since an employer name was provided.

Best Practices & Notes

Best Practices

List only profile URLs the person actually controls and that are kept up to date, since a stale or wrong sameAs link undermines the identity signal it's meant to provide.
Use the person's canonical bio or author-page URL for the url field, not a generic homepage link.
Keep jobTitle in the schema matching what's visibly displayed on the page, the same consistency principle Google applies to other structured data types.
Include worksFor when the person's organizational affiliation is relevant context (staff bios, speaker pages), and omit it when it isn't (personal blogs, freelancer portfolios).

Developer Notes

sameAs is emitted as an array even for a single profile URL, matching the array shape schema.org's own documentation uses, and empty lines in the input box are filtered out before the array is built so accidental blank lines don't produce empty string entries in the output.

Person Schema Generator Use Cases

Adding Person schema to an author bio block on a blog or publication
Building a team page where each member gets their own Person JSON-LD block
Generating a speaker profile's structured data for a conference site

Common Mistakes

Listing sameAs URLs that are dead links or profiles the person no longer controls.
Nesting worksFor as a bare organization name string instead of the required typed Organization object.

Tips

Run the generated output through the Structured Data Validator tool in this category before publishing to confirm required fields parsed correctly.
When this Person object is meant to be nested inside an Article's author field rather than used standalone, drop the surrounding @context/@type wrapper and paste just the inner object.

Person Schema Generator