AEO Optima Docs
Features

Edge AI Delivery

Inject enriched structured data (Organization JSON-LD + AI meta tags) for AI crawlers at your CDN edge, managed entirely from AEO Optima — deploy a snippet once, change rules anytime.

Overview

Edge AI Delivery serves enriched structured data to AI crawlers (GPTBot, ClaudeBot, PerplexityBot, and others) the moment they fetch your pages — without changing what human visitors see.

AI crawlers read your raw HTML and, unlike browsers, do not run client-side JavaScript. So a normal analytics-style <script> tag in your <head> would be invisible to them — the bot has already taken the static HTML and left. Edge Delivery solves this by injecting the enrichment server-side at your CDN edge, before the bot receives the response.

It works like a tag manager: you deploy one small snippet to your edge once, and from then on every rule and enrichment change you make in AEO Optima propagates to your live site automatically — no re-deploy.

Plan gate: Edge AI Delivery is part of the advanced AI insights feature set.

How it works

  1. In Edge Delivery you choose which AI bots to enrich and which structured data to inject (Organization JSON-LD from your Brand Facts, plus AI-oriented meta tags).
  2. The platform generates a non-secret edge token and a ready-to-paste edge snippet (Cloudflare Worker, a generic edge-function/proxy variant, or a static fallback).
  3. You paste the snippet once into your CDN/edge layer.
  4. On every request, the snippet checks the visitor's user-agent. For a configured AI bot, it fetches your latest config from AEO Optima (CDN-cached, ~5-minute freshness) and injects the structured data into the HTML response. Human visitors get the page untouched.
  5. Because the snippet pulls config live, changing your rules in the dashboard updates your live site within minutes — you never re-paste.

The snippet fetches data (your config) from us at runtime; it never imports remote code. We never proxy, host, or sit in front of your site — the snippet runs on your own CDN.

What gets injected

  • Organization JSON-LD — built from your project's Brand Facts (company name, URL, description, logo, contact email). This is the same Organization schema the Schema Builder produces, so the two never drift.
  • WebPage JSON-LD — a per-URL node added by the snippet for the page being requested.
  • AI meta tags — robots and ai-content-type hints.

FAQ schema injection is not yet available at the edge: it requires saved, grounded FAQ answers (we never inject placeholder answers). Generate and save FAQs first; edge FAQ injection will use them once a persisted FAQ source ships.

Setup

  1. Open Edge Delivery from the sidebar.
  2. Choose which bots to enrich and which structured data to inject.
  3. Click Save Config — this generates your edge token.
  4. Enable Edge Delivery with the master toggle.
  5. Copy the snippet for your platform and deploy it to your CDN.
  6. Use Test Bot Detection to preview exactly what the snippet will inject for a given user-agent before (and after) deploying.

Readiness check (2026-06-12)

Before (and after) deploying the snippet, run the Edge Readiness Check on a key page. It measures how your origin behaves for an AI crawler right now:

  • Server response — fetched with a GPTBot user agent; HTTP status and response time (aim under ~1.5s — slow origins get crawled less)
  • Content visible without JavaScript — AI crawlers execute no JS; a JS-dependent page is exactly what edge serving fixes
  • Schema reachable in the served HTML — whether JSON-LD exists in the raw response (Edge Delivery can inject it for bots when it doesn't)
  • AI crawler access — robots.txt / ai.txt permissions; a blocked engine never reaches the edge layer at all
  • Indexability — flags noindex directives

Each check returns pass / warn / fail with the measured evidence, plus a 0-100 readiness score and verdict.

Verifying it works

  • Use the in-page Test Bot Detection panel to see the JSON-LD, meta tags, and headers your snippet will inject for a sample bot user-agent.
  • After deploying, fetch your own page with a bot user-agent (e.g. curl -A "GPTBot" https://yoursite.com/) and confirm the injected <script type="application/ld+json"> appears.
  • The Crawler Intelligence page shows which AI crawlers are actually reaching your site.

Best practices

  • Keep Brand Facts complete and accurate. The Organization schema is only as good as the facts behind it.
  • Don't serve contradictory facts. Edge enrichment should add structure, not rewrite claims — conflicting facts hurt your entity clarity.
  • Re-submit changed URLs via IndexNow so AI crawlers re-fetch and pick up the new enrichment sooner.
  • Cloudflare is the simplest path — the Worker sits in front of your site and rewrites the response with no extra configuration. The generic snippet suits other edge platforms but needs your origin host set.

Previous

GEO Audit

Next

IndexNow

On this page

Edge AI Delivery — AEO Optima