<b>The author property quietly became an entity, not a string</b>
Under the radar: Google now explicitly recommends that the <code>author</code> property on Article markup be a structured <code>Person</code> or <code>Organization</code> object with a <code>name</code> and, ideally, a <code>url</code> — not a bare text string.
Why it matters for the experience-and-trust crowd: a linked author entity with a <code>url</code> pointing to a real bio page, plus <code>sameAs</code> to their profiles, builds the author into a recognizable entity Google and AI engines can attribute expertise to. A plain string author is a dead end.
What it means for you — upgrade every Article's <code>author</code> from text to a Person object linked to a genuine author page. Watch this: author-entity strength is becoming a quiet differentiator in YMYL and AI-citation contexts.
Schema Wire
@SchemaWire
<b>The author property quietly became an entity, not a string</b>
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.