How to Export and White-Label Your AI Visibility Reports

Exports are usually the least interesting screen in any product — a formality bolted on so people can get their data out.

Here it is closer to the point. AI visibility is a new enough measurement that most of the people who need to act on it are not the people logged into the dashboard. Your client, your CMO, the developer who has to fix a robots.txt — none of them will open this tool.

Whether this work gets funded next quarter usually depends on a document, not a dashboard.

Why Exports Matter More Here

With an established channel, everyone already knows what the numbers mean. Search traffic needs no explanation; a drop is understood without commentary.

AI visibility has none of that shared vocabulary yet. A score of 46 means nothing to someone seeing it for the first time, and share of voice is not a metric anyone has an instinct for.

The Five Formats

The Export & Reports screen offers five, and they are genuinely different documents rather than the same content in five wrappers.

The complete picture: every platform score, the prompt tests and the action plan. This is the reference document — the one you attach rather than the one you expect anyone to read end to end.

Scores, top issues and the key recommendations, built from the pages you have run Content Audit on. This is the one that actually gets read.

All scores, prompt results and competitor data in spreadsheet form. For analysis, not for sending — the format you open when you have a question the reports do not answer.

The comparison document: where you sit against competitors, with gap analysis and recommendations. The most persuasive of the five, because it puts a name next to the problem.

Structured output for integration with other tools and dashboards. The only format that stops AI visibility living in its own silo.

Choosing the Right One

The mistake is defaulting to the biggest document because it feels most thorough. Match the format to the reader instead:

A Note on the Executive Summary

The summary is built from the pages you have run Content Audit on. That is worth reading twice, because it is the most common cause of a disappointing export.

With two pages audited, the summary has two pages' worth of issues to summarise. It will look thin, and the reader will conclude there is not much going on — which is the opposite of what you wanted the document to say.

Audit one page per template before generating a summary you intend to send.

CSV and JSON

These two are the least used and the most valuable to the people who use them.

CSV arrives as multiple sheets covering scores, prompt results and competitor data. It is where you answer questions the PDFs do not: which prompts moved this month, which platform contributes most of your visibility, whether your gains cluster in one topic.

JSON is the integration path. Pipe it into the BI tool, the client dashboard, the warehouse — anywhere the numbers sit beside the other numbers.

That last point is the difference between a channel that gets managed and one that gets forgotten. A metric living only in its own tool is a metric nobody checks in a busy quarter.

White-Label Settings

Below the export options sit the White-Label Settings: an Enable White-Label toggle, then Company / Agency Name, Logo URL and Brand Color. The fields stay disabled until white-labelling is enabled, and it is an Enterprise plan feature.

Three practical notes:

The Agency Workflow

For agencies this screen is most of the product's commercial value, because AI visibility is currently an easy thing to sell and a hard thing to show.

In a pitch, the comparison document does more work than any score. "Here are the questions your buyers ask, and here is who the AI names instead of you" is a conversation that starts itself.

Name, logo URL and colour. Every export after that inherits it, and you never send an unbranded document by accident.

One page in the body of the email, the reference document attached. The client reads the first and trusts the existence of the second.

Six months of monthly exports is a real dataset. It is also the evidence that your work moved something, in a form no dashboard screenshot can match.

How Often to Send One

Monthly, for almost everyone.

AI visibility moves on the timescale of published content and re-read sources. A weekly report mostly documents variance, and the effect is worse than no report — the reader learns that the document rarely contains news and stops opening it.

Monthly gives changes time to be real, and gives you time to have done something between editions.

Common Mistakes

Fifteen pages to someone with four minutes gets skimmed and remembered as "complicated". Send the one-pager.

The summary is built from your content audits. Thin audit history, thin summary, wrong impression.

It is the only format that puts these numbers where people already look. Ignoring it keeps AI visibility a side project.

A report that names three problems and produces no tasks was a document, not a decision. The action list is where it should land.

Frequently Asked Questions