Free Person Schema Generator
Generate Person JSON-LD schema for author/profile pages. Name, image, social, role. Free, instant.
JSON-LD Schema
{
"@context": "https://schema.org",
"@type": "Person",
"name": "",
"jobTitle": "",
"url": "",
"image": "",
"telephone": "",
"email": "",
"worksFor": {
"@type": "Organization",
"name": ""
},
"sameAs": []
}What this tool does
Person Schema Generator delivers fast, reliable results for generate person json-ld schema for author/profile pages. name, image, social, role. free, instant.
Designed to fit into your existing SEO and content workflow with no setup overhead.
How to use it
Five steps.
Enter author basics
Provide name, photo URL, jobTitle, and a one-paragraph bio that matches the visible author box.
Add employer and education
Enter employer and education names if they are relevant to the profile.
Add sameAs profiles
Paste LinkedIn, X, GitHub, Wikipedia, or other authoritative URLs to anchor the entity.
List expertise and credentials
Use knowsAbout, hasCredential, and award fields for stronger EEAT support.
Copy and embed
Place the generated Person JSON-LD on the author or profile page.
When teams use it
Six common workflows.
Content publishers building author pages
Generate Person schema for every author so EEAT signals are properly structured for Googles ranking systems.
YMYL site editors establishing credibility
Add hasCredential and alumniOf to authors writing about health, finance, or legal topics for stronger authority signals.
Marketing teams managing executive bios
Maintain Person schema on About page leadership profiles for Knowledge Panel coverage.
Newsroom editors enabling author rich results
Add Person schema to journalist profiles so Google can show author cards in news results.
Conference organizers showcasing speakers
Generate Person schema for each speaker page to feed event aggregators and search rich results.
Agency consultants building portfolio pages
Establish individual professional identity for solo practitioners with full schema coverage.
Platform guides
Integrate with major platforms.
WordPress (Yoast)
- Open Users > Profile.
- Fill in name, social URLs, bio, and avatar.
- Yoast emits Person schema on author archive pages automatically.
- For per-post author embedding, use the Yoast author meta plugin.
Webflow
- Create a Webflow CMS collection for Authors.
- Add fields for name, image, jobTitle, sameAs links.
- On the author page template, paste the Grigora-generated JSON-LD with Liquid-style references.
- On article templates, reference the author via @id.
Next.js
- Create a /authors/[slug] page.
- Export metadata with the Person JSON-LD as a structuredData prop.
- On article pages, include "author": {"@id": "..."} in Article schema.
- Validate via Google Rich Results Test.
Ghost
- Open Settings > Staff > each author.
- Fill in cover image, profile image, bio, and social links.
- Ghost emits Person schema on /author/slug/ pages automatically.
- For custom fields (hasCredential), use the Ghost API.
Shopify (blog authors)
- Open Online Store > Themes > Edit Code.
- Find article-template.liquid and add Person schema referencing article.author.
- Use metafields to capture additional attributes (sameAs, jobTitle).
- Validate the live URL with Schema Markup Validator.
Grigora vs. alternatives
Side-by-side.
| Capability | Grigora | Schema.dev | TechnicalSEO.com | Merkle Schema | Manual |
|---|---|---|---|---|---|
| Generates valid Person JSON-LD | Yes | Yes | Yes | Partial | Manual |
| @id reference output | No | No | Yes | No | Manual |
| Validates against Google Rich Results | No | No | Yes | No | No |
| hasCredential and alumniOf fields | Yes | Limited | Yes | No | Manual |
| sameAs platform suggestions | Yes | Generic | Yes | Generic | Manual |
| Free without signup | Yes | Login required | Free tier | Yes | N/A |
| Image URL validation | No | No | Yes | No | Manual |
| Article author embed snippet | No | No | Yes | No | Manual |
Common errors and fixes
Eight issues users hit.
Image URL returns 404
Cause: The author photo was renamed or moved without updating the schema.
Fix: Verify the URL returns 200 over HTTPS and matches the displayed author box image; redeploy schema after fix.
sameAs link to wrong profile
Cause: A typo or generic handle pointed to the wrong individual.
Fix: Open each sameAs URL in incognito and confirm name and photo match; remove or update mismatches.
Person duplicated across articles instead of @id reference
Cause: CMS template embeds full Person on each article rather than linking via @id.
Fix: Refactor template to emit Person schema on author pages only and reference via @id from articles.
Schema validator flags missing name
Cause: The name property was empty due to a CMS field mapping issue.
Fix: Ensure your author CMS record has a name field populated and the template references it correctly.
Author byline does not match schema
Cause: Visible UI uses a pen name but schema uses a legal name.
Fix: Pick one canonical name and use it consistently in both the byline and schema; avoid mismatches.
Wikipedia URL points to disambiguation page
Cause: Common name (e.g., John Smith) resolves to a list of people.
Fix: Use the specific Wikipedia page URL (e.g., John_Smith_(author)) or omit if no specific entry exists.
jobTitle includes company name
Cause: CMS concatenated title and employer ("CEO of Acme Inc").
Fix: Use jobTitle for the role only and worksFor (linked to Organization @id) for the employer.
birthDate in wrong format
Cause: Date formatted as MM/DD/YYYY instead of ISO 8601.
Fix: Use YYYY-MM-DD format (e.g., 1985-04-15) for all dates in JSON-LD.
Original data
2026 study.
Frequently asked questions
Twelve answers.
Related free tools
Other utilities.