Hi All, I just wanted to chime in here and note that I continue to have yearly meetings with the Google Scholar team to touch base on how DSpace sites are being indexed "in the wild". As of yet, they have not brought me any general concerns specific to DSpace (which is normally what they do when they realize there's a common issues affecting many DSpace sites).
That doesn't necessarily mean there's not issues affecting many DSpace sites, but it does mean that Google Scholar may not realize whether a specific issue is common or not. When they realize there's a common issue, they always reach out to me to get a bug ticket created so that it can be resolved quickly. There are so many factors that may impact indexing these days, including whether sites are accidentally blocking or limiting access Google Scholar bots. For example, last year I did hear from Google Scholar that they were finding some DSpace sites that were accidentally blocking the Google Scholar bots while attempting to deal with bad-behaving AI-related bots. So, these days, it's also possible for indexing problems to be related to firewall issues or other bot-management tools/services that are in front of your DSpace. Overall, my primary recommendation is two things: 1. First, double check that you are following *all recommendations* of our SEO guide. These recommendations were created in conjunction with the Google Scholar team: https://wiki.lyrasis.org/display/DSDOC9x/Search+Engine+Optimization If you've missed or ignored one recommendation, then it may decrease the indexing of your site in Google Scholar. 2. Second, please also reach out to Google Scholar directly if you are having continued issues. They may be able to narrow down the problem for you... it could be DSpace-related, or could be something else that blocking or slowing down their bot. If it turns out to be DSpace-related, then Google Scholar will report back to us any common issues they are seeing so that we can create a bug ticket & get them solved in future versions of DSpace. Overall, I wish there's more advice we can offer here. But, we don't control how/when Google Scholar indexes your site, and cannot debug indexing issues they may be having. Only Google Scholar can do that, and they will report back to us if there's ways to improve DSpace to further improve/streamline indexing. Thanks, Tim On Thursday, March 26, 2026 at 8:28:06 AM UTC-5 [email protected] wrote: > 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/8d1c3d67-9378-4ed9-94d2-28bb99f885can%40googlegroups.com.
