Yes. The plugin keeps a short recent-blocks log alongside its rule lists in option keys. SleekView indexes those values into queryable rows so the four chart cards stay populated even on a fresh install, without any add-ons or custom logging code on the site.

Country Blocker logs the blocked requests it rejected. Allowed traffic does not land in the same log because the plugin lets it pass without recording a row. The dashboard therefore focuses on the blocked side, which is also where the policy questions live.

Yes. The block log captures the request URI alongside the country code, so a Stacked Bar card grouped by country_code with request_uri as a series shows whether a single country mostly hits wp-login.php, xmlrpc.php, or specific endpoints exposed by the site.

No. Charts read from the existing Country Blocker option keys and never write to them. The plugin continues to evaluate the country list and reject requests exactly as before, with no added load and no changes to its own runtime behavior on the site.

Yes. Each card supports CSV export of its aggregated values, and the underlying SleekView grid is one click away for the raw block rows behind any chart. Useful for sharing geo block summaries in a monthly security review or a client report.

No. Rule edits live inside Country Blocker's own settings screens. The dashboard is intentionally read-only so the visual layer never modifies the country lists or interferes with the plugin's runtime rejection behavior on incoming requests.

Yes. Country Blocker stores its data per blog, and SleekView respects that scope. A network admin can build a per-site dashboard or one network-wide rollup that ranks sites by daily blocked volume or by the top blocked nation across the entire network.

The chart settings reference indexed log fields. Moving to another geo plugin means pointing the same chart card definitions at the new source. The visual layout, the saved date ranges, and the role-scoped dashboards survive even if the underlying blocker is swapped out.