Example report
An unedited report from the live database, so you can judge the output before paying for it.
Open it
This is our own site, anifusion.art, measured the same way a customer's site is — most recently on 2026-09-18. The score it came out with is 32, which is not a flattering number and is the real one.
No account needed. The same thing a free scan gives you, on a site you do not own.
Four things worth checking in it
A report is only useful if you can tell good output from confident output, so here is what to look at rather than a list of features:
- The answer text. Every number in the report is derived from stored answers, and the report shows them. If a claim in the summary does not match the text underneath it, the text is right and the summary is a bug — tell us.
- The interval next to the score. A visibility number without a range is a guess wearing a suit. The report states how many questions the range comes from, and says plainly when it is too wide to act on.
- Which engines ran. The report names them. Two scans on different engines are not comparable, and the report refuses to compare them rather than drawing a line through the difference.
- The competitor section. Being absent matters less than who is present instead. The names in that list are the ones the models reach for when someone describes your market — they are your real competition in this channel, whether or not they look like it on a search results page.
Where the number comes from
The formula, the weights, the sampling and the known weaknesses are all on the methodology page. You can check the report against it line by line, which is the only reason to publish it.
If you would rather see the method applied across a whole market instead of one site, the AI brand monitoring category is measured on the same pipeline — including our own entry, sitting wherever it sits.
What you do not get
The free report is the real measurement, not a teaser with the useful part removed. There is no locked section and no blurred chart. What the paid plans add is repetition: monitoring that re-runs on a schedule, history you can compare against, alerting when something moves, and re-checking a fix you have made. Those are the parts that need a database and a schedule, and they are what you are buying.