applicantLocationRequirements

applicantLocationRequirements · Recommended

Appears in

JobPosting

What is it?

The geographic area where applicants must be located to qualify for a remote position. This field specifies countries, states, or cities from which candidates can work. It is used exclusively with remote jobs and must be paired with jobLocationType: "TELECOMMUTE".

Why this matters for AEO

When someone asks "What remote jobs are available for people in Texas?" an AI engine uses applicantLocationRequirements to filter listings by eligible locations. Without this field, AI assistants cannot determine whether a remote candidate qualifies based on where they live. A job marked TELECOMMUTE without location requirements appears open to everyone, which may misrepresent the actual hiring policy.

What the specs say

Schema.org:AdministrativeArea. The location(s) applicants can apply from. This is usually used for telecommuting jobs where the applicant does not need to be in a physical office. Note: This should not be used for citizenship or work visa requirements. schema.org/applicantLocationRequirements

Google: Recommended. "The geographic location(s) in which employees may be located for to be eligible for the Work from home job." Google Search Central

How to find your value

• Legal/Compliance — States or countries where the company has nexus for payroll
• HR policy — The "eligible locations" section of the remote work policy
• Job requisition — Location restrictions listed in the hiring req
• Tax team — Jurisdictions where the company can legally employ workers

This field describes where the applicant can be physically located. Do not use it for citizenship requirements or work authorization status. Those are legal qualifications, not geographic eligibility.

Format and code

Type: AdministrativeArea (Country, State, or City)

Single country:

{
  "applicantLocationRequirements": {
    "@type": "Country",
    "name": "USA"
  },
  "jobLocationType": "TELECOMMUTE"
}

Multiple states:

{
  "applicantLocationRequirements": [
    {
      "@type": "AdministrativeArea",
      "name": "Michigan, USA"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Texas, USA"
    }
  ],
  "jobLocationType": "TELECOMMUTE"
}

Multiple countries:

{
  "applicantLocationRequirements": [
    {
      "@type": "Country",
      "name": "USA"
    },
    {
      "@type": "Country",
      "name": "Canada"
    },
    {
      "@type": "Country",
      "name": "United Kingdom"
    }
  ],
  "jobLocationType": "TELECOMMUTE"
}

Valid subtypes of AdministrativeArea: Country, State, City. Use whichever matches the granularity of your location restriction.

Required pairing: This field must always appear alongside jobLocationType: "TELECOMMUTE". Omitting applicantLocationRequirements when jobLocationType is TELECOMMUTE triggers a Google Search Console error. Google guidelines require at least one Country when specifying applicant locations.

Webflow implementation

Static pages

Add the location requirements in your JSON-LD in Page Settings > Custom Code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Remote Data Analyst",
  "jobLocationType": "TELECOMMUTE",
  "applicantLocationRequirements": {
    "@type": "Country",
    "name": "USA"
  }
}
</script>

CMS template pages

For a single country requirement, use a plain text CMS field:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "jobLocationType": "TELECOMMUTE",
  "applicantLocationRequirements": {
    "@type": "Country",
    "name": "{{wf {&quot;path&quot;:&quot;eligible-country&quot;,&quot;type&quot;:&quot;PlainText&quot;} }}"
  }
}
</script>

For multiple locations, a single CMS field cannot produce an array. Either hardcode the array for all remote jobs or use Schema HQ to handle the dynamic mapping.

In Schema HQ

Schema pulls CMS location fields and builds the correct AdministrativeArea objects. It handles arrays of multiple countries or states, validates the pairing with jobLocationType, and ensures the output structure matches Google's expected format.

Real examples

Google documentation (Google Search Central):

{
  "applicantLocationRequirements": {
    "@type": "Country",
    "name": "USA"
  },
  "jobLocationType": "TELECOMMUTE"
}

Alexander Chukovski (alexanderchukovski.com):

{
  "applicantLocationRequirements": [
    {
      "@type": "AdministrativeArea",
      "name": "Michigan, USA"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Texas, USA"
    }
  ],
  "jobLocationType": "TELECOMMUTE"
}

Related fields

• jobLocationType: must be set to TELECOMMUTE when using this field
• jobLocation: physical office location for non remote positions
• hiringOrganization: the company setting these location requirements
• title: the remote position these requirements apply to

FAQ

Is applicantLocationRequirements required for remote jobs?

Google generates a Search Console warning when jobLocationType is TELECOMMUTE but applicantLocationRequirements is missing. While technically listed as "Recommended," omitting it for remote jobs creates validation issues. Include at minimum a Country entry.

Can this field be used for visa or citizenship requirements?

No. Schema.org explicitly states: "This should not be used for citizenship or work visa requirements." This field describes physical residency eligibility only. Visa and work authorization belong in the job description text, not in structured data.

How specific can the location requirement be?

You can use Country, State, or City types. For a role requiring applicants in the Portland metro area, use "@type": "City", "name": "Portland, OR, USA". Most remote positions use Country or State level restrictions since city level limits are uncommon for remote work.