To show author expertise AI search can read, put an accurate byline on each article and link it to an author page that explains who the author is and what they write about (1). Google's guidance treats clear sourcing, evidence of expertise and background about the author as signals of trust. Mark the same author details up in structured data so machines can parse them (2).
How do I show author expertise on my pages so search and AI systems trust them?
Show the author on the page where a reader would expect to see one, and link that byline to information about the person (1). Google's guidance asks whether content presents clear sourcing, evidence of the expertise involved, and background about the author or site, such as links to an author page or About page. It also asks whether the content was written or reviewed by someone who demonstrably knows the topic.
Trust matters more than the other E-E-A-T aspects, and a page does not have to demonstrate all of them (1). Some content is helpful because of the experience it shows, while other content is helpful because of the expertise it shares. Where experience is the point, state it plainly: first-hand use of a product or a visit to a place is the kind of evidence Google asks for.
Recala's own articles follow this pattern. Andrés Naves, Founder, is the named author and reviewer on recala.co, and the company's authorship policy requires real authors linked to their articles. Naming the author makes responsibility visible; it does not turn AI-assisted writing into experiences the author never had.
E-E-A-T is not itself a specific ranking factor, and this guidance describes Google's systems, not every AI model (1). Google also asks whether a byline leads to further information giving background about the author and the areas they write about.
How should I mark up author and credential information so machines can parse it?
Google's Article documentation requires the object to be based on Article, NewsArticle or BlogPosting (2). Each author belongs in the author property with the Person type for people and Organization for organizations.
List every author shown on the page, each in its own author field (2). Do not merge several names into one field. Keep author.name to the name only, and add a url or sameAs property with a valid URL that uniquely identifies the author, such as a bio page or social profile. If that URL is an internal profile page, Google recommends marking it up with profile page structured data.
Add datePublished and dateModified in ISO 8601 format so the publication and revision dates are readable (2).
Article markup with separate Person authors shows the literal shape of author markup for two authors (2).
The Article documentation gives jobTitle and honorificPrefix only as example Person fields (2).
Author markup rules for article pages
| Markup element | Rule from Google's documentation |
|---|---|
| Article type | Base the object on Article, NewsArticle or BlogPosting. |
| author type | Use Person for people and Organization for organizations; do not use the wrong type. |
| All authors | Include in the markup every author presented on the page. |
| Multiple authors | List each author in their own author field and do not merge names into one field. |
| author.name | Specify only the author's name, with no other information. |
| author.url | Link a page that uniquely identifies the author, such as a bio or about-me page. |
| Internal profile page | Mark up the author with profile page structured data. |
| sameAs | Use it as an alternative to url; Google understands both when disambiguating authors. |
| url and sameAs values | Use valid URLs. |
| datePublished | The date and time the article was first published, in ISO 8601 format. |
| dateModified | The date and time the article was most recently modified, in ISO 8601 format. |
Example: Article markup with separate Person authors
{
"@context": "https://schema.org",
"@type": "Article",
"author": [
{
"@type": "Person",
"name": "Willow Lane",
"honorificPrefix": "Dr",
"jobTitle": "Editor in Chief",
"url": "https://example.com/authors/willow-lane"
},
{
"@type": "Person",
"name": "Regula Felix",
"sameAs": "https://example.com/profiles/regula-felix"
}
],
"publisher": [
{
"@type": "Organization",
"name": "Bugs Daily"
}
]
}How do I keep author and date information accurate and honest over time?
Only name real authors (1). Google warns that fabricated creator profiles, such as AI-generated headshots, made-up names or false credentials, make a page untrustworthy to users and to its automated quality systems. Make each byline lead to further information about the author, giving background about them and the areas they write about.
Google asks whether you are changing a page's date to make it seem fresh when the content has not substantially changed (1). Set dateModified to the date and time the article was most recently modified, in ISO 8601 format, so it moves only when the article has actually been modified (2).
Where readers might reasonably ask how content was created, Google suggests an AI or automation disclosure (1).
Next step
Continue with Recala to turn this plan into a concrete next step.