Question 1

Is this cloaking?

Accepted Answer

No. The agent view only restructures and re-represents content already on your page — and that boundary is enforced in the generation engine, not left to editorial policy, so it cannot emit a claim your human page doesn’t make. SEO crawlers are untouched: Googlebot and Bingbot receive exactly what they received before, because routing applies only to AI agent user agents.

Question 2

Will it change what my customers see?

Accepted Answer

Nothing changes for customers or for Google. The routing check happens in your CDN before anything else, so any request that isn’t a recognised AI agent passes straight through to your origin, byte-identical to today. We verify it at setup with a test you can run yourself.

Question 3

Will it hurt my existing SEO or rankings?

Accepted Answer

No — no mechanism exists for it to. Your rankings are determined by what SEO crawlers and users receive, and both are byte-identical to before AXP Edge. There is no new URL, no redirect, and no change to your sitemap, canonical tags, internal linking or crawl budget.

Question 4

How long does setup take?

Accepted Answer

Under two hours of actual work — one small function deployed on the CDN you already use, two environment values, one route binding, with one-click rollback. Typically same-day once whoever manages your CDN picks it up. We then verify together: an agent request carries our header, a human request is byte-identical to before, and a simulated backend failure falls back cleanly to your origin.

Question 5

Which CDNs and platforms are supported?

Accepted Answer

Cloudflare, Amazon CloudFront and Akamai — the same routing contract implemented natively on each. If you’re on a different CDN, or serving directly from origin webservers, tell us your stack and we’ll scope it; the architecture is CDN-agnostic by design.

Question 6

What if something breaks on your side?

Accepted Answer

It fails safe, structurally. If our backend errors, times out or is unreachable, the edge function serves your origin page directly with a diagnostic header, so the worst case at any moment is your site exactly as it is today. Publive’s infrastructure runs at 99.995% uptime across 1B+ pageviews a month, and failover rate is a first-class dashboard metric.

Question 7

Does it slow down my site or add latency?

Accepted Answer

No. Human traffic never enters the AXP Edge path, so visitor page-speed and Core Web Vitals are unchanged by construction. Agents are served from a pre-warmed cache in under 500ms — typically faster than origins manage today, given the median Indian enterprise brand takes 1.3 seconds to answer an AI agent.

Question 8

How do you decide who gets the agent view?

Accepted Answer

By user agent. The requester’s declared user agent is matched against a list of known AI agents that we maintain and update as new ones appear, and you choose which agent families and which paths are covered. Everything else — every human browser, every SEO crawler — passes straight through to your origin untouched. We also record each connecting IP, so verification that a claimed agent is genuine can be layered on without you touching your edge config again.

Question 9

How is this different from AI Streams?

Accepted Answer

Edge makes the pages you already have legible and extractable to AI agents. AI Streams publishes new, AI-first content on your domain to expand what you can be cited for. Streams is the offence, Edge is the eligibility layer — most brands run both, and Edge is usually the faster first step because it needs no content production.

Page	Agent traffic	AI citations	AI referrals
Publive \| AI Visibility Platform publive.online/	6,240+34%	41+18%	318+27%
Publive \| AXP Edge /axp-edge	2,180+52%	12+60%	96+44%
Publive \| Streams /streams	1,940+21%	23+15%	142+12%
Publive \| Blog: the GEO playbook /blog/geo-playbook	1,360+28%	9+12%	71+9%
Publive \| CMS /cms	980+15%	6flat	38+6%

AXP Edge

Get found in AI answers, without changing your website

Before AI can choose you, it has to read you

Discover

Understand

Trust

Choose

The foundation, rebuilt at the edge

One request in. The right page out for every visitor.

One web address. Two audiences.

Health insurance that keeps up with your family

Only AI gets the clean view

Two things start to move in the first few weeks

Enterprise-safe by design

Nothing changes for customers

This is not cloaking

It stays on your own domain

It cannot break your site

Pricing that scales with your AI visibility

Questions, answered

Start being the answer today