FAQ pages are where AI looks for direct answers. When a prospective patient asks an AI about your clinic's insurance policy, walk-in availability, or wait times, structured FAQ data lets AI pull your answer verbatim — with attribution back to your clinic.
FAQ pages are one of the highest-value pages for AI citation. When someone asks an AI "does this clinic accept walk-ins" or "what insurance does the clinic take," AI looks for structured question-and-answer pairs it can use directly. Without structured data, AI has to parse your HTML and guess which text is a question and which is an answer.
FAQPage tells AI the entire page is a collection of questions and answers, not a generic web page that happens to contain some Q&A text.Question type with a name (the question text) and an acceptedAnswer of type Answer. This explicit pairing removes all ambiguity about which answer belongs to which question.Answer should contain a complete response in the text field. AI systems prefer answers that stand on their own without needing surrounding context from the page.Without these fields, AI may read your FAQ page but have no structured way to match questions to answers — so it pulls from a competitor whose FAQ data is 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
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 Medical Clinic FAQ 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. Answer 2. Clinic name 3. Domain 4. Question 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 Medical Clinic FAQ" - 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 Question objects in the mainEntity array to match the number of questions on your page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "FAQPage",
"@id": "https://YOUR_DOMAIN.com/faq/#faqpage",
"name": "Frequently Asked Questions — YOUR_CLINIC_NAME",
"url": "https://YOUR_DOMAIN.com/faq/",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_ANSWER_3"
}
}
]
},
{
"@type": "MedicalClinic",
"@id": "https://YOUR_DOMAIN.com/#clinic",
"name": "YOUR_CLINIC_NAME",
"url": "https://YOUR_DOMAIN.com"
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/faq/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#clinic"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/faq/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/faq/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "FAQ",
"item": "https://YOUR_DOMAIN.com/faq/"
}
]
}
]
}
Include every question that appears on the visible page. The structured data should mirror what a user sees. If your page shows 15 questions about insurance, walk-ins, and wait times, include all 15 in the mainEntity array. Do not add questions to the schema that are not visible on the page — AI systems and search engines may treat that as a mismatch.
If your clinic has enough insurance questions to fill a dedicated page, create one with its own FAQPage schema. Otherwise, include insurance questions here. The key is that every FAQ visible on the page must be in the schema. AI will pull from whichever page has the structured answer to the specific question asked.
Use plain text in the text field. While Schema.org technically allows HTML in answer text, AI systems parse plain text more reliably. If your answer needs a link, include the full URL as text rather than an anchor tag. Keep each answer self-contained and concise — AI prefers answers that can be quoted directly without cleanup.