[Archivesspace_Users_Group] Google, etc indexing and searching

[Kevin Clair]

Hello,

I know that our public site is indexed, and there doesn’t seem to be a limit to how far down into a resource tree it will index, as long as the records are published. Here’s a sample search from our public site: https://www.google.com/webhp?hl=en#hl=en&q=marjorie+hornbein+site:duarchives.coalliance.org  -k

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Flanagan, Patrick" <PJFlanagan at ship.edu<mailto:PJFlanagan at ship.edu>>
Reply-To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Monday, February 1, 2016 at 12:41 PM
To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Google, etc indexing and searching

Good afternoon,

I’m relaying a question by a member of the Keystone Library Network in regards to how data in ArchivesSpace is crawled and indexed by search engines (Google, Yahoo, et. al)

“Are AS records searchable via Google and other search engines down through the component level? I searched some terms on VMI’s AS pages and they all came up in a Google search right at the top. However they did not have any components, they were all upper-level titles or scope and content notes. As far as you know, are AS records searchable down through the lowest levels of a finding aid?”

I don’t think our instances are being indexed yet, so I have no way of knowing for sure. Is there a limit to how deeply the site is indexed and if so, is there any way to influence the depth of the search?

Thanks for your time,

~Patrick Flanagan
KLN Applications Administrator
Keystone Library Network
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160201/274d5f7e/attachment.html>