Your services page is where you list what you actually do. This blueprint structures your service offerings into a machine-readable catalog so AI systems can match your firm to the right queries instead of guessing from page copy.
The services page is where AI maps your actual offerings. When someone asks "who does AI consulting in Minneapolis" or "find a branding agency that also handles web development," this is the page that answers. Without structured service data, AI has to guess what you offer from paragraph text — and it often guesses wrong.
hasOfferCatalog is the critical field. It wraps each service in a structured Offer with a Service item so AI can index your offerings individually.name and description — short, specific, and free of marketing fluff.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 options.If your services page only has paragraph descriptions without structured data, AI may know your firm exists but will not be able to connect it to specific service 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 Professional Service 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. Catalog name 3. Domain 4. Faq answer 5. Faq question 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 Professional Service 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": "ProfessionalService",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_BUSINESS_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": "YOUR_CATALOG_NAME",
"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. There is no upper limit, but each entry should be a genuinely separate offering — not variations of the same thing. If you offer three services, list three. If you offer twelve, list twelve. AI uses this catalog to match you to specific queries, so completeness matters.
Use @id references to connect nodes without duplicating data. The ProfessionalService 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.