Skip to content
50% OFF $299 $599
Lock in
§ 3.9 ARTICLE
Published VerifiedEvery 6 weeks Sources3 named Authored bySquareRank Team

Schema · § 3.9 · How-to

Person (author) schema for E-E-A-T

Person schema1 is the E-E-A-T entity anchor for a Squarespace site. The founder bio page (typically /founder/ or /about/) carries one Person JSON-LD block with name, jobTitle, url, image, description, knowsAbout (an array of expertise topics), and sameAs (an array of URLs to LinkedIn, Twitter/X, GitHub, podcast appearances, Wikidata). Every Article on the site sets its author.url field to /founder/, which Google and AI engines resolve to the full Person entity. The canonical implementation lives on this site at /founder/ — view source on that page for the live block.

Person schema produces no specific Google rich result, but it carries disproportionate weight for AI engine citation. Search Engine Land's 2026 GEO research3 describes the mechanism: an entity-linked author with strong sameAs is materially easier for an AI to confidently attribute than an anonymous byline, which directly affects whether the engine cites the page or a competitor.

What Person schema is

Person is the Schema.org type for an individual human — distinct from Organization (a company) and from generic Author (a literal property name, not a type). The inheritance chain runs Thing > Person. Properties most relevant to E-E-A-T and AI citation: name, givenName, familyName, jobTitle, url (the canonical page describing the person), image, description (a short bio), knowsAbout (an array of topics the person has expertise in), sameAs (an array of URLs to verified profiles), worksFor (an Organization the person is affiliated with), alumniOf (educational institutions).

The mental model: Person describes one specific human, with sameAs as the entity graph that confirms identity across the open web. A LinkedIn URL on the Person.sameAs array tells Google — and any AI engine consuming the schema — that this exact human owns this exact LinkedIn profile. Pile up five strong sameAs URLs (LinkedIn, Twitter/X, GitHub, a podcast appearance, a Wikidata Q-ID) and the entity becomes hard to confuse with anyone else.

When to use Person schema

Install Person schema on the founder bio page (or every author bio page if the site has multiple authors). Reference the Person entity from every Article's author field via the url property. Do not install Person on home pages, service pages, or product pages — those use Organization or LocalBusiness or Service. Do not install Person blocks for fictional characters or pseudonyms unless the entity is genuinely a public-facing identity with sameAs.

For a single-author site (most Squarespace small-business sites), one Person entity covers the whole site. The pattern: /founder/ hosts the Person schema; every Article points author.url at /founder/; the Person schema carries the full sameAs graph. The result: AI engines consistently attribute every article on the site to one confidently-identified human, lifting citation odds across the board.

Rich-results and AI engine extraction

Person schema does not trigger a specific Google rich result. It does contribute to knowledge-panel surfacing for the named person (when combined with sufficient external signal) and to E-E-A-T evaluation for the pages the person authors. The bigger 2026 payoff is AI engine attribution: ChatGPT, Perplexity, Claude, and Gemini parse Person schema as a fast path to author identity, which directly affects citation confidence and the visible attribution in AI answers.

Person schema in 2026

sameAs

the property doing most of the work — verified URLs to LinkedIn, X/Twitter, podcast appearances, Wikidata Q-IDs.

Schema.org · 2026-03-19
E-E-A-T

the Google framework Person schema supports — Experience, Expertise, Authoritativeness, Trustworthiness.

Google Search Central · 2025-12-10
AI

engines weight entity-linked authors materially over anonymous bylines when deciding which source to cite.

Search Engine Land · 2026-02-23

Required and recommended fields

Schema.org imposes no hard required properties on Person. The useful minimum: name, jobTitle, url, image, description, sameAs (an array of at least 2-3 verified profile URLs). The recommended expansion for serious E-E-A-T: knowsAbout (an array of expertise topics), worksFor (the Organization the person founded or works at), award (notable recognition), alumniOf (educational institutions where verifiable).

  • name — the full name as the person uses it publicly.
  • jobTitle — the person's role.
  • url — the canonical bio page (typically /founder/ on a Squarespace site).
  • image — a photo. URL to a square, high-resolution headshot.
  • description — a short bio paragraph.
  • knowsAbout — an array of expertise topics. Strings or URLs to Wikipedia/Wikidata entries.
  • sameAs — an array of URLs to verified profiles. LinkedIn, Twitter/X, GitHub, podcast pages, Wikidata Q-IDs.
  • worksFor — an Organization the person is affiliated with.
  • email — the person's professional email (optional).

Copy-paste JSON-LD example

The block below is a complete Person schema for a single-author Squarespace site. It mirrors the pattern shipping live at /founder/ on this site, anchored to a real founder with verified sameAs profiles. Replace name, jobTitle, image, description, knowsAbout, and sameAs URLs with your real data — every sameAs URL must resolve to a page that visibly identifies the same human.

JSON-LD Person schema for the founder bio page (the canonical pattern lives at /founder/) 
 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Person", "name": "Billy Reiner", "givenName": "Billy", "familyName": "Reiner", "jobTitle": "Founder, SquareRank", "url": "https://squareranked.com/founder/", "image": "https://squareranked.com/images/founder-headshot.jpg", "description": "Ten years building Squarespace sites by hand, over a thousand of them. Founder of SquareRank.", "email": "[email protected]", "knowsAbout": [ "Squarespace SEO", "Answer Engine Optimization", "Generative Engine Optimization", "JSON-LD structured data", "AI search visibility", "llms.txt", "Squarespace 7.1" ], "sameAs": [ "https://www.linkedin.com/in/billyreiner", "https://github.com/billyrei", "https://dribbble.com/TheBillyReiner", "https://www.behance.net/billyreinerdesigns", "https://www.billyreiner.com/", "https://billyreiner.de/" ], "worksFor": { "@type": "Organization", "name": "SquareRank", "url": "https://squareranked.com/" } } </script>

Where to paste it on Squarespace

Person schema goes on the founder bio page (typically /founder/), per-page rather than site-wide. Open the bio page in the Squarespace editor, Page Settings > Advanced > Page Header Code Injection, paste the script block, save. The schema lives on one page; every Article elsewhere on the site references it by URL via the author.url field. Do not duplicate the Person schema on every Article — point at the canonical instance instead.

For multi-author sites (uncommon on Squarespace, common on agency sites with several contributors), each author gets their own bio page with their own Person schema. The pattern stays the same: one canonical Person per human, referenced by URL from every Article that author wrote.

Validation steps

Run the founder bio page URL through Google's Rich Results Test. Confirm Person is detected and zero errors are reported. The Rich Results Test will report 'no rich result available' — that's expected, Person isn't a Google rich-result type. The success signal is structural validity and clean sameAs URLs. Click through each sameAs URL manually to confirm none have rotted.

A second validation worth running for serious E-E-A-T: Google's Knowledge Graph Search API or the Wikidata reconciliation tools to confirm the entity is discoverable. If the founder has a Wikidata Q-ID, include it as a sameAs URL (in the form https://www.wikidata.org/wiki/Q{your-id}) — this is the highest-confidence sameAs link available.

Common gotchas on Squarespace

Three gotchas catch most Person installs. First: weak or broken sameAs links — URLs to LinkedIn profiles that 404, abandoned Twitter accounts, podcast pages that no longer resolve. Each broken link weakens the entity graph rather than strengthens it. Audit annually. Second: duplicating Person across many pages instead of referencing one canonical page — confuses the entity graph and produces 'which Person is the real one' ambiguity. Third: padding knowsAbout with topics the person has no demonstrable expertise in — AI engines weight knowsAbout against demonstrated content; padded expertise hurts more than it helps.

A fourth gotcha specific to Squarespace's contributor system: Squarespace blogs auto-emit a basic Person object inside BlogPosting.author when a blog post lists a contributor. That auto-emitted Person is name-only — no sameAs, no knowsAbout, no entity wiring. Override by setting the article's author.url to /founder/ in your manual Article schema, which redirects the entity reference to the full Person definition.

Person typically references Organization (via worksFor) and is referenced from Article (via author). The same Person can also be the organizer on Event, the author on Review, or the provider on Service when the offering is delivered by one person. BreadcrumbList belongs alongside on the bio page.

Keep reading · § 3.9