search-insights

Search Insights

Analyze internal site search to understand what visitors are looking for and identify content gaps.

Site selection

If $ARGUMENTS contains a site ID or name, use that. If the conversation already has a site in context, use that. Otherwise, call matomo_list_sites, present a short numbered list (ID, name, URL), and ask which site to analyze. Do not proceed until a site is selected.

Steps

1. Top search keywords using matomo_get_search_keywords with limit 20 for the requested period (default: last 30 days, period: day, date: last30)

2. Failed searches using matomo_get_search_no_results with limit 20 for the same period

3. Present findings:

   • Most searched terms (table: keyword, searches, results found)
   • Top failed searches (terms with no results) as content gap opportunities
   • Patterns: are visitors searching for things that should be easy to find?
   • Recommendations: which content should be created or made more discoverable

If $ARGUMENTS contains a specific keyword, focus analysis around that topic.

If the user asks about mobile-only search behavior, pass device: "mobile" to both calls above to scope the analysis to smartphone+tablet+phablet traffic.

Fallback when segments return zero

If a device-filtered call comes back with all-zero metrics while the same query without device returns normal numbers, the Matomo server is refusing to aggregate the segment for this API token (it lacks process_new_segment or the segment isn't pre-archived). Do not claim "no mobile traffic" — that's almost never the real answer.

Try these in order:

1. Switch to matomo_count_visits_by_segment. It uses the Live API under the hood and does NOT need segment archiving. For mobile: {siteId, period, date, device: "mobile"} returns {visits, byDevice, byCountryTop10}.
2. Check matomo_list_segments to find saved segments on the instance. Any segment with auto_archive=1 is pre-archived and will always return real numbers when you reference its definition string in segment.
3. Open the Matomo UI in a logged-in browser session as a last resort.
4. Longer-term fix: ask the Matomo admin to grant process_new_segment on the token or pre-archive common segments.