The words we use.
AI visibility has collected a lot of vocabulary, some of it ours. Each definition here is the same wording that appears on the product page it belongs to, so nothing means one thing in a glossary and another thing in the app.
- Brand Intelligence
-
Brand Intelligence is Ooky's reviewed set of recurring public facts from a connected site. You can edit the public profile, while private Studio guidance remains separate. Ooky adds the shared public facts to each AI-ready page, compiles the JSON-LD types it can provide, and gives every page its own source check and release status.
Brand Intelligence - Source check
-
For a page with a captured source, at least 95% of the distinct normalized content tokens in its AI-ready version must also appear on the visible page. A separate 10% Jaccard sanity floor helps catch empty content or content from the wrong page. A missing source capture produces an unverified status.
Security - Content match
-
Content match is the result Ooky reports for a page's source check. An AI-ready page must reach at least a 95% content match with its captured visible source before it can be served, and a page that falls short is held rather than published.
Site Health - Do-not-infer
-
A do-not-infer instruction can be included with compiled page data when a missing value must stay unknown. It is separate from the editable public profile and is not a visibility setting on every Brand Intelligence field.
How do-not-infer works - Query Fanout
-
Query Fanout shows the grounding searches a provider disclosed while producing an answer. Ooky groups related wording and maps the destinations. Providers may hide searches, and these strings are not search-volume estimates.
Brand Tracker - AI Session
-
AI Traffic is the product area. An AI Session groups captured crawler requests into one journey. You can open the individual events beside it, and Ooky labels inferred intent as an inference.
AI Traffic
A term here that we've explained badly?
Tell us. Vocabulary that only makes sense to the people who built the product is a documentation bug, and we would rather fix it than defend it.