Tutorials and common workflows

Safely test the three-strike workflow

1. Export current strikes if the site already has active records.
2. Use Testing Tools → Add Test Strike and confirm one Activity Log entry.
3. Repeat until the configured limit is reached and confirm the blocked experience.
4. Open Strike Management and clear the controlled record.
5. Reload the front end and confirm access is restored.

Resolve a false positive

1. Open Activity Logs and locate the affected page, address, browser identification, reason, and signals.
2. Confirm the traffic belongs to a person or service you recognize.
3. For a one-time mistake, clear its strikes. For a stable trusted address, add a temporary whitelist entry first.
4. If the same legitimate service repeats, use a narrow trusted-service pattern or provider-supplied IP range.
5. Reproduce the visit and confirm no new strike appears.

Determine whether Cache Compatibility Mode is needed

1. Leave Standard mode active, clear all page/CDN caches, and perform a controlled suspicious visit to a normal HTML page.
2. Warm the page cache, repeat the visit, and compare Activity Logs.
3. If only the uncached request appears, enable Cache Compatibility Mode and clear caches again.
4. Repeat the cached visit and confirm one document request creates one strike.
5. Reach the limit and confirm the blocked overlay. If the check cannot reach WordPress, ask the host to exclude the Bot Guard background request from caching or blocking.

Connect and verify GA4

1. Enable Google Analytics Tracking.
2. Choose Existing Site Setup unless you intentionally want a separate property or container.
3. Save, open Testing Tools, and review the reported connection mode.
4. Select Test GA4 Event.
5. Use GA4 DebugView or your GTM preview to confirm the event and parameters.
6. After live traffic arrives, compare bot_detected and bot_blocked by affected page.

Introduce Rate Limiting safely

1. Enable the module with Log Only.
2. Exclude logged-in users and add known integration IPs to the module whitelist.
3. Observe normal page, background, and integration volume for several days.
4. Set limits above legitimate peaks and test configuration.
5. Move to Throttle or Add Delays before Block Completely.

Introduce Geographic Analysis safely

1. Select a provider, add its key if required, and run Test Geolocation Service.
2. Choose blacklist mode unless the site truly serves only a small list of countries.
3. Begin VPN/proxy handling with Log Only or Flag for Review.
4. Review mobile, corporate, and privacy-network traffic.
5. Enable active blocking only after expected customers and administrators are covered.