Why it matters
- Google's Article documentation lists
authoramong its recommended properties, with the author'snameand aurlthat identifies them. It helps Google understand who wrote the article and show it correctly. - Readers, and the assistants that quote articles, look for who wrote what they read. A byline in the markup states it plainly.
- It is a recommendation, not a requirement: Article markup has no required properties, and a page without an author stays eligible. That is why this is minor.
Example
"@type": "BlogPosting", "headline": "كيف تختار عطر العود" }
"headline": "كيف تختار عطر العود", "author": { "@type": "Person", "name": "سارة العامري", "url": "/" }
How to fix
Add the author, as a Person or an Organization, with a name and a page about them:
json
"author": { "@type": "Person", "name": "سارة العامري", "url": "https://shop.example/ar/authors/sara" }- Use the name as it appears on the page, in Arabic if the byline is Arabic.
- For several authors, give a list. For an editorial team, an
Organizationwith its name. - Show the byline on the page too: the markup describes what readers see.
How we detect
- We read the
Article,NewsArticleandBlogPostingobjects (and their subtypes) the page describes of itself: at the top of a JSON-LD block or in its@graph, not the articles a list names in passing. - We report one without
author, or whose authors all lack a name. A name as plain text, and a reference (@id) to an author defined elsewhere in the graph, count as named.
The visible byline is not looked for: telling a byline from other text would be a guess. Microdata and RDFa are not read here.