Client reports

A client report is a scheduled monthly summary of a Website's performance, opened by a plain-English narrative and delivered by email to recipients you name. It also has a share link, so a stakeholder can read it without an account.

The narrative is written by RankX AI from the period's already-computed metrics. It is metered, and it degrades rather than blocking: if it cannot be generated, the report still sends with its metrics.

What a report contains

A narrative opening, in plain English, written from the period's metrics. Reporting that leads with a sentence rather than a chart is measurably better at keeping clients: the benchmark this feature was built against found clients who engage with narrative-driven reports churn at a fraction of the rate of those who do not.

The metrics for the period, with the same denominators and the same honesty rules as every other surface: a rate carries the checks behind it, and an unmeasured figure is blank rather than zero.

Scheduling

Reports are scheduled monthly, on a send day you choose. The day is capped at 28 so that every month has it, which is a small thing that matters exactly once a year in February.

Recipients are set per schedule, and the list is bounded: a client report is a report, not a mailing list.

A schedule can be switched off without being deleted, which keeps the history and the recipients for when it comes back.

The narrative is metered

Generating the narrative is provider work on your agency wallet, so it reserves credits before and settles after, at the published rate. It appears in your usage report like any other spend, attributed to the Website it was written about, and counts against that client's budget if one is set.

The rate is on the credit cost reference.

It degrades, it never blocks

If the narrative cannot be generated, the report still sends, with its metrics, and the failure is recorded.

That is the right trade for this artefact: the narrative decorates the report, it does not constitute it. A client expecting a report on the first of the month should get one, and a missing paragraph is a much smaller failure than a missing report.

The opposite trade is correct elsewhere in RankX AI, and the difference is worth naming: an article generation that produced no body throws, because an empty article is not a degraded article, it is nothing.

The share link

A report has an unauthenticated, token-scoped share link. Anyone with the link can read that report, and it needs no account.

That is the point: the person who most needs to read a client report is often not the person with the login. It is also worth understanding before you forward one, because the link is the credential.

See share links for every shareable surface and what each exposes.

Sending from your own address

With white label configured, reports send from your agency's own address rather than from RankX AI, and per-client template overrides sit on top of your agency defaults.

That is usually the highest-value part of white label, because email is the surface a client sees most often.

Reading a report before your client does

Worth doing for the first one on any new client, for two reasons: the narrative is written from metrics rather than from your relationship, so it will say plainly what the numbers say, and a period with a large not-measured share reads very differently from one without.

If the numbers are thin because a connection is not ready or a cadence is slow, fix that before the report goes rather than explaining it afterwards.

Where to go next

• White label, for branding and sending.
• The client portal, for clients who do log in.
• Share links, for every unauthenticated surface.