Detailed Query Logs

The Detailed Query Logs provide a granular look at the specific interactions between your visitors and the AI Search Block. While aggregate analytics offer a bird’s-eye view of performance, the raw query logs allow administrators to perform a deep-dive analysis into exact phrases, user behaviors, and the resulting AI-generated responses. By monitoring these logs, you can bridge the gap between user intent and content availability, ensuring your knowledge base remains relevant and comprehensive.

• Understanding the Search Queries Log
• Key Data Points Captured
• Advanced Filtering and Timeframes
• Troubleshooting AI Responses
• Frequently Asked Questions

Understanding the Search Queries Log

The Search Queries tab within the AI Search Intelligence module serves as a definitive audit trail for your search block’s activity. Unlike the , which focuses on trends and totals, this log records every single transaction in real-time. This level of transparency is essential for high-traffic sites where understanding the nuance of user language can lead to better content strategies.

Each entry in the log represents a specific search event. By reviewing these logs regularly, site owners can identify “content gaps”—topics that users are searching for but which the AI may not be adequately answering because the information is missing from the .

Key Data Points Captured

The system records several critical pieces of metadata for every search query performed. This information is displayed in an easy-to-read table format:

• Search Query: The exact phrase or question typed by the user. This is preserved in its raw form to help you understand natural language patterns.
• Date and Timestamp: The precise moment the query was executed, allowing you to correlate search spikes with marketing campaigns or site updates.
• User Identity: If the user is logged into your WordPress site, their username or ID is recorded. For guest users, the system typically records them as anonymous, helping maintain privacy while still tracking usage.
• Response ID/Status: A unique identifier for the AI’s response. This status indicates whether the AI successfully generated an answer or if it encountered an error (such as an API timeout or a moderation block).

Advanced Filtering and Timeframes

As your search history grows, finding specific information requires robust filtering tools. Antimanual includes built-in options to narrow down the log entries based on your specific needs:

Keyword Filtering: You can search the logs for specific terms to see how often they appear. For example, filtering for “pricing” or “refund” can show you exactly how users are phrasing their financial concerns.

Date Range Selection: This feature allows you to define a specific timeframe for analysis. This is particularly useful for measuring the impact of new documentation releases or analyzing search volume during a specific promotional period.

Troubleshooting AI Responses

One of the most powerful applications of the Detailed Query Logs is quality control. If a user reports a “bad” answer, you can locate the exact query in the logs and examine the Response ID. By cross-referencing this with your , you can determine if the issue was related to the AI model used, the instructions provided, or a lack of source material in the knowledge base.

Practical Example: If you notice multiple queries for “How to install the Pro version” returning a status of “No information found,” you can immediately go to the Knowledge Base and upload the relevant PDF or URL to satisfy that user intent in future searches.

Frequently Asked Questions

Are user IP addresses stored in the logs?
By default, Antimanual focuses on user identity via WordPress accounts to ensure privacy compliance. IP logging depends on your specific server configuration and security plugins.

How long are query logs kept?
Logs are stored in your WordPress database. You can manually clear them or set retention policies depending on your database management preferences to ensure site performance remains optimal.

Can I export these logs for external analysis?
Yes, query data can be exported via the analytics dashboard tools, allowing you to process the raw data in spreadsheet software for deeper business intelligence.