-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation on new and improved process of making Dataverse indexed by Google and other search engines #5639
Comments
…e installation for indexing by search bots. (#5639)
I checked in the documentation for the new process now in use in production. |
With much input from @landreev and @pdurbin, I was able to confirm in my work for #5637 that the images directory, which contains the favicon images, needs to be added to the
|
Also, as part of feedback investigations for #5641, I discovered there is a problem with the social media robots accessing dataset thumbnails that I was not able to resolve. This needs to be addressed as part of that thumbnails issue, or this robots.txt issue. See the warnings produced by the Twitter developer tool card validator.
|
…e twitter/facebook/linkedin preview cards. (#5639)
This is the knowledge that was acquired after we reopened the site to Googlebot; and addressing reports of datasets not being properly indexed by owners (issue IQSS/dataverse.harvard.edu#1).
The new approach is a combination of advertising the datasets and dataverses that we want to be indexed, and blocking the robots from actually crawling the site (i.e., discouraging them from following the URLs of the facets and pages of search results). It appears to be much more efficient and produces better search results. Explaining it in the guide will benefit other Dataverse installations.
The text was updated successfully, but these errors were encountered: