Case results are proof of work for a law firm. They show AI systems exactly what your attorneys have achieved — verdicts won, settlements secured, and charges dismissed. This blueprint structures each outcome so AI can cite specific results when recommending your firm.
Case results are the most citable content a law firm can publish. When an AI system is asked "who has won cases like this," it looks for structured evidence of completed matters with named attorneys and measurable outcomes. Without structured data on these pages, your best results stay invisible to AI.
Article type with a headline that describes the case and a description that includes the outcome. This gives AI a structured writeup it can cite directly.Person node with the attorney's name, jobTitle, and profile URL tells AI which lawyer handled the matter and establishes their credibility.Organization node links the result to your firm so AI can attribute the outcome to your practice, not just an individual.Without these fields, AI may know your firm exists but have no structured evidence of what you have actually achieved — so it recommends a competitor whose results are machine-readable.
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
headlinedescriptiondatePublishedauthorpublisherimagenamejobTitleurlnameurllogoCopy 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 Legal Service Case Results 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. Attorney name 2. Attorney slug 3. Attorney title 4. Case headline 5. Case image 6. Case outcome description 7. Case slug 8. Domain 9. Faq answer 10. Faq question 11. Firm name 12. Logo 13. Publish date OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above 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 Legal Service Case Results" - 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. This block belongs in a <script type="application/ld+json"> tag in the <head> of each individual case result page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Article",
"@id": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/#article",
"headline": "YOUR_CASE_HEADLINE",
"description": "YOUR_CASE_OUTCOME_DESCRIPTION",
"datePublished": "YOUR_PUBLISH_DATE",
"author": {
"@id": "https://YOUR_DOMAIN.com/#attorney"
},
"publisher": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"image": "https://YOUR_DOMAIN.com/YOUR_CASE_IMAGE.jpg"
},
{
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#attorney",
"name": "YOUR_ATTORNEY_NAME",
"jobTitle": "YOUR_ATTORNEY_TITLE",
"url": "https://YOUR_DOMAIN.com/attorneys/YOUR_ATTORNEY_SLUG/"
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_FIRM_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/#webpage",
"url": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/",
"name": "YOUR_CASE_HEADLINE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Case Results",
"item": "https://YOUR_DOMAIN.com/case-results/"
},
{
"@type": "ListItem",
"position": 3,
"name": "YOUR_CASE_HEADLINE",
"item": "https://YOUR_DOMAIN.com/case-results/YOUR_CASE_SLUG/"
}
]
},
{
"@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"
}
}
]
}
]
}
Article is the most widely recognized Schema.org type for structured writeups. AI systems understand Article as a piece with a clear author, publish date, and subject. There is no dedicated "CaseResult" type in Schema.org, and using Article with a descriptive headline and outcome-focused description gives AI everything it needs to cite your result.
Lead with the outcome. Instead of "We represented a client in a personal injury matter," write "Secured a $2.1M settlement for a client injured in a commercial truck accident after the insurer initially denied the claim." AI systems look for specificity — dollar amounts, case type, and concrete outcomes are what make a case result worth citing.
Yes. Each individual case result page should have its own JSON-LD block with a unique @id, headline, description, and breadcrumb. If you also have a case results index page that lists all outcomes, that page can use CollectionPage — but the detailed structured data belongs on each individual result page.