Level 6
Adding a link to the site in question for reference: https://matchup.us/cities/cincinnati
Jul 14, 2020
3
Level 6
Structured Data (schema.org) In Markup (SEO)
Not really a Laravel question, but curious if anyone has a good suggestion about using structured data.
Tl;dr: Is it good practice to use structured data in markup for both an index view (excerpts) as well as a show (detail) view?
I have an Event resource (like a sports event with a time and physical location, etc.) with an index view and a detail view. The index view shows a list of excerpts of events. You can click into them to get to an event detail view. Very typical.
My question is, should I be using structured data on both the index view and detail view? I think it's pretty clear that the detail view could benefit for the structured data, but is it necessary (perhaps duplicative) on the index view?
i.e. itemscope itemtype="http://schema.org/Event", itemprop="startDate", itemprop="location"
What prompted this question was the "requirements" for marking up an Event. When you have a location it is looking for a physical address. I don't show the physical address in the index (excerpt) view. But I could include it in the meta data if it is important.
Hopefully that makes sense. Any thoughts?
Level 80
@nathangross I tend to use Schema.org mark-up on detail pages, so the actual event page itself. Also be sure to add a mainEntity itemprop to the wrapping mark-up to indicate that it’s the main entity of that URL:
<article itemprop="mainEntity" itemscope itemtype="http://schema.org/SportsEvent">
<!-- Event mark-up -->
</article>
1 like
Level 1
@martinbean thanks.. Very helping
Please or to participate in this conversation.