Diagnosis defines the problem and available evidence

Identify the business question, public information, technical constraints and authorized measurement sources. Distinguish information that can be tested immediately from observations that require external access.

A missing analytics export is a data limitation, not zero performance. A page's technical availability does not answer whether a model cited it. The diagnostic record should preserve these distinctions so later reports do not treat an implementation checklist as proof of business success.

Strategy assigns priorities and acceptance criteria

Choose the information gaps that matter to the audience and define a reviewable deliverable for each. Priorities should identify the source of truth, responsible owner and evidence required for completion.

A useful criterion might be consistent product conditions across documentation and structured data. Another might be an observation protocol with explicit questions and valid-response rules. Neither should be renamed as a guaranteed increase in citation rate.

Execution produces versioned public assets

Implement approved content and technical changes, then verify the delivered result. Dates, sources, authorship and review notices must agree across HTML, Markdown and discovery files.

Keep the previous record when a correction changes an important claim. If a result narrative lacks its source, preserve the pending state rather than replacing the evidence with a general industry citation. A platform's documentation cannot substantiate a client's revenue claim.

Monitoring evaluates a defined observation

Record what was tested, when and in which interface. Compare compatible windows and question sets. Publish uncertainty, failures and configuration changes alongside favorable observations.

The institutional site is the source for current method and service scope. A project-specific case should separately identify the client when authorized, baseline, period, changes and data source. This article does not supply those records and therefore does not report aggregate client outcomes.

Frequently asked questions

Is AI Referral Engine an external certification?

No. It is Quaerion's method name. Platform documentation and independent evidence should be evaluated separately from a company's description of its own process.

How many phases does the method have?

The operational description uses four phases: Diagnosis, Strategy, Execution and Monitoring. Map, Structure and Position are the three strategic movements, not a competing count of operational phases.

Where can I verify outcomes?

Use a project-specific report with authorized sources, baseline, period and method. A general methodology page does not prove a particular client's traffic, citation or revenue outcome.

Conclusion

A method is useful when it makes work and evidence reviewable. AI Referral Engine provides Quaerion's operational structure; each project's claims still require their own supporting records and limits.

Sources

  1. Quaerion — institutional method — First-party description; not independent validation.
  2. Google — generative AI search guidance — Official guidance for site owners; implementation is not a guarantee of selection. Accessed October 4, 2026.
  3. Microsoft Bing — Citation Share and AI visibility — June 16, 2026 announcement of preview reporting capabilities and their limits. Accessed October 4, 2026.