Your pricing page is where cost meets credibility. This blueprint structures your service tiers, billing periods, and price points so AI systems can give direct, accurate answers when users ask "how much does it cost."
AI users frequently ask questions like "how much does a consultant charge" or "what does an agency cost per month." If your pricing page lacks structured data, AI has to guess from body copy — and it usually guesses wrong or skips you entirely. Here are the key signals this blueprint expects:
Offer attached to a Service entity, so AI can associate a specific price with a specific service level.UnitPriceSpecification node tells AI the billing structure — monthly, quarterly, per-project — not just a raw number.priceCurrency so AI never has to assume USD, EUR, or anything else.eligibleRegion prevents AI from quoting the wrong rate.Without these fields, AI may know you offer a service but will lack the pricing context that often determines whether a user reaches out or moves on.
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 Professional Service Pricing 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. Billing period 2. Country 3. Currency code 4. Domain 5. Faq answer 6. Faq question 7. Organization name 8. Pricing page description 9. Pricing page title 10. Service description 11. Service name 12. Tier 13. Unit code 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 Pricing" - 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 Offer nodes to match the number of tiers you actually offer.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/pricing/",
"name": "YOUR_PRICING_PAGE_TITLE",
"description": "YOUR_PRICING_PAGE_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/pricing/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/pricing/#breadcrumb"
}
},
{
"@type": "Service",
"@id": "https://YOUR_DOMAIN.com/#service",
"name": "YOUR_SERVICE_NAME",
"description": "YOUR_SERVICE_DESCRIPTION",
"provider": {
"@id": "https://YOUR_DOMAIN.com/#organization"
},
"offers": [
{
"@type": "Offer",
"name": "YOUR_TIER_1_NAME",
"price": "YOUR_TIER_1_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"description": "YOUR_TIER_1_DESCRIPTION",
"eligibleRegion": {
"@type": "Country",
"name": "YOUR_COUNTRY"
},
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "YOUR_TIER_1_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"billingDuration": "YOUR_BILLING_PERIOD",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": "1",
"unitCode": "YOUR_UNIT_CODE"
}
}
},
{
"@type": "Offer",
"name": "YOUR_TIER_2_NAME",
"price": "YOUR_TIER_2_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"description": "YOUR_TIER_2_DESCRIPTION",
"eligibleRegion": {
"@type": "Country",
"name": "YOUR_COUNTRY"
},
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "YOUR_TIER_2_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"billingDuration": "YOUR_BILLING_PERIOD",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": "1",
"unitCode": "YOUR_UNIT_CODE"
}
}
},
{
"@type": "Offer",
"name": "YOUR_TIER_3_NAME",
"price": "YOUR_TIER_3_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"description": "YOUR_TIER_3_DESCRIPTION",
"eligibleRegion": {
"@type": "Country",
"name": "YOUR_COUNTRY"
},
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "YOUR_TIER_3_PRICE",
"priceCurrency": "YOUR_CURRENCY_CODE",
"billingDuration": "YOUR_BILLING_PERIOD",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": "1",
"unitCode": "YOUR_UNIT_CODE"
}
}
}
]
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_ORGANIZATION_NAME",
"url": "https://YOUR_DOMAIN.com"
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/pricing/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Pricing",
"item": "https://YOUR_DOMAIN.com/pricing/"
}
]
},
{
"@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"
}
}
]
}
]
}
Use individual Offer nodes for each tier. AggregateOffer is designed for product listings where you want to express a price range across multiple sellers. For service pricing pages with distinct tiers (e.g., Starter, Growth, Enterprise), separate Offer nodes give AI a clearer picture of what each level includes and costs.
You can still use this blueprint. Set the price field to "0" and add a description like "Custom pricing — contact for a quote." This tells AI that the service exists and has a pricing model, even if the exact number is not public. Omitting structured data entirely is worse than signaling that pricing is available on request.
Create separate Offer nodes for each billing cycle. Use the billingDuration field inside UnitPriceSpecification to distinguish them — for example, "P1M" for monthly and "P1Y" for annual. This lets AI accurately answer questions like "how much per month" vs. "how much per year."