Should AI visibility reports show both raw and canonical URLs?

A citation can look different across AI answers while resolving to the same document: tracking parameters, redirects, HTTP/HTTPS variants, trailing slashes, mobile routes, and declared canonicals all create noise.

I think an auditable visibility report should keep two layers:

1. The raw URL exactly as the answer engine returned it.

2. A normalized record containing the resolved URL, declared canonical, registrable domain, and every transformation applied.

That lets teams deduplicate without erasing evidence. It also prevents a normalization update from silently rewriting historical results.

The transformations should be conservative: remove only approved tracking parameters, preserve query values that change meaning, cap redirect hops, and record failures instead of dropping them.

For the product and marketing teams here: would you rather see one cleaned citation count, or a cleaned count that expands into the raw URL and transformation ledger?

We are working through this reporting question at https://corank.ai, and I am especially interested in how founders want uncertainty presented without overwhelming the main dashboard.