Google Structured Data missing

how did you get on because you won’t get any support from here. I have the same issue with salary and job location address, so I am interested if you resolve your issue and how?

Hi @petebocken !

Can you please check out the document here: https://wpjobmanager.com/document/fixing-structured-data-issues/

Let us know if you still have problems when you apply the solutions mentioned on that page.

@bindlegirl I did look at that document.

I’ve since fixed the posted date issue (in the other support ticket), I’m waiting for Google to update to show that change.

Testing is showing the following errors still:

hiringOrganization
A value for the hiringOrganization field is required.

(I have “Hospice Alliance” set up in the Company Name WP Job Manager field)

jobLocation
A value for the jobLocation field is required.

(I have “10220 Prairie Ridge Blvd. Pleasant Prairie, WI 53158” set up in the Location WP Job Manager field)

jobCategory
Nonexempt (The property jobCategory is not recognized by the schema (e.g. schema.org) for an object of type JobPosting.)

(I have the “Nonexempt” job category checked in WP Job Manager)

What I have that is displayed in the testing when I click on jobCategory: <li class=”job-category” itemprop=”jobCategory”>Nonexempt

hiringOrganization and jobLocation do not show HTML when I click on them in the testing.

Hey @petebocken !

I checked your job listing here: https://search.google.com/test/rich-results?id=-S2POy7EP21qKiQYa17tgg

What I see is two sets of schema info. One is added by WP Job Manager (6 warnings) and the other one is not (3 errors 3 warnings). See here: https://d.pr/i/YO6PTt

Is your theme (or some other plugin) adding the schema info to the code?

@bindlegirl I had a “job_manager” template folder set up in my themes folder. On Friday, I renamed that folder to “job_manager.bak” and I see some visual edits that were made previously are now gone.

Doing another Structured Data Test right now, it looks like the posted date issue is now resolved.

I now see warnings for addressLocality, addressRegion, streetAddress, postalCode. Looking at https://wpjobmanager.com/document/fixing-structured-data-issues/ I see these mentioned, however for the Location field we have the full address entered “10220 Prairie Ridge Blvd. Pleasant Prairie, WI 53158”, so I’m not sure what I am supposed to do to address this.

However, as you also stated in the link above, those are not required for Google to post your job listings, they are just warnings. So having those be warnings shouldn’t stop the jobs from coming up in results, correct?

baseSalary has a warning, but again not required. We also don’t and don’t want to specify salaries for these positions anyway.

The last warning is validThrough which I’m assuming maps to the Listing Expiry Date: field? I do not populate that and nor would we want to.

@petebocken , I checked the test for your site again and I see the 6 warnings you mention. The reason Google doesn’t interpret your full address as you expect it is that you don’t seem to be using the Google Maps API (geolocation). That is why your address is interpreted as a string (“name”) in Google test results: https://d.pr/i/s816tW

To get full structured data when you enter the address, you need to have a Google Maps API key and add it to WP Job Manager as described here: https://wpjobmanager.com/document/geolocation-with-googles-maps-api/

Once you add the key, you will need to resave the job (with a slight change such as a blank in the description) to trigger the geolocation code. You will know it worked if you see new custom geolocation fields created in the job posting editor in WP Admin.

@bindlegirl Will I see this geolocation field in the “Job Data” section of the job edit screen?

I added the Geocoding API to the dev console and then added the API to the plugin, but I don’t see any change.

@petebocken If the Google geolocation is working there will be some new fields added in WP-Admin for each job like this: https://d.pr/i/kGQsua

Other than that, you will see no difference.

@bindlegirl OK, I got the custom fields showing now. However, I cannot get the geolocation codes to populate the custom fields.

I set up the Google API with Geocoding library and restricted to https://*.hospicealliance.org/*

I added an extra period to the end of a sentence in one job post description, saved and refreshed the tab.

I tried this on another site and got the same results. Not sure what I’m doing wrong.

@bindlegirl all current jobs are showing in Google Job listings now. Thanks.

@petebocken I’m happy you got it fixed.
Was the problem with Geocoding caused by Google API settings (restrictions)? Just curious ??

@bindlegirl I honestly don’t know which piece actually fixed it, since so many changes were done. You can see from the structured data test that it still has warnings for address, base salary and validthrough, but it appears to be fine with that (which I figured should have been the case anyway.

https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Fwww.hospicealliance.org%2Fcareer%2Fon-call-hospice-rn%2F