Here is a Full Guide to Rightly Debug Google Scholar Metadata for WordPress Including Debugging JSON-LD, Dublin Core and Conflicting Meta Tags. If you can not debug rightly, basically you’ll never get the Citation Links, Related Articles and other important stuffs which peoples basically seek for. There is a Plugin named Google Scholar Plugin for adding Google Scholar Metadata in WordPress – it is basically buggy and to much backdated. There is thing named Matthew effect, Google Scholar and Search gives high weight on citation counts in it’s ranking algorithm.
Google Scholar Metadata : Read Our Previous Articles
We have lot of articles on Micro-formats and other semantically important things. Each link will open in new window; you can only open the desired web pages :
- WordPress as Academic Journal : All plugins listed. This is the most important article.
- Dublin Core : Dublin Core in HTML5 for WordPress.
- JSON LD – JSON-LD is discussed in details. Probably Google Scholar does not understand JSON-LD at the time of publication of this article.
- TechArticle schema– This will give you a good idea how to dynamically add various new, not present features in WordPress.
- Adding new itemprops – We gave example to add Itemprop image schema in WordPress posts. You can use this idea for adding your needed stuffs.
Google Scholar Metadata : Guide For WordPress
Header and Footer is a very good Plugin for WordPress. If you are using StudioPress Genesis, then you will get more better plugins for finer control. Both will allow to execute PHP snippets – this is important to dynamically generate the tags. There are two helpful web based tools :
---
|
1 2 3 4 5 |
# copy paste in a text editor first https://developers.google.com/structured-data/testing-tool/ http://greycite.knowledgeblog.org/ # also read https://scholar.google.com/scholar/inclusion.html#troubleshooting |
You will need these things at maximum at header :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
<html> <head> <title>NAME OF POST IN HTML5</title> ... <meta name="citation_title" content="Meta Description" /> <meta name="citation_journal_title" content="Website Name"> <meta name="citation_author" content="Last Name1, First Name1" /> <meta name="citation_author" content="Ghosh, Abhishek " /> <meta name="citation_pdf_url" content="/wp-content/uploads/pdf/this_article.pdf" /> <meta name="citation_journal_title" content="Journal Name"> <meta name="citation_title" content="Article Title"> <meta name="citation_publication_date" content="06-04-2015" /> <meta name="citation_date" content="06-04-2015"> <meta name="citation_volume" content="10"> <meta name="citation_issue" content="1"> <meta name="citation_firstpage" content="1"> <meta name="citation_lastpage" content="15"> <meta name="citation_doi" content="give if exists"> <meta name="citation_abstract_html_url" content="short link or full permalink"> <meta name="citation_fulltext_html_url" content="short link or full permalink"> <meta name="dc.Contributor" content="Last Name1, First Name1"> <meta name="dc.Contributor" content="Last Name2, First Name2"> <meta name="dc.Title" content="Article Title"> <meta name="dc.Date" content="06-04-2015"> <meta name="citation_publisher" content="Website Name"> <meta name="citation_online_date" content=" "> <meta name="citation_conference_title" content=" "> <meta name="citation_volume" content=" "> <meta name="citation_issue" content=" "> <meta name="citation_issn" content=" "> <meta name="citation_isbn" content=" "> <meta name="citation_firstpage" content=" "> <meta name="citation_lastpage" content=" "> <meta name="citation_dissertation_institution" content=" "> <meta name="citation_technical_report_institution" content=" "> <meta name="citation_technical_report_number" content=" "> ... </head> |
As said above, Google Scholar does not understand JSON-LD. Google is basically a cheating company to find people’s data and supply to NSA, what extra stuffs we found during these finding are quite odd :
All of us, worked with schema.org stuffs for WordPress development. Google’s version or need of schema.org markups actually does not matches with schema.org’s official guide. This Microformat testing tool is new. KCite is best example to show you that so much markup is not needed :
we guess, unless 1 citation is counted by Google, you basically can not fully debug. That url http://greycite.knowledgeblog.org/ is giving information which are not given by Google’s tool. Actually NOTABILITY to Google is a meaningless word. We will avoid too many conflicting data. Newer issue is :
Blog is not a known valid target type for the mainContentOfPage property error.
According to Google, Blog can not be used as a type of mainContentOfPage. You have to work a bit to fix.
Tagged With examples of scholar metadata , google prefers schema org over dublin core , Google scholar matadata update , google scholar meta data , google scholar metadata , metadata tagging scholars , provide metadata to google scholar , wordpress not appearing in google scholar