By the standard HTML meta tags in your pages (including SharePoint ones) – e.g. Title, Keywords, Description, Robots, etc is reasonably common. Apart from these you can use custom meta tags (specifying custom values in the name attribute) to define (or extend) your custom meta data for the page. These can be crawled by search engines including the SharePoint search engine and can be used for various filtering and sorting purposes when by the search functionality. Normally in SharePoint the list item (publishing pages are list items) meta data is stored in the list items’ fields but there are cases in which storing meta data in HTML meta tags may have some advantages.

First off – HTML meta tags can be made relatively simple – you can place a custom control in your master page (pages) which outputs the meta tags in the HTML of your pages, an even better solution here is to use a delegate control. So, basically with a single control you ensure that all your pages contain your set of custom meta tags. A particularly excellent scenario for the meta tags made in this way is when you need them for meta properties whose values can be easily generated or calculated based on other meta data (like list fields) or certain criteria. For example these can be the URLs of the pages or the type of the parent web, etc. In the case of such calculable meta properties you can imagine the overhead of making auxiliary list fields and maintaining them in all your page libraries compared to the clean deal with of the custom web control that generates all meta data in a single piece of code.

A recent example of by meta tags with SharePoint search that I had was for a solution where I needed to show the rollup image of every page in the search consequences. The problem with the publishing rollup image (really with the publishing image field type) is that it stores its value as HTML markup (a single HTML img element with several attributes) and the SharePoint crawler austerely ignores all HTML markup. The result is that you have your image field containing the source of the image file but the search service just can’t get it for you. A possible solution that I have seen for this problem is to make an additional field that will be populated with just the path of the image file by a list item event receiver for updating it when the rollup image field gets changed. The thing is that implementing and maintaining this is not so simple and not that economically looking.

Here is a small code snippet to demonstrate a simple way to generate the meta tag HTML for the standard rollup image source attribute:

The crawl properties that the SharePoint search crawler makes for the custom HTML meta tags are in the Web crawled properties category – they are with the same name as the name of the custom meta tags – just uppercase. These can be made with code too – the ID of the propset for the meta tag crawled properties is d1b5d3f0-c0b3-11cf-9a92-00a0c908dbf1 (this is really the ID of the meta tag Web crawled properties subcategory). The last step before you can use the meta tag crawled properties is to make managed properties mapped to them.

Check it out:Stefan Stanev’s SharePoint blog