Is Job Posting Markup Without Location Data Valid or Not?

Why Does Google Emphasize Location Data in JobPosting?

Job postings without geographical information have no value for users. Google seeks to provide relevant results based on the user's search and location. JobPosting markup without specific location cannot be filtered, sorted, or properly displayed in Google for Jobs.

Location allows the algorithm to match the job offer with geolocalized queries. A user searching for "developer Paris" does not want to see a job offer in Lyon without clear indication of the location. Thus, Google rejects any incomplete markup on this point, even if the rest of the data is correct.

What Are the Exact Required Location Fields?

The JobPosting schema requires a jobLocation property of type Place. Within this Place, you must provide at least a structured address including addressLocality (city) and addressCountry (country). The addressRegion (region/department) field is recommended but not strictly mandatory for validation.

If the job is fully remote, you must use the jobLocationType property with the value TELECOMMUTE. However, even in this case, a reference address (headquarters, main office) is often expected for legal compliance and relevance.

What Happens If I Don't Fill in These Fields?

Your markup will be flagged as invalid in Google’s enriched results test. The affected job offers will not show up in the Google for Jobs carousel. You will lose all the additional visibility provided by this enriched format.

Google Search Console will show structured data validation errors. You will receive notifications indicating that some pages contain incomplete JobPosting markup. The eligibility rate of your offers will drop, mechanically reducing your organic traffic on job queries.

• The jobLocation fields with addressLocality and addressCountry are mandatory to validate the JobPosting schema
• Incomplete markup will be rejected by Google and will not appear in Google for Jobs enriched results
• Remote work requires the property jobLocationType=TELECOMMUTE but does not exempt you from providing a reference address
• Validation errors are reported in Search Console and directly impact the organic visibility of job offers
• Location allows for geographical filtering of results for the user

Is This Requirement Consistent with Observed Practices in the Field?

Absolutely. Career site audits show that nearly 40% of JobPosting markups are rejected due to missing or incorrectly structured location information. Recruiters often neglect this field, thinking the city name in the job title is sufficient. This is a fatal mistake.

Google has always favored complete structured data. For JobPosting, location has been a non-negotiable quality criterion since the launch of Google for Jobs. Sites that cut corners on this markup mechanically lose traffic to more diligent competitors.

What Nuances Should Be Considered Regarding This Directive?

The notion of "required fields" can be confusing. The Google validator accepts markup with only addressLocality and addressCountry. However, in practice, a minimalist markup performs worse than enriched markup containing streetAddress, postalCode, and addressRegion.

Offers with precise location (postal code, complete address) benefit from better matching on local queries. If you settle for the bare minimum, you validate the schema but do not maximize your visibility chances. This is technically compliant but strategically suboptimal.

[To be verified] Google has never published quantitative data on the impact of enriched versus minimalist location. Field observations suggest visibility gains, but no official Google study quantifies this.

When Does This Rule Pose Problems?

Multi-site or itinerant positions complicate matters. A salesperson covering three regions, a consultant working with different clients: how to structure the location? Google recommends creating a posting for each main place or using multiple jobLocation values, but the documentation remains vague.

Pure-play remote work firms (startups without a physical office) find themselves stuck. Should you indicate the founder's address? That of an administrative domicile? Google requires an address but does not specify how to handle distributed organizations. The risk is entering a fake address just to validate the schema, skewing results.

What Should I Implement Concretely in the Code?

Add the jobLocation property in each JobPosting object of your JSON-LD. This property must contain a Place-type object with a structured address. Minimum requirement: addressLocality ("Paris") and addressCountry ("FR" in ISO code).

For optimal markup, also complete streetAddress, postalCode, and addressRegion. These fields enhance geographic matching and strengthen the relevance of your offers in local searches. If the position is remote, add jobLocationType with the value TELECOMMUTE in addition to the address.

What Mistakes Should Be Avoided During Implementation?

Never leave jobLocation empty or with generic values like "France" without a city. Google rejects this type of markup. Do not use free text in addressLocality: "Paris region" or "Île-de-France" are not valid cities.

Avoid duplicating the same offer with 10 different locations to artificially inflate your visibility. Google detects these practices and may demote all your offers. If one position covers multiple cities, create separate offers with differentiated content or use a table of jobLocation values (but test validation).

How Can I Check That My Markup is Compliant?

Use Google’s Rich Results Test. Paste the URL of your offer pages or your JSON-LD directly. The validator immediately flags any missing or incorrectly formatted fields on JobPosting.

Check the Structured Data report in Google Search Console. Filter by JobPosting type and verify the number of valid vs invalid elements. If you find an error rate exceeding 5%, audit your code to identify problematic offers.

• Add jobLocation with addressLocality and addressCountry in each JobPosting
• Complete streetAddress, postalCode, and addressRegion to maximize local relevance
• Use jobLocationType=TELECOMMUTE for fully remote positions
• Test each type of offer with Google’s Rich Results Test
• Monitor the Structured Data report in Search Console to detect errors
• Never duplicate an offer with multiple identical locations to artificially boost visibility