Voho bot manager

توسط

Voho bot manager hardens WordPress against the new wave of AI-driven crawlers—including stacks associated with OpenClaw—that attempt to scrape, snapshot, and probe your content through non-interactive, headless browsing pipelines.

When a high-risk automation session is identified, the plugin terminates the request with HTTP 403, returns a concise English denial page, and persists structured telemetry (UTC timestamp, client IP, requested URL, and an intercepted flag reserved for richer policy engines) inside {prefix}voho_bot_manager_intercepted_log.

Operational visibility

  • Dedicated Voho Bot Manager admin hub with paginated history.
  • Timestamps rendered in your configured WordPress timezone so responders can correlate events quickly.
  • View log shortcut on the Plugins screen for one-click access.

Roadmap-aware positioning: automated threat actors evolve weekly; Voho bot manager ships iterative detection upgrades so your perimeter keeps pace with emerging AI browsing agents without waiting for a full rewrite.

OpenClaw and similar names refer to widely discussed AI browsing ecosystems; Voho bot manager is an independent security tool and is not affiliated with any third-party vendor.

  1. Upload the voho-bot-manager folder to /wp-content/plugins/.
  2. Activate Voho bot manager through the Plugins menu in WordPress.
  3. Open Voho Bot Manager in the admin sidebar (or use View log on the plugin row) to review intercepted requests.

On activation the plugin creates the {prefix}voho_bot_manager_intercepted_log table automatically.

سوالات متداول

How does this help against OpenClaw-style AI crawlers?

The plugin blocks the non-human automation paths these agents rely on, answers with HTTP 403, and logs each attempt so you can audit abuse, tune upstream controls, and brief stakeholders with concrete evidence.

Will it catch every crawler on the internet?

No defensive layer can promise universal coverage. Voho bot manager focuses on the high-risk automation families behind modern AI scrapers and continuously expands detection as new behaviours appear.

Does the plugin work with caching or CDN layers?

If a cache or proxy serves a response without executing WordPress/PHP for matching requests, interception must happen at that layer instead. Otherwise behaviour is unchanged.

What data is stored?

Each intercepted request stores UTC time, client IP (or the first value from X-Forwarded-For when present), full requested URL, and a boolean intercepted flag.

تصویری برای این آیتم موجود نیست.
نظری برای این آیتم موجود نیست.
0 0 رای ها
امتیازدهی
اشتراک در
اطلاع از
0 نظرات
قدیمی‌ترین
تازه‌ترین بیشترین رأی
هیچ نسخه‌ای برای این آیتم موجود نیست.
بدون امتیاز

قیمت:

رایگان

نگارش

آخرین انتشار

21 اردیبهشت 1405

آخرین بروزرسانی

3 ماه پیش

نصب های فعال

-

نگارش وردپرس

وردپرس 6.2+

تست شده از نسخه

وردپرس 6.9.4

نگارش PHP

PHP 7.4+

نسخه ها

0 نسخه