SEO improvements: Add json+ld schema.org microdata for Blog Posts #653
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
|
@onnimonni is attempting to deploy a commit to the Saasify Team on Vercel. A member of the Team first needs to authorize it. |
|
Love this; just need to clean up and remove the comments. I think my personal branch has some code to pull dates. |
|
Thanks @onnimonni 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Description
Initial steps on improving SEO for the blog posts. This adds https://schema.org/BlogPosting type microdata to the website which is one way to help Google/Bing to understand what the content is about.
@transitive-bullshit if you can show me how to get the publish dates and edited dates from the content that would be great 👌
We can also move this into the body if accessing these are easier there.
Notion Test Page ID
7875426197cf461698809def95960ebf