## Summary
Removed `<meta name="author" />` tag
1. `<meta name="author" />` has been dropped back in 2014.
2. `<meta name="author" />` is used incorrectly in the template.
## Further information:
- [Special tags currently supported by Google](https://support.google.com/webmasters/answer/79812?hl=en)
- [Moz on "author" tag, listed under "Bad Metas"](https://moz.com/blog/the-ultimate-guide-to-seo-meta-tags)
- [Google Authorship Markup](https://webmasters.googleblog.com/2011/06/authorship-markup-and-web-search.html)
- [Google Scholar Metadata & the `author` tag](https://www.monperrus.net/martin/accurate+bibliographic+metadata+and+google+scholar
)
The correct way to use the `authorship` tag is:
```
<a href="/authorname/archive" rel="author">Author Name</a>
```
or when citing a source:
```
<meta name="citation_title" content="Crystal structure of squid rhodopsin" />
<meta name="citation_publication_date" content="1999" />
<meta name="citation_author" content="Murakami, Midori" />
<meta name="citation_author" content="Kouyama, Tsutomu" />
<meta name="citation_pdf_url" content="crist_struct.pdf" />
```
This is directly related to an outdated pull #363
#77 and #78 added support for different images on Twitter and Facebook, an advanced feature of SEO
Tag Gem. The implementation has led to complications updating JSON-LD data in #151. Under Pareto
principal we can reasonably assume this feature is not often used, and, as such, should be removed.
The result of which simplifies template logic, offers a fallback experience by leverages Twitter's
use of `og:image` in place of `twitter:image` (sees twitter card tag ref) and helps unblock #151.
Users can no longer specify a separate twitter and Facebook image. If both a Facebook (Open Graph)
and Twitter image are provided in the `image` object, the Facebook image will take precedence.
Replaces the "-" used as a title separator with "|".
Ref: https://moz.com/learn/seo/title-tag
Also updates docs to specify title optional and fix errata.
This adds the rest of the JSON fields to pass all errors and blog postings.
- Adds page.image.url for the image url. (Will default to image if not present).
- Add page.image.height and page.image.width for an image object (Will default back to image url if not present).
- Add dateModified (will capture from yaml if present, if not it will use datePublished)
- (I feel there should be a manual option for this as I sometimes save parts of my blog that shouldn't update the modified field, but still
change the file timestamp).
This should create JSON that will pass all warnings/strong recommendations/errors from [Google's Structured Data Testing Tool](https://search.google.com/structured-data/testing-tool).