A Jekyll plugin to add metadata tags for search engines and social networks to better index and display your site's content. This fork deals with the issue JSON-LD Alt Property Not Recognized.
Go to file
jekyllbot a937289d05 Update history to reflect merge of #284 [ci skip] 2019-10-30 12:00:04 -04:00
docs Merge branch 'master' into add-custom-paginator-message 2019-10-03 18:49:45 +02:00
lib Make Twitter card without having Twitter account (#284) 2019-10-30 12:00:00 -04:00
script move docs to their own folder 2017-05-25 09:50:01 -04:00
spec prefix config key with 'seo_' to avoid conflicts 2019-01-08 20:27:50 +05:30
.gitignore move docs to their own folder 2017-05-25 09:50:01 -04:00
.rspec add tests for drop 2017-04-06 22:34:11 -04:00
.rubocop.yml Test against Jekyll 4.x (#336) 2019-03-25 07:33:55 -04:00
.rubocop_todo.yml Test against Jekyll 4.x (#336) 2019-03-25 07:33:55 -04:00
.travis.yml Use the latest version of Rubygems 2019-05-17 00:23:04 +05:30
Gemfile Test against Jekyll 4.x (#336) 2019-03-25 07:33:55 -04:00
History.markdown Update history to reflect merge of #284 [ci skip] 2019-10-30 12:00:04 -04:00
LICENSE.txt Update LICENSE.txt 2018-01-03 19:52:21 +01:00
jekyll-seo-tag.gemspec Test against Jekyll 4.x (#336) 2019-03-25 07:33:55 -04:00

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.

Gem Version Build Status

What it does

Jekyll SEO Tag adds the following meta tags to your site:

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: