How to Fix Missing Author Person Schema and Credentials
This check fails when your article pages have no JSON-LD structured data describing the author as a schema.org Person. By the end of this guide, every article will output a Person entity with the author's name, profile URL, job title, credentials and sameAs links, connected to the Article markup and visible byline.

Why it matters
Search engines and AI answer engines try to work out who wrote a page and whether that person is qualified to write it. A plain-text byline is a weak signal. A Person entity with sameAs links to LinkedIn, ORCID or a professional register lets crawlers match your author to a known entity and their expertise.
That makes your content more likely to be cited in AI answers and better aligned with Google's guidance on author information. This matters most for YMYL topics like health, finance and legal, where an unverifiable author is a real disadvantage.
What you need
Step-by-step fix
Audit the current markup on one article
Open one of your blog posts or news articles and view the page source (Ctrl+U / Cmd+Option+U). Search for application/ld+json and check what @type values are present. You need a node with "@type": "Person", either nested as the Article's author or as a separate node in an @graph.
A string like "author": "Jane Doe" or an Organization author does not count, and neither does microdata or RDFa.
Collect each author's entity data
For each writer, gather the facts you can show publicly and verify:
- Full name as used on the byline
- Author page URL on your site
- Job title and employer
- Degrees or certifications, with the issuing body
- Topics they cover
- Headshot URL
- 2-5 authoritative profiles for sameAs, such as LinkedIn, ORCID, Google Scholar, a professional register, Wikidata or an X/Mastodon account
Only include credentials that are also stated on the visible bio page.
Write the Person JSON-LD with credentials
Build a Person object with a stable @id (the author page URL plus #person). Use these properties:
jobTitleandworksForfor role and employerhasCredential(typeEducationalOccupationalCredential) for licenses and certificationsalumniOffor educationknowsAboutfor expertise topicssameAsfor external profiles
Place this same object on the author's bio page as well.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/authors/jane-doe/#person",
"name": "Jane Doe",
"url": "https://example.com/authors/jane-doe/",
"image": "https://example.com/images/authors/jane-doe.jpg",
"jobTitle": "Senior Building Engineer",
"worksFor": { "@type": "Organization", "name": "Example Co", "url": "https://example.com/" },
"alumniOf": { "@type": "CollegeOrUniversity", "name": "Example University" },
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"credentialCategory": "Professional license",
"name": "Chartered Engineer (CEng)",
"recognizedBy": { "@type": "Organization", "name": "Example Engineering Council" }
},
"knowsAbout": ["Home insulation", "Building energy efficiency"],
"description": "Jane Doe is a chartered engineer with 12 years of experience in residential energy retrofits.",
"sameAs": [
"https://www.linkedin.com/in/janedoe-example",
"https://orcid.org/0000-0000-0000-0000"
]
}
</script>Attach the Person as the Article author
In your article template, set the Article or BlogPosting author to a Person object instead of a string. Include at least @type, @id, name and url inline. You can also reference the full node by @id inside an @graph.
If a post has several authors, use an array of Person objects.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Insulate a Pitched Roof",
"datePublished": "2026-01-14",
"dateModified": "2026-02-02",
"author": {
"@type": "Person",
"@id": "https://example.com/authors/jane-doe/#person",
"name": "Jane Doe",
"url": "https://example.com/authors/jane-doe/",
"jobTitle": "Senior Building Engineer",
"sameAs": ["https://www.linkedin.com/in/janedoe-example"]
},
"publisher": { "@type": "Organization", "name": "Example Co", "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" } }
}
</script>Make it dynamic in the article template
Hard-coding one author won't scale. Pull name, URL, job title and sameAs from your author or user records so every article outputs the correct Person automatically. Store credentials and profile URLs as custom fields on the author record, not on each post.
Match the visible byline and bio
Structured data should describe content users can see. Make sure each article shows:
- A byline linking to the author page
- A short bio with the same job title and credentials
On the author page, show the full bio, headshot and links to the sameAs profiles.
<p class="byline">By <a href="https://example.com/authors/jane-doe/" rel="author">Jane Doe</a>, CEng, Senior Building Engineer</p>
Validate and re-run the audit
org. Confirm that a Person item appears with no errors. Then check a second article by a different author to confirm the template outputs the correct person.
Finally, re-run the audit and confirm this check now passes.
curl -s https://example.com/blog/roof-insulation-guide/ | grep -o '"@type": *"Person"'
Platform-specific notes
WordPress (Yoast / Rank Math)
Yoast SEO automatically outputs a Person node as the article author. Add sameAs URLs under Users > Profile > Contact Info, and fill in Biographical Info. Rank Math also outputs a Person author; adding credentials there requires a custom schema template or the rank_math/json_ld filter. In either plugin, adding hasCredential or alumniOf needs a filter: wpseo_schema_person in Yoast, rank_math/json_ld in Rank Math.
Shopify
In Shopify, article.author is only a text name. Create an Authors metaobject (Content > Metaobjects) with fields for job title, credentials and sameAs URLs, then link it to articles through an article metafield. Output the JSON-LD in your article template, for example sections/main-article.liquid, using the | json filter on each field.
Webflow
Create an Authors CMS collection with fields for job title, credentials and profile links. Add a reference field from Blog Posts to Authors. In the Blog Post template, open Page Settings > Custom Code > Before </body> tag and add the JSON-LD script. Insert the referenced author's fields into the script as CMS dynamic values.
Wix
Wix Blog adds BlogPosting markup automatically, but the author details are minimal. To add a fuller Person with sameAs and credentials, go to Marketing & SEO > SEO Settings > Blog Posts > Edit, and add custom markup under Structured data markup. Keep the Wix writer profile (Blog > Writers) consistent with the markup.
Next.js
Render the JSON-LD on the server, in the page or layout component, as <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }} />. Build the data from your CMS author record. Avoid injecting it in a useEffect hook, because the markup won't be in the initial HTML.
Check that it worked
✅ How to verify
- Run an article URL through Google's Rich Results Test and confirm a Person item is detected as the article's author.
- Use validator.schema.org to check that hasCredential, sameAs and worksFor parse without errors or warnings.
- View the page source (not DevTools) and search for "@type": "Person" to confirm the markup is server-rendered.
- Re-run the site audit and confirm the "Author entities and credentials" check passes.
⚠️ Common mistakes
- Setting author to a plain string ("author": "Jane Doe") or to the Organization, which gives no Person entity.
- Adding the Person markup only to the author bio page and not to the article pages themselves.
- Listing credentials or sameAs profiles in the schema that aren't shown on the visible bio, or linking to profiles of a different person with the same name.
- Injecting the JSON-LD with client-side JavaScript or a tag manager, so crawlers that don't render JavaScript never see it.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Does Google require Person schema for article authors?
No, it isn't required. However, Google's author markup guidance recommends using Person with a name and url (or sameAs) for each author. It helps Google and AI systems tell who wrote the content and connect them to their other work.
What should I put in sameAs for an author?
Use URLs of profiles that clearly describe the same person. Good choices are LinkedIn, ORCID, Google Scholar, a professional licensing register, Wikidata, Wikipedia or an active social account. Use full absolute URLs and skip profiles that are empty or unrelated.
How do I mark up an author's qualifications in schema?
Use hasCredential with an EducationalOccupationalCredential that has a name, credentialCategory and recognizedBy organization. Use alumniOf for education, jobTitle and worksFor for current role, and knowsAbout for topics of expertise.
Can I use Person schema for guest authors or multiple authors?
Yes. Give each guest author their own author page and @id. For co-written articles, set author to an array of Person objects, listed in the same order as the visible byline.
How to Add dateModified Freshness Signals for AI Search
How to Fix Prompt-Aligned Content for AI Assistant Questions
How to Build a Reddit and UGC Footprint That AI Cites
How to Add "What Is" Definition Sections for AI Search
How to Get Your Brand Into "Best X" Listicles AI Tools Cite
How to Add Comparison Tables That AI Search Can Extract