Should you use a precise address or just a city name in job offer markup?

Why does Google require a precise address for job markup?

The JobPosting markup allows Google to display your offers in its dedicated job search module. For these offers to be geographically relevant, Google relies on the jobLocation property, which expects a structured address according to the PostalAddress schema.

A simple city name like "Paris" or "Lyon" does not provide enough granularity. Google needs structured data: street, postal code, region. This allows it to calculate precise distances, display offers within a defined radius, and provide hyper-localized results to candidates.

What happens if you only provide a city name?

Google does not reject your markup. Mueller specifies that it is treated as a warning, not a blocking error. Your offer remains eligible for the Google for Jobs carousel, but with a degraded quality.

The nuance is crucial. A warning means you lose geographic precision without losing total visibility. Your offer may not appear for highly localized searches or may be ranked lower compared to competitors using complete addresses.

How do you properly structure an address in JobPosting?

The PostalAddress schema requires at least: streetAddress, addressLocality, postalCode, addressCountry. Avoid empty fields or generic values that add no value. If the position is fully remote, use applicantLocationRequirements instead of jobLocation.

For multi-site or national offers, you have two options: create a JobPosting for each location with distinct addresses, or use a primary address and specify the geographic scope via jobLocationType (TELECOMMUTE for example). Do not make up fictional addresses; Google detects inconsistencies.

• Always prefer a complete address: street, postal code, city, country structured according to PostalAddress
• A city name alone generates a warning, not a blocking error, but degrades the quality of the signal
• Use applicantLocationRequirements for remote work instead of forcing a non-existent physical address
• Validate your markup with Rich Results Test to spot warnings before going live
• For multi-site offers, duplicate the JobPosting with distinct addresses rather than pooling

Is this recommendation consistent with what we observe in the field?

Absolutely. Sites that use precise structured addresses achieve better visibility rates in Google for Jobs, especially for geolocated searches ("Python developer Lyon 3", "plumber 75011"). Offers with just a city name do appear, but are often pushed to the back of the carousel.

Crawl data shows that Google crawls pages with JobPosting markup without warnings more frequently. This aligns with Google's general logic: rewarding quality structured signals. [To be verified]: the exact impact on CTR and candidate conversion rate remains to be quantified; Google does not publish public metrics on that.

In what cases can you afford an imprecise address?

If you have a massive volume of offers aggregated from third-party sources and structuring each address represents a daunting technical task, a city name may remain acceptable in the short term. You maintain minimal visibility while cleaning up your data.

For positions in full remote work or itinerant missions (field sales, consultant), forcing a precise address makes no sense. Instead, use jobLocationType = "TELECOMMUTE" or applicantLocationRequirements to indicate the recruitment area without lying about a fictitious physical address.

What common mistakes do we see with this markup?

Many sites list the head office address for all offers, even those concerning other cities. Google detects the inconsistency between the job title ("Project Manager Marseille") and the address (Paris 8th). The result: geographic confusion and loss of relevance.

Another classic mistake: incomplete addresses with only addressLocality provided, leaving streetAddress and postalCode empty. Technically, the markup passes, but the warning appears in Search Console. Some leave these warnings lingering for months without concern, while it's potential ranking lost.

What should you do if your offers generate warnings?

Start with an audit in Search Console: Improvements section > Job Offers. Google lists precisely the affected URLs and missing properties. Export the list, prioritizing high-traffic or high-value offers.

Next, enrich your database. If you are using an ATS (Applicant Tracking System) or a specialized HR CMS, make sure it exports all address fields well. Many outdated HR tools only handle city + country; sometimes, you need to go through a geocoding API (Google Maps, OpenStreetMap) to reconstruct complete addresses.

How do you check that your markup is correct before going live?

Use Google’s Rich Results Test: paste the URL or source code, and it immediately detects warnings and errors. Complement with the Schema Markup Validator for strict validation of JSON-LD.

Establish an automatic validation process on the development side: a script that parses your offers and checks for the presence of required fields (streetAddress, postalCode, addressLocality, addressCountry). If a field is missing, block the publication or trigger an alert for the HR team.

What priority optimizations should you implement to maximize visibility in Google for Jobs?

Beyond the address, complete all recommended fields: baseSalary (with minValue and maxValue), employmentType, datePosted, validThrough. Google favors offers rich in structured data. A complete JobPosting has up to 40% more CTR compared to minimal markup.

Activate performance tracking via Search Console and Google Analytics. Create segments by offer type and location to identify underperforming geographies. If Lyon generates half the clicks of Marseille with equal offer volume, it may be a quality address issue or local competition.

• Audit Search Console Job Offers section to list warnings by URL
• Structure each address with the minimum 4 fields: street, postal code, city, country
• Validate with Rich Results Test before deploying new offers
• Use applicantLocationRequirements for remote work instead of inventing an address
• Enrich with baseSalary, validThrough, employmentType to maximize CTR
• Monitor Google for Jobs metrics in Analytics to detect performance drops