How can I let Google Scholar index some of my documents, but not provide public access? Preventing the public viewing a content type is easy, in Drupal permissions, but this locks out Google Scholar too.

Comments

gisle’s picture

You can't.

This is not only a technical limitation, it is a policy one. Google Scholar will not index anything that is not accessible to the public.

iantresman’s picture

I believe that Google Scholar will index articles that are available by subscription only, as implied here and here. As they say, only a publicly accessible abstract is required.

In 2009 they explained to me how to prepare Google Scholar meta data, and give their crawlers access.

gisle’s picture

Thanks for the heads-up!

I see that I may have misunderstood the checklist Google provides you when you request an inclusion of "Other repository". The third item they list is: "All article URLs can be read by any user without a login or payment" (it is a "required field"). I interpreted this as a policy statement.

However, when I read the letter from Google Scholar you linked to, I see that it says that they will index your stuff if you just allow Google's crawler to pass through your login-wall (e.g. filtering on IP-adress range).

If that is correct, I was wrong. I.e.: you can get Google Scholar to index a non-public file.

As it happens, I've recently uploaded a Google Scholar abstract generator to contrib here on Drupal.org.

If you're interested, please take a look at it. If nobody responsible for the Bibilography module responds to your support request, maybe this can be moved to Google Scholar abstract as a feature request?

iantresman’s picture

Thanks for the update. I suspect I will wait until I've updated my sites to Drupal 8 (and jump D7), at which point your modules may come into their own. I also suspect that D8 may be easier to customise, allowing features such as "access by IP address", I guess similar to "Restrict IP".

liam morland’s picture

Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.