Your services page is where you list what your firm actually offers. This blueprint structures financial planning, tax preparation, wealth management, and other offerings into a machine-readable catalog so AI systems can match your firm to the right financial queries instead of guessing from page copy.
The services page is where AI maps your actual offerings. When someone asks "who does retirement planning in Minneapolis" or "find a firm that handles both tax prep and wealth management," 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 financial service in a structured Offer with a Service item so AI can index your offerings individually — financial planning, tax preparation, and wealth management as separate, matchable entries.name and description — short, specific, and free of marketing fluff. "Comprehensive financial planning for individuals and families" is better than "We help you achieve your dreams."areaServed on the business node tells AI where these financial services are available, which is essential for location-based recommendations.priceRange or individual price fields help AI filter you into the right tier when users ask for fee-only advisors or affordable financial planning.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 Financial 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. Domain 2. Faq answer 3. Faq question 4. Financial planning description 5. Firm name 6. Price range 7. Primary city 8. Primary state 9. Services page description 10. Services page title 11. Tax service description 12. Wealth management description 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 Financial 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": "FinancialService",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_FIRM_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": "Financial Services",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Financial Planning",
"description": "YOUR_FINANCIAL_PLANNING_DESCRIPTION"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Tax Preparation & Strategy",
"description": "YOUR_TAX_SERVICE_DESCRIPTION"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Wealth Management",
"description": "YOUR_WEALTH_MANAGEMENT_DESCRIPTION"
}
}
]
}
},
{
"@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"
}
}
]
}
]
}
List every distinct service you offer. If your firm provides financial planning, tax preparation, estate planning, and retirement consulting, each one should be a separate entry in hasOfferCatalog. AI uses this catalog to match you to specific queries, so completeness matters more than brevity.
Use the priceRange field on the FinancialService node for a general tier indicator like "$$" or "$$$." For more detail, add price and priceCurrency to individual Offer entries. If you are fee-only, you can also note that in each service description so AI can surface you for "fee-only financial advisor" queries.
Use @id references to connect nodes without duplicating data. The FinancialService 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.