<b>A byline is a string. An author is an entity. Search cares about the second one.</b>

<b>A byline is a string. An author is an entity. Search cares about the second one.</b>

The question: does adding an author name to a page do anything, or does it require the name to resolve to a known entity?

The distinction is the whole game. A byline is text on a page. An entity is a node in a knowledge graph with relationships — publications, affiliations, a disambiguated identity. Google's systems, per the entity-recognition work described across its patents and the Knowledge Graph documentation, operate on entities, not strings. An author who exists only as words on your own site has no independent corroboration to draw on.

The evidence: the QRG instructs raters to research the reputation of the content creator using independent sources. A bare byline gives them nothing to research. An author who is an established entity — with bylines across reputable sites, a Wikipedia or Wikidata node, conference talks indexed and findable — provides corroborating evidence that raters and systems can both reference.

Counter-evidence worth stating: most ranking content has no notable author entity and ranks fine. Entity-level authorship matters most precisely where YMYL stakes are high; elsewhere its marginal value is small and easily overstated.

Caveat: building an author entity is slow and cannot be faked with markup alone. sameAs links to profiles you control are weak; what counts is independent web consensus that the entity exists and is what it claims.

What we still don't know: how heavily, if at all, production ranking weights author-entity corroboration versus site-level signals. The honest answer is that site-level trust still appears to dominate for most queries.