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.

Question 10

Is this just AI-spun content that will get penalised?

Accepted Answer

No. Every page is built from your own Brand Knowledge Hub, fact-checked by agents, then human-reviewed and client-approved before it publishes. It’s original, governed content grounded in your approved sources, not scraped or spun. We optimise for being cited by answer engines, not for gaming a ranking algorithm.

Question 11

Will Google treat this as spam or hurt my existing SEO?

Accepted Answer

The opposite. Pages are server-side rendered, schema-rich and genuinely useful, which is what both search and AI reward. They live in a subdirectory on your own domain and are additive. Your existing pages and rankings are untouched.

Question 12

Who owns the content, and what happens if we leave?

Accepted Answer

You do. Every page is work-for-hire and yours to keep. If you ever stop, the content, the pages and the Brand Knowledge Hub remain with you. No lock-in.

Question 13

How is this different from a content agency or an AI writer?

Accepted Answer

Agencies give you words; AI writers give you volume. Neither owns the infrastructure (SSR, schema, crawler hygiene) or measures the outcome. Publive pairs agent-built, human-approved content with AI-ready infrastructure and reports Citations % and Share of Voice: the full rail from published page to cited answer.

Question 14

How do you decide what to write about?

Accepted Answer

The Prompt Curator Agent builds a query universe from the questions your buyers actually ask AI, ranked by citation gap, demand and competition. You approve the prompt set before anything is written, so effort goes where it moves your Share of Voice.

Question 15

How do you measure success, and when do we see it?

Accepted Answer

Baseline Citations % is captured up front. Pages typically get discovered and start attracting AI bot traffic within the first weeks, with citation movement building over months 2–6 and a formal benchmark review at month 6.

Question 16

Is our brand data safe, and is content on-brand and compliant?

Accepted Answer

The Brand Knowledge Hub is built only from sources you validate, and a Compliance QA agent checks voice, claims and schema before human review. Nothing is invented. Content only reorganises and represents what you’ve approved.

Question 17

How much work is this for my team?

Accepted Answer

Light. A Publive CSM runs onboarding and the workflow; your team’s main role is validating the Hub, approving the prompt set, and approving pages before publish.

Simple pricing, for both products

Not a content budget, a digital infrastructure investment

Questions, answered

Let’s find the right fit on a quick call