Your services page is where you list every repair, maintenance, and detailing service you offer. This blueprint structures your offerings into a machine-readable catalog so AI systems can match your shop to the right queries — from "brake repair near me" to "full synthetic oil change in Minneapolis."
The services page is where AI maps your actual offerings. When someone asks "who does transmission repair near me" or "find a shop that does state inspections," this is the page that answers. Without structured service data, AI has to guess what you offer from paragraph text.
hasOfferCatalog field wraps each service in a structured Offer with a Service item so AI can index your repair and maintenance offerings individually.name and description — "Oil Change," "Brake Pad Replacement," "Engine Diagnostics" — specific and clear.areaServed tells AI where these automotive services are available, which is critical for location-based queries like "mechanic near downtown."priceRange or individual price fields help AI filter you into the right tier when users ask for affordable or certified repair options.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
nameurltelephonepriceRangeCopy 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 Automotive Business 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. Business name 2. Domain 3. Faq answer 4. Faq question 5. Phone number 6. Price range 7. Primary city 8. Primary state 9. Services page description 10. Services page title 11. Service description 12. 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 Automotive Business 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": "AutomotiveBusiness",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_BUSINESS_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"priceRange": "YOUR_PRICE_RANGE",
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Automotive 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": "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 service you offer. Oil changes, brake repair, tire rotation, diagnostics, transmission work — list them all. AI uses this catalog to match you to specific queries, so completeness matters more than brevity.
You can use a single hasOfferCatalog with all services listed, or nest multiple OfferCatalog entries if you want to group them by category. For most auto shops, a single flat list with clear service names is the simplest and most effective approach.
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.