# Fresh structured data on every page, without touching your code.

**Cloudflare edge injection** — MetaPilot runs as a managed Cloudflare Worker that rewrites your HTML in-flight at the edge, injecting up-to-date JSON-LD and Open Graph before a single byte reaches your visitor. Connect your Cloudflare account once and MetaPilot installs and manages the Worker for you.

---

## The problem

Getting structured data onto a live site normally means editing templates, waiting on a deploy, or wrestling a CMS plugin — for every change, forever.

If your metadata lives in your build, keeping it fresh means rebuilding. Most teams ship schema once and never touch it again, and it quietly rots while the content moves on. **Cloudflare Worker SEO** flips that: metadata stops being a build artifact and becomes something served.

---

## How it works

1. **Connect Cloudflare in one click** — Authorize your account through OAuth. No API tokens to paste, no scripts to run, no credentials sitting in a config file.
2. **We install the Worker** — MetaPilot deploys and manages the injector Worker on your zone, and keeps it upgraded as the product evolves. You never maintain it.
3. **Every request gets fresh metadata** — The Worker rewrites the response in flight: your latest JSON-LD and Open Graph into the head, your answer blocks into the body, and your `robots.txt`, `llms.txt` and Markdown at their own paths.

---

## What you get

- **Inject JSON-LD without code** — No template edits, no CMS plugin, no build step. The Worker sits in the request path so changes go live without touching your origin.
- **No-redeploy schema, ever** — A metadata update is live on the next request, not the next deploy.
- **Edge speed, not origin load** — HTML is rewritten across Cloudflare's global network with no added origin requests and no measurable latency.
- **Fail-open, one piece at a time** — If a lookup errors or times out, the Worker gets out of the way and your origin response is served unchanged. Each injected section fails open independently.
- **Fully managed, versioned, upgraded** — MetaPilot installs it, versions it, and rolls new capabilities into it. You keep full visibility and control from your Cloudflare dashboard.
- **One request path, many features** — The same Worker serves your `llms.txt` and `robots.txt`, powers AI-crawler analytics, answers Markdown requests, and injects answer blocks.

---

## Plan availability

Available on **every plan, including Free**. On this channel the Worker carries everything else, so it is never the thing you upgrade for.

Requires your domain's DNS to be proxied through Cloudflare (the orange cloud). Sites on **Shopify** and **Wix** use the platform app channel instead — each platform page lists exactly what MetaPilot can and cannot deliver there.

---

## Frequently asked

**Do I have to be on Cloudflare?**
For this channel, yes. The Worker only runs on a domain proxied through Cloudflare. If your site is on Shopify or Wix, you connect the platform app instead.

**Will this slow my site down?**
No. The Worker rewrites HTML in-flight at the edge and adds no origin requests. It is fail-open, so a problem never blocks a page load.

**Do I need to give you an API key?**
No. You authorize through Cloudflare's OAuth flow. Nothing to copy, nothing to rotate by hand.

**What if I already have a Worker or custom rules?**
MetaPilot installs and manages its own injector Worker alongside what you have. You keep full control from your Cloudflare dashboard.

**What if my Shopify store also sits behind my own Cloudflare zone?**
You get one copy, not two. Where the Shopify app owns the host, the Worker stands down for it so the same FAQ or schema node is never served twice.

**What if my zone is on hold or managed elsewhere?**
MetaPilot's zone hold guide walks through releasing it.

---

## Keep reading

- What is edge injection?
- Guide: connect Cloudflare
- What gets injected: AI structured data
- Check whether your site is compatible

---

*Connect Cloudflare and go live in minutes. One OAuth click installs the Worker — from then on, every metadata change is live on the next request.*