It seems this is a general issue affecting some DSpace repositories. Below are a few repositories that appear, based on what we can see, to be poorly indexed in Google Scholar, and we cannot understand why: Cambridge University Library: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Awww.repository.cam.ac.uk&btnG= Kyoto University's: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepository.kulib.kyoto-u.ac.jp&btnG= UDESC: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepositorio.udesc.br&btnG= Harvard DASH: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Adash.harvard.edu&btnG= National University of SIngapore: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Ascholarbank.nus.edu.sg&btnG= Fraunhofer-Publica: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Apublica.fraunhofer.de&btnG= Infocience: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Ainfoscience.epfl.ch&btnG= King Abdullah University of Science & Technology: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepository.kaust.edu.sa&btnG= UNSW: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Aunsworks.unsw.edu.au&btnG= UGSpace: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Augspace.ug.edu.gh&btnG= Makerere University Institutional Repository: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Amakir.mak.ac.ug&btnG= UPSpace: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepository.up.ac.za&btnG= University of Nottingham Repository: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepository.nottingham.ac.uk&btnG= ReIn UW: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepozytorium.uw.edu.pl&btnG= I also include some repositories that seem to be working properly:
Universidad de los Andes: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepositorio.uniandes.edu.co&btnG= UNAL: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Arepositorio.unal.edu.co&btnG= Jagiellonian University Repository: https://scholar.google.com/scholar?hl=es&as_sdt=0%2C5&q=site%3Aruj.uj.edu.pl&btnG= Chalmers Open Digital Repository: https://scholar.google.com/scholar?start=0&q=site:odr.chalmers.se&hl=es&as_sdt=0,5 I am aware that the "site:" search does not fully represent what is indexed in Google Scholar, but in many cases there is not even a single item indexed, and this does not seem to be the expected behavior. It is also worth mentioning that I did not include any older repositories, but in general, DSpace 5/6 repositories tend to be well indexed, or at least within acceptable ranges. El lunes, 23 de marzo de 2026 a las 21:44:32 UTC-3, Annabel Gooder escribió: > We’ve also had issues with Google Scholar indexing since we upgraded to > DSpace 7 in December 2024. It lost a large number of our records, and while > it seems to be adding new records ok it hasn’t recovered a significant > number of the lost ones. We’ve since moved to DSpace 8, but it hasn’t > helped. > > > Ngā mihi > > Annabel > > > > *Annabel Gooder* > > *Digital Library Specialist* > > Te Kahu Tauira | Student and Scholarly Services > > Waipapa Taumata Rau | University of Auckland > > On Tue, 17 Mar 2026 at 03:50, Rafael Bértoli <[email protected]> > wrote: > >> Hello, >> >> We have noticed that Google Scholar is not properly indexing the items in >> the repository we manage using DSpace 7: >> https://digital.cic.gba.gob.ar/home. Currently, only about 20% of the >> publications appear as the canonical version, while in some cases they are >> listed only as alternative versions of the work. >> >> This issue is of critical importance for us because we have a migration >> to DSpace 9 of another repository ready to be deployed in production. >> However, we are concerned about potentially losing visibility in Google >> Scholar, so we started investigating other repositories running DSpace >> 7/8/9. >> >> As a general observation, most repositories we checked using DSpace 7/8/9 >> either did not appear in Google Scholar searches at all or had very low >> indexing coverage. The few repositories we found with a good indexing rate >> appeared to be very similar to those that were poorly indexed, at least in >> terms of meta tags. In some cases, the well-indexed repositories seemed to >> have more extensive visual customization, but this should not affect Google >> Scholar indexing. >> >> At this point, we have not been able to reach any clear conclusion from >> our investigation. We cannot determine whether this is an issue related to >> DSpace in its newer versions (7/8/9) or simply an indexing behavior on >> Google Scholar’s side. >> >> We are also aware of the issue reported on GitHub: >> https://github.com/DSpace/dspace-angular/issues/4509. However, it does >> not seem that the absence of this element alone fully explains the indexing >> problem. >> >> Does anyone running a repository on these versions have good indexing in >> Google Scholar? If so, did you need to apply any specific configuration >> changes, or did the repository get indexed correctly without additional >> adjustments? >> >> Thank you in advance. >> >> -- >> > All messages to this mailing list should adhere to the Code of Conduct: >> https://lyrasis.org/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion visit >> https://groups.google.com/d/msgid/dspace-tech/a615ca20-8319-47f1-90fb-c5f367414b2fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/dspace-tech/a615ca20-8319-47f1-90fb-c5f367414b2fn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/52774a3d-5b6a-414b-b035-9dedace2e046n%40googlegroups.com.
