Why Attorney Entity Data Matters More Than Ever

When a prospective client asks ChatGPT "who are the best employment lawyers in Hamilton, Ontario," the AI doesn't guess. It draws on information it has accumulated about specific attorneys — from their firm websites, from legal directories, from news articles, from published opinions — and synthesizes a recommendation based on what it believes to be true about each person's expertise, credentials, and reputation.

The problem for most law firms is that their attorney bio pages contain excellent information that AI systems struggle to parse reliably. A beautifully written bio describing an attorney's 18 years of family law experience, their Queen's University law degree, and their Law Society of Ontario membership is genuinely valuable — but it's sitting in prose paragraphs that require the AI to interpret and extract rather than simply read structured data.

Person schema solves this. It's structured data markup that explicitly labels who an attorney is, what they do, where they trained, who employs them, and where else they appear online. Instead of making AI systems guess, you're handing them a machine-readable dossier. That clarity translates directly into more accurate and more frequent attorney mentions in AI-generated recommendations.

This complements the firm-level structured data covered in our guide to LocalBusiness schema for law firms. Together, firm-level and attorney-level schema create a complete entity hierarchy that AI systems can navigate and trust.

What Person Schema Looks Like for an Attorney

Person schema is implemented as a JSON-LD block in the head of an attorney's bio page. Here's a realistic example for a family law attorney at a Toronto firm:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://yourfirm.com/team/sarah-chen#person",
  "name": "Sarah Chen",
  "jobTitle": "Family Law Partner",
  "description": "Sarah Chen is a family law partner with 14 years of experience in divorce, custody, and asset division for Ontario families.",
  "url": "https://yourfirm.com/team/sarah-chen",
  "image": "https://yourfirm.com/images/sarah-chen.jpg",
  "worksFor": {
    "@type": "LegalService",
    "@id": "https://yourfirm.com/#organization",
    "name": "Chen & Associates Family Law"
  },
  "knowsAbout": [
    "Family Law",
    "Divorce Law",
    "Child Custody",
    "Property Division",
    "Spousal Support"
  ],
  "hasCredential": [
    {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "degree",
      "name": "Juris Doctor",
      "recognizedBy": {"@type": "Organization", "name": "Osgoode Hall Law School"}
    },
    {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "license",
      "name": "Member, Law Society of Ontario",
      "recognizedBy": {"@type": "Organization", "name": "Law Society of Ontario"}
    }
  ],
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "Osgoode Hall Law School"
  },
  "sameAs": [
    "https://www.linkedin.com/in/sarah-chen-lawyer",
    "https://lso.ca/lawyer-search/sarah-chen"
  ]
}
</script>

Notice the key properties: worksFor links the attorney to the firm entity. knowsAbout explicitly lists practice area specialisations. hasCredential captures bar admission and law degree. sameAs connects the attorney to their LinkedIn profile and Law Society directory listing — external signals that help AI systems corroborate the entity data on your site.

The @id property is important. It creates a unique identifier for this person entity that allows other structured data on the same site to reference the attorney by ID. If you later add an Article schema block for content this attorney wrote, you can link the author to this Person entity rather than repeating all the person data.

The Most Valuable Properties for Attorney Schema

Not all Person schema properties are equally important for law firm SEO. Here's a practical priority ranking based on what delivers the most signal to AI systems and search engines:

Highest priority — include on every attorney's schema:

High value — add when the data is available:

Add for attorneys who publish content:

Connecting Attorney Schema to Content They've Written

One of the most powerful uses of Person schema is connecting it to content that attorney has written or contributed to. When you publish an article on your blog or insights page, the Article schema block includes an author property. If you link that author property to the attorney's Person schema entity using the @id reference, you're building a connected knowledge graph — one that AI systems can traverse.

The result is that every article attributed to this attorney reinforces their expertise signal in a structured, machine-readable way. An attorney who has published 10 articles about family law matters, all attributed via schema to a Person entity that lists "Family Law" in its knowsAbout array, has built a significantly stronger AI authority signal than an attorney whose bio page and articles are completely disconnected in structured data terms.

This is how individual attorney authority gets built over time in AI search — not through a single schema block, but through a network of interconnected entity signals that compound as the attorney publishes more, gets mentioned more, and accumulates more structured data pointing back to their core Person entity. For more on how to build this broader entity authority, see our guide to topical authority for law firms.

The sameAs Property: Why External Profiles Are Critical

The sameAs property deserves special attention because it's one of the most powerful things you can add to attorney Person schema. It tells search engines and AI systems that this attorney entity is the same person who appears on LinkedIn, in the Law Society of Ontario's public registry, on Avvo, on Martindale-Hubbell, or wherever else they have a verified professional profile.

This cross-reference matters enormously for AI trust signals. AI systems build entity knowledge from multiple sources across the web. When your schema explicitly connects the person on your website to a LinkedIn profile with 400 connections, an LSO registry entry, and a Martindale-Hubbell profile, you're corroborating the entity's existence and credentials through multiple independent sources. An AI system is much more confident recommending a lawyer whose entity data is corroborated across several authoritative sources than one who exists only on a single website.

The practical checklist for sameAs URLs to include for Ontario lawyers:

For a complete look at how all these entity-building pieces fit together, see our article on entity SEO vs keyword SEO for law firms and the guide to attorney Knowledge Panel optimisation.

Building Out Your Entire Team's Schema in One Pass

Once you understand the schema structure, the fastest approach is to build out all your attorneys' Person schema in one focused session. Create a spreadsheet with one row per attorney. Columns: name, title, URL, image URL, knowsAbout (comma-separated), hasCredential (law school, year called to bar), sameAs URLs. Fill it out completely for everyone on the team before writing a single line of markup.

Then use the template from earlier in this article as a starting point for each attorney's bio page, substituting in their specific data. Each schema block takes about 15 minutes to write and validate once you have the template and the attorney's data in front of you. A 5-attorney firm can have complete Person schema across all bio pages in under two hours.

After implementing, validate each page using Google's Rich Results Test. Person schema doesn't typically produce a specific rich result in Google Search the way FAQPage or Review schema does — but validating confirms that Google can correctly parse the markup, which is what matters for entity knowledge graph building and AI citation. Then submit each updated bio page URL in Google Search Console's URL Inspection tool to request a fresh crawl.

For the complete structured data picture for your law firm, see our full schema markup guide for lawyers which covers all the schema types that matter across your entire site.

Frequently Asked Questions

Person schema is structured data markup added to attorney bio pages that explicitly identifies the attorney — their name, job title, employer, areas of expertise, credentials, and professional profiles — to search engines and AI systems. It's the primary structured data tool for building individual attorney authority in search and AI recommendations.

Yes, significantly. AI systems build knowledge about individuals from web content, and Person schema is one of the clearest signals you can provide about who an attorney is and what they specialize in. It's especially valuable for attorneys who publish articles or are mentioned in legal news, as it helps AI systems attribute that content correctly and builds the attorney's expertise profile.

Yes — every attorney with a bio page should have Person schema markup on that page. Each attorney's schema should be unique to them: their specific name, title, practice areas, credentials, and profiles. Don't use a generic schema block for all attorneys. Even for junior associates, accurate schema helps AI systems build a complete picture of your firm's team and expertise.

At minimum: name, jobTitle, worksFor (linking to your firm's Organization schema), description, url, knowsAbout (practice area specialisations), and sameAs (LinkedIn and Law Society directory URLs). Highly recommended additions: hasCredential for bar admissions and law degrees, alumniOf for law school, and image for their headshot URL.

LocalBusiness schema describes the firm as an entity — its name, address, phone number, services, and overall identity. Person schema describes individual attorneys within the firm. The two are linked via the worksFor property in the Person schema. Together they create a complete entity hierarchy: the firm is the organization, and each attorney is a person who belongs to it, with their own individual expertise clearly defined.