Common Job Posting Issues in Google Search Console and How to Fix Them
If you're using Google Search Console to track your job board’s performance, the JobPostings enhancement report (found in the left panel of your Search Console) highlights any structured data issues that may affect visibility on Google Jobs.
While JBoard does everything possible to ensure that job postings have the proper schema markup for Google, there are certain elements that are your responsibility to monitor to ensure full compatibility.
In JobPostings enhancement report, you may encounter two types of issues:
These are errors that prevent a job from appearing in Google for Jobs. They require immediate attention to ensure your job postings are indexed and visible.
What it means:
When a job is marked as remote, the location field is still important as it tells Google where the job seeker should be located to be eligible for the role.
If the location value is too broad or not a geographic location (e.g., "Worldwide", "Anywhere", "Only United States"), Google may fail to detect it correctly, and show this error.
How to fix it:
In your dashboard, navigate to the Jobs section and edit the affected job’s location by either:
Leaving the location field empty (if the job is open to applicants globally), or
Selecting one of the populated locations from the dropdown to specify where applicants must be located to apply
These do not block your job from appearing in Google for Jobs, but may limit how well it performs or reduce the richness of how it’s displayed
Below are the most common issues found in the JobPostings section, what they mean, and how to fix them:
What it means:
The job post does not include compensation details in the structured data.
How to fix it:
In your JBoard admin panel, go to the Jobs section and edit the specific job. Add the following fields:
Minimum Compensation
Maximum Compensation
Currency
Compensation Frequency (e.g., per hour, per month, per year)
What it means:
The job post does not include a valid Job Type in the structured data.
How to fix it:
In your JBoard admin panel, go to the Jobs section and edit the specific job. Under the Job Type dropdown, make sure you select one of the available job types (e.g., full-time, part-time, temporary, etc..)
Important: If you've modified the default Job Types in Taxonomy > Job Types, make sure to map each one to the appropriate Google Jobs employment type from the same section; this helps ensure we are sending accurate data to Google.
What it means:
The job post is missing one or more key location details in the structured data. This can affect how accurately your job appears on Google for Jobs when someone searches by location.
How to fix it:
When editing a job in the Jobs section of your JBoard admin panel, make sure to select a location from the dropdown that includes the full address (city, state/region, country).
Once selected, the system will automatically populate all the required address fields (Including the postal code) in the structured data.
What it means:
The job posting is missing the full street-level address in the structured data (e.g., 123 Main St).
This is a rare field to find in job postings on the internet, as most employers only specify city, region, or country. Unfortunately, JBoard currently does not provide a dedicated field to populate the street address.
This is an optional enhancement that may help improve data completeness, but is not required for eligibility on Google for Jobs.
As shown in the screenshots above, each issue lists the number of affected items. To identify the specific jobs that are affected, simply click on the issue, and Google will display the URLs of the impacted job postings.
Since the most common error in the enhancement report relates to job location, you can prevent this by using the "Geo Location Not Detected" filter in your Jobs section, as highlighted below.
This will display the jobs for which our system hasn't detected a geo-location—these are likely to be flagged by Google.
To fix this, update the job locations by selecting a value from the dropdown menu to ensure they are geo-coded correctly.
While JBoard does everything possible to ensure that job postings have the proper schema markup for Google, there are certain elements that are your responsibility to monitor to ensure full compatibility.
In JobPostings enhancement report, you may encounter two types of issues:
Critical Issues: How To Fix Them
These are errors that prevent a job from appearing in Google for Jobs. They require immediate attention to ensure your job postings are indexed and visible.
Invalid Object Type for field "applicantLocationRequirements" (Only Remote Jobs)
What it means:
When a job is marked as remote, the location field is still important as it tells Google where the job seeker should be located to be eligible for the role.
If the location value is too broad or not a geographic location (e.g., "Worldwide", "Anywhere", "Only United States"), Google may fail to detect it correctly, and show this error.
How to fix it:
In your dashboard, navigate to the Jobs section and edit the affected job’s location by either:
Leaving the location field empty (if the job is open to applicants globally), or
Selecting one of the populated locations from the dropdown to specify where applicants must be located to apply
Non Critical Issues: How To Fix Them
These do not block your job from appearing in Google for Jobs, but may limit how well it performs or reduce the richness of how it’s displayed
Below are the most common issues found in the JobPostings section, what they mean, and how to fix them:
Missing field "baseSalary"
What it means:
The job post does not include compensation details in the structured data.
How to fix it:
In your JBoard admin panel, go to the Jobs section and edit the specific job. Add the following fields:
Minimum Compensation
Maximum Compensation
Currency
Compensation Frequency (e.g., per hour, per month, per year)
Missing field "employmentType"
What it means:
The job post does not include a valid Job Type in the structured data.
How to fix it:
In your JBoard admin panel, go to the Jobs section and edit the specific job. Under the Job Type dropdown, make sure you select one of the available job types (e.g., full-time, part-time, temporary, etc..)
Important: If you've modified the default Job Types in Taxonomy > Job Types, make sure to map each one to the appropriate Google Jobs employment type from the same section; this helps ensure we are sending accurate data to Google.
Missing address fields ("postalCode", "addressRegion", "addressCountry", "addressLocality")
What it means:
The job post is missing one or more key location details in the structured data. This can affect how accurately your job appears on Google for Jobs when someone searches by location.
How to fix it:
When editing a job in the Jobs section of your JBoard admin panel, make sure to select a location from the dropdown that includes the full address (city, state/region, country).
Once selected, the system will automatically populate all the required address fields (Including the postal code) in the structured data.
Missing field "streetAddress"
What it means:
The job posting is missing the full street-level address in the structured data (e.g., 123 Main St).
This is a rare field to find in job postings on the internet, as most employers only specify city, region, or country. Unfortunately, JBoard currently does not provide a dedicated field to populate the street address.
This is an optional enhancement that may help improve data completeness, but is not required for eligibility on Google for Jobs.
How To Know Which Jobs Require Attention?
As shown in the screenshots above, each issue lists the number of affected items. To identify the specific jobs that are affected, simply click on the issue, and Google will display the URLs of the impacted job postings.
From the JBoard Dashboard: How to Identify Jobs Without Correct Locations
Since the most common error in the enhancement report relates to job location, you can prevent this by using the "Geo Location Not Detected" filter in your Jobs section, as highlighted below.
This will display the jobs for which our system hasn't detected a geo-location—these are likely to be flagged by Google.
To fix this, update the job locations by selecting a value from the dropdown menu to ensure they are geo-coded correctly.
Updated on: 17/06/2025
Thank you!