Organizations › Services › EmploymentAgency

Team Page Blueprint — Employment Agency

The team page introduces the people behind a staffing agency. Structured data here tells AI who your recruiters and account managers are, what industries they specialize in, and what qualifications they hold — turning a list of headshots into a machine-readable roster of verifiable expertise.

View Prompt View JSON

What this page needs

AI systems evaluate the people behind an organization as part of their trust assessment. A team page with structured data lets AI match individual expertise to specific queries, such as recommending an agency whose recruiters specialize in a particular industry.

EmploymentAgency with employee array. The EmploymentAgency node should include an employee array containing each team member as a Person node. This connects every individual to the organization in a way AI can traverse.
Person nodes with jobTitle and specializations. Each Person should have a jobTitle like "Senior Recruiter" or "Account Manager" and a knowsAbout array listing their industry specializations such as "Healthcare Staffing" or "IT Recruitment."
sameAs for professional profiles. Include sameAs links to each team member's LinkedIn profile or other professional pages. AI uses these to cross-reference and verify the person's identity and credentials across the web.
BreadcrumbList for navigation. The BreadcrumbList places the team page within the site hierarchy so AI understands this is a supporting page under the agency's main presence.

Why these fields matter to AI

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

EmploymentAgency

name: Non-negotiable. AI cannot cite or recommend an unnamed entity.
url: AI needs a stable URL to attribute recommendations and route users correctly.

Person

name: Named humans increase citation confidence in high-liability niches. A faceless organization is harder for AI to recommend for law, medicine, or finance.
jobTitle: AI uses job title to classify expertise level and match the provider to credential-specific queries.
sameAs: AI cross-references the person against external sources to confirm they exist. LinkedIn is the strongest signal for professional services.

Use This Prompt to Implement Your Schema

Copy 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 Team 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. Member
6. Specialization
7. Team member
8. Team page title

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 Team"
- 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

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. Add or remove Person nodes in the employee array to match your actual team size.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/team/#webpage",
      "url": "https://YOUR_DOMAIN.com/team/",
      "name": "YOUR_TEAM_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",
      "employee": [
        {
          "@type": "Person",
          "name": "YOUR_TEAM_MEMBER_1_NAME",
          "jobTitle": "Senior Recruiter",
          "image": "https://YOUR_DOMAIN.com/YOUR_MEMBER_1_PHOTO.jpg",
          "sameAs": [
            "https://www.linkedin.com/in/YOUR_MEMBER_1_LINKEDIN"
          ],
          "knowsAbout": [
            "YOUR_SPECIALIZATION_1A",
            "YOUR_SPECIALIZATION_1B"
          ]
        },
        {
          "@type": "Person",
          "name": "YOUR_TEAM_MEMBER_2_NAME",
          "jobTitle": "Account Manager",
          "image": "https://YOUR_DOMAIN.com/YOUR_MEMBER_2_PHOTO.jpg",
          "sameAs": [
            "https://www.linkedin.com/in/YOUR_MEMBER_2_LINKEDIN"
          ],
          "knowsAbout": [
            "YOUR_SPECIALIZATION_2A",
            "YOUR_SPECIALIZATION_2B"
          ]
        },
        {
          "@type": "Person",
          "name": "YOUR_TEAM_MEMBER_3_NAME",
          "jobTitle": "Staffing Coordinator",
          "image": "https://YOUR_DOMAIN.com/YOUR_MEMBER_3_PHOTO.jpg",
          "sameAs": [
            "https://www.linkedin.com/in/YOUR_MEMBER_3_LINKEDIN"
          ],
          "knowsAbout": [
            "YOUR_SPECIALIZATION_3A",
            "YOUR_SPECIALIZATION_3B"
          ]
        },
        {
          "@type": "Person",
          "name": "YOUR_TEAM_MEMBER_4_NAME",
          "jobTitle": "Business Development Manager",
          "image": "https://YOUR_DOMAIN.com/YOUR_MEMBER_4_PHOTO.jpg",
          "sameAs": [
            "https://www.linkedin.com/in/YOUR_MEMBER_4_LINKEDIN"
          ],
          "knowsAbout": [
            "YOUR_SPECIALIZATION_4A",
            "YOUR_SPECIALIZATION_4B"
          ]
        }
      ]
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/team/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Team",
          "item": "https://YOUR_DOMAIN.com/team/"
        }
      ]
    },
    {
      "@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"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Should every team member have their own Person node?

Ideally, yes. Each recruiter, account manager, or coordinator who appears on the page should have a Person node inside the employee array. AI uses these individual nodes to match expertise to specific queries. If someone asks AI for a staffing agency with healthcare recruiters, your structured data is what makes that match possible.

What should I put in the knowsAbout field?

Use knowsAbout to list each team member's industry specializations and areas of expertise. Examples include "Healthcare Staffing," "IT Recruitment," "Light Industrial," "Accounting and Finance," or "Executive Search." These are the terms AI uses to determine whether your team has relevant expertise for a given query.

Is it better to list team members on the about page or a separate team page?

Either approach works for AI, but a dedicated team page lets you give each person more structured detail without cluttering the about page. If your agency has more than three or four team members, a separate team page with its own WebPage node and full employee array gives AI a cleaner, more focused data source to parse.