How do I mark a remote job in JobPosting structured data?

Definition: Remote job markup uses JobPosting, the structured data type for a job listing, with jobLocationType set to "TELECOMMUTE" and applicantLocationRequirements describing eligible work locations. As of October 2026, Google requires a fully remote working option for this value.

Key facts

• Google's remote job requirements require the description to state that the job is fully remote and require at least one eligible country.
• Schema.org's applicantLocationRequirements definition covers locations applicants can apply from and excludes citizenship and work visa requirements.
• Schema.org's jobLocationType definition accepts a text value and gives TELECOMMUTE as its example for telecommuting jobs.
• Google's Rich Results Test help lists job postings among the supported types and allows testing a URL or pasted code.

What markup describes a remote role with location restrictions?

Google's work from home examples include this combination for a role performed remotely within the United States. The following object shows the location fields to merge into a complete JobPosting object:

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

The same documentation includes an array of State objects named "Michigan, USA" and "Texas, USA" for narrower eligibility. The visible description must state the permitted locations.

Schema.org's property example also represents the United States as a Country object. Its expected value type is AdministrativeArea, meaning an administrative geographic area. The property belongs on JobPosting. Citizenship and visa conditions belong outside this location field.

When does a remote job need a physical address?

Google's jobLocation guidance allows omission of the physical workplace when applicantLocationRequirements is present for a remote role. A supplied jobLocation needs addressCountry.

The same documentation permits a fully remote option alongside an optional physical workplace. If applicant locations are omitted in that arrangement, Google uses the workplace country for remote eligibility. Occasional home working and a negotiable remote benefit do not qualify for TELECOMMUTE.

How should the markup be checked?

Google's Rich Results Test instructions describe a Code input for pasted markup and a URL input for a page address. The test supports JSON-LD, a structured data format encoded as JSON. Testing the complete job object allows the tool to report issues beyond the location fragment shown above.

Expand detected items to inspect errors and warnings. Clicking an issue opens the corresponding location in the rendered code explorer. For URL tests, the page and its resources must be accessible without login; password protection and firewalls prevent access. The help page also advises removing comments from JSON-LD before publication.

Related terms

• Structured data
• JSON-LD
• How do I test a URL or code snippet with Google's Rich Results Test?
• How do I remove an expired job from Google's job results?

FAQ

Can I use applicantLocationRequirements for work visa eligibility?

No. Schema.org's definition explicitly excludes citizenship and work visa requirements. Use this field for the geographic locations from which applicants can apply.

Can I use TELECOMMUTE when remote working is negotiable?

No. Google's requirements exclude a negotiable remote benefit and occasional home working from TELECOMMUTE. Your description must clearly state that the role offers fully remote work.

Sources

1. Google Search Central, "Job posting (JobPosting) structured data for Job Search", updated 8 September 2026
2. Schema.org, "applicantLocationRequirements", accessed 17 October 2026
3. Schema.org, "jobLocationType", accessed 17 October 2026
4. Google Search Console Help, "Rich Results Test", accessed 17 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer