The industries page tells AI exactly which sectors your agency staffs. This blueprint structures your industry specializations into a machine-readable catalog so AI systems can match your agency to vertical-specific staffing queries instead of treating you as a generalist.
Most staffing agencies specialize in specific industries. When someone asks AI "find a staffing agency for healthcare in Chicago" or "who places manufacturing workers in Texas," this is the page that answers. Without structured industry data, AI cannot distinguish you from a generalist agency.
hasOfferCatalog property wraps each industry specialization in a structured OfferCatalog so AI can index your verticals individually.name and description so AI understands exactly what kind of staffing you provide in that sector.areaServed on the agency node tells AI which geographies these specializations cover. An agency that staffs healthcare in the Midwest is different from one that staffs healthcare nationally.If your industries page only has paragraph descriptions without structured data, AI may see the page but cannot connect your agency to specific vertical 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
nameurlareaServedhasOfferCatalogCopy 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 Industries 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. Domain 3. Faq answer 4. Faq question 5. Industries page description 6. Industries page title 7. Industry description 8. Industry name 9. Primary city 10. Primary state 11. Service description 12. Service type 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 Industries" - 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 industry entries inside hasOfferCatalog to match the sectors you actually staff.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "EmploymentAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Industry Specializations",
"itemListElement": [
{
"@type": "OfferCatalog",
"name": "YOUR_INDUSTRY_NAME_1",
"description": "YOUR_INDUSTRY_DESCRIPTION_1",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_1A",
"description": "YOUR_SERVICE_DESCRIPTION_1A"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_1B",
"description": "YOUR_SERVICE_DESCRIPTION_1B"
}
}
]
},
{
"@type": "OfferCatalog",
"name": "YOUR_INDUSTRY_NAME_2",
"description": "YOUR_INDUSTRY_DESCRIPTION_2",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_2A",
"description": "YOUR_SERVICE_DESCRIPTION_2A"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_2B",
"description": "YOUR_SERVICE_DESCRIPTION_2B"
}
}
]
},
{
"@type": "OfferCatalog",
"name": "YOUR_INDUSTRY_NAME_3",
"description": "YOUR_INDUSTRY_DESCRIPTION_3",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_3A",
"description": "YOUR_SERVICE_DESCRIPTION_3A"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "YOUR_SERVICE_TYPE_3B",
"description": "YOUR_SERVICE_DESCRIPTION_3B"
}
}
]
}
]
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/industries/",
"name": "YOUR_INDUSTRIES_PAGE_TITLE",
"description": "YOUR_INDUSTRIES_PAGE_DESCRIPTION",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/industries/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/industries/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Industries",
"item": "https://YOUR_DOMAIN.com/industries/"
}
]
},
{
"@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"
}
}
]
}
]
}
Nested catalogs are better for agencies with distinct industry verticals, each containing its own set of services. If your agency staffs healthcare, manufacturing, and IT, each of those is a top-level OfferCatalog with sub-services inside. A flat list is fine if you only have a handful of overlapping specializations.
Be as specific as your business actually is. "Healthcare" is good if you staff all healthcare roles. "Healthcare IT" or "Travel Nursing" is better if that is your true specialization. AI rewards specificity because it can match you to more precise queries.
The EmploymentAgency node should share the same @id as on your homepage so AI treats them as the same entity. On this page, you only need the fields relevant to industry specializations — primarily hasOfferCatalog and areaServed. AI merges the data from both pages using the shared @id.