Your team page is where AI learns who actually works at your firm. Named humans with real titles, credentials, and linked profiles make your organization citable at the individual level. This blueprint provides the JSON-LD graph that connects every team member back to your organization so AI can surface the right person for the right query.
The team page is where AI connects named humans to your firm. When someone asks "who leads strategy at X agency" or "does this consultancy have certified professionals," the answer comes from structured data on this page. Named humans with credentials raise trust significantly — anonymous teams get skipped.
Person node with their name, jobTitle, url, and image. This is what AI reads when it needs to attribute expertise to a specific individual.hasCredential with an EducationalOccupationalCredential tells AI this person holds a real qualification. Only include it when the credential is genuine.sameAs array pointing to LinkedIn profiles lets AI cross-reference your team members across the web. This is the strongest identity signal for individual people.Person should include worksFor pointing to your Organization node by @id. This closes the loop — AI can see that the person belongs to your firm, and your firm employs that person.Organization node should list an employee array referencing each Person by @id, giving AI a complete roster from the company side.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
nameurlnamejobTitleurlsameAshasCredentialconditionalCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Professional Service Team page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Credential 2. Domain 3. Faq answer 4. Faq question 5. Organization name 6. Person 7. Team page title OPTIONAL — ask for these but proceed if I skip them: 1. hasCredential Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Professional Service Team" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. Add or remove Person nodes to match the size of your team. Remove the hasCredential field for any team member who does not hold a formal credential.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/team/",
"name": "YOUR_TEAM_PAGE_TITLE",
"url": "https://YOUR_DOMAIN.com/team/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/team/#breadcrumb"
}
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_ORGANIZATION_NAME",
"url": "https://YOUR_DOMAIN.com",
"employee": [
{ "@id": "https://YOUR_DOMAIN.com/#person-1" },
{ "@id": "https://YOUR_DOMAIN.com/#person-2" }
]
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#person-1",
"name": "YOUR_PERSON_1_NAME",
"jobTitle": "YOUR_PERSON_1_TITLE",
"url": "https://YOUR_DOMAIN.com/team/YOUR_PERSON_1_SLUG/",
"image": "https://YOUR_DOMAIN.com/YOUR_PERSON_1_IMAGE.jpg",
"sameAs": [
"https://www.linkedin.com/in/YOUR_PERSON_1_LINKEDIN"
],
"worksFor": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"credentialCategory": "YOUR_CREDENTIAL"
}
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#person-2",
"name": "YOUR_PERSON_2_NAME",
"jobTitle": "YOUR_PERSON_2_TITLE",
"url": "https://YOUR_DOMAIN.com/team/YOUR_PERSON_2_SLUG/",
"image": "https://YOUR_DOMAIN.com/YOUR_PERSON_2_IMAGE.jpg",
"sameAs": [
"https://www.linkedin.com/in/YOUR_PERSON_2_LINKEDIN"
],
"worksFor": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/team/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Team",
"item": "https://YOUR_DOMAIN.com/team/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
You should include a Person node for every team member you want AI to know about. At minimum, include leadership and client-facing staff. If AI cannot see a person in structured data, it cannot attribute expertise to them or recommend them by name.
Include hasCredential only when the person holds a genuine license, certification, or professional credential — such as a CPA, JD, PMP, or medical license. If there is no formal credential, omit the field entirely rather than leaving a placeholder. Fake or inflated credentials hurt credibility.
Structured data works best when relationships are declared from both sides. The employee array on the Organization tells AI "this firm has these people," while worksFor on each Person tells AI "this person belongs to that firm." Both directions reinforce the connection and make it harder for AI to miss or misattribute.