I’ve been exploring adding JSON-LD schema markup to parts of our website to improve SEO. Here are some things I have added, or am thinking about:
I’ve added Organization schema to our homepage.
I’ve added Person schema to our fac/staff pages.
I’ve added BreadcrumbList schema to all pages.
I’m planning on adding NewsArticle schema to stories.
I’m planning on adding Event schema to event pages.
I was a little surprised to find that LiveWhale wasn’t already generating schema markup for things like news and events. Any chance that is changing in LW 3.0?
Has anyone else gone down this road? I’m learning as I go, so any advice would be helpful.
I’d second a call for integrating schemas that align with what LiveWhale does out of the box (events, stories). For profiles, feels like that has to be on the client given varied setups and needs, but perhaps an example of the “Person” schema on faculty/staff/employee profiles would be a suitable example to include and let developers adapt.
LiveWhale core does include code to general LD+JSON blocks for News and Events (details pages and on the interactive Calendar pages), feel free to flag examples if you see any issues with the code as presented on those pages. Otherwise, thanks for filing this request for other types!
@karl Interesting. I didn’t notice there was already schema on news and events. I was looking in the dev tools inspector and it’s not there. If I view page source, I see it in a .lw_hidden div, but that same div is empty when viewed through dev tools. Thanks for letting me know.
I would agree with this. Every client will have different custom profile fields, and profiles are used for more than just people, so this would be tricky. The only way I can envision this working is having the option in the profile type editor to map specific fields to specific schema properties.
An easier addition would be schema for blog posts. I checked, and I don’t believe that exists at the moment.
Side question… I have been looking at the most sustainable way to add/maintain schema code to a number of key pages, like all the program descriptions. – If I use the “add custom code in the head” field in Page Details, it actually gets mostly erased the next time someone edits the details. Fun! – Further, I tried stuffing a file widget in that field, and… again, it is erased on save. – Thoughts? Soul-preserving workarounds?
I can’t say I’ve ever seen anything get stripped out of those fields before. You could try just putting that file widget in the body of the page. I don’t think there is a requirement that schema be in the <head>.
I’d be interested to see what schema you are using on program descriptions. I may be want to look at doing that next.
Interestingly (and frustratingly), about a third of the file widgets are returning “no results.” Either a cache problem, or a widget one… which probably is the universe telling me to just go home for the weekend and worry about this next week.
