AI SHIELDPROTECT WHAT'S YOURS
Start Scan

AI SHIELD

PROTECTION CENTER

Control how automated AI systems access your website.

WEBSITE

No website configured

CONFIGURATION READYNOT CONNECTED

YOUR WEBSITE

WEBSITE PROTECTION

NOT CONNECTED

Your website has been analyzed, but AI Shield does not yet have permission to enforce access policies on your website.

No enforcement connection configured. Policies are saved as configuration only.

VIEW SCAN REPORT

CONFIGURATION INTELLIGENCE

What AI Shield learned by scanning your public website. Scanning alone does not block any AI crawler.

ENFORCEMENT

What AI Shield can actually control after your website infrastructure is connected and verified.

PROTECTION MODE

Default AI access policy

Control selected AI systems individually while maintaining a default access policy. AI Shield is not anti-AI — it gives you control.

AI SYSTEMS

AI crawler access policy

Configuration only — AI Shield does not observe live crawler traffic on your website yet, so no request counts are shown.

NOT CONNECTED

GPTBot

NOT CONFIGURED

AI Training · Model training

Configuration only

OAI-SearchBot

NOT CONFIGURED

AI Search · Search and discovery

Configuration only

ChatGPT-User

NOT CONFIGURED

AI Agent · User-initiated retrieval

Configuration only

ClaudeBot

NOT CONFIGURED

AI Training · Model/web data

Configuration only

Google-Extended

NOT CONFIGURED

AI Training · Google AI controls

Configuration only

PerplexityBot

NOT CONFIGURED

AI Search · Search/answers

Configuration only

Bytespider

NOT CONFIGURED

AI Training · Web data collection

Configuration only

CCBot

NOT CONFIGURED

AI Training · Common Crawl data

Configuration only

CONTENT PROTECTION

Which content should policies apply to?

Scope your AI access policies to your whole website, page categories from your scan, individual pages, or URL patterns.

GENERAL

—pages

CONTENT

—pages

COMMERCIAL

—pages

PRICING

—pages

COMPANY

—pages

RULE BUILDER

Create access rule

Rules are policy configuration. They are only enforced once an infrastructure connection is verified.

WHEN — CRAWLER

AND — URL

THEN

RULE PREVIEW

Crawler
GPTBot
Target
/pricing/*
Action
BLOCK

GPTBot requests matching this URL pattern will be blocked once your website enforcement connection is verified.

ACCESS RULES

0 configured rules

Draft and paused rules are never enforced. Active rules show ENFORCED only after an infrastructure connector confirms it.

No rules match this filter yet. Create an access rule above.

POLICY SIMULATION

Test policy

This simulates how your configured rules would evaluate a request. It is not live traffic.

CONNECTION CENTER

Connect your website for enforcement

AI Shield reports connection state truthfully. A provider without a live integration is shown as NOT CONFIGURED.

Cloudflare

NOT CONNECTED

Deploy rules through your Cloudflare zone.

CDN / WAF

NOT CONNECTED

Fastly, Akamai, AWS CloudFront and similar.

Reverse proxy

NOT CONNECTED

Nginx or Caddy in front of your website.

Server / middleware

NOT CONNECTED

Application middleware on your own server.

Manual setup

NOT CONNECTED

Copy a generated configuration and deploy it yourself.

CONNECT YOUR WEBSITE

Give AI Shield visibility into the automated traffic reaching your website

AI Shield does not need your website passwords or customer data. The forwarder sends limited request metadata to AI Shield so we can identify automated traffic, measure activity, and compare requests against your protection policies.

NOT CONNECTED
01 CONNECT02 INSTALL03 TEST04 VERIFY

YOUR WEBSITE STAYS YOURS

AI Shield does not receive:

PasswordsCookiesRequest bodiesForm submissionsAuthentication tokens

Traffic metadata is sent securely using your unique signing secret.

YOUR WEBSITE

Enter the website you want to connect. Scanning it first also shows your page count and AI exposure score here.

CHOOSE CONNECTION METHOD

STEP 1 · COPY YOUR AI SHIELD SIGNING SECRET

AI Shield generates a signing secret that belongs only to this website. Every forwarded batch must be signed with it.

STEP 2 · ADD IT TO YOUR WEBSITE

Endpoint /api/public/traffic/webhook/server · header x-aishield-signature · hex(HMAC-SHA256(secret, body))

// AI Shield forwarder — Node.js (Express/Connect middleware).
// Runs on YOUR server. Forwards request metadata only.
import crypto from "node:crypto";

const AISHIELD_URL = "/api/public/traffic/webhook/server";
const AISHIELD_SECRET = process.env.AISHIELD_SECRET; // <YOUR_AI_SHIELD_SIGNING_SECRET>
const AISHIELD_DOMAIN = "yourwebsite.com";

export function aiShieldForwarder(req, res, next) {
  res.on("finish", () => {
    const body = JSON.stringify({
      domain: AISHIELD_DOMAIN,
      events: [
        {
          eventType: "TRAFFIC",
          timestamp: new Date().toISOString(),
          requestUrl: req.originalUrl,
          method: req.method,
          statusCode: res.statusCode,
          responseBytes: Number(res.getHeader("content-length")) || null,
          userAgent: req.headers["user-agent"] ?? null,
          sourceIp: req.headers["x-forwarded-for"]?.split(",")[0] ?? req.socket.remoteAddress,
          action: "UNKNOWN"
        }
      ]
    });

    const signature = crypto.createHmac("sha256", AISHIELD_SECRET).update(body).digest("hex");

    fetch(AISHIELD_URL, {
      method: "POST",
      headers: { "content-type": "application/json", "x-aishield-signature": signature },
      body
    }).catch(() => {}); // never let telemetry affect your website
  });

  next();
}

// app.use(aiShieldForwarder);

STEP 3 · DEPLOY

Deploy the forwarder to the infrastructure that receives your website requests. It sends request metadata only — never request bodies, cookies, authorization headers, session tokens or form contents. AI Shield hashes source addresses with a server-side salt and never stores raw addresses.

STEP 4 · TEST THE CONNECTION

AI Shield signs one test event with your stored secret and sends it through the real ingestion path: webhook → authenticate → validate → deduplicate → normalize → classify → store. Test events never count as website traffic.

NEED HELP?

What does the forwarder do?
It runs on your own infrastructure and sends AI Shield limited metadata about each request — the time, the URL path, the method, the response status, and the User-Agent. AI Shield uses that to identify automated traffic and compare it against your protection policies.
Does AI Shield see my customers' information?
No. The forwarder never sends request bodies, cookies, form contents or authentication tokens. Source addresses are hashed with a server-side salt and raw addresses are never stored or shown.
Does this block AI crawlers?
Not by itself. Stage 4.2 connects traffic intelligence. Your Protection Center policies determine what you want to allow or block, while actual enforcement depends on a verified enforcement integration.
Will this slow down my website?
The forwarder sends metadata after your response has already been returned, and failures are ignored, so your visitors are not made to wait on AI Shield.
Where do I install it?
On whatever layer actually receives your website's requests — your application server, your reverse proxy, or your own Cloudflare Worker.

WHAT AI SHIELD COLLECTS

Limited request metadata needed for traffic intelligence: timestamp, domain, request URL, method, status code, response size, User-Agent, country and network (ASN), plus a salted hash of the source address.

WHAT AI SHIELD DOES NOT COLLECT

  • · Passwords
  • · Cookies
  • · Request bodies
  • · Form submissions
  • · Authentication tokens

AUDIT LOG

Policy change history

Every policy change is recorded for review and enterprise reporting.

No policy changes recorded yet.