Processby

<p>The plugin allows you to create and edit the robots.txt file on your site.</p>
<h4>Features</h4>
<ul>
<li>Works with multisite network on Subdomains;</li>
<li>An example of the correct file for WordPress;</li>
<li>Works out of the box;</li>
<li>Totally Free.</li>
</ul>


Robots.txt Editor

Lightweight and perfect for multisite installations.

But in documentation need to say where the option/editor is installed (Settings > Read options).

Perfect!

valvai

<p><strong>Valvai turns your WordPress into an AI traffic control center.</strong></p>
<ul>
<li>Block or allow GPTBot, ClaudeBot, PerplexityBot & co.  </li>
<li>Live dashboard with filters (All / AI / Allowed / Blocked)  </li>
<li>Per‑bot tabs to choose JSON vs HTML feed, content types, pricing  </li>
<li>Active 403 hard‑block for disallowed tokens  </li>
<li>robots.txt auto‑updates on every setting change</li>
</ul>
<p>Roadmap: HTTP 402 paywall handshake, revenue dashboard, token marketplace.</p>
<h3>Configuration</h3>
<ol>
<li>Visit Settings ▸ Valvai. You will see tabs: Dashboard, Permissions, and an AI‑specific tab for each allowed crawler.  </li>
<li>Permissions tab:
<ul>
<li>Toggle Allow/Block for detected bots (e.g., GPTBot, ClaudeBot, PerplexityBot).  </li>
<li>Or edit the manual lists “Blocked” and “Allowed” using comma‑separated names.  </li>
</ul>
</li>
<li>AI‑specific tabs (appear after a bot is allowed):
<ul>
<li>Data format: pick JSON or HTML.  </li>
<li>Content sources: check which post types and taxonomies are exposed.  </li>
<li>Pricing: choose currency and price per 1,000 words (FREE disables pricing).</li>
</ul>
</li>
</ol>
<h3>Usage / How it works</h3>
<ul>
<li>Logging: Every request from a suspected crawler is logged to the <code>wp_valvai_crawl_log</code> table. View the last 200 entries on the Dashboard and filter by All / AI / Allowed / Blocked.  </li>
<li>Blocking: Disallowed bots receive an HTTP 403 immediately.  </li>
<li>robots.txt: Your robots.txt is automatically augmented. Disallowed tokens get <code>Disallow: /</code>. Allowed tokens get an <code>Allow</code> rule pointing to a feed endpoint.</li>
</ul>
<h3>Testing the plugin</h3>
<ol>
<li>After activation, open Settings ▸ Valvai ▸ Dashboard. It will show “No logs yet” on a fresh site.  </li>
<li>In a new browser tab, visit any public URL on your site with a test crawler User‑Agent, for example:
<ul>
<li>Use <code>curl -A "GPTBot" https://your-site.example/</code>  </li>
<li>Or in the browser with a UA switcher extension.  </li>
</ul>
</li>
<li>Refresh the Dashboard: you should now see an entry with token <code>GPTBot</code>.  </li>
<li>Go to the Permissions tab and switch GPTBot to Allow or Block.  </li>
<li>Visit <code>/robots.txt</code> to verify entries update accordingly.  </li>
<li>If allowed, open the AI‑specific tab for that bot to set JSON/HTML and sources.</li>
</ol>
<h3>Notes for developers</h3>
<ul>
<li>All public PHP identifiers use the unique <code>valvaitcc_</code> prefix to avoid conflicts.  </li>
<li>Legacy options (<code>valvai_*</code>) are automatically migrated to <code>valvaitcc_*</code> on activation; legacy reads are still honored for backward compatibility.  </li>
<li>robots.txt feed query uses <code>?valvaitcc=TOKEN&fmt=json|html</code>.</li>
</ul>


Valvai – AI Traffic Control Center

Block, log and monetise AI crawlers directly from your WordPress dashboard.

Robots.txt Editor vs Valvai – AI Traffic Control Center