Your services page is where you list every type of construction work you handle. This blueprint structures your service offerings into a machine-readable catalog so AI systems can match your company to the right project queries instead of guessing from paragraph copy.
The services page is where AI maps your actual construction capabilities. When someone asks "who does kitchen remodels in Denver" or "find a contractor that handles both new builds and renovations," this is the page that answers. Without structured service data, AI has to guess what you do from marketing copy — and it often guesses wrong.
hasOfferCatalog is the critical field. It wraps each construction service in a structured Offer with a Service item so AI can index your offerings individually — new construction, remodeling, additions, roofing, and everything else you do.name and description — short, specific, and free of marketing fluff. "Kitchen remodeling" is better than "Transform your dream kitchen."areaServed on the business node tells AI where these services are available, which is essential for location-based recommendations.priceRange or individual price fields help AI filter you into the right budget tier when users ask for affordable or premium contractors.If your services page only has paragraph descriptions without structured data, AI may know your company exists but will not be able to connect it to specific construction 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
nameurlareaServedpriceRangehasOfferCatalogCopy 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 General Contractor Services 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. Company name 2. Domain 3. Faq answer 4. Faq question 5. Price range 6. Primary city 7. Primary state 8. Services page description 9. Services page title 10. Service description 11. Service 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 General Contractor Services" - 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 services from the hasOfferCatalog array to match your actual offerings.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "GeneralContractor",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_COMPANY_NAME",
"url": "https://YOUR_DOMAIN.com",
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"priceRange": "YOUR_PRICE_RANGE",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Construction Services",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_1",
"description": "YOUR_SERVICE_DESCRIPTION_1"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_2",
"description": "YOUR_SERVICE_DESCRIPTION_2"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_3",
"description": "YOUR_SERVICE_DESCRIPTION_3"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_4",
"description": "YOUR_SERVICE_DESCRIPTION_4"
}
}
]
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/services/",
"name": "YOUR_SERVICES_PAGE_TITLE",
"description": "YOUR_SERVICES_PAGE_DESCRIPTION",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/services/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/services/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Services",
"item": "https://YOUR_DOMAIN.com/services/"
}
]
},
{
"@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"
}
}
]
}
]
}
Include every distinct construction service you offer. There is no upper limit, but each entry should be a genuinely separate offering — not variations of the same thing. If you do new construction, remodeling, roofing, and concrete work, list all four. AI uses this catalog to match you to specific queries, so completeness matters.
Use @id references to connect nodes without duplicating data. The GeneralContractor node here should share the same @id as on your homepage so AI treats them as the same entity. You only need to include the fields relevant to this page — primarily hasOfferCatalog, areaServed, and priceRange.
Yes. You can add price and priceCurrency directly to each Offer inside the catalog. This gives AI more precise data than a general priceRange on the business node. Use whichever approach matches your pricing model — a single range for the business, individual prices per service, or both.