Make changes to schema easier #3085
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ElponeNote
added a commit
to ElponeNote/ElponeNote-github.io
that referenced
this pull request
Jun 13, 2024
This reverts commit 2f5e771.
minyoongi96
pushed a commit
to minyoongi96/minyoongi96.github.io
that referenced
this pull request
Aug 26, 2024
* Make changes to schema easier * Only show on one page not on all pages * Move schema.html to _includes/ and move the URL guard out --------- Co-authored-by: iBug <git@ibugone.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an enhancement or feature.
Summary
By moving the schema to it's own file it is easier to change it to your likings without having to edit the seo.html.
The schema markup plays a bigger and bigger role for Google, it seems, and this change will make it easier to improve the Schema implemented. And Google prefers the JSON-implementation.
I can make a follow up pull request to make a better out-of-the-box Schema-implementation with JSON, if improvements here would be considered?
Context
This is not related to any current open Github issue.