Author schema SEO is often reduced to one instruction:
Add a name underneath the article.
That misses most of the point.
Google strongly encourages accurate authorship information where readers would reasonably expect it. Its Article structured data guidance also recommends identifying the author with a Person or Organization and using an author URL or sameAs reference to help Google understand who that author is. Google for Developers
That does not mean adding Person schema creates an automatic ranking advantage.
And it certainly does not mean an anonymous article automatically loses to an otherwise identical page with a named author.
The more useful principle is this:
If expertise matters to the content, make it easy for people and machines to understand who produced it and why that person is relevant.
That requires more than a decorative byline.
It means connecting the article to a real author entity, a useful biography and, where appropriate, external references that support that identity.
Table of Contents
- What author schema actually does
- E-E-A-T made concrete
- What Google recommends for article authors
- Which Person schema fields actually matter?
- What makes an author page worth having?
- The problem with an uncorroborated bio
- Does a LinkedIn profile help?
- How to connect an author to an organisation
- A copy-and-adapt author schema example
- What about freelancers?
- What about AI-assisted content?
- Common author markup mistakes
- The honest limit of author schema for AI search
- Frequently Asked Questions
What author schema actually does
Article structured data lets you explicitly identify who authored a piece of content.
Google’s current Article guidance supports Person or Organization as an author and recommends author information including:
- author.name
- author.url
- author.sameAs
- author type
Google specifically says that url or sameAs can help it better understand and disambiguate authors. Google for Developers
That means the markup can express:
This article was written by Jane Smith.
And:
This is the page that identifies Jane Smith.
That is more useful than leaving a search system to infer authorship from an arbitrary line of HTML.
But schema is only the declaration.
The author page and visible content still need to make sense.
E-E-A-T made concrete
E-E-A-T often gets discussed as though it were a technical score hiding inside Google.
It is not.
Google explicitly says E-E-A-T itself is not a specific ranking factor. Instead, its systems use multiple factors that can align with experience, expertise, authoritativeness and trustworthiness. Google for Developers
Authorship is one practical part of that picture.
Google’s people-first content guidance asks publishers:
- Is it clear who authored the content?
- Is there a byline where one would reasonably be expected?
- Does the byline lead to information about the author’s background and areas they write about?
Google says it strongly encourages accurate authorship information where readers would expect it. Google for Developers
That turns an abstract E-E-A-T conversation into something much more practical.
Instead of asking:
Have we added enough E-E-A-T?
ask:
Can the reader see who wrote this, what their relevant background is and where they can verify that information?
For more on creating content around extractable, clearly structured information, use the internal anchor:
Content structures generative AI engines can understand and cite
What Google recommends for article authors
Google’s Article documentation goes beyond simply adding a name.
It recommends that all visible authors also appear in the structured data.
If there are multiple authors, Google recommends listing them individually rather than combining multiple names into one author value. Google for Developers
For example, this is clearer:
“author”: [
{
“@type”: “Person”,
“name”: “Jane Smith”
},
{
“@type”: “Person”,
“name”: “David Jones”
}
]
than creating a single author called:
Jane Smith, David Jones
Google also strongly recommends adding the author’s type and url or sameAs. Google for Developers
If you have a genuine author profile on the website, that profile is normally the most logical url.
Which Person schema fields actually matter?
There are two slightly different questions here.
Google explicitly recommends these kinds of author identity fields in its Article guidance. Google for Developers
What Schema.org can additionally describe
The wider Person vocabulary can represent information such as:
- jobTitle
- worksFor
- affiliation
- hasCredential
- image
- description
- sameAs
Schema.org defines worksFor as the organisation the person works for, while hasCredential can describe credentials awarded to a Person or Organization. Schema.org
That does not mean every one of those properties is a Google ranking signal.
They are semantic fields that can help construct a more accurate Person entity.
Use the properties because they truthfully describe the person.
Not because your schema plugin offers them.
What makes an author page worth having?
Do not create an author page solely because an SEO checklist told you to.
Give it a useful purpose.
Google’s ProfilePage documentation explicitly recognises author pages and employee pages as valid examples of profile pages where the main focus is one person affiliated with the site. Google for Developers
A good author page can include:
Full name
Use the name the person genuinely publishes under.
Current role
For example:
Senior B2B Marketing Consultant
rather than:
Marketing Ninja
Relevant expertise
Keep it specific.
If the author writes about facilities-management lead generation, explain their experience in B2B marketing or that sector.
Do not add unrelated qualifications simply to make the biography longer.
Professional credentials where relevant
For regulated or specialist topics, valid credentials may be useful to readers.
Keep them accurate and current.
External profiles
Where relevant, link to genuine pages representing the same person.
Articles written by that author
This makes the author page useful in its own right rather than a 70-word biography created for schema.
The problem with an uncorroborated bio
You can write anything in an author biography.
That does not automatically make it credible.
Consider this:
Jane Smith is one of the UK’s leading experts in artificial intelligence marketing.
Where did that claim come from?
If the website itself is the only place making the claim, the bio has not provided much independent context.
A stronger profile might make specific, verifiable statements:
Jane Smith is Marketing Director at Example Ltd and has worked in B2B search marketing since 2018.
Then link appropriately to the company profile, professional profile or other genuine identity references where useful.
The objective is not to create twenty links around every author.
It is to avoid making the biography a collection of self-awarded superlatives.
This follows the same entity principle we covered in the Organisation schema guide:
Organisation schema and external identity references
Does a LinkedIn profile help?
It can be a sensible author identity reference.
Google explicitly recommends author.url or sameAs to help identify an author, and gives social-media or author profile pages as examples of useful author identity URLs. Google for Developers
That means an accurate LinkedIn page can be useful for saying:
This Person entity refers to this same individual.
What we cannot say is:
Add LinkedIn to schema and rankings improve.
Google has not published that rule.
Use the profile because it provides genuine identity context.
How to connect an author to an organisation
Schema.org’s worksFor property can connect a Person with an Organization. Schema.org
For example:
“worksFor”: {
“@id”: “https://example.co.uk/#organization”
}
This becomes particularly useful when your wider schema graph already defines the company with the same stable @id.
You now have:
Article
→ written by Person
→ who works for Organization
Rather than three unrelated blocks of structured data.
For the broader GEO approach, use the internal anchor:
Copy-and-adapt author schema example
Here is a simple Article example.
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Article”,
“headline”: “Example Article Title”,
“datePublished”: “2026-09-29”,
“dateModified”: “2026-09-29”,
“author”: {
“@type”: “Person”,
“@id”: “https://example.co.uk/authors/jane-smith/#person”,
“name”: “Jane Smith”,
“url”: “https://example.co.uk/authors/jane-smith/”,
“sameAs”: [
“https://www.linkedin.com/in/example-profile/”
],
“jobTitle”: “Senior B2B Marketing Consultant”,
“worksFor”: {
“@id”: “https://example.co.uk/#organization”
}
},
“publisher”: {
“@id”: “https://example.co.uk/#organization”
}
}
</script>
Replace every example value with real information.
Also check whether your SEO plugin already generates Article and Person entities before adding custom JSON-LD.
Duplicating the same author in several competing schema graphs can make the implementation harder to maintain.
What if the writer is a freelancer?
Use the real author when that is genuinely how the content was produced and readers would reasonably expect authorship information.
You do not need to pretend the freelancer is a permanent employee.
Their author page can describe the relationship accurately:
Freelance B2B copywriter contributing to Lobo Digital.
rather than:
Senior Lobo Digital Strategist
if that is not their role.
Google’s Article markup supports individual authors, and all authors presented on the page should also be represented correctly in markup. Google for Developers
Truthful attribution beats an artificial staff biography.
What about AI-assisted content?
Using AI does not automatically make content good or bad.
Google’s guidance focuses on the quality, originality, accuracy and usefulness of the resulting content rather than simply whether AI was involved. It also warns against scaled generation that adds little value. Google for Developers
Google specifically says that AI or automation disclosures can be useful where readers would reasonably wonder how the content was created. Google for Developers
And Google has previously said that listing AI itself as the author is generally not the best way to provide that transparency. Google for Developers
A better model is:
Written or reviewed by a real person
plus, where relevant:
AI-assisted research, drafting or analysis was used as part of the production process.
The named author should genuinely take responsibility for the published content.
Common author markup mistakes
A byline that goes nowhere
If the author name is clickable, give the destination a purpose.
A proper author profile is more useful than sending every writer to the generic About page.
Inventing qualifications
Do not add credentials to a bio or Person schema unless the person genuinely holds them.
Using one employee as author for everything
If ten people contribute to the website, do not automatically assign the company founder to every article because their profile looks authoritative.
Authorship should reflect reality.
Adding a Person in schema that users cannot see
Your structured data should agree with the visible page.
Google’s guidance for AI features and structured data continues to emphasise that markup should match visible content. Google for Developers
Treating sameAs as a backlink dump
An external URL should help identify the same person.
A random article mentioning them is not automatically a suitable identity reference.
Schema.org defines sameAs as a reference page that unambiguously indicates the identity of the entity. Schema.org
The honest limit of author schema for AI search
There is no published formula saying:
Person schema = more AI citations.
There is no known threshold for how many profiles an author needs.
There is no evidence that adding LinkedIn creates an automatic ChatGPT recommendation boost.
For Google’s generative AI features specifically, Google says normal SEO fundamentals remain relevant and that no special Schema.org markup is required for AI Overviews or AI Mode. Google for Developers
What we can say is:
Google encourages clear authorship.
Google’s Article markup explicitly supports author identity.
Google recommends url or sameAs to help it understand authors.
Schema.org gives us a standard way to describe a Person and their relationships.
And readers themselves benefit from knowing who is responsible for expert content.
That is enough reason to get authorship right.
You do not need an invented AI-ranking claim on top.
Author schema should identify a real person, not manufacture expertise
The cheapest improvement is not adding twenty Person properties.
It is making sure the basics agree.
Visible byline
Who wrote the article?
Author page
Who are they and what is their relevant background?
Article schema
Does the structured data identify the same person?
External identity
Are there genuine profiles that help distinguish that person from somebody with the same name?
Organisation relationship
Does the markup correctly connect the author with the company where appropriate?
Published work
Can readers see what else this person has contributed?
That creates a much cleaner authorship model.
And if there is one rule worth keeping, it is this:
Do not use schema to manufacture authority. Use it to describe authority and identity that genuinely exist.
identity that genuinely exist.
Get your free AI visibility audit
Learn how to write Content AI Will cite:
