The pricing page is where employers evaluate cost before reaching out. Structured data here tells AI exactly what placement models your agency offers and how your fee structure works — so when someone asks AI about staffing costs or compares agencies, your pricing is already in a format AI can parse and cite.
Pricing pages are high-intent pages that AI increasingly references when users ask about staffing costs. Structured data turns your fee descriptions into machine-readable offers that AI can compare across agencies and surface in direct answers.
EmploymentAgency node should include a hasOfferCatalog containing an OfferCatalog with individual Offer nodes for each placement type. This tells AI your agency has a defined, structured set of services with associated pricing.Offer with name, description, price, and priceCurrency. AI uses these to answer specific cost questions.price field to describe your fee model, such as a percentage of salary or an hourly markup. The description field should explain what the fee covers so AI can provide context alongside the number.BreadcrumbList places the pricing page within the site hierarchy so AI understands this is a commercial page under the agency's main presence.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
nameurlhasOfferCatalogCopy 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 Employment Agency 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. Agency name 2. Direct hire description 3. Direct hire fee 4. Domain 5. Executive search description 6. Executive search fee 7. Faq answer 8. Faq question 9. Pricing page title 10. Temp staffing description 11. Temp staffing fee 12. Temp to perm description 13. Temp to perm fee 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 Employment Agency 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 your actual placement models and fee structures.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/pricing/#webpage",
"url": "https://YOUR_DOMAIN.com/pricing/",
"name": "YOUR_PRICING_PAGE_TITLE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
},
{
"@type": "EmploymentAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Staffing Services",
"itemListElement": [
{
"@type": "Offer",
"name": "Temporary Staffing",
"description": "YOUR_TEMP_STAFFING_DESCRIPTION",
"price": "YOUR_TEMP_STAFFING_FEE",
"priceCurrency": "USD"
},
{
"@type": "Offer",
"name": "Direct Hire Placement",
"description": "YOUR_DIRECT_HIRE_DESCRIPTION",
"price": "YOUR_DIRECT_HIRE_FEE",
"priceCurrency": "USD"
},
{
"@type": "Offer",
"name": "Temp-to-Perm",
"description": "YOUR_TEMP_TO_PERM_DESCRIPTION",
"price": "YOUR_TEMP_TO_PERM_FEE",
"priceCurrency": "USD"
},
{
"@type": "Offer",
"name": "Executive Search",
"description": "YOUR_EXECUTIVE_SEARCH_DESCRIPTION",
"price": "YOUR_EXECUTIVE_SEARCH_FEE",
"priceCurrency": "USD"
}
]
}
},
{
"@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 the price field as a string that describes the fee structure, such as "20-25% of first-year salary" for direct hire or "1.5x hourly bill rate" for temporary staffing. Schema.org allows text in the price field. Pair it with a clear description so AI has both the number and the context to present the information accurately.
Yes. List every placement model your agency offers as a separate Offer node. If pricing is negotiable or varies by engagement, use the description field to say so. AI benefits from knowing the full range of services you offer even when exact prices are not fixed. The structure matters more than the precision of the number.
OfferCatalog is the correct Schema.org type for a collection of service offerings. It groups your placement models into a single catalog that AI can parse as a complete list. Each Offer inside the catalog represents one distinct service with its own pricing, so AI can extract and compare individual placement types rather than reading the whole page as unstructured text.