The homepage is the identity anchor for a staffing or recruitment agency. It tells AI systems who the agency is, what industries it staffs, where it operates, and how to navigate the rest of the site. This blueprint provides the complete JSON-LD graph your homepage needs so AI can classify, cite, and recommend your agency with confidence.
The homepage is the single most important page for AI discoverability. It is where AI systems look first to understand who your agency is and whether it is worth citing. Every other page on the site inherits credibility from what the homepage declares. Without structured data here, AI may index deeper pages but still lack the identity anchor needed to recommend your agency.
EmploymentAgency node declares your agency's name, logo, address, contact information, founding date, and social profiles. This is the canonical record AI uses to identify your staffing business across the web.WebSite node anchors your entire site graph. It gives AI a root-level reference that every other page can point back to with isPartOf.SearchAction inside potentialAction tells search engines and AI systems that your site has internal search, which can trigger a sitelinks search box in results.WebPage node with an about reference to the EmploymentAgency connects the homepage to the entity it represents, closing the loop between the page and the business.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
nameurltelephoneemailaddressgeoareaServedsameAslogocontactPoint@idCopy 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 Homepage 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 description 2. Agency name 3. City 4. Company 5. Domain 6. Email 7. Employee count 8. Faq answer 9. Faq question 10. Founding year 11. Handle 12. Homepage title 13. Latitude 14. Logo 15. Longitude 16. Maps cid 17. Phone number 18. Primary city 19. Primary state 20. Site name 21. State 22. Street address 23. 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 Homepage" - 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 belongs in a <script type="application/ld+json"> tag in the <head> of your homepage.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "EmploymentAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png",
"email": "YOUR_EMAIL",
"telephone": "YOUR_PHONE_NUMBER",
"description": "YOUR_AGENCY_DESCRIPTION",
"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"
},
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"sameAs": [
"https://www.linkedin.com/company/YOUR_COMPANY",
"https://twitter.com/YOUR_HANDLE",
"https://www.google.com/maps?cid=YOUR_MAPS_CID"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support"
},
"foundingDate": "YOUR_FOUNDING_YEAR",
"numberOfEmployees": {
"@type": "QuantitativeValue",
"value": "YOUR_EMPLOYEE_COUNT"
}
},
{
"@type": "WebSite",
"@id": "https://YOUR_DOMAIN.com/#website",
"name": "YOUR_SITE_NAME",
"url": "https://YOUR_DOMAIN.com",
"potentialAction": {
"@type": "SearchAction",
"target": "https://YOUR_DOMAIN.com/?s={search_term_string}",
"query-input": "required name=search_term_string"
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/#webpage",
"url": "https://YOUR_DOMAIN.com/",
"name": "YOUR_HOMEPAGE_TITLE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
},
{
"@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"
}
}
]
}
]
}
EmploymentAgency is a more specific Schema.org type that tells AI your business places people in jobs. Using the generic Organization type forces AI to guess what kind of company you are. The more specific type means AI can immediately classify you as a staffing or recruitment firm and surface you for relevant queries.
No. The SearchAction inside potentialAction is only useful if your site has a working internal search. If it does not, remove the entire potentialAction block. Including a broken search URL can hurt rather than help.
Yes. The homepage sits at the top of the site hierarchy, so its breadcrumb only contains a single item: "Home" at position 1. Deeper pages will reference longer breadcrumb chains, but the homepage itself is the root.