How to Get Your OJS Journal Indexed in Google Scholar

How Google Scholar indexing works

Google Scholar indexing for an OJS journal does not start with an application. There is no form to fill in, no committee and no sign-up. Google Scholar's crawler visits websites periodically, follows ordinary HTML links, reads each article page and decides whether it qualifies under the Google Scholar inclusion guidelines. Open Journal Systems (OJS) is specifically mentioned in those guidelines as a platform that can export the bibliographic meta tags Scholar needs.

In practice, the guidelines come down to four things:

• Scholarly content only. Journal articles, conference papers, theses, preprints and technical reports qualify. News items, editorials and book reviews generally do not.
• One article per URL. Each paper needs its own page. Several abstracts on one page, or several papers in one PDF, are not supported.
• A visible abstract or full text. Visitors must see at least the complete author-written abstract without logging in, dismissing pop-ups or installing anything.
• Easy discovery. Every article should be reachable from the homepage through a small number of simple HTML links. Google suggests no more than ten. The OJS Archive → Issue → Article structure already does this.

Google Scholar and Google Search are separate indexes. An article can rank well in normal Google results and still be missing from Scholar, and the reverse also happens.

What OJS already does for Google Scholar indexing

A correctly configured OJS 3 journal already provides almost everything Google Scholar asks for.

The Google Scholar Indexing plugin (citation_* meta tags)

This generic plugin adds Highwire Press-style citation_* meta tags to the <head> of every article landing page. Google Scholar prefers this tag format. Check that it is enabled in each journal under Settings → Website → Plugins → Installed Plugins → Generic Plugins → Google Scholar Indexing Plugin (the same path in OJS 3.3, 3.4 and 3.5). Journals upgraded from OJS 2.x to early 3.x releases sometimes found it switched off, so do not assume.

A typical article page outputs tags like these (abridged; the exact set depends on your version and which metadata you filled in):

<meta name="citation_journal_title" content="Journal of Example Research">
<meta name="citation_issn" content="1234-5678">
<meta name="citation_author" content="Ayesha Rahman">
<meta name="citation_author_institution" content="University of Dhaka">
<meta name="citation_title" content="Soil salinity and rice yield in coastal districts">
<meta name="citation_language" content="en">
<meta name="citation_date" content="2026/03/15">
<meta name="citation_volume" content="12">
<meta name="citation_issue" content="1">
<meta name="citation_firstpage" content="1">
<meta name="citation_lastpage" content="14">
<meta name="citation_doi" content="10.12345/jer.v12i1.123">
<meta name="citation_abstract_html_url" content="https://journal.example.org/index.php/jer/article/view/123">
<meta name="citation_pdf_url" content="https://journal.example.org/index.php/jer/article/download/123/456">

Note that citation_pdf_url is only output for galleys that are real PDF files, and the date tag falls back to the issue year when the article's publication year and the issue year differ. Both details matter when troubleshooting.

Other things OJS does out of the box

• Dublin Core Indexing plugin adds DC.* tags. Google treats Dublin Core as a last resort, but it does no harm and other services read it.
• Article landing pages at /article/view/ID show the title, authors, abstract and galley links: one article per URL, as Scholar requires.
• A built-in XML sitemap (next section).
• An OAI-PMH interface at /index.php/your-journal/oai that harvesters and aggregators use. Google Scholar does not need it, but other discovery services do.

How is journal indexing done in OJS?

People often ask whether OJS has an "index service" or a button that submits the journal to databases. It does not. OJS exposes your metadata in several standard ways, and each indexing service uses one of them:

Selective databases such as DOAJ and Scopus also evaluate the journal itself before they accept any metadata. Technical setup gets you into Google Scholar; editorial quality is what those databases judge. For DOIs, see setting up DOIs and Crossref in OJS.

The OJS sitemap: URLs and Google Search Console

OJS generates an XML sitemap automatically. You do not need a plugin, and you do not need to regenerate it: it is built fresh each time a crawler requests it. There are two levels:

• Journal sitemap: lists that journal's pages, issues and articles.
• Site-wide sitemap index: points to the sitemap of every journal on the installation. It is useful when one OJS installation hosts several journals.

Replace jmr with your journal's path (the part of the URL after index.php/). On the rare servers where disable_path_info = On, PKP's sitemap README gives the query-string form instead, for example index.php?journal=index&page=sitemap. Open the URL in a browser before you submit it. A journal sitemap should start with a <urlset> element and the site-wide one with <sitemapindex>. If you see an HTML page or an error, fix that first.

Submit the sitemap in Google Search Console

1. Add your site as a property

   In Google Search Console, add either a Domain property (verified with a DNS record) or a URL-prefix property for your exact journal address, including https://.

2. Verify ownership

   For a URL-prefix property, the HTML tag method is easiest. In OJS 3.3–3.5, paste the tag into Settings → Distribution → Search Indexing → Custom Tags and save.

3. Submit the sitemap

   Open Indexing → Sitemaps, enter the sitemap URL from the table above and click Submit. For a single journal, submit the journal sitemap. For several journals, submit the site-wide index or each journal's sitemap.

4. Check the status

   After Google fetches it, the status should read Success with a count of discovered URLs. "Couldn't fetch" or "could not be read" usually means a redirect problem, a wrong base_url, a firewall blocking Googlebot, or an old OJS bug (some OJS 3.4 users reported a namespace error on the site-wide sitemap that later patch releases fixed).

<meta name="google-site-verification" content="paste-the-code-google-gives-you" />

Be realistic about what this does. Google's Scholar guidelines do not require a sitemap; clear browse links matter more. A sitemap helps Google's crawlers find new articles sooner, and Search Console is the only place you will see crawl errors, blocked pages and security warnings for your domain. If you would like this set up and monitored for you, our OJS SEO service covers Search Console, sitemaps and Scholar metadata.

robots.txt dos and don'ts

OJS does not need a robots.txt file to be indexed, but many hosts or previous developers add one. A single wrong line can hide an entire journal from Google Scholar, so review it.

User-agent: *
Disallow: /index.php/jmr/search
Disallow: /index.php/jmr/login
Disallow: /index.php/jmr/user

Sitemap: https://journal.example.org/index.php/jmr/sitemap

Place the file in your web root so it loads at https://journal.example.org/robots.txt. Search Console's robots.txt report (under Settings) shows the version Google last fetched. Google's robots.txt documentation explains the syntax.

PDF requirements for Google Scholar

Most "Google Scholar is not indexing my articles" cases we see involve the PDF galleys. These are the rules from Google's inclusion guidelines, with what they mean for an OJS journal:

Article pages, metadata and consistent author names

Each OJS article already has its own abstract page. What usually goes wrong is the metadata on it. Before publishing each issue:

• Complete metadata: full title (not in ALL CAPS), every author, affiliations, the full abstract as text, keywords, page numbers or article number, and the DOI if you use them.
• Matching dates: the article's publication date, the issue date and the date printed on the PDF should agree. If the article's publication year differs from the issue year, OJS outputs only the issue year.
• Consistent author names: given and family names in the correct OJS fields, spelled and ordered the same way in OJS and on the PDF, issue after issue. Inverted, abbreviated or misspelled names split an author's citations in Scholar. Encourage ORCID iDs.
• One language per field: enter metadata in the language of the full text. Don't put "Indonesian title / English title" into one field; use OJS's multilingual fields instead. PKP notes that Scholar indexes an article in its primary language.
• Stable URLs: never rename the journal path or switch domains without article-level 301 redirects. Redirecting every old article to the homepage loses them from Scholar.

PKP's Google Scholar guide for OJS covers these metadata issues in more detail.

How to check what Google Scholar has indexed

1. Search exact titles

   Search a few article titles in quotation marks on Google Scholar. Google itself says this is the reliable check, more reliable than counting site: results.

2. Search by journal name

   In Scholar's Advanced search, use "Return articles published in" with your journal title to list what Scholar has attributed to you.

3. Confirm the meta tags

   Open an article page, view the page source and search for citation_. No tags means the plugin is off or your theme is not outputting the page head correctly.

4. See what Googlebot sees

   Hacked OJS sites sometimes show spam only to search engines. Fetch a page with a Googlebot user agent and compare it with what you see in the browser.

curl -s -A "Googlebot" https://journal.example.org/index.php/jmr/article/view/123 | grep -i "citation_"

Why articles are not showing in Google Scholar (and fixes)

If you have worked through this table and articles are still missing, our OJS SEO and Google Scholar audit checks crawlability, metadata, PDFs and server behaviour, then fixes what is wrong.

How long Google Scholar indexing takes

Google gives only broad ranges, and so should anyone advising you:

• New articles: typically a few days to several weeks after Scholar's crawler finds them. A brand-new site may take longer to be discovered in the first place.
• Corrections to already-indexed articles: usually six to nine months, according to Google's guidelines.
• Large back-file uploads or migrations: can take many months, and longer if the server responds slowly.

There is no way to request faster indexing, and Google says it cannot make exceptions for individual sites.

Google Scholar Metrics (h5-index) basics

Google Scholar Metrics ranks publications by their h5-index: the largest number h such that h articles published in the last five complete calendar years each have at least h citations. The h5-median is the median citation count of those top articles.

• Each release covers the five most recent complete years (the release based on Scholar's July 2025 index covers 2020–2024).
• A publication is only included if it published at least 100 articles in that five-year window and received at least one citation. That works out to an average of 20 articles a year, so many small journals are indexed in Scholar but have no Metrics page.
• There is no application. Metrics are calculated automatically from what Scholar has indexed.

An h5-index is not an "impact factor". Journals that advertise a "Google Scholar impact factor" are misleading their authors.

Beware of fake "Google Scholar indexing services"

Because Google Scholar has no application process, anyone claiming to "submit" or "register" your journal with Google Scholar is offering something that does not exist. Red flags:

• "Google Scholar indexing certificates", approval letters or badges. Google does not issue them.
• Guaranteed indexing "within 7 days" or promises of a minimum number of citations.
• Claims of partnership with Google or "priority submission" to Scholar.
• Offers to boost citations through citation exchanges or self-citation rings. These distort your metrics and damage your reputation with selective databases.
• Creating a Google Scholar profile for the journal. Scholar profiles are designed for individual authors and do not make a journal "indexed".

Legitimate help is purely technical: fixing metadata, PDFs, robots.txt, redirects, speed and security, then letting the crawler do its work.

Google Scholar indexing checklist for OJS

• Google Scholar Indexing plugin enabled in every journal; citation_ tags visible in the page source.
• Journal sitemap opens as XML and is submitted in Google Search Console with status Success.
• robots.txt does not block article, download, issue or archive URLs.
• Every article has its own landing page with the full abstract as text.
• One text-based PDF per article, under 5 MB, uploaded to OJS (not linked from elsewhere).
• Title, authors and dates identical in OJS metadata and on the PDF's first page.
• HTTPS works, the site is fast and stable, and old URLs redirect with 301s.
• The site is patched and free of injected spam.

Google Scholar is the foundation. Once it works, the next milestones are usually DOIs and DOAJ (for open access journals); see our DOAJ indexing guide. For a full technical review of your journal's search visibility, explore our OJS SEO services.

Frequently Asked Questions