Hello,

In 8.1 and 7.6.2 a new feature was added that enables SSR only for certain
pages
<https://wiki.lyrasis.org/display/DSDOC8x/User+Interface+Configuration#UserInterfaceConfiguration-ServerSideRendering(SSR)Settings>
.
The default values should be fine, I just tested it with 8.1 images
(backend and frontend) and it is working on the necessary pages for Google
indexing.

You can test whether your instance has SSR enabled for the item pages by
either disabling Javascript temporarily in your browser
<https://developer.chrome.com/docs/devtools/javascript/disable> or
executing a *curl <url to item page>* in a terminal.

If in either case you are unable to view the item page, the issue may be
with your SSR configuration or how you are starting/deploying the front-end.


Em sex., 6 de jun. de 2025 às 03:59, Vicente Zapatero Martin <
[email protected]> escreveu:

> Hi all,
>
> We experimented the same issue but in version 7.6.2, I know I must upgrade
> to last version to improve in everything. I have followed the search
> optimizations: robots, host headers behind proxy,... We have read the brief
> guide from Google Scholar too. We sent email to Google Scholar support too.
>
> This is not a complaint to the dspace team that makes a great job. We need
> more info about google scholar behavior. In a couple of weeks we are
> missing from search results first. Few days ago, we surprisingly we have
> reappeared and now we are completly dissapeared. What kind of joke is this?
> Any more tips?
>
> I don't want to just sit and wait or even pray to "Google Scholar God".
>
> Thanks a lot.
>
>
> El miércoles, 4 de junio de 2025 a las 18:54:12 UTC+2, DSpace Technical
> Support escribió:
>
>> Hi all,
>>
>> You should check our Search Engine Optimization guidelines for DSpace 8,
>> which were written based on feedback from the Google Scholar team.
>>
>> https://wiki.lyrasis.org/display/DSDOC8x/Search+Engine+Optimization
>>
>> Especially make sure that your robots.txt looks correct, and that your
>> Sitemaps are enabled & working.  You also should verify you are running in
>> production mode, which ensures that server side rendering is enabled (as
>> this is required for search engine bots).
>>
>> Assuming you've followed those guidelines, there should be no issues with
>> indexing your DSpace 8 site in Google Scholar.  In that scenario, you also
>> could contact Google Scholar via their troubleshooting guidelines at
>> https://scholar.google.com/intl/en/scholar/inclusion.html#troubleshooting
>>
>> Tim
>>
>> On Wednesday, June 4, 2025 at 10:05:51 AM UTC-5 [email protected]
>> wrote:
>>
>>> Dear Ezequiel and all,
>>>
>>> I’m experiencing the same issue after upgrading our repository to *DSpace
>>> 8*. It's been over *three months* since the migration, and Google
>>> Scholar has *not resumed indexing* our content. Additionally, several
>>> records that were previously indexed now appear to be *missing from
>>> search results*.
>>>
>>> I’ve reviewed the sitemap and robots.txt configurations, which appear
>>> correct, and the repository is accessible publicly. It would be helpful if
>>> anyone who has resolved this issue or has insights into potential causes
>>> post-DSpace 8 upgrade could share their experience.
>>>
>>> Best regards,
>>> Wael
>>>
>>>
>>>
>>> On Sat, 31 May 2025, 02:48 Ezequiel Esposito, <[email protected]>
>>> wrote:
>>>
>>>> Hello! After a few days of beeing down our repository, google scholar
>>>> stop indexing it and the records that already have been indexed seem to be
>>>> missing.
>>>>
>>>> What could be happening?
>>>>
>>>> --
>>>> All messages to this mailing list should adhere to the Code of Conduct:
>>>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>>>> ---
>>>> 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/2a9a8353-bc78-4dc1-a816-0a87d035c82dn%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/dspace-tech/2a9a8353-bc78-4dc1-a816-0a87d035c82dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> 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/98c91ecb-8e2b-4c2c-8a06-98b650676c69n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/98c91ecb-8e2b-4c2c-8a06-98b650676c69n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/CANSAG053dfWW%2BD4PjXR4gedWV1kcAUOrA0CxU8AcHJHrygjtXg%40mail.gmail.com.

Reply via email to