Skip to content
Menu

The mechanism

Why a third-party domain changes the outcome

How AI assistants and search engines decide which sources to cite, and why a case study on your own site structurally cannot be one of them.

Last reviewed: September 18, 2026

Most B2B companies already produce customer stories. They are usually well written, well designed, and almost never cited. The reason has nothing to do with quality.

How an AI answer is actually assembled

When a buyer asks an assistant to compare options in your category, the system does not retrieve "the best content". It retrieves passages it can attribute, then assembles an answer from the ones it treats as sources. Two properties decide whether a passage makes it in: whether the claim is stated in a form that can be lifted and attributed, and whether the publisher is something other than the party that benefits from the claim.

A page on your own domain fails the second test by construction. It does not matter how rigorous the underlying work was. The system is not evaluating your honesty. It is evaluating the structural relationship between the publisher and the claim, and on your own site that relationship never changes.

The same logic has governed search for years

Search engines have weighted source independence for a long time; it is the reason a review in a trade publication outranks the vendor's own page for the same query. What is new is that generative systems make the consequence visible. In a list of ten blue links, your own page could still appear. In a synthesised answer that names three sources, it usually does not.

What a citable source actually looks like

Across both systems, the properties that matter are consistent and fairly mundane:

  • A publisher distinct from the subject. A separate domain, with its own editorial identity.
  • A named author who resolves to a real person. An author entity with live, verifiable profiles attached is treated very differently from a byline that exists only as text.
  • A stated method. Published, versioned, and specific enough to be checked.
  • Dates. When it was published, when it was last reviewed.
  • Specific, self-contained claims. A figure with its baseline and its timeframe attached can be quoted; a sentence about "significant improvements" cannot.
  • Machine-readable structure. The claim, the author, the publisher and the dates expressed as structured data, not only as visual design.

What we do about each of them

That list is, more or less, the specification for this site. We publish on a separate domain under a public methodology. Every story carries a named analyst whose profile links to their real, live professional presence. Every figure is published with its origin, its baseline and its timeframe. Every story states its evidence tier and what we could not confirm. All of it is emitted as structured data as well as visible text, and every page is server-rendered so its content exists in the HTML source instead of being assembled by a browser.

None of this is a trick, and none of it is a backlink scheme. It is the ordinary practice of publishing, applied deliberately, by someone who is not you.

What we cannot promise yet

This domain is new. Citation authority accumulates; it cannot be bought, and anyone telling you otherwise is selling something worse than this. A story published here today is structurally correct and will be indexed and attributed properly, but the weight it carries grows as the publication does.

We would rather state that plainly than let you infer a promise we have not made. It is also why we publish research that nobody pays for: a publication earns the right to be cited by being worth citing, and paid stories inherit that standing rather than creating it.