Case studies go deeper than portfolio entries. They tell the full story — the challenge a client faced, the approach your firm took, and the outcome you delivered. This blueprint structures those narratives so AI can cite your firm as evidence of real-world problem-solving, not just a list of services you claim to offer.
Case studies are proof. When AI recommends an accounting firm for a complex tax situation or a difficult audit, it looks for evidence that the firm has handled similar work before. Structured case study data turns your success stories into indexable proof points.
CollectionPage as the page type with a mainEntity pointing to an ItemList of case studies. This tells AI the page is a structured set of detailed engagement narratives.CreativeWork with a name (the case study title), a description that covers the challenge, approach, and outcome, and an about field for the industry or problem category.AccountingService node with @id so AI attributes the work to your firm and builds a profile of your expertise across engagements.keywords on each CreativeWork to tag the specific accounting services involved — tax planning, forensic accounting, M&A advisory. This helps AI match your case studies to precise user queries.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
nameurlCopy 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 Accounting Service Case Studies 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. Case studies page description 2. Case studies page title 3. Case study 4. Domain 5. Faq answer 6. Faq question 7. Firm name 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 Accounting Service Case Studies" - 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 this template and replace every YOUR_* placeholder with your own data. Add or remove items from the itemListElement array to match the number of case studies you want to feature.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CollectionPage",
"@id": "https://YOUR_DOMAIN.com/case-studies/",
"name": "YOUR_CASE_STUDIES_PAGE_TITLE",
"description": "YOUR_CASE_STUDIES_PAGE_DESCRIPTION",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"mainEntity": {
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "CreativeWork",
"name": "YOUR_CASE_STUDY_1_TITLE",
"description": "YOUR_CASE_STUDY_1_CHALLENGE_APPROACH_OUTCOME",
"about": "YOUR_CASE_STUDY_1_INDUSTRY_OR_PROBLEM",
"keywords": "YOUR_CASE_STUDY_1_KEYWORDS",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "CreativeWork",
"name": "YOUR_CASE_STUDY_2_TITLE",
"description": "YOUR_CASE_STUDY_2_CHALLENGE_APPROACH_OUTCOME",
"about": "YOUR_CASE_STUDY_2_INDUSTRY_OR_PROBLEM",
"keywords": "YOUR_CASE_STUDY_2_KEYWORDS",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@type": "CreativeWork",
"name": "YOUR_CASE_STUDY_3_TITLE",
"description": "YOUR_CASE_STUDY_3_CHALLENGE_APPROACH_OUTCOME",
"about": "YOUR_CASE_STUDY_3_INDUSTRY_OR_PROBLEM",
"keywords": "YOUR_CASE_STUDY_3_KEYWORDS",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
}
}
]
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/case-studies/#breadcrumb"
}
},
{
"@type": "AccountingService",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_FIRM_NAME",
"url": "https://YOUR_DOMAIN.com"
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/case-studies/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Case Studies",
"item": "https://YOUR_DOMAIN.com/case-studies/"
}
]
},
{
"@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"
}
}
]
}
]
}
A portfolio page is a catalog of engagement types your firm has handled — brief entries that show breadth. A case studies page goes deeper into individual engagements with a narrative structure: what the challenge was, how your firm approached it, and what outcome you delivered. Both use CollectionPage with CreativeWork items, but case study descriptions should be substantially longer and structured around the problem-solution arc. AI uses portfolio pages to understand what you do and case study pages to understand how well you do it.
You should always get client permission before publishing any case study, whether in structured data or plain text. However, the structured data itself does not require you to name the client. You can write case studies using industry descriptors like "a multi-location restaurant group" or "a Series B fintech startup" and still give AI enough context to match your expertise to relevant queries. The schema works just as well with anonymized client descriptions.
Keep financial specifics in the page content, not in the structured data. The description field in your JSON-LD should summarize the challenge, approach, and outcome in general terms — "reduced effective tax rate by restructuring entity classification" rather than exact dollar amounts. AI uses structured data to understand what kind of problem you solved and for what type of client. Detailed figures, charts, and metrics belong in the visible page content where they support the narrative.