Indexing OJS into Google Scholar

Dear OJS Team,

Currently, we use OJS (Open Journal Systems - for our journal ( But still, our journal articles are not indexed in Google Scholar. In this regard, if anybody could help us then I kindly request you to give the solution for this problem.

Thank you

Hi @Babu,

We are currently working on a document specific to OJS Google Scholar. For the time being, I would suggest taking a look at the Inclusion and Publisher tab - Google Scholar Help. There maybe things with the article metadata that might need to be corrected.

Kind Regards,
Patricia M.

Prezado, recomendo a judicialização. Tentei tudo mas não tiv obtive resposta ou êxito. Coloquei o Google na justiça e já na audiência de conciliação eles vieram com a solução.

We have the same problems; it is appear when we upgrade from 2.4 to 3.2.x ojs, so i thing it is best to reinstal ojs 2.4

Dear @pmangahis

Due to the google scholar issue recently we have moved our journal, ‚ÄúInternational Journal of Physical Education, Fitness and Sports‚ÄĚ (International Journal of Physical Education, Fitness and Sports), to the new website, which is self-hosted on a shared Linux hosting platform. All our old issues were properly indexed in google scholar, but unfortunately, our latest two issues were not indexed in Google Scholar.

Any suggestions or connections, kindly support.

Hi @Babu,

You may want to have a look at our Google Scholar guide, that Patricia mentioned, which has been completed: Google Scholar Guide

In particular, you may want to have a look at the troubleshooting section: Google Scholar Indexing

PKP Team

you can submit your sitemap in google search console… it take about 2 to 4 weeks to be indexed in google scholar

you do need to put some id files in the root folder of your ojs installation

your journal sitemaps is

1 Like

Dear @mohd_arshad
Thank you very much for your valuable comments. We have already tried it but still, the articles are not indexed in Google Scholar. Recently we have upgraded our OJS software and after that only we have encountered this issue.