Your FAQ page answers the questions people ask most about plumbing services. This blueprint structures those question-and-answer pairs as the primary FAQPage type so AI can pull your answers directly into search results, voice assistants, and chatbot responses.
A dedicated FAQ page is one of the highest-impact pages for AI visibility. When someone asks "how much does a plumber charge for a drain cleaning" or "should I repair or replace my water heater," AI looks for structured FAQ data first. If your questions and answers are marked up correctly, AI can cite your answer word for word.
FAQPage with its own @id, name, and url. This tells AI the entire page is dedicated to questions and answers, not just a section of a larger page.mainEntity as a Question with an acceptedAnswer. AI reads these as authoritative responses you endorse — not user-generated content.about reference to your Plumber node ties the FAQ content back to your business identity, so AI knows which company these answers come from.BreadcrumbList places the FAQ page within your site hierarchy, helping AI understand that these questions relate specifically to your plumbing business.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 Plumber 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. Business name 2. Domain 3. Faq answer 4. Faq page title 5. Faq 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 Plumber 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 items in mainEntity to match your actual FAQ content. This block belongs in a <script type="application/ld+json"> tag in the <head> of your FAQ page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "FAQPage",
"@id": "https://YOUR_DOMAIN.com/faq/#faqpage",
"name": "YOUR_FAQ_PAGE_TITLE",
"url": "https://YOUR_DOMAIN.com/faq/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#business"
},
"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"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_4",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_4"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_5",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_5"
}
}
]
},
{
"@type": "Plumber",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_BUSINESS_NAME",
"url": "https://YOUR_DOMAIN.com"
},
{
"@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": "FAQs",
"item": "https://YOUR_DOMAIN.com/faq/"
}
]
}
]
}
Include at least five and as many as you can answer well. There is no upper limit in Schema.org, but every question should be something real customers actually ask. AI prioritizes pages with more structured FAQ data when deciding which source to cite, so a page with fifteen well-written Q&A pairs outperforms one with three generic ones.
When a page is dedicated entirely to questions and answers, using FAQPage as the primary type tells AI this is an authoritative FAQ source — not just a regular page that happens to have a few questions on it. AI systems treat FAQPage as a direct signal to pull answers into rich results and voice responses.
Your dedicated FAQ page should be the comprehensive collection. If you have FAQs on your homepage or services page, those should be a subset of what appears here. AI will not penalize you for having the same question on multiple pages, but the dedicated FAQ page carries more weight because its primary type signals that Q&A is the page's purpose.