schema.org: Only show post's own keywords

[brunoamaral]

At the moment, the _internal/shchema.html template outputs the full list of tags as part of the <meta itemprop="keywords">.

<!-- Output all taxonomies as schema.org keywords -->
<meta itemprop="keywords" content="{{ range $plural, $terms := .Site.Taxonomies }}
{{ range $term, $val := $terms }}{{ printf "%s," $term }}{{ end }}{{ end }}" />
{{ end }}

My suggestion is to make this conditional so that it's more relevant to search engines.

I'm usure this code would work, but the logic should be close to this:

{{if .IsPage}}{{ range $index, $tag := .Params.tags }} {{ $tag }},{{ end }}
{{ else }}
    {{ range $plural, $terms := .Site.Taxonomies }}
    {{ range $term, $val := $terms }}{{ printf "%s," $term }}{{ end }}
{{ end }}">

[bep]

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

The resources of the Hugo 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 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, and you feel that it is still relevant and valuable, please tell us why.

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

[bep]

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.

If this is a bug and you can still reproduce this error on the latest release or the master 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, and you feel that it is still relevant and valuable, please tell us why.

[juh2]

I think it is simply wrong to spam the itemprop metadata field with all keywords ever used on a site. That makes the field unusable. So yes, please improve this.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.