Person JSON-LD supports E-E-A-T by making authorship, expertise, and verifiable profiles machine-readable. Markup must match visible content on the page.
Basic
Provide at least one of given or family name; both together build a full name in JSON-LD.
Person schema is structured data that describes an individual—usually as Schema.org type Person—published as JSON-LD in your HTML. It tells search engines the canonical name for a human entity, their official profile URL, how they relate to an employer or publisher, which social profiles are authoritative, and what topics they are known for. That machine-readable layer sits alongside visible biographies, bylines, and team pages; it does not replace honest editorial content, but it helps crawlers connect the same person across articles, profiles, and third-party references.
Person markup has grown in importance as Google and other systems emphasize Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T), especially on Your Money Your Life (YMYL) topics and anywhere authorship matters. When a journalist, physician, executive, or educator is a core reason users should trust a page, clarifying who they are—with consistent URLs, bios, and verifiable profiles—supports how search systems evaluate entities and attribute content. Google may use Person signals when assembling knowledge panels, linking authors to articles, or reconciling names that appear in different languages or formats. Structured data is not a ranking guarantee and does not automatically create a panel; eligibility depends on entity strength, query context, and policies. Still, omitting Person JSON-LD on dedicated author or profile URLs when you already publish rich biographical content is a missed opportunity for clarity.
This SynthQuery Person Schema Generator runs entirely in your browser. You enter given and family names, job title, description, image and profile URLs, optional employment under worksFor, multiple alumniOf institutions, sameAs links for LinkedIn, X (Twitter), Facebook, Instagram, GitHub, a personal site, and Wikipedia, plus contact fields, birth date, nationality, awards, knowsAbout topics, and languages. The JSON-LD preview updates in real time with syntax highlighting. Validate checks required fields and URL shapes; Copy JSON-LD and Download help you ship the snippet. Use templates for authors, executives, freelancers, and speakers as starting points, then replace every placeholder with real, page-visible facts. Explore more utilities on the /free-tools hub or the full catalog at https://synthquery.com/tools.
What this tool does
The form maps to Person and common related types you are likely to publish in production. The top-level object is always @type Person with @context https://schema.org. Given name and family name populate givenName and familyName; when either is present, a combined name is emitted for the name property so consumers that expect a single string still receive one. The canonical url should match the primary public profile or author page where this block appears. image expects an absolute URL to a representative photo—typically a headshot aligned with what users see on the page.
worksFor nests a lightweight Organization with name and url when you provide employer or publisher details. That relationship is especially useful on team and leadership pages where the same organization also exposes Organization schema elsewhere on the site. alumniOf supports multiple rows, each modeled as EducationalOrganization with optional institution URL—add rows with Add alumni and remove extras when you only need one school. This pattern fits journalists, academics, and executives without forcing hand-edited JSON arrays.
Social inputs feed the sameAs property: LinkedIn, X/Twitter, Facebook, Instagram, GitHub, personal website, and Wikipedia. Only non-empty, valid http(s) URLs are included; relative paths are rejected because they would break when pasted into arbitrary hosts. sameAs is a primary mechanism for entity reconciliation—search systems can tie your domain profile to verified third-party identities when those URLs are stable and accurate.
Contact fields emit email and telephone when provided. birthDate accepts ISO-style dates; nationality is output as a Country object with name for readability. award collects multiple free-text honors; knowsAbout collects expertise strings that should mirror topics you visibly cover. knowsLanguage accepts comma-separated BCP 47 tags such as en-US or en-US, es-MX, and serializes to a string or array depending on count.
Template presets—Author/Writer, Executive, Freelancer, and Speaker—load realistic placeholder data you must replace before publishing. Validate enforces at least one of given or family name, requires person url, validates image and social URLs, nudges for image and sameAs when missing, and warns when worksFor is half-complete or alumni rows lack names. Export actions match our Organization and FAQ generators so teams learn one workflow across tools.
Technical details
Person schema is one of several Schema.org types that feed Google’s understanding of entities on the web. It connects to E-E-A-T-style signals indirectly: clear authorship, consistent identifiers, and verifiable profiles help systems evaluate whether a named individual plausibly stands behind the content. Person does not replace medical licensure disclaimers, editorial policies, or independent reviews—but it reduces ambiguity when multiple people share similar names.
The relationship between Person and Organization is often modeled with worksFor, affiliation, or references from Article.author to Person and Organization publisher. Keep URLs stable and cross-check that Organization name strings match your Organization JSON-LD name when both appear on the same site. conflicting strings across types can dilute entity confidence.
Google knowledge panels for people draw from many sources—Wikidata, Wikipedia, official sites, social profiles, and news coverage—not from JSON-LD alone. sameAs is still valuable because it explicitly lists authoritative URLs for the same person, aiding reconciliation. Use only profiles you control or that are clearly about the same individual.
When linking Person to articles, Article.author typically references a Person object or a URL identifying the author page. Implementations vary by CMS; the critical rule is parity between visible byline and structured author data. knowsAbout is often expressed as strings or Thing references; this generator uses strings for simplicity, which is valid Schema.org and easy to audit against your topical coverage.
After launch, re-validate whenever you migrate domains, change headshots, or update employer branding. Structured data testing is a snapshot; ongoing consistency with visible content is what sustains trust.
Use cases
Blog and newsroom author pages: publishers attach Person JSON-LD to journalist and contributor profiles so entity signals align with article bylines. Pair Person with Article or NewsArticle author properties where your CMS allows, and keep bios, photos, and sameAs URLs synchronized with what subscribers see in the footer or author box.
Company team and leadership pages: enterprises describe executives with jobTitle, worksFor pointing at the corporate Organization URL, and alumniOf for visible education. This complements Organization schema on the homepage and helps disambiguate individuals with common names when combined with unique profile URLs and consistent images.
Speaker and event bios: conference sites highlight keynote speakers with descriptions, awards, knowsAbout topics that match session themes, and sameAs links to slides, recordings, or professional profiles. Person markup supports discovery when users search for the speaker by name alongside the event brand.
Freelancer portfolios: independent consultants emphasize personal website URLs in sameAs, GitHub or LinkedIn for credibility, and knowsAbout for service areas. Omit worksFor when the person is not a full-time employee, or use it for an umbrella company they legally operate.
Executive and thought-leadership hubs: SaaS vendors and agencies publish leadership essays under named executives; Person schema on the leader’s profile reinforces who authored the perspective and how they connect to the brand’s Organization entity. Combine with Meta Checker and Open Graph tuning so social shares and structured data tell a coherent story.
Public figures and subject-matter experts: where a person is the primary trust anchor—medical reviewers, financial educators, certified trainers—Person fields should be conservative, accurate, and mirrored in on-page credentials. Use Review or FAQ generators on adjacent pages when testimonials or Q&A support the same funnel, and Organization or Local Business generators when location or brand entities are also in play.
How SynthQuery compares
Many free schema examples show a three-line Person snippet with name and url only. That is valid but underuses properties search documentation frequently illustrates for authors and public figures—image, sameAs, worksFor, and knowsAbout. Manual coding works until you need multiple alumni rows, several awards, seven social URLs, and BCP 47 language lists; then spreadsheets and copy-paste errors creep in.
SynthQuery’s Person Schema Generator focuses on E-E-A-T-aligned fields in one workspace: employment nesting, repeatable alumni and awards, topic tags, social inputs that roll into sameAs, live highlighted JSON, and client-side validation before you open Google’s Rich Results Test. Nothing is uploaded to a server while you experiment with bios or embargoed launch copy. Templates accelerate common personas without hiding the underlying JSON. The comparison table summarizes how this differs from minimal generators—not to dismiss them, but to set expectations when you need author-grade coverage in one pass.
Aspect
SynthQuery
Typical alternatives
Field coverage
Person with name parts, jobTitle, description, image, url, worksFor, alumniOf, sameAs from seven profile types, email, telephone, birthDate, nationality, award array, knowsAbout, knowsLanguage.
Often name and url only; sameAs and employment still typed by hand in a text editor.
Repeatable fields
Add/remove alumniOf rows, awards, and knowsAbout topics with dedicated controls.
Single text areas or static JSON templates without per-row validation.
E-E-A-T alignment
Copy and UI nudges emphasize image, sameAs, expertise topics, and bio length for author pages.
Generic schema demos with no author-specific guidance.
Cost & privacy
Free, unlimited client-side generation—no account required for the tool itself.
Some hosted tools log inputs or require signup for export.
How to use this tool effectively
1) Choose a template or start blank. Templates illustrate typical combinations—bylines with worksFor for a publication, leadership bios with alumni, freelancers emphasizing personal site and GitHub, speakers with awards and Wikipedia-style links. Replace every example.com URL, email, and phone with authentic values that appear on the live page.
2) Complete Basic. Enter given name and/or family name; at least one side is required so the Person has a recognizable name. Add jobTitle that matches how the person is credited on articles or in the org chart. Write description as a concise third-person bio aligned with visible copy—avoid keyword stuffing or claims the page does not support. Paste an absolute HTTPS image URL for a headshot users actually see. Set url to the canonical URL of this profile or author page (the page where the JSON-LD will be embedded).
3) Configure Employment. If the person is employed by or primarily associated with an organization readers expect, fill worksFor organization name and URL. Pairing these fields strengthens the link between Person and Organization entities when your site also publishes Organization markup on the company homepage or about page. Leave both blank for independent freelancers if that matches reality.
4) Add alumniOf. Click Add alumni for each degree-granting or accredited institution you want to disclose. Include the official school URL when it exists; validation warns if a URL is present without a name. Remove unused rows so you do not ship empty shells in JSON.
5) Add Social profiles. Paste full profile URLs only. Prioritize networks you link to from the visible bio and control directly—LinkedIn and a personal site are common starting points for B2B authors; X and GitHub may matter more for developers. Wikipedia belongs only when a stable article exists about the person.
6) Fill Contact if appropriate. Only publish email and telephone in JSON-LD when those values are already public on the page or in your organization’s contact policy; do not expose private numbers for E-E-A-T “completeness.”
7) Use Additional for birthDate, nationality, and knowsLanguage when they are appropriate to disclose and consistent with visible content. For multilingual authors, comma-separated BCP 47 tags map cleanly to knowsLanguage.
8) Add Awards and knowsAbout. Use Add award for each distinct honor string; use Add topic for skills or subject-matter areas that match articles or service pages the person is tied to. These fields support expertise signals when they reflect real, demonstrable focus areas.
9) Watch the Live JSON-LD preview as you type. When satisfied, click Validate, then Copy JSON-LD or Download. Inject a single script tag with type application/ld+json on the profile or author URL—avoid duplicating conflicting Person blocks on the same address.
10) Open Test in Rich Results to paste into Google’s Code tab, then monitor Search Console after deployment. Update markup when titles, employers, or social handles change.
Limitations and best practices
Structured data must reflect content users can actually see. Do not fabricate degrees, employers, awards, or social profiles to manipulate search features—misrepresentation can violate spam policies and erode trust. Only include birth dates, personal emails, or phone numbers when they are already public and appropriate for your jurisdiction’s privacy expectations.
Person JSON-LD belongs on the person’s dedicated URL or author archive you treat as canonical—not on every article if that creates duplicate or conflicting graphs. Coordinate with your CMS so author plugins do not emit a second incompatible Person block. Continue investing in crawlable bios, internal links to topical hubs, and quality writing; schema supports discovery and disambiguation rather than substituting for substance.
Pair this tool with the Organization Schema Generator for brand entities, the Local Business Schema Generator when individual practitioners map to storefront locations, FAQ and Review generators for supporting content types, Meta Checker and OG Tag Generator for snippet and social alignment, and the full product directory at https://synthquery.com/tools for AI-assisted content workflows beyond markup.
AI detection, readability, grammar, plagiarism, and the broader marketing suite.
Frequently asked questions
Person schema is Schema.org structured data—almost always JSON-LD—that describes an individual: name, profile URL, image, job title, bio, relationships such as worksFor and alumniOf, social profiles via sameAs, and optional facts like languages or topics they know about. Search engines use it to understand who authored or is responsible for content and to reconcile that person with profiles across the web. It should always match visible information on the page where it is embedded.
E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is a quality framework Google’s guidelines discuss for assessing pages, especially on sensitive topics. Person schema does not “award” E-E-A-T, but it makes authorship and credentials easier for systems to interpret consistently: a stable profile URL, aligned bio, image, employer linkage, and verifiable sameAs profiles support the story your content already tells. Thin or misleading markup that contradicts the page can undermine trust, so accuracy comes first.
Embed Person JSON-LD on the canonical author, team member, or speaker profile URL—the page that best represents the individual. Use a single script element with type application/ld+json in the head or before the closing body tag, following your theme’s pattern. Avoid duplicating conflicting Person objects on the same URL. For articles, you may also reference the author via Article.author, but ensure those references point to the same URLs and names users see in the byline.
Knowledge panels are generated from many signals—Wikidata, Wikipedia, official sites, news, and social presence—not from Person markup alone. Person schema can still help disambiguate entities and list authoritative sameAs URLs, which supports reconciliation. Panels appear only for some queries and entities; focus on factual, consistent public information rather than treating schema as a panel shortcut.
Include profiles you control, link to from the visible bio, and intend as official representations—commonly LinkedIn and a personal website for professionals, X for media-facing roles, GitHub for engineers, and Facebook or Instagram when they are primary channels. Add Wikipedia only when a stable article about the person exists. Omit networks that are inactive, unofficial fan pages, or redundant duplicates; quality and accuracy beat sheer quantity.
Person describes the human being. ProfilePage is a WebPage type representing a profile viewing experience—sometimes used to wrap a page about a person. A single URL can include both concepts in a graph, but many sites publish Person JSON-LD on an About or author page without explicitly typing the page as ProfilePage. Choose patterns your CMS and Google’s documentation examples support; consistency matters more than stacking every eligible type.
When you maintain dedicated author URLs with bios and photos, Person JSON-LD on each URL is a sensible default. For one-off guest posts without a profile page, you might reference a minimal Person inline on the article or skip structured person data until a canonical profile exists—avoid inventing URLs that 404. Prioritize authors whose expertise underpins trust on YMYL or competitive queries.
Use Article (or NewsArticle, BlogPosting, etc.) with an author property that references the Person—either as an embedded object sharing name and url or as @id references if you use a linked graph. Ensure the name matches the byline and the url points to the author’s profile. Some platforms automate this; others require theme or plugin customization. Always validate the combined graph in Rich Results Test.
knowsAbout lists topics, disciplines, or skills associated with the person. Schema.org allows Text or more detailed Thing values; this generator outputs strings for simplicity. Use topics you visibly demonstrate through articles, credentials, or service pages—think “Technical SEO,” “Pediatric nursing,” or “Climate policy”—rather than keyword lists unrelated to the person’s public work.
It can improve how clearly search engines understand who you are and how you connect to your content, which may help visibility indirectly when you already publish strong pages and earn mentions elsewhere. It is not a substitute for reputation building, backlinks, or high-quality work. Treat Person schema as precision engineering on top of a brand you are already investing in—accurate, maintained, and aligned with everything users see.