OUHUD combines website checks, content work supported by evidence and samples of AI answers. This page explains which evidence matters and what it can tell you.
The method applies to customer websites and our own website. Data available for a particular website depends on connected sources, the agreed scope and successful measurements.
A crawler fetch, an AI source and a customer inquiry are different events. We treat them as separate evidence.
| Signal | What it demonstrates | What it does not demonstrate |
|---|---|---|
| Cited page | The answer names a specific URL as a source. | It does not show whether anyone opened that link. |
| Brand mention | The company name appears in the answer examined. | It does not establish a linked source or a recommendation. |
| Visit | Connected web analytics records a session under its own measurement rules. | Organic search traffic is not automatically AI traffic. Missing referrers limit attribution. |
| Inquiry | An event configured for this purpose, such as a submitted contact form, was recorded. | Not every key event is an inquiry. An inquiry does not prove causation by one particular change. |
Compare the same questions, languages and systems over named periods. Record website changes and measurement failures. Without a successful measurement, the result is ‘no data’; zero means that a measurement was completed and nothing was found. More visits after a change are an observation, not yet evidence that the change caused them.
Our product descriptions are statements by the provider. These public documents help you assess them; they do not replace an independent customer reference.
These documents explain technical requirements and measurement terms. They do not establish an OUHUD success rate or an effect for a particular customer.
Google describes SEO basics, accessible text and internal links. Special AI markup is not required, and inclusion is not guaranteed.
Questions to assess original insights, verifiable sources and clear authorship.
Definitions of sessions, landing pages and key events. The documentation does not turn a sequence of events into proof of causation.
Bing describes aggregated citations per URL and samples of grounding queries. They show neither rankings nor complete user questions. Such a report remains separate from your own API sample.
Sources checked:
Bring an important service page, its supporting company sources and your customers’ questions. Together, these provide a starting point you can verify.
