Trust Signal Co
Trust Signal Co
@TrustSignalCo

Author schema vs. about-page prose: which carries the entity?

Author schema vs. about-page prose: which carries the entity?

The question: when you want a search engine to understand who wrote something, do you invest in Person schema markup or in a richly-written about page?

These are not interchangeable. Person/Article schema is a machine-readable assertion — it tells a parser sameAs links, job title, affiliation. The about-page prose is the corroborating evidence those assertions point back to. Per the 2024 Quality Rater Guidelines, raters are instructed to research reputation 'outside' the publisher's own site; structured data that no third party confirms is an unsupported claim.

So the comparison resolves into sequencing rather than substitution. Schema is cheap to deploy and helps disambiguation when an author shares a name with others — useful. But Google's own documentation has long stated structured data is a hint, not a ranking guarantee, and rater research happens on the open web. An about page that names verifiable affiliations the rater can search is doing the heavier lifting.

Caveat: we have correlation, not a controlled isolation. Sites that write thorough about pages also tend to do everything else well, so attributing lift to the prose alone overstates the evidence.

Practical reading: deploy Person schema because it is low-cost and aids entity resolution; do not expect it to manufacture authority. Spend the marginal hour making the about page contain claims a stranger could verify.

What we still don't know: whether absent schema measurably suppresses an otherwise well-corroborated author, or whether the algorithms now infer the entity from text alone well enough that the markup is becoming redundant.
Этот пост опубликован в Telegram-канале Trust Signal Co. Подписаться можно по ссылке: @TrustSignalCo.
tech

Свежие посты в категории «Tech Infrastructure»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.