One Worker, one proxy, one agent
A Cloudflare Worker routes your traffic through our edge proxy, which rewrites what search engines see and serves your blog. An AI agent decides what that content should actually say.
The edge path
What happens to a request
Nothing about your site, hosting or codebase changes. A single Worker sits in front of it and hands requests to our proxy, which does the rest.
A Cloudflare Worker goes up in front of your site
Connect your Cloudflare account and we deploy the Worker for you, in about two seconds. It forwards every request to our proxy along with your site's token, and it fails open: if our proxy ever errors or times out, the Worker sends the request straight to your origin instead.
The proxy rewrites what search engines see
For each URL, the proxy fetches your real page, then injects the title, meta description, response headers and JSON-LD structured data the agent has decided on for that page, live, without ever touching your source code or your origin server.
Blog paths are served straight from the engine
Any request under the blog path you configure (for example /blog) is served directly by our hosted blog engine instead of your origin, so the AI-written articles just show up on your own domain.
In every mode, your visitors are one hop from your origin: if SEOEdgeAI is ever unreachable, the Worker and the proxy both fall back to serving your site directly.
Request by request
Your domain, our worker, your origin
The same request always makes this trip. What changes is what the proxy adds along the way.
Visitor or crawler
Requests your domain as usual.
Cloudflare Worker
Forwards it to our proxy, fails open on any issue.
SEOEdgeAI proxy
Adds headers, JSON-LD, or serves the blog.
Response
Reaches the visitor, built from your origin.
The agent
It runs the strategy, not just the requests
The proxy is only the delivery mechanism. Behind it, an AI agent continuously pulls in your site's SEO and traffic data, works out what would move the needle, and pushes that plan back through the same edge path: new titles, new structured data, and new articles on your blog.
- 01
It collects the data
Every page on your site, plus Google Search Console rankings, clicks, impressions and traffic patterns, pulled in on a schedule.
- 02
It builds a strategy
From that data it decides which searches are worth targeting for your business, and drafts a plan to go after them.
- 03
It applies the strategy
Titles, meta descriptions and JSON-LD change at the edge to match the plan, and new blog posts get drafted and published around it.
- 04
It adjusts from results
A few weeks later it reads the real rankings and traffic, keeps what worked, and revises the titles, JSON-LD and editorial plan accordingly.
Your Google data
What SEOEdgeAI asks Google for, and why
You sign in to SEOEdgeAI with Google, and the agent reads your Google Search Console performance so it knows what to fix and can prove whether it worked. That is the whole list. Here is what each permission is for, before you grant anything.
- Name, email address and profile picture
To sign you in
- SEOEdgeAI has no password of its own: your Google account is your account. We store your name, email and picture to identify you, show you your own dashboard, and contact you about your sites.
- Google Search Console, read only (webmasters.readonly)
To decide what to change, and to measure it
- The agent reads your impressions, clicks, click-through rate and average position, page by page. That is how it picks which pages are worth rewriting and how it checks, weeks later, whether the rewrite actually moved anything. It is read only: SEOEdgeAI never edits, submits or removes anything in your Search Console.
- Optional, and revocable at any time
You stay in control
- You can decline the Search Console permission and still use the rest of the product. You can revoke access whenever you like from your Google Account's “Third-party apps & services” page, and deleting your SEOEdgeAI account deletes the stored tokens and the data with them.
SEOEdgeAI's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Your Google data is never sold, never used for advertising, and never used to train an AI model.
Read the full Privacy PolicySee it running on your own site
Free to start. Connect Cloudflare and the agent takes it from there.