Help and guides
Setting up NORG edge routing, and the technical documentation behind it. If you are evaluating rather than installing, start with the white paper.
Start here
Edge routing: a technical white paper
How NORG serves AI agents structured data at your own URLs while humans and search engines get your origin untouched. Routing mechanics, the cloaking question, and how to trial it on one page. Written for the engineer or security reviewer who has to approve it.
Norg Edge Mirror Routing: Solution Architecture
The end-to-end architecture for a technical review: where data is stored, how it flows, the configuration, access and dependencies each pattern needs, and the end state with its security and governance positions.
Set up AI Retrievability by Norg in Claude
The smallest way to start: NORG builds and serves up to 25 of your pages on its own hostname, with nothing installed on your infrastructure and your domain untouched.
AI Retrievability by Norg hosting options
NORG-hosted by default, or self-hosted on your own Cloudflare account. The three ways to self-host, how to switch during the trial, and what leaves your account.
Install
WP Engine: let the WordPress plugin reach AI agents
The one WP Engine Internal rewrite Web Rule that carries AI-agent requests past the page cache to the plugin, how to check it worked, how to undo it, and what the ?norg_edge marker does.
Install the NORG connector (Starter)
Add the NORG connector to Claude (from the directory or as a custom connector), ChatGPT, Claude Code or any other AI agent, and sign in with your signup email. No API key on this plan.
Install NORG's private MCP (Growth)
Connect any agent to the full private NORG MCP with your API key: ready-to-paste config for Claude Desktop, Claude Code, ChatGPT and Gemini CLI, a curl check, and the first call your agent should make.
Set up Cloudflare from scratch
No CDN yet? The step before every other install guide: a free Cloudflare account, your DNS moved across from your current provider, and your nameservers repointed at the registrar — without taking your email down on the way.
Install a Cloudflare Worker mirror
Serve a NORG-optimised mirror of your own site to AI agents, at your own URLs, with a small Worker on your zone.
Install in front of an existing Cloudflare Worker
Already run a Worker on your zone? Put the NORG Worker in front of it, bound to your Worker through a Service Binding named ORIGIN: a new NORG route when your Worker is a Workers Custom Domain, or your route moved to NORG when your Worker owns it. People and search engines reach your existing router unchanged while verified AI agents get the mirror. Record-only first, then serving.
Installing NORG alongside your own Cloudflare Worker
The short, plain-English version: the two ways a Worker can be attached, why NORG binds yours as ORIGIN, what changes and what does not, how to undo it, and who to ask if NORG could not read your set-up.
Install the NORG Edge Router WordPress plugin
No CDN? The router runs inside WordPress as a plugin: install it, paste a Site ID and Site Key, and click Run checks. No DNS change.
WP Engine: let the WordPress plugin reach AI agents
On WP Engine the page cache answers AI agents before WordPress runs, so the plugin never sees them. Add one Internal rewrite Web Rule in the User Portal — no support ticket — then verify and undo.
Add the NORG edge router to your Vercel middleware
Hosted on Vercel? Add the @norg-ai/edge-router-vercel npm package to your Next.js or Vercel middleware, set two environment variables and redeploy. No DNS change.
Install on a Shopify store
The Online Store 2.0 variant, for stores whose DNS is on a myshopify.com CNAME zone.
Fix a WP Engine site Cloudflare bypasses (O2O)
Worker installed but never runs? If the apex is an A record to WP Engine, Cloudflare skips your zone. Back up the zone, swap two records for one proxied CNAME, verify — with an instant undo.
Reference
NORG Edge Router for WordPress: technical reference
Every constant, header, timeout and surface the WordPress plugin has, read from its source: request lifecycle, serving policies, where the Site Key lives, outbound calls, updates and removal.
NORG Edge Router for WordPress: measured performance
How much latency the WordPress plugin adds with the mirror on, measured on plugin 0.1.4 on 5 November 2026: the results table against the proposed targets, including the mirror TTFB target it did not meet, the test site, method and caveats.
CNAME setup for a CDN edge worker
Putting Cloudflare or Fastly in front of one hostname by CNAME without moving DNS: the steps, the plan and usage costs, the apex and TLS details, and how it differs from moving the whole zone.
CloudFront edge routing architecture
What an install puts in your AWS account, and how it behaves. The four deployed artifacts, the request lifecycle, where the site key lives and who can read it, every timeout with the constant it comes from, and the Lambda@Edge limits that shaped the design.
Enterprise authentication for the NORG connector
Administrator setup for the MCP connector: the endpoint, OAuth 2.1 with mandatory PKCE, the single scope an approval grants, the two client-registration routes, just-in-time provisioning, and what the connector never does. Written for the IT or security administrator approving it.
MCP tool reference for AI Retrievability by Norg
Every tool the live connector exposes, what each one reads or changes, example prompts, and what data the connector collects. The single source of truth for the tool surface.
Cloudflare Worker latency measurements
How much latency the Norg Edge Router Worker adds on a Cloudflare zone, measured on foxx.ai, with the method, caveats and a reproduction recipe.
Upgrade to Cloudflare Workers Paid
Why the free Workers request cap matters for a mirrored site, and what happens when it is reached.
Cannot find what you need? Write to solutions@norg.ai.