Your services page is where you list every treatment, package, and offering. This blueprint structures your service catalog into machine-readable data so AI systems can match your salon, spa, or studio to specific queries like "balayage near me" or "deep tissue massage downtown" instead of guessing from paragraph text.
The services page is where AI maps your actual offerings. When someone asks "who does keratin treatments in my area" or "find a nail salon that also does facials," 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 wraps each treatment in a structured Offer with a Service item so AI can index your offerings individually rather than treating the entire page as one blob of text.name, description, and optionally a price so AI can answer pricing and availability questions accurately.areaServed tells AI where your services are available, which is essential for location-based recommendations.priceRange on the business node or individual price fields on each offer help AI filter you into the right tier when users ask for affordable or premium 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
nameurlpriceRangeCopy 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 Health and Beauty 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 7. Price range 8. Primary city 9. Primary state 10. Services page description 11. Services page title 12. Service description 13. 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 Health and Beauty 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 the template below and replace every YOUR_* value with your own data. Add or remove services from the hasOfferCatalog array to match your actual menu of treatments.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "HealthAndBeautyBusiness",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_BUSINESS_NAME",
"url": "https://YOUR_DOMAIN.com",
"priceRange": "YOUR_PRICE_RANGE",
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "YOUR_CATALOG_NAME",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_1",
"description": "YOUR_SERVICE_DESCRIPTION_1"
},
"price": "YOUR_PRICE_1",
"priceCurrency": "USD"
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_2",
"description": "YOUR_SERVICE_DESCRIPTION_2"
},
"price": "YOUR_PRICE_2",
"priceCurrency": "USD"
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_NAME_3",
"description": "YOUR_SERVICE_DESCRIPTION_3"
},
"price": "YOUR_PRICE_3",
"priceCurrency": "USD"
}
]
}
},
{
"@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 treatment or service you offer. There is no upper limit, but each entry should be a genuinely separate offering — not minor variations of the same thing. If you offer haircuts, coloring, and extensions, list all three. AI uses this catalog to match you to specific queries, so completeness matters.
Yes. Use a starting price or a price range. AI systems frequently answer pricing questions, and having any structured price data puts you ahead of competitors who leave pricing as unstructured paragraph text. You can use priceRange on the business node for a general range or individual price values per service.
Yes. You can nest multiple OfferCatalog nodes inside hasOfferCatalog, each with its own name (such as "Hair Services" or "Skin Treatments"). This gives AI a structured way to understand your service categories rather than treating everything as a flat list.