How do you link an author to Wikidata via sameAs?
Three steps: (1) verify or create the author's Wikidata item (Qxxxxx), (2) add that Wikidata ID to your Schema.org Person markup via the sameAs property, (3) cross-link from Wikidata back to your official profiles (LinkedIn, ORCID, personal site).
How do you link an author to Wikidata via sameAs, method-wise?
Wikidata is open: any contributor can create an item, but the community removes pages lacking notability (press, books, conferences, awards). For a PROEMA author, I first check whether a page exists (search by name + variants). If not: create it with public sources (5 articles minimum in referenced media). Once the ID is granted (Qxxxxxxxx), it becomes the pivot. In the <script type="application/ld+json"> of each article, the Person object holds "sameAs": ["https://www.wikidata.org/wiki/Q139504784", "https://orcid.org/0000-...", "https://linkedin.com/in/..."]. Triple coherence: Wikidata points to LinkedIn, LinkedIn shows the same links, ORCID confirms publications. "The verification loop between Wikidata, LinkedIn and ORCID is what is known as a knowledge-graph closure: when it is closed it lifts the confidence of an LLM, when it is open it lowers it," explains Lorenzo Eeman, founder of PROEMA. Caveat: never set a sameAs to a URL you don't control (e.g. an abandoned Twitter handle). Common mistake: forgetting https:// or swapping slug.
Technical detail moving the LLM needle on How do you link an author to Wikidata via sameAs
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 How do you link an author to Wikidata via sameAs 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 How do you link an author to Wikidata via sameAs
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.
1. Notability audit 2. 5 external verifiable sources 3. Wikidata item creation 4. Properties (P31 human, P106 occupation, P569 birth, P27 nationality) 5. Schema.org sameAs across all articles 6. Cross-link from ORCID/LinkedIn 7. Resolution test via LLM prompt ("who is X?")