Entity SEO for Individual Attorneys: The Person Schema for Law Firm Citation

The Person entity is a schema.org structured-data type that represents a human individual as a standalone, verifiable entity with professional credentials, affiliations, and accomplishments. For attorneys, it is the most granular way to declare expertise to AI search engines — more precise than burying lawyer names in firm bios. When you mark up an attorney's profile page with a Person node, you are telling ChatGPT, Claude, and Gemini: "This is a specific person with verifiable qualifications; you can cite them as an expert."

Traditionally, law firm websites handle attorney information as content pages (names, photos, case wins, bar admissions) with minimal machine-readable structure. The Person entity changes this: it makes attorney identity, credentials, and affiliations explicit and machine-readable. An AI search engine can then extract fields like hasCredential ("California Bar Member #123456"), worksFor (the firm entity), knowsAbout ("intellectual property law"), and sameAs (links to LinkedIn, verified personal website, bar directory) — and use that structured information to answer queries about expertise.

Why this matters: modern AI search privileges corroborated, externally-verified identity. When you say "Jane Smith is an IP attorney," the engine assigns that claim low trust. When you say "Jane Smith, corroborated by her CA Bar License #234567, LinkedIn profile at linkedin.com/in/janesmith, a personal website at janesmith.law, and 15 published papers on patent litigation" — the engine assigns that claim much higher trust. The Person entity is the scaffold for this corroboration.

The shift from content-centric to entity-centric SEO is where modern law firm visibility lives. A generic practice-area page can rank in Google organic search. But a query like "best IP attorney in San Francisco who writes about trade secrets" — a specific, expert-hunting query — is increasingly answered by AI search engines that pull from attorney Person entities with the right sameAs links and keywords.

A complete Person entity for an attorney includes name, title, professional photo, workplace affiliation (worksFor pointing to the firm entity), credentials, education, and a set of sameAs URIs linking to external authorities. Each field contributes to how the entity embeds in an AI system's vector space — the semantic neighborhood where the attorney is discoverable. Start with name (givenName, familyName), image, jobTitle (e.g., "Partner, Intellectual Property"), and worksFor referencing your firm's LegalService or Organization entity by its @id. Then layer in hasCredential (license, bar admission, certifications), alumniOf (law school, undergrad), knowsAbout (practice areas and substantive expertise — e.g., "trade secret litigation," "patent prosecution," "copyrights in digital media"), and sameAs linking to external profiles.

The hasCredential field is powerful for legal professionals. A credential is a recognized qualification: "Admitted to California State Bar, License #234567" is a credential. So is "Certified Specialist, Intellectual Property Law" or "AV Preeminent Rating by Martindale-Hubbell." Each credential you mark up makes the attorney's authority more concrete. The structure is a Credential object with credentialCategory (text, usually the credential name) and recognizer (the issuing body: the State Bar, ABA, Martindale, etc.). An AI engine reading this structure understands that the attorney's expertise is independently verified, not self-proclaimed.

The sameAs array is the most important for AI citation because it anchors the Person entity to external identity graphs. If you set sameAs to include the attorney's LinkedIn profile URL (e.g., linkedin.com/in/janesmith), and an AI engine cross-references that LinkedIn page to verify the attorney's education and job history, the engine gains confidence in your Person entity's claims. The same applies to the State Bar website (e.g., the official license lookup page), a verified personal website, Wikidata if applicable, and directories like Avvo or Justia. Each sameAs link is a vote of confidence from an external source.

publishingPrinciples and verifiableCredential are emerging fields that let you link to a personal website or a public CV, further corroborating the Person's identity. If an attorney has a personal branding site or a published CV accessible at a fixed URL, include it in publishingPrinciples (or add a url field pointing to a personal portfolio). This creates multiple touch points where an AI engine can verify the Person's claims. Additionally, the url field (distinct from sameAs) should point to the person's canonical page on your firm website (e.g., example.com/attorneys/jane-smith). This is the primary location where they are claimed; sameAs are the corroborating references.

Don't over-populate the entity with marginal fields. An oversaturated Person node risks schema validation errors and dilutes the semantic signal. Stick to name, givenName, familyName, image, jobTitle, worksFor, telephone (optional, usually the firm's main line or direct dial if public), email (optional, only if the attorney has published their own email), alumniOf, hasCredential, knowsAbout, sameAs, and url. Leave out generic or speculative fields like award or birthDate (birthDate is controversial and privacy-sensitive; omit it unless the attorney is a public figure or has published their birthdate themselves).

A Person entity is not standalone; it is part of your firm's entity graph. The attorney's Person node references the firm's LegalService, Organization, or LocalBusiness entity via the worksFor property (which points to the firm entity's @id). Simultaneously, the firm entity should list the attorney in a memberOf or employee array (reverse edge). This bidirectional linking tells AI systems that there is a verified professional relationship: the attorney works for the firm, and the firm employs the attorney. This is far more powerful than having separate, disconnected pages.

Example: your firm's Organization entity has @id = "http://example.com/#org". Your attorney Jane Smith's Person entity has @id = "http://example.com/attorneys/jane-smith#person" and includes "worksFor": {"@id": "#org"}. The Organization entity, in turn, should have a member or employee array that includes a reference back to jane-smith#person. When an AI engine traverses this graph, it sees a coherent entity relationship, not fragmented claims. This coherence boosts trust.

For multi-office firms, the structure becomes more nuanced. If Jane Smith is a partner at the San Francisco office and the firm also has a Los Angeles office, her worksFor should point to the firm-level entity (not a per-office entity) for maximum scope. However, you might also add an areaServed or location field to her Person node to indicate where she primarily works (San Francisco). This is more specific than omitting location entirely and helps AI engines serve her profile to users searching for attorneys in her region.

The firm entity should also link to its attorney entities, not just the reverse. For example, a LegalService entity representing the firm's practice in intellectual property might have a member array listing all IP attorneys. This creates a three-level graph: Firm → Practice Area → Attorneys. AI engines use this structure to answer "Who are the IP specialists in this firm?" and to surface individual attorneys in response to specific expertise queries.

E-E-A-T stands for Expertise, Experience, Authoritativeness, Trustworthiness — Google's quality rater guidelines and a concept modern AI search engines also prioritize. A rich Person entity is one of the most direct ways to signal E-E-A-T for an attorney. Expertise is conveyed through knowsAbout (what the attorney specializes in), publications (academic papers, bar journal articles, books), and hasCredential (certifications, specialist designations). Experience comes from employment history (worksFor with dates, education, and years-in-practice if available). Authoritativeness is boosted by sameAs linking to high-authority external profiles and by mentions in legal directories and earned media. Trustworthiness is reinforced by license verification (a real, verifiable bar license number) and consistency across all platforms.

The most important lever for E-E-A-T in the Person entity is the sameAs strategy. When you link an attorney's Person entity to their verified LinkedIn profile, their bar registration page, and their Avvo profile, you are not just adding redundancy — you are creating corroboration checkpoints. An AI engine will cross-reference these profiles to verify the attorney's claims. If the attorney's profile on your website says they graduated from Stanford Law School, but their LinkedIn profile and your own bar database say Yale Law School, the inconsistency signals an error or outdated information. Conversely, perfect consistency across platforms (same graduation year, bar admission year, practice areas) signals reliability.

Published content authored by the attorney — law review articles, book chapters, bar journal columns, and podcasts — dramatically strengthen the Person entity. When you add a publishedPaper or relatedLink field (or use a separate BibliographicReference or CreativeWork to represent a publication), you are creating a trail of external evidence of expertise. An AI engine reading an attorney profile knows that if the attorney has published 10 papers on patent law, they are not casually claiming patent expertise — they have demonstrated it publicly. Publications are especially valuable because they typically reside on high-authority domains (law review sites, university presses, bar association websites), which AI engines trust.

Don't fabricate or embellish credentials. If an attorney claims a certification they do not hold, or misrepresents a publication, this will be discovered when an AI engine cross-references the sameAs links or when a user checks. The result is immediate credibility damage and potential ranking penalties. Instead, focus on genuine credentials and real publications. If an attorney has a sparse publication record, that is fine — it is honest. Build the Person entity on what is true and verifiable; over time, as the attorney publishes more and accumulates years of practice, the entity naturally grows richer.

When a user asks an AI search engine "Who is an expert in trade secret litigation in Northern California?", the engine does not simply return a list of firms. It retrieves relevant Person entities of attorneys who have published on trade secrets, have verified credentials in the relevant jurisdiction, and appear in high-authority directories. If your firm has rich Person entities for its attorneys, your attorneys are more likely to be named in the answer. This is a form of earned visibility: your attorney becomes a face of the firm's expertise, cited individually alongside the firm.

The mechanism is passage-level retrieval combined with entity retrieval. When the engine searches for trade secret expertise, it embeds the query and finds relevant passages (blog posts, case results pages, news mentions) and it also retrieves relevant Person entities from its knowledge graph. A well-built Person entity with dense knowsAbout fields, multiple publications, and verified sameAs links will rank high in entity relevance. The engine then generates an answer that might read: "Jane Smith, an IP attorney at Example Law Group with 12 years of trade secret litigation experience and published research on digital confidentiality, recommends..." followed by a link to Jane's profile or firm page.

This type of citation is especially valuable because it is far more granular than a generic firm mention. When a potential client searching for trade secret expertise sees a named expert (Jane Smith) with verifiable credentials and publications, they are far more likely to click through and contact the firm. The individual attorney becomes a lead-generation asset — a point of entry into the firm's broader service offering.

Attribution also matters for firm reputation and attorney branding. If an attorney is regularly cited by AI engines on topics they specialize in, they build a personal brand independent of the firm. This can be valuable for attorney retention: an attorney with a strong personal brand is more marketable and can command higher compensation. Conversely, law firms that invest in attorney entity SEO are investing in a retention and recruitment tool as much as a marketing tool.

To build a Person entity that AI engines will trust and cite, follow this step-by-step approach. First, create a canonical attorney profile page on your website at a fixed, semantic URL (e.g., example.com/attorneys/jane-smith or example.com/team/jane-smith). This is the url field in your Person entity. Second, gather and verify all credentials: bar license number and state, law school graduation year and institution, specialty certifications (e.g., AV Preeminent, certified patent agent), and any bar admissions beyond the primary jurisdiction. Third, audit the attorney's public presence: do they have a LinkedIn profile? An Avvo profile? A personal website? Bar database entries? Collect all the verified URLs; these become sameAs entries.

Fourth, compile publications and media appearances. Search Google Scholar, your firm's website, bar association journal databases, and legal news sites for any articles or presentations authored or co-authored by the attorney. Gather URLs for each publication. Fifth, structure case results: compile notable wins and settlements the attorney has led. Do not exaggerate or misrepresent outcomes; list only cases the attorney can publicly discuss and for which you can cite sources (court records, press releases, or client testimonials). Sixth, write a brief bio (200–300 words) that weaves expertise, experience, and personality. The bio should be in plain English, not resume-style jargon, and should mention specific practice areas, notable case types, and credentials naturally.

Seventh, create the JSON-LD. Use validator.schema.org to ensure syntax correctness. Include name, givenName, familyName, image (a professional photo, 300x300px minimum), jobTitle, worksFor (@id reference to the firm), url (the attorney's profile page on your site), sameAs (array of verified external URLs), hasCredential (array of Credential objects with name and recognizer), alumniOf (array of school/university references), and knowsAbout (array of practice areas as text strings: "trade secret litigation," "patent prosecution," etc.). If the attorney has published papers, create a relatedLink array or separate CreativeWork/BibliographicReference nodes. If they are frequently quoted in media, add mentions via a url field or separate reference.

Eighth, render the entity on the attorney's profile page. Use schema.org's recommended JSON-LD format. Include an opt-in for the attorney to verify their profile, in case they want to claim it on external platforms (LinkedIn, Avvo). Ninth, update the firm's main Organization entity to include a reference to the attorney in its member or employee array (reverse edge). Tenth, annually refresh the Person entity: add new publications, update years of experience, add new credentials as they are earned, and verify that all sameAs links remain live. A sameAs link that 404s (the external profile no longer exists) signals that the entity is neglected and erodes trust.

Finally, monitor for disambiguation and duplicate entity issues. If your attorney has a common name like "John Smith," make sure your Person entity for that attorney is sufficiently specific (include middle initial, location, specialty) so that AI engines do not conflate them with another attorney named John Smith. Tools like Google Search Console, Ahrefs, and Semrush can flag duplicate or conflicting entity claims on the web.

Entity SEO for individual attorneys is not a quick ranking hack; it is a long-term brand-building strategy. As an attorney's Person entity accumulates publications, case results, media mentions, and verified credentials over years, that entity becomes a discoverable, citable asset in AI search. Law firms that invest in this strategy today position their attorneys as recognized experts 2–3 years from now when AI search engines have indexed and corroborated all the claims.

For attorneys, the payoff is visibility and personal brand value. An attorney who is regularly cited by AI search engines as an expert in their field becomes more recruitble to other firms, more valuable for business development, and more attractive to potential clients. For law firms, the payoff is lead generation: clients searching for expert advice on specific topics find your attorneys directly, not just your firm homepage. This is especially valuable for high-stakes, specialized practices (IP law, healthcare law, employment law) where a potential client's first question is often "Who at this firm specializes in this?"

Additionally, the entity data you build for your attorneys is reusable. Once you have invested in collecting and structuring publications, credentials, and media mentions for your attorneys, you can surface that data across your website, on social media, in email marketing, and in directory submissions. The same core dataset — the attorney's name, credentials, and accomplishments — powers your website, your LinkedIn company page, your bar directory profiles, and your AI search presence.

The trend in legal marketing is toward individual-attorney visibility, not just firm-level visibility. Generative Engine Optimization (GEO) accelerates this trend. As AI search becomes the primary way potential clients find legal expertise, firms that build strong, corroborated Person entities for their attorneys will outrank competitors with generic firm-only messaging. The long-term advantage is compounding: each new publication, each media mention, each credential addition strengthens the attorney's entity, making them more discoverable and more citable. Over time, your firm's attorneys become known experts, and the firm benefits from their visibility.