Block Bad Queries Pro keeps a detailed log of every request it stops: the request URI, query string, rule that fired, IP address, user agent, and timestamp. The plugin's log viewer is a paginated list, good for spot-checks and slow when the question is about a specific IP across the day or a specific rule across the week.

SleekView reads the BBQ log table directly. Sort by timestamp to see the last hour. Filter by rule name to follow a signature, by IP to follow one offender, by URI to find the targeted endpoints. The same data shows up in saved views the team reopens with one click instead of rebuilding the filter set every morning.

BBQ keeps owning the rules and the request-time decisions. SleekView only adds the triage surface, so the rich log BBQ already writes becomes a queryable workspace inside WP Admin.

Block Bad Queries does the blocking, but the log it produces is only useful when somebody actually reads it. A paginated viewer is fine for incident response, less so for the weekly question of whether the rule set is working. SleekView reads the same log table BBQ writes and renders it as one sortable, filterable workspace.

The plugin keeps owning the rules, SleekView just turns the log into a queue the security team can scan in seconds. Saved views travel with the site, filtered rows export as CSV for monthly reports, and one analyst can hand the daily review to another without rebuilding any filter set.