help to better help you:
Please: add always Joomla / JEM version and details to your posts, so we can try to reproduce your issue!
JEM and structured data
JEM and structured data
5 years 10 months ago
Hi there,
before I start to figure out what already has been dealt with in the JEM cummunity:
Has anybody fully adapted the JEM template to structured data according to schema.org/Event ?
A good deal has already been done but I started to get notifications from the Google Search Console about missing mandatory fields, e.g. the location field in the simple list view.
before I start to figure out what already has been dealt with in the JEM cummunity:
Has anybody fully adapted the JEM template to structured data according to schema.org/Event ?
A good deal has already been done but I started to get notifications from the Google Search Console about missing mandatory fields, e.g. the location field in the simple list view.
Please Log in or Create an account to join the conversation.
Re: JEM and structured data
5 years 10 months ago - 5 years 10 months ago
Do you use JEM responsive? There I invest a lot of time for structured data.
I think I did that because the old layout was not complete.
If you hide the location in the simplelist then it is missing naturally
I think I did that because the old layout was not complete.
If you hide the location in the simplelist then it is missing naturally
Last edit: 5 years 10 months ago by Egnarts.
Please Log in or Create an account to join the conversation.
Re: JEM and structured data
5 years 10 months ago
Cool, good to know. Thank you!
As I have my own responsive template version I didn't check out yours – which I will now.
It sounds somehow contradictorily, but the mandatory fields in structured data must be there even if they are hidden for the visitor. My approach is to store all the mandatory structured data fields next to the displayed date field or the displayed name field, since they are always displayed in JEM (as far I know) …
Other suggestions?
As I have my own responsive template version I didn't check out yours – which I will now.
Yes and that's a problem, because this will result in an incomplete ( = incorrect) representation of the structured data.If you hide the location in the simplelist then it is missing naturally
It sounds somehow contradictorily, but the mandatory fields in structured data must be there even if they are hidden for the visitor. My approach is to store all the mandatory structured data fields next to the displayed date field or the displayed name field, since they are always displayed in JEM (as far I know) …
Other suggestions?
Please Log in or Create an account to join the conversation.
- faustralia
- Offline
- New Member
- Posts: 4
- Thanks: 1
Re: Location on schema.org
5 years 9 months ago
I published a list, i can see: start date, end date, name of event, but the "itemprop location" is not available in my page.
Do ou know how I can add?
Why JEM not produce location metadata?
Do ou know how I can add?
Why JEM not produce location metadata?
The following user(s) said Thank You: jojo12
Please Log in or Create an account to join the conversation.
Re: Location on schema.org
5 years 9 months ago - 5 years 9 months ago
Because it's about the same, I move it to
JEM and structure data
JEM and structure data
Last edit: 5 years 9 months ago by jojo12.
The following user(s) said Thank You: faustralia
Please Log in or Create an account to join the conversation.
- faustralia
- Offline
- New Member
- Posts: 4
- Thanks: 1
Re: JEM and structured data
5 years 9 months ago
I translated the fields in a different way, and I don't remember if I'm publishing City or Venue.
In my html of the list I can see:
itemprop=startDate
itemprop=endDate
itemprop=name
and only a headers=jem_location, not an itemprop.
How can I add an itemprop=location to the list?
In my html of the list I can see:
itemprop=startDate
itemprop=endDate
itemprop=name
and only a headers=jem_location, not an itemprop.
How can I add an itemprop=location to the list?
Please Log in or Create an account to join the conversation.
Time to create page: 0.543 seconds