Fresh structured data on every page, without touching your code.
On the Cloudflare channel, MetaPilot runs as a managed 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 we install and manage the Worker for you.
GET https://yoursite.com/pricing → worker metapilot-injector → lookup meta cache HIT (0.4ms) → origin 200 text/html → rewrite <head> += ld+json, og:* → serve 200 x-managed-by: metapilot origin requests added ......... 0 redeploys required ............ 0 on error ...................... fail open
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. So most teams ship schema once and never touch it again, and it quietly rots while the content moves on. Cloudflare Worker SEO flips that: the metadata stops being a build artifact and becomes something served.
How it works
-
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. See the walkthrough →
-
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.
-
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.txtand 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 we change what is served without ever changing your origin, and your engineers never get a ticket.
No-redeploy schema, ever
A metadata update is live on the next request, not the next deploy. Build-time generators and CMS plugins physically cannot update a page without a rebuild or a save.
Edge speed, not origin load
HTML is rewritten across Cloudflare’s global network. Injection happens in-flight, adding no origin requests and no measurable latency to the page your visitor waits for.
Fail-open, one piece at a time
If the lookup errors or times out, the Worker gets out of the way and your origin response is served unchanged. Each injected section fails open on its own too: an anchor that stops matching drops that one block, never the others and never the page.
Fully managed, versioned, upgraded
We install it, version it, and roll new capabilities into it. You keep full visibility and control from your own Cloudflare dashboard at any time.
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. Connect once, get all of it.
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.
It does require your domain’s DNS to be proxied through Cloudflare (the orange cloud). Most sites already are, and onboarding walks you through connecting.
Sites on Shopify and Wix have no zone to install into, so the platform app is their channel instead. It is a different channel, not the same one by another name: each platform page lists what MetaPilot can and cannot deliver there, generated from the code rather than written down.
Frequently asked
For this channel, yes. The Worker only runs on a domain proxied through Cloudflare, and onboarding walks you through connecting your account (see what Cloudflare is if you are not sure whether you already use it). If your site is on Shopify or Wix you connect the platform app instead, which reaches your pages a different way and covers a different amount of ground. Each platform page says exactly how much.
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.
No. You authorize through Cloudflare’s OAuth flow, and we manage the Worker on your zone from there. Nothing to copy, nothing to rotate by hand.
MetaPilot installs and manages its own injector Worker alongside what you have. You keep full control from your Cloudflare dashboard.
You get one copy, not two. Where the Shopify app owns the host, the Worker stands down for it and the theme serves the section, because that is the channel the store is configured on. Without that rule the page would carry the same FAQ twice and two competing schema nodes describing it.
That happens with resold or partner-managed zones. Our zone hold guide walks through releasing it.
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.
Ask an AI whether edge injection fits your stack