Quick Tips for Improving Search in SharePoint 2010
How much time have you spent looking for a document within your SharePoint site? You can’t remember the name, location, or even much about it, but you know you need it. Maybe it’s an HR form or maybe it’s an RFP. You don’t have much to go on, but you do know some general facts surrounding it.
Welcome to the world of poorly designed document structure within SharePoint. If it’s true that time equals money, then the time you spend looking for documents is actually costing your company money. There is a perception that as more documents get added to a SharePoint site, it becomes a black hole with search becoming a useless function due to the overwhelming amount of returned.
While this may be a problem for some, if not most, it doesn’t need to be the fate for your SharePoint. With a few simple guidelines offered by SharePoint Server MVP John Ross, you can learn how to improve search relevancy within SharePoint 2010; and the best part…it’s all out of box functionality! No code, no add on’s, no 3rd party vendors.
#1 Put more important documents near the root of the site, less important documents farther down the hierarchy. They say the cream always rises to the top, and with search the same is true. There are many factors that work together to determine the relevancy of a document but one rule of thumb is that the deeper the document is buried in your hierarchy the less relevant SharePoint is going to assume the document is in comparison to a similar document closer to the root. As a rule of thumb, the less “/” in a URL to a piece of content the more relevant it is. For example a document at http://sales/sharepoint-presentation.docx would be considered more relevant that http://sales/products/sharepoint-presentation.docx.
Just remember that you can use this to your advantage. Less important documents and sites can be nested deeper in your hierarchy and more important ones can be closer to the top.
#2 Use natural language for site and file names. Among the easiest and most effective things people can do to improve search relevancy is to name their sites and files effectively.
Look at these two URLs:
The first document has a URL which has actual words used for the sites and document where the second one has some shorthand for the sites and document names. The first one is far more effective because the URL and file names for a document in SharePoint are a heavily weighted component of the relevancy algorithm. If you were to type a search query of “sales presentations widgets” SharePoint would be able to determine clearly that the first document was relevant to the query. Although the second document might have some of those words typed somewhere in the content, and would likely still show up somewhere in the results -- the first one will be considered more relevant simply because of the way it is named.
It should also be noted that in order for this to work as effectively as possible it is important to NOT run your words together. This is because SharePoint doesn’t know where words break unless you’ve got something between them that it identifies as a “wordbreaker.” Although spaces are recognized as a word breaker in SharePoint, my recommendation is to use “-“ between words instead. The main reason for this is because if you use spaces in things like site or page names when SharePoint will automatically remove them and you’ll lose out on the relevancy benefit you’d get otherwise. Other common word breakers that get used are things like underscores (_), periods, semi-colons. If you happen to be using these, they are also all valid word breakers.
#3 Supply metadata for your files. If you are not’t familiar with the term metadata it basically means “data about data.” If you were talking about a car some common pieces of metadata would be make, model, color, mileage -- think about the types of things you’d use to find a car on a web site. All of those pieces of data describe the car; they are its metadata.
For your files in SharePoint, by tagging them with descriptive metadata you can make it easier for your users to find what they are looking for. Remember, that metadata is always going to carry a heavier relevancy weight than content in the body of a document.
How much metadata do you need? Generally I recommend 5 to 10 fields that would be useful for categorizing a file. Common examples would be: department, product name, type of document, client, etc. The key to metadata is that it needs to be clear and consistent. Here are a few metadata recommendations:
Use managed metadata fields, choice, or lookup fields so your users don’t have to manually type in metadata to ensure consistency.
Make as much of it required as possible - if you don’t your users likely won’t fill it out!
Resist the temptation to add too many fields. The idea is to make it easier for your users to find things, not make them have to take an hour to upload documents.