search

jekyll / jekyll-seo-tag

A Jekyll plugin to add metadata tags for search engines and social networks to better index and display your site's content.
https://jekyll.github.io/jekyll-seo-tag
MIT License
1.66k stars 294 forks source link

Critical feature req: Ability to turn off or better modify JSON-LD #473

Closed maxnorton closed 1 year ago

maxnorton commented 2 years ago

I'm finding this plugin very useful for its handling of og tags and Twitter cards but there are so few options to customize JSON-LD output that it is impossible to serve Google even a basic level of rich data. Issue 135 is related but appears to have been closed without any resolution.

Would it not be straightforward to either (a) allow users to turn off JSON-LD and handle Schema markup themselves, or (b) enable more Schema properties? The discussion in the issue above is around products events, but my use case is completely different (details about a person) and it is just as important to be able to customize the output.

tpluscode commented 1 year ago

I second this. I'm adding SEO with the plugin to a site where I already created a complex JSON-LD markup, including opening hours etc.

I would ideally disable the generated output. Config like...

seo:
  jsonld: false

Or similar to title: {% seo jsonld=false %}

maxnorton commented 1 year ago

@tpluscode FWIW, I have a fork here where I started trying to implement a liquid tag to turn it off. I didn't get it working, but the last commit simply comments out the JSON-LD injection in lib/template.html. I'm not planning on keeping the fork up to date but you're welcome to use it. If I get the time I will get the liquid tag working and open a PR.

jekyllbot commented 1 year ago

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.