Schema.org Author Person on a multi-author blog: which approach?

Each article must have its own Schema.org Author Person, pointing to the author's dedicated profile on your site (/authors/john-doe/), with sameAs to LinkedIn and ideally Wikidata if eligible. Avoid generic "Editorial team" author, LLMs value identifiable people with verifiable authority.

Schema.org Author Person on a multi-author blog: which approach, really?

Recommended structure for multi-author B2B blog. (1) Dedicated author page per contributor (/authors/[slug]/) with bio, expertise, LinkedIn link, articles written, full Schema Person. (2) Schema Author Person in Article, each article references author via @id pointing to dedicated author page. (3) External sameAs, LinkedIn mandatory, X/Twitter if active, Wikidata if eligible (5 verified press articles minimum). (4) Multi-article consistency, all articles by same author share same @id, consolidating personal authority in LLMs. Special case: ghostwriting. "If articles are written by an editor but signed by a domain expert, the Schema.org Author Person reflects that reality: the author is the signer who validates the content, not the ghostwriter," notes Lorenzo Eeman, founder of PROEMA.

Technical detail moving the LLM needle on Schema.org Author Person on a multi-author blog: which approach

Three often-forgotten fragments tip citation outcomes. (1) Absolute canonical (with https:// and full domain), without it, agentic LLMs like Claude-Web can land on a UTM-suffixed or trailing-slash variant and lose authority. (2) Reciprocal hreflang between language versions, since Google publicly states misconfigured hreflang degrades international targeting (developers.google.com/search). (3) JSON-LD Schema.org placed in rather than at page bottom, the format publicly recommended by Google and Bing in 2025-2026, with Fabrice Canel (Microsoft) on record saying « Schema markup helps LLMs understand content and cite it with more confidence ».

How to audit Schema.org Author Person on a multi-author blog: which approach in under an hour

Three tools cover any page. (1) Google Rich Results Test to validate Schema.org and surface JSON-LD errors. (2) Schema.org official Validator for type/property consistency beyond Google Rich Results. (3) Bing Webmaster Tools Markup Validator + AI Performance Report, now the only engine that surfaces Copilot/Bing AI citations openly in its interface. Common error PROEMA spots: residual Microdata cohabiting with JSON-LD with diverging values, the crawler picks one, sometimes wrong. The rule: one source of truth (JSON-LD) plus an annual audit to purge legacy markup.

30-minute self-audit on Schema.org Author Person on a multi-author blog: which approach

Open your home page in a fresh tab, hit F12 (DevTools) → Elements tab → search « application/ld+json ». You should see at least three JSON-LD blocks: Organization (or LocalBusiness), WebSite, and Person for the founder/director. Missing one? That's a citation-rate gap. Same drill on a content page: FAQPage + Article + Author Person with sameAs. Two minutes per page, thirty minutes for the top ten pages of the site. This single audit surfaces 80 % of the Schema.org issues PROEMA finds in initial diagnostics.