af87d9fbe8
Deterministic output is desired to improve diffability between builds. If the output randomly changes order each time it's built, then every page on a given site will change with every Jekyll build. Tools like rsync and git which can diff files will always show a change even when the content hasn't truly changed. |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| lib | ||
| script | ||
| spec | ||
| .gitignore | ||
| .rspec | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| Gemfile | ||
| History.markdown | ||
| LICENSE.txt | ||
| jekyll-seo-tag.gemspec | ||
docs/README.md
About 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.
What it does
Jekyll SEO Tag adds the following meta tags to your site:
- Page title, with site title or description appended
- Page description
- Canonical URL
- Next and previous URLs on paginated pages
- JSON-LD Site and post metadata for richer indexing
- Open Graph title, description, site title, and URL (for Facebook, LinkedIn, etc.)
- Twitter Summary Card metadata
While you could theoretically add the necessary metadata tags yourself, Jekyll SEO Tag provides a battle-tested template of crowdsourced best-practices.
What it doesn't do
Jekyll SEO tag is designed to output machine-readable metadata for search engines and social networks to index and display. If you're looking for something to analyze your Jekyll site's structure and content (e.g., more traditional SEO optimization), take a look at The Jekyll SEO Gem.
Jekyll SEO tag isn't designed to accommodate every possible use case. It should work for most site out of the box and without a laundry list of configuration options that serve only to confuse most users.
Documentation
For more information, see: