jobLocationType

jobLocationType · Recommended

Appears in

JobPosting

What is it?

A flag that marks a job as fully remote. The only accepted value is "TELECOMMUTE". When present, this tells search engines and AI assistants that the position does not require the employee to report to a physical office. It replaces or supplements jobLocation for remote roles.

Why this matters for AEO

Remote work is one of the most common filters in job searches. When someone asks "Show me remote software engineering jobs" or "What companies are hiring remotely?" AI engines look for jobLocationType: "TELECOMMUTE" to identify qualifying listings. Without this field, a remote position will not surface in remote filtered queries regardless of what the job description says about working from home.

What the specs say

Schema.org:Text. A description of the job location (e.g. TELECOMMUTE for telecommute jobs). schema.org/jobLocationType

Google: Recommended. "Set this property with the value TELECOMMUTE for jobs in which the employee may or must work remotely 100% of the time." Google Search Central

How to find your value

• 100% remote, no office required — "TELECOMMUTE"
• Hybrid (some remote, some office) — "TELECOMMUTE" plus jobLocation with the office address
• Fully on site — Omit jobLocationType entirely; use jobLocation only

Google's documentation specifies TELECOMMUTE for positions where the employee "may or must" work remotely 100% of the time. For hybrid roles, include both the physical location and the TELECOMMUTE flag.

Format and code

Type: Text (single value: "TELECOMMUTE")

Fully remote position:

{
  "@type": "JobPosting",
  "title": "Remote Product Manager",
  "jobLocationType": "TELECOMMUTE",
  "applicantLocationRequirements": {
    "@type": "Country",
    "name": "USA"
  }
}

Hybrid position (remote with physical office):

{
  "@type": "JobPosting",
  "title": "Software Engineer",
  "jobLocationType": "TELECOMMUTE",
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "555 Clancy St",
      "addressLocality": "Detroit",
      "addressRegion": "MI",
      "postalCode": "48201",
      "addressCountry": "US"
    }
  },
  "applicantLocationRequirements": [
    {
      "@type": "AdministrativeArea",
      "name": "Michigan, USA"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Texas, USA"
    }
  ]
}

Required pairing: When jobLocationType is set to TELECOMMUTE, Google expects applicantLocationRequirements to specify where remote applicants can be based. Omitting it triggers a Search Console warning.

Invalid patterns:

"jobLocationType": "REMOTE"

"jobLocationType": "Work from Home"

"jobLocationType": "Hybrid"

Only "TELECOMMUTE" is accepted. There is no separate value for hybrid roles.

Webflow implementation

Static pages

Add the TELECOMMUTE value in your JSON-LD:

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

CMS template pages

Use a Webflow switch field to control whether the TELECOMMUTE value appears. In your embed, conditionally include the field:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "jobLocationType": "TELECOMMUTE"
}
</script>

Since Webflow embeds cannot conditionally include or exclude JSON properties, you may need two template versions (one for remote jobs, one for on site) or use Schema HQ to handle the conditional logic.

In Schema HQ

The value is read from CMS "Remote" switch field and adds jobLocationType: "TELECOMMUTE" only when the job is marked remote. It also pairs the field with the appropriate applicantLocationRequirements automatically, preventing Search Console warnings.

Real examples

Google documentation (Google Search Central):

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

Alexander Chukovski (alexanderchukovski.com):

{
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "555 Clancy St",
      "addressLocality": "Detroit",
      "addressRegion": "MI",
      "postalCode": "48201",
      "addressCountry": "US"
    }
  },
  "applicantLocationRequirements": [
    {
      "@type": "AdministrativeArea",
      "name": "Michigan, USA"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Texas, USA"
    }
  ],
  "jobLocationType": "TELECOMMUTE"
}

Related fields

• applicantLocationRequirements: must be paired with TELECOMMUTE to specify eligible locations
• jobLocation: physical address for hybrid or on site positions
• employmentType: full time, part time, contract status of the remote role
• title: the remote position name

FAQ

Can jobLocationType have any value other than TELECOMMUTE?

No. Google's documentation only defines "TELECOMMUTE" as a valid value. There is no "HYBRID," "REMOTE," or "ON_SITE" option. For on site positions, omit jobLocationType entirely and rely on jobLocation alone.

How do you mark a hybrid job that is partially remote?

Include both jobLocationType: "TELECOMMUTE" and a jobLocation with the physical office address. Google interprets the combination of both properties as a hybrid arrangement. Add applicantLocationRequirements to specify where remote applicants can be based.

Is jobLocationType required for remote positions?

Google lists it as Recommended, not Required. However, omitting it for a remote position means the listing will not appear when candidates filter for remote jobs in Google's job search. For practical purposes, it is essential for any position advertised as remote.