Analytics tells you which pages people visited. It doesn’t tell you what they wanted and couldn’t find.
Your search box does. Someone typing into it has bypassed your navigation entirely and described what they came for in their own words, unprompted, with no survey and no incentive. It’s the cleanest signal about demand you’ll ever get from your own site, and on most sites it’s thrown away.
Fetchie keeps it.
What you see
The Insights tab shows four things.
Volume. How many searches ran over the period. On its own it’s a health check, but the trend is where the value is. Search volume climbing while traffic is flat usually means your navigation has stopped working for people.
Top searches. The queries people run most, with counts. This is the list that tells you what your site is really about, as opposed to what you think it’s about. It’s frequently a surprise.
Searches that found nothing. The queries that returned an empty page. This is the most actionable list in the plugin, and it has its own place in the interface for that reason.
The log itself. Every search as it was typed, newest first, with the time and the number of results it found. The summaries above it answer "what is the pattern"; this answers "what did that person actually type", which is the question you want when a single odd search catches your eye.
What people do with it
Stock and range decisions. A search term appearing forty times a month for something you don’t sell is a demand signal that cost you nothing to collect. It’s also the cheapest possible market research: these are people who came to your site specifically expecting to find it.
Naming. You call it a "consultation". Every visitor searches for a "quote". You aren’t wrong and neither are they, but their word is the one that should be on the page, in the heading, and in the navigation. Search logs surface this mismatch faster than anything else, because you see the volume behind it.
Content planning. Recurring questions that only get a partial answer on your site are a content brief written by your own visitors. You don’t have to guess what to write next.
Navigation. If a page has a spike of searches for it, people can’t find it by clicking. That’s a menu problem, not a search problem, and search is how you find out.
Support load. On a store with a helpdesk, the same questions turn up in both places. The searches that find nothing today are the tickets you get tomorrow.
The dashboard widget
There’s a "Fetchie this week" widget on the WordPress dashboard, so the headline numbers are in front of you when you log in rather than behind a tab you have to remember to open.
Most site owners will never go looking for search data on purpose. Putting it on the dashboard is the difference between insight that gets used and insight that sits in a table.
Where the data comes from
Searches are logged as they run, while recording is switched on. It’s a toggle under Settings, Features, on by default, and turning it off stops the writing rather than just hiding the report.
There’s no tracking script, no third-party service and no external request, because the data was already passing through your own site.
Queries are recorded without any visitor identity attached. Fetchie stores what was searched, not who searched it, and the log is capped to a retention window you choose. It’s aggregate demand data, and it’s deliberately built so it can’t become anything else.