Your contact page is where AI looks to confirm that an agency is reachable. This blueprint makes your phone number, email, mailing address, and office hours machine-readable so AI systems can surface you as a trustworthy, contactable staffing provider for both job seekers and employers.
Reachability is a trust signal. When AI evaluates whether to recommend your agency, it checks whether a real human can actually get in touch. A contact page without structured data forces AI to guess from raw HTML — and guessing means you get skipped in favor of a competitor who made that information explicit.
ContactPage as the page type tells AI this is the canonical location for reaching your agency, not just a page that happens to mention a phone number.telephone and email tells AI exactly how someone — whether a candidate or an employer — can reach your team and what kind of support you offer.PostalAddress node so AI can confirm your physical office location without parsing free-text.Without these fields, AI may know your agency exists but still cannot confirm that someone can walk in, call, or email — so it recommends a competitor who made that information explicit.
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
nameurltelephoneemailaddressgeoopeningHoursSpecificationcontactPointCopy 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 Contact 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. City 3. Close time 4. Domain 5. Email 6. Faq answer 7. Faq question 8. Language 9. Latitude 10. Longitude 11. Open time 12. Phone number 13. State 14. Street address 15. Zip 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 Contact" - 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. This block goes in the <head> of your contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/",
"name": "Contact — YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com/contact/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb"
}
},
{
"@type": "EmploymentAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_OPEN_TIME",
"closes": "YOUR_CLOSE_TIME"
}
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support",
"availableLanguage": "YOUR_LANGUAGE"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@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"
}
}
]
}
]
}
Yes. AI crawlers do not always combine data across pages. The contact page should carry its own ContactPage and EmploymentAgency nodes so the reachability signals are self-contained on the page where a user — or an AI — expects to find them.
If you have different phone numbers or email addresses for job seekers and employer clients, include multiple ContactPoint nodes with different contactType values. Use "customer support" for candidates and "sales" for employer inquiries. This helps AI route the right audience to the right channel.
Include a separate PostalAddress for each office, or create multiple EmploymentAgency nodes with distinct @id values for each branch. If you have a single contact page for all locations, list each address. If each branch has its own contact page, put the relevant address on each page.