\n \n \n Evidence before conclusions — Searqon™
METHOD & EVIDENCE

Evidence before conclusions.
Method before metrics.

Every assessment has a scope, input class, method and boundary. Results should be repeatable and inspectable—not presented as an unexplained score.

ASSESSMENT SEQUENCE

What happens
to an input.

01

Declare scope

Identify the supplied document or explicitly authorized public URL. A source label is not a permission grant.

02

Validate acquisition

For remote single-page scans, apply URL, DNS, redirect, robots and bounded-fetch controls. Broader crawling and browser execution are not implied.

03

Preserve evidence

Record source identifiers, timestamps, content digests and methodology metadata. A digest is not, by itself, proof of immutable storage.

04

Run deterministic rules

Analyze the supplied content with versioned rules. Report findings, coverage and limitations without inventing universal scores.

05

Interpret observations

GEO observations remain classified by source type. Consumer-facing observations and direct model API responses are not treated as interchangeable.

06

Review and verify

Recommendations and correction proposals require human review. Automated publishing, model-weight changes and guaranteed ranking outcomes are not claimed.

OBSERVATION CLASSES

Context changes
what evidence means.

ClassMeaningInterpretation
crawlBounded page acquisitionEvidence about the fetched page and fetch context.
first_partyOwner-supplied or first-party sourceEvidence whose origin and attestation should remain explicit.
consumer_observationObserved output from a consumer-facing AI productMust not be conflated with direct API responses.
model_apiResponse from an approved model APIDepends on provider, model, prompt, region and configuration.
derivedComputed from other observationsMust retain links to its inputs and method.
estimateExplicitly estimated valueMust remain labelled as an estimate, never a measured fact.
Important limitation

Current GEO analysis and citation alerts operate on caller-supplied observations. They do not collect live provider data or scrape consumer AI interfaces. Synthetic fixtures verify software behavior, not market accuracy.