Start here in the Get Started sequence: This is article 1 of 5. Start here to understand why analytics should guide relevance decisions before you choose scope, run a workflow, or tune features.
Analytics matters for relevance because it shows what people search for, what they click, and where search is falling short. You can use that data to choose the next tuning task based on impact instead of guesswork.
Why This Comes First
If you tune relevance before you understand user behavior, you can spend time on low-impact changes. Starting with analytics gives you a repeatable way to decide what to fix first.
Analytics Turns Relevance into a Measurable Process
Search relevance isn't a one-time setup task. It improves through repeated analysis and tuning. SearchStax Site Search gives you analytics pages to measure behavior over time and track progress.
Start with the Dashboard for a high-level view, then use the Searches page for deeper query-level analysis.
How Analytics Reveals Relevance Problems
Relevance issues usually show up first in a few key metrics:
- Click-Through Rate: How often a search leads to at least one click.
- % No Results: How often users get zero results.
- Average Click Position: How far down the results list users go before clicking.
- Searches with No Clicks: Where users saw results but didn't engage.
Use these metrics to spot patterns that point to relevance or content gaps.
Why Query-Level Analytics Matters
Aggregate metrics show overall performance. Query-level data shows what users are actually trying to do.
- Most Popular Searches: The topics users ask about most often.
- No Result Searches: Unmet user intent and likely content or tuning gaps.
- Search Details: Which result items users clicked for a specific query.
- Searches with No Clicks: Queries where results were returned but users didn't find a useful option.
These views help you prioritize relevance work by frequency and user impact.
Why Shared Definitions Improve Team Decisions
Relevance work moves faster when marketers and technical teams use the same metric definitions. Use the Analytics Glossary as a shared reference for terms like click-through rate, searches with clicks, and average click position so your team can evaluate issues the same way.
Use Analytics as an Ongoing Relevance Feedback Loop
Analytics tables and graphs refresh hourly, so give changes enough time to produce meaningful data before you compare results over a similar time period.
This process helps you measure impact and plan the next iteration. It keeps your relevance strategy tied to user behavior instead of assumptions.
Next Steps
Next, read Understand Analytics at the App, Profile, and Language Levels (article 2 of 5). It explains how to choose the right scope so your metric comparisons are valid before you act on them.