hammadtq

OpenBotAuth helps publishers control automated access from AI crawlers and agents. It verifies requests using RFC 9421 HTTP Message Signatures (via a configurable verifier) and applies per-site or per-post policies like allow, deny, teaser previews, and 402 payment-required responses. It also publishes AI-friendly endpoints like llms.txt, a JSON feed, and per-post Markdown.
Instead of blocking all bots or allowing unrestricted access, you can:
<ul>
<li>See AI bot traffic – Local-only analytics showing which bots are crawling your site</li>
<li>Verify bot identity using cryptographic signatures (RFC 9421)</li>
<li>Show teasers to unverified bots (first N words)</li>
<li>Rate limit bot access per agent</li>
<li>Whitelist/blacklist specific bots</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Bot Traffic Analytics – See which AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) are visiting your site</li>
<li>Signature Verification – Verifies RFC 9421 HTTP Message Signatures using Ed25519 cryptography</li>
<li>Content Teasers – Show first N words to unverified bots with customizable per-post settings</li>
<li>Rate Limiting – Per-agent rate limits with configurable time windows</li>
<li>Access Control – Whitelist/blacklist with wildcard pattern matching</li>
<li>Local Analytics – Visual dashboard with charts, stats cards, and decision breakdowns (no external tracking)</li>
<li>AI-Ready Endpoints – Serve llms.txt, JSON feed, and markdown for AI crawlers</li>
<li>Tabbed Admin Interface – Clean organization with Analytics, AI Endpoints, and Configuration tabs</li>
</ul>
<h4>AI-Ready Endpoints</h4>
OpenBotAuth provides machine-readable endpoints for AI systems:
<ul>
<li>/llms.txt – Standardized AI feed discovery (also at /.well-known/llms.txt)</li>
<li>/.well-known/openbotauth-feed.json – JSON list of all published posts</li>
<li>/.well-known/openbotauth/posts/{ID}.md – Per-post markdown content</li>
</ul>
Configure which post types to include (posts, pages, or custom types) and set the feed limit (up to 500 items). All data is served locally from your WordPress database. No external tracking or telemetry. Only published, non-password-protected posts are exposed.
<h4>How It Works</h4>
<ol>
<li>AI agent signs HTTP request with its private key (RFC 9421 signature)</li>
<li>WordPress plugin extracts signature headers and sends them to a verifier service</li>
<li>Verifier fetches agent’s public key from registry and verifies signature</li>
<li>Plugin applies policy: allow full content, show teaser, require payment, or deny</li>
</ol>
<h4>External Service Disclosure</h4>
This plugin connects to an external verifier service. When a signed bot request is received, the plugin sends the following data to your configured verifier URL via <code>wp_remote_post</code>:
<ul>
<li>HTTP method (GET, POST, etc.)</li>
<li>The accessed URL (including query string, if present)</li>
<li>HTTP signature headers (Signature, Signature-Input, Signature-Agent)</li>
<li>Additional HTTP header values explicitly listed in the Signature-Input header (e.g., content-type, accept, user-agent)</li>
</ul>
Privacy protection: Sensitive headers (cookies, authorization, proxy-authorization, www-authenticate) are NEVER forwarded, even if present in the request. If a bot’s signature covers a sensitive header, verification will fail with a clear error.
No WordPress user accounts or personal data is transmitted. Only the headers explicitly covered by the bot’s signature are forwarded to enable cryptographic verification. Note that the URL may include query parameters depending on your site’s structure.
You can: 
* Use the hosted verifier at <code>https://verifier.openbotauth.org/verify</code> 
* Self-host the verifier service (see documentation) 
* The verifier service may log requests server-side depending on your configuration
Analytics are local-only. Decision counts (allow/teaser/deny/pay/rate_limit) and bot traffic observations (User-Agent based) are stored in your WordPress database. No analytics data is sent to external servers.
For more information, please review our <a href="https://openbotauth.org/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://openbotauth.org/privacy" rel="nofollow ugc">Privacy Policy</a>.
<h3>Developer Hooks</h3>
<h4>Filters</h4>
openbotauth_policy 
Modify policy before applying:
<pre><code>add_filter('openbotauth_policy', function($policy, $post) {
 if ($post->post_type === 'premium') {
 $policy['price_cents'] = 1000;
 }
 return $policy;
}, 10, 2);
</code></pre>
<h4>Actions</h4>
openbotauth_verified 
Triggered when a bot is verified:
<pre><code>add_action('openbotauth_verified', function($agent, $post) {
 error_log("Bot {$agent['jwks_url']} accessed post {$post->ID}");
}, 10, 2);
</code></pre>
openbotauth_payment_required 
Triggered when 402 is returned:
<pre><code>add_action('openbotauth_payment_required', function($agent, $post, $price) {
 // Track payment requests
}, 10, 3);
</code></pre>
<h4>AI Endpoint Filters (v0.1.2+)</h4>
openbotauth_should_serve_llms_txt 
Disable llms.txt endpoint (e.g., when using Yoast):
<pre><code>add_filter('openbotauth_should_serve_llms_txt', '__return_false');
</code></pre>
openbotauth_should_serve_feed 
Disable JSON feed endpoint:
<pre><code>add_filter('openbotauth_should_serve_feed', '__return_false');
</code></pre>
openbotauth_should_serve_markdown 
Disable markdown endpoints:
<pre><code>add_filter('openbotauth_should_serve_markdown', '__return_false');
</code></pre>
openbotauth_feed_item 
Modify feed items:
<pre><code>add_filter('openbotauth_feed_item', function($item, $post) {
 $item['custom_field'] = get_post_meta($post->ID, 'my_field', true);
 return $item;
}, 10, 2);
</code></pre>
openbotauth_markdown_content 
Post-process markdown output:
<pre><code>add_filter('openbotauth_markdown_content', function($markdown, $post) {
 return $markdown . "\n\n---\nCopyright notice here";
}, 10, 2);
</code></pre>

OpenBotAuth – AI Crawler Access Control

Verify AI crawlers with HTTP Signatures and enforce allow/deny/teaser policies; also serves llms.txt and AI-ready feeds.

mediterraneaservices

Be visible in AI search. IA SEO Generator creates a clean, AI-readable /llms.txt so modern assistants and AI crawlers can discover and understand your site — without risky root writes. Appear in answers on ChatGPT, Perplexity, Claude, Gemini, Copilot, Comet and more by providing the structured signals they expect.
What you get (Free) 
– One-click llms.txt generation (no filesystem/root writes) 
– Preview, Copy, Download or serve /llms.txt dynamically (save Permalinks once) 
– Structured output with header metadata (site, site_name, ISO date, language) 
– Pages/Posts sections (Title, URL, Updated, Excerpt) 
– Built-in llms.txt language selector (EN/ES) 
– Lightweight admin UI in English, i18n-ready for GlotPress language packs 
– No tracking, no phone-home
Who is it for? 
Stores, corporate sites, blogs and agencies that want their content to be understood by AI assistants and LLM search.
How it works 
1. Install and activate IA SEO Generator. 
2. Click Generate to build the file. 
3. (Optional) Enable dynamic <code>/llms.txt</code> and visit Settings → Permalinks → Save once.
<h3>Go Premium and get all these advantages</h3>
<ul>
<li>✔️ Fully automatic upload of the generated files </li>
<li>✔️ AI-optimized files: llms.txt, humans.txt, metadata.json, sitemap.xml, ai-plugin.json </li>
<li>✔️ Generate, View and Edit the content of each file </li>
<li>✔️ Indexing in ChatGPT, Perplexity, Copilot, Gemini, Claude, Comet and more</li>
<li>✔️ AI MODE Google Ready </li>
<li>✔️ Direct upload via FTP/API to the site root </li>
<li>✔️ Compatible with all WordPress builders </li>
<li>✔️ Priority support and continuous improvements </li>
</ul>
Your website can be invisible to the new generation of AI-based search engines.
Engines like ChatGPT, Gemini, Perplexity or Copilot do not work like Google. If your site is not properly structured for AI, it simply does not appear. And that means one thing: you are losing customers.
The Premium version of IA SEO Generator turns your website into information readable and preferred by these new AIs. The result? Greater visibility, more qualified traffic and more conversions. Ideal for online stores, corporate websites, blogs and professional services.
Be the first in your sector to appear in AI results and multiply your digital reach. It is not the future, it is the present.
Why are these files so important? 
Files such as llms.txt, humans.txt, metadata.json, sitemap.xml or ai-plugin.json are essential for AIs to understand your site. While traditional search engines parse HTML, generative AIs look for structured, clear and standardized files.
Generating these files not only improves your visibility now, it strategically positions you for the future. It is the way to tell AI: “here is my content, perfectly organized and ready to be indexed.”
👉 <a href="https://iaseogenerator.com" rel="nofollow ugc">Get Premium →</a>
<h3>(ES) Sé visible en la búsqueda con IA</h3>
IA SEO Generator crea un llms.txt limpio y legible por IA para que los asistentes modernos entiendan tu sitio — sin escrituras peligrosas en la raíz. Aparece en respuestas de ChatGPT, Perplexity, Claude, Gemini, Copilot, Comet y más aportando las señales estructuradas que esperan.
Qué incluye (Free) 
– Generación con un clic de llms.txt (sin escribir en el sistema/raíz) 
– Previsualizar, Copiar, Descargar o servir /llms.txt de forma dinámica (guarda Enlaces Permanentes una vez) 
– Salida estructurada con metadatos de cabecera (site, site_name, fecha ISO, language) 
– Secciones de Páginas/Entradas (Título, URL, Actualizado, Extracto) 
– Selector de idioma para llms.txt (EN/ES) 
– Panel ligero en inglés, listo para i18n (GlotPress) 
– Sin tracking, sin llamadas externas
Para quién es 
Tiendas, webs corporativas, blogs y agencias que quieren que su contenido sea entendido por asistentes de IA y búsquedas LLM.
Cómo funciona 
1. Instala y activa IA SEO Generator. 
2. Pulsa Generar para crear el archivo. 
3. (Opcional) Activa el /llms.txt dinámico y ve a Ajustes → Enlaces permanentes → Guardar una vez.
<h3>Ve a Premium y consigue todas estas ventajas</h3>
<ul>
<li>✔️ Subida automática de los archivos generados </li>
<li>✔️ Archivos optimizados para IA: llms.txt, humans.txt, metadata.json, sitemap.xml, ai-plugin.json </li>
<li>✔️ Generar, Ver y Editar el contenido de cada archivo </li>
<li>✔️ Indexación en ChatGPT, Perplexity, Copilot, Gemini, Claude, Comet y más</li>
<li>✔️ AI MODE Google Ready </li>
<li>✔️ Subida directa por FTP/API a la raíz del sitio </li>
<li>✔️ Compatible con todos los builders de WordPress </li>
<li>✔️ Soporte prioritario y mejoras continuas </li>
</ul>
Tu web puede ser invisible para la nueva generación de buscadores basados en IA.
Motores como ChatGPT, Gemini, Perplexity o Copilot no funcionan como Google. Si tu sitio no está bien estructurado para IA, simplemente no aparece. Y eso significa una cosa: estás perdiendo clientes.
La versión Premium de IA SEO Generator convierte tu web en información legible y preferida por estas nuevas IAs. Resultado: más visibilidad, tráfico cualificado y conversiones. Ideal para tiendas online, webs corporativas, blogs y servicios profesionales.
Llega antes que tu competencia a los resultados en IA y multiplica tu alcance digital. No es el futuro, es el presente.
¿Por qué son importantes estos archivos? 
Archivos como llms.txt, humans.txt, metadata.json, sitemap.xml o ai-plugin.json son esenciales para que las IAs entiendan tu sitio. Mientras los buscadores tradicionales analizan HTML, las IAs generativas buscan información estructurada, clara y estandarizada.
Generarlos no solo mejora tu visibilidad hoy; te posiciona estratégicamente para el futuro. Es la forma de decirle a la IA: “aquí tienes mi contenido, perfectamente organizado y listo para indexar.”
👉 <a href="https://iaseogenerator.com" rel="nofollow ugc">Consigue Premium →</a>

IA SEO Generator

Make your site visible to AI: serve an AI-ready /llms.txt (no root). Appear in answers on ChatGPT, Perplexity, Claude, Gemini, Copilot, Comet.

OpenBotAuth – AI Crawler Access Control vs IA SEO Generator