Skip to content

Remote job schema shows the wrong applicant location

Align remote JobPosting markup with the role's real location restrictions, distinguish applicant geography from office addresses, and verify the public job page.

By Crawlito · 6 min read

In short

  • A remote work arrangement and the places applicants may work from are different facts.
  • Use Google's documented remote-job properties only when they match the visible role description.
  • Validate the public job page and application path; correct markup does not guarantee a search appearance.
On this page

If a remote job's structured data suggests the wrong geography, compare the role's actual work arrangement with jobLocationType and applicantLocationRequirements. A company office address is not automatically the place a remote applicant must live. Correct the source fields and visible description together, then validate the public job page and its application path.

Do not label a hybrid role as fully remote merely to expand its apparent reach. The markup should describe the real opportunity, including any location restrictions supplied by the employer.

Write down the role's actual location rules

Ask the job owner to state three facts plainly: whether work is fully remote, whether office attendance is required, and where an eligible employee may be located.

These facts should come from the employer's approved posting. Do not infer eligibility from the headquarters address, the applicant's browser location, or another role in the same department.

Record the public job URL and the exact text that communicates the arrangement. If the page says only “remote” while the application requires a specific country, the content itself needs clarification.

Google's JobPosting documentation describes remote-job properties and examples with geographical restrictions.

Use the current documentation for the actual scenario. A hybrid role, a fully remote role restricted to certain locations, and a role available at either an office or remotely may need different combinations of fields.

Keep the business decision about eligibility separate from the technical task of representing it accurately.

Inspect the delivered JobPosting object

Read the JSON-LD on the public job page and identify the object that describes this specific vacancy. A site's organization address or unrelated location object is not the same field.

Compare jobLocation, jobLocationType, and applicantLocationRequirements with the approved description. Inspect the full object for inherited defaults that may come from a shared template.

The JSON-LD troubleshooting guide covers finding and parsing the delivered markup. A valid JSON document can still describe the wrong facts.

Check for duplicate JobPosting objects emitted by an ATS integration, theme, or SEO plugin. One corrected object does not resolve a contradictory second object.

Save the source-system fields and generated output side by side. That reveals whether the error comes from incorrect job data or from a mapping that uses the wrong field.

Do not copy the company's general address into every job object just to satisfy a validation warning. Establish the role-specific meaning first.

Distinguish remote status from applicant geography

For a hypothetical fully remote role open to applicants located in Canada, a partial example is:

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

This is only the location portion of a JobPosting, not a complete eligible job object. The other required and applicable fields still need to describe the actual vacancy.

Google's documentation explains when these remote properties are appropriate and requires the visible description to communicate the relevant geographical conditions.

Do not use an office's street address as a shortcut for a remote applicant restriction. It answers a different question.

Likewise, do not treat TELECOMMUTE as a promise that anyone in the world can apply. The work arrangement and permitted applicant locations are separate facts.

If the employer changes eligibility, update the public description and source fields together. A schema-only change can leave applicants with contradictory instructions.

Repair the mapping at the publishing source

Find the system that owns the job record: the ATS, CMS, integration layer, or template. Correct the field mapping there so the next synchronization does not restore the wrong geography.

Use explicit fields for work arrangement and applicant location where the publishing system supports them. Avoid deriving these facts from free-text fragments when a maintained structured field already exists.

If the source contains only ambiguous text, improve the editorial input before generating more confident markup. The generator should not invent a country or remote classification.

For multiple eligible regions, follow the documented representation and the employer's actual requirements. Do not expand a list automatically based on where the company has customers or offices.

Keep a neighboring office-based role as a control. A shared-template repair should not convert every vacancy into a remote posting.

The structured-data guide explains the broader principle: markup should match the visible entity and page content.

Validate the public page and its application journey

Run the corrected public URL through Google's supported structured-data testing tools. Inspect the extracted JobPosting object, not only a generic statement that the page contains structured data.

Confirm that the visible work arrangement and eligible locations agree with the parsed properties. A validator can catch supported-field issues, but it cannot establish every employer fact.

Follow the application link and review the relevant location questions. If the job page says one geography while the application rejects it, the publishing repair is incomplete.

Check the final URL after redirects. The linked application should correspond to this vacancy rather than a general careers homepage or a different role.

Keep the test date and a copy of the corrected public output. Search surfaces can update separately from a live page, so distinguish current publication evidence from later appearance observations.

Do not promise that passing validation will cause the job to appear in a particular search feature.

Review shared templates with representative job types

Test a fully remote role, an office-based role, and a mixed arrangement if the employer actually publishes all three. Each should retain its intended classification.

Inspect older active roles that may have been created before the new source fields existed. A default value can be correct for new records while misrepresenting migrated ones.

Do not bulk rewrite every job based on one example. Use the approved source data and flag ambiguous records for the job owner.

If a vacancy is no longer open, handle its lifecycle separately. The expired job guide covers why an outdated active posting needs more than a location correction.

Check localization too. Translated job descriptions should communicate the same eligibility conditions as the structured fields used to publish them.

A useful acceptance set is small enough to review carefully but broad enough to exercise the distinct mappings the template supports.

Keep the report useful to recruiters and developers

Describe the incorrect field, the actual approved role condition, the mapping change, and the verified public output. This gives recruiters and developers a shared understanding of the defect.

Avoid saying that location markup changes the legal eligibility of applicants. It communicates the employer's stated conditions; it does not decide them.

Do not infer lost applications or search traffic from the field mismatch alone. If outcome data exists, analyze it with the publication dates and measurement limits clearly marked.

For ongoing maintenance, assign ownership of work-arrangement changes. A role becoming hybrid or moving to a different eligibility region should trigger a content and markup update together.

Keep application links, active status, and location facts in the same editorial review. Applicants experience them as one opportunity even when different systems own each field.

The practical result is a clearer, consistent public job page that readers and supported parsers can interpret without conflicting geography.

Frequently asked questions

Does TELECOMMUTE mean the job is open worldwide?

No. Remote work status and applicant location requirements are separate facts. Use the employer's actual conditions and the documented properties.

Can I use the company headquarters as the remote location?

Do not substitute headquarters for applicant eligibility. Identify what each field is intended to represent for this role.

Will correcting the schema guarantee a job search listing?

No. Validate the implementation and keep the posting accurate, but search appearance depends on additional requirements and platform decisions.

After validating the job markup, use the free Crawlito check on the public vacancy page to review its access and page-level content.

Filed under Structure and schema. Topics: structured-data, google, jobs