설명

Valvai turns your WordPress into an AI traffic control center.

Block or allow GPTBot, ClaudeBot, PerplexityBot & co.
Live dashboard with filters (All / AI / Allowed / Blocked)
Per‑bot tabs to choose JSON vs HTML feed, content types, pricing
Active 403 hard‑block for disallowed tokens
robots.txt auto‑updates on every setting change

Roadmap: HTTP 402 paywall handshake, revenue dashboard, token marketplace.

Configuration

Visit Settings ▸ Valvai. You will see tabs: Dashboard, Permissions, and an AI‑specific tab for each allowed crawler.
Permissions tab:
- Toggle Allow/Block for detected bots (e.g., GPTBot, ClaudeBot, PerplexityBot).
- Or edit the manual lists “Blocked” and “Allowed” using comma‑separated names.
AI‑specific tabs (appear after a bot is allowed):
- Data format: pick JSON or HTML.
- Content sources: check which post types and taxonomies are exposed.
- Pricing: choose currency and price per 1,000 words (FREE disables pricing).

Usage / How it works

Logging: Every request from a suspected crawler is logged to the wp_valvai_crawl_log table. View the last 200 entries on the Dashboard and filter by All / AI / Allowed / Blocked.
Blocking: Disallowed bots receive an HTTP 403 immediately.
robots.txt: Your robots.txt is automatically augmented. Disallowed tokens get Disallow: /. Allowed tokens get an Allow rule pointing to a feed endpoint.

Testing the plugin

After activation, open Settings ▸ Valvai ▸ Dashboard. It will show “No logs yet” on a fresh site.
In a new browser tab, visit any public URL on your site with a test crawler User‑Agent, for example:
- Use curl -A "GPTBot" https://your-site.example/
- Or in the browser with a UA switcher extension.
Refresh the Dashboard: you should now see an entry with token GPTBot.
Go to the Permissions tab and switch GPTBot to Allow or Block.
Visit /robots.txt to verify entries update accordingly.
If allowed, open the AI‑specific tab for that bot to set JSON/HTML and sources.

Notes for developers

All public PHP identifiers use the unique valvaitcc_ prefix to avoid conflicts.
Legacy options (valvai_*) are automatically migrated to valvaitcc_* on activation; legacy reads are still honored for backward compatibility.
robots.txt feed query uses ?valvaitcc=TOKEN&fmt=json|html.

설치

Upload the /valvai/ folder or use Plugins ▸ Add New ▸ Upload.
Activate Valvai – AI Traffic Control Center.
Go to Settings ▸ Valvai to review logs and set permissions.

FAQ

Does Valvai hurt SEO?: No. Only tokens you block get 403. Googlebot, Bingbot, etc. remain untouched.
Why do blocked bots still show in the log?: Valvai logs the hit before sending 403, so you have an audit trail.
Can I give JSON but not HTML?: Yes. In each AI tab pick JSON under “Data format” and select allowed sources.
When will pricing go live?: Token‑based HTTP 402 paywall is scheduled for v0.5 (Q4 2025).

후기

이 플러그인에 대한 평가가 없습니다.

기여자 & 개발자

“Valvai – AI Traffic Control Center”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

valvai

자국어로 “Valvai – AI Traffic Control Center”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록을 RSS로 구독하세요.

변경이력

0.4.13

Switched to unique prefix valvaitcc_ for all functions, options, nonces, and slugs to avoid conflicts.
Added activation migration for legacy options.
Expanded readme with clear configuration, usage, and testing steps.

0.4.11

Renamed plugin to Valvai.

0.4.4

Escaped all outputs per WP Coding Standards.
Removed unused Plugin URI header; readme cleaned.