Situation

We have a need to accurately report on what visitors are searching for on our website. However our website contains a lot of pages which have search content. So for example page X has a search web part that list of all content types Z another page filters on other indexed columns and so on. As a result we are seeing an enormous amount of searches which include "page clicks". The queries per search term far outweigh any realistic values. eg we only have around 100 visitors a day yet search terms are recording 1000 queries per day.

Is their any way to get more granular analytics for search queries? For example, to only show queries from page "a" and page "b"?

Hi,

We are currently looking into this issue and will give you an update as soon as possible.

Best Regards,

Dean Wang

Hi,

Would you please describe your requirements more specifically? In SharePoint 2013, all the search result analytic reports are linked to database, and you can use SQL or PowerShell to query what you want. The following article may contain useful information for your requirement:

http://blogs.msdn.com/b/nathan_brackett/archive/2014/07/03/search-reporting-and-sharepoint-2013-introduction.aspx

Thanks,
Reken Liu

Hi Reken,

Problem

The SharePoint 2010 search analytics for queried terms have impossibly high counts. Why do I call it impossible? Because we only have 100 visitors a day yet 1,000 search queries a day are being logged. Hence the daily search queries are impossibly high.

We need to be able to get the current accurate analytics right now from our 2010 farm for the past 12 months of search queiries so we can improve our website. (promises of SP2013 are not helpful at all)

Possible cause of the problem?

We have written a custom content search webpart which allows us to roudup content from across the whole site on certain pages. eg show all content type X and filter by an indexed column. By default this search web part has a default search which includes a default filtered value (show all).

Possible solution?

If the cause is our custom content search web part. Can we filter out queries from those pages where queries origionate from our custom content search web part? This would hopefully allow us to get a more accure picture of what people have previously searched for.