What Changed in CitePulse in October 2026: White-Label Agency Reports, the Public AI Visibility Badge, and Traffic from AI

Three things shipped this month, all live. An agency now delivers the client report under its own brand, as a PDF and as a public link that needs no login. Every monitored brand has a public AI Visibility profile at /verify, with a badge you can embed. And GA4 traffic from AI is now self-serve, so you connect it yourself and see the sessions that already arrive from assistants. Here is what each one does, what it deliberately does not do, and what it costs.

White-label reports for agencies

An agency on the Scale plan manages client domains under its own identity. The client report now carries the agency logo, colours and reply-to, with no CitePulse mark by default. A small “Measured by CitePulse” line is an opt-in switch, off by default, because a powered-by footer in a client deliverable is an anti-pattern: it hands the client the name of the tool to go to directly.

There are two ways to deliver it. The agency opens the signed-in preview from its panel, and sends the client a public link that needs no login at all. That public link is token-gated and served with an X-Robots-Tag: noindex, nofollow header on every response, HTML and PDF alike, so a report shared by email never ends up in a public search index. Adding ?format=pdf serves a PDF built after each monitoring run; when no PDF has been rendered yet, the same link falls back to the live HTML, so a fresh client never sees a broken download.

Two smaller pieces round it out. Alert routing is now per client: a dropdown chooses agency only, agency and client, or client only, and when an alert does go to the client it is sent under the agency reply-to with no CitePulse mention. And the panel keeps an open view log, so the agency can see when and how often a client opened the report link. The IP address and user agent are hashed with a per-client salt before anything is stored, so the agency reads “opened four times this week” with no personal data kept at rest. For programmatic use there is an API v1 key that lists clients and reads each client’s score, source presence and badge state, at 120 requests a minute. Ten client domains are included on the Scale plan, and each additional domain is a flat thirty dollars a month.

A public AI Visibility profile and badge

Every brand we monitor now has a public profile at citepulse.ai/verify/yourdomain.com. It shows the live composite score, the trend across recent runs, which answer engines were checked, and when it was last verified. A brand with an active, eligible subscription shows as AI Visibility Verified and gets a badge it can embed on its own site. The embed links back to the live profile, so the number a visitor sees is always the current one, never a screenshot that quietly goes stale.

The score is an observation of how often assistants cite the brand on a fixed set of questions. It is not a guarantee of ranking, traffic or sales, and the page says so. A domain without an active badge shows no score and no detail at all: the page states the brand is not currently verified and is marked noindex, so nothing private leaks through a guessed URL.

GA4 traffic from AI, now self-serve

CitePulse already read Google Analytics; now you connect it yourself, without us touching anything. In the SEO and AI tab, “Connect GA4” runs a read-only Google authorisation, “Sync GA4” finds your property and pulls the data, and the “Traffic from AI” card shows the sessions and conversions that arrived from ChatGPT, Perplexity, Gemini and other assistants. The connection is read-only and you can remove it in one click.

One thing to be clear about: a session tagged as coming from an assistant is a referral that already shows up in your own analytics. It is a correlation, not proof that a citation caused the visit, and the card does not claim otherwise. It tells you that AI-sourced traffic is arriving and from where, which is a different question from whether a given citation moved anyone.

Want to set this up on your own site first? Our founder wrote a step-by-step walkthrough: How to track ChatGPT traffic in Google Analytics 4.

What did not change

The free audit is the same five-question, three-engine, three-repetition matrix with a fixed budget. Every number still comes from a real answer, not from reading your HTML. Google AI Overviews are read as a source, not counted as an engine. The public noise panel keeps running every day. And every result is still an observation: beyond the engines’ own noise band, or within it. Never proof of cause.

Frequently asked questions

Can I send a client a report without giving them a login?

Yes. The public report link needs no login, carries your agency branding (logo, colours, reply-to), and is served with an X-Robots-Tag: noindex header on every response, so it never reaches a public search index.

Is the agency client report really unbranded?

By default there is no CitePulse mark. A small “Measured by CitePulse” line is an optional switch, off by default.

What does the public /verify page show for a brand without a badge?

No score and no detail. The page states the brand is not currently verified and is marked noindex, so nothing private is exposed.

Is GA4 traffic from AI proof that a citation drove the visit?

No. It is a referral visible in your own analytics, reported as correlation. CitePulse does not claim the citation caused the visit.

Does the public AI Visibility score guarantee anything?

No. The score is an observation of how often assistants cite the brand on a fixed set of questions. It is not a guarantee of ranking, traffic or sales.

See it before you sign in: the live demo runs on sample data for a fictional company, or run your free audit. Related reading: what changed in September and citation share, the new share of voice. See also: daily AI visibility monitoring · CitePulse for agencies · Fact Integrity, wrong prices and facts in AI answers.