Evidence
Observed or deterministically normalized web facts: timestamps, HTTP state, fingerprints, structured-data observations, headers, links, text similarity, word counts, verification events, and provenance records.
Evaluate GoGuides on the evidence model, not the marketing language
GoGuides v3 is hybrid web-evidence infrastructure for systems that consume the open web. It combines independent observation and provenance with longitudinal state, deterministic comparison, source-use decision context, bounded derived evidence, and model-assisted analysis while keeping those evidence classes distinguishable.
The core model: Evidence → Interpretation → Decision
Interpretation
Deterministic comparisons, GoGuides-derived assessments, bounded relationship evidence, and model-assisted analysis remain identifiable as interpretation rather than being presented as raw observation.
Decision
A consuming system decides how to rank, cite, recommend, retrieve, transact, or abstain. GoGuides exposes decision context but does not require an outside system to adopt it.
Scope matters: domain/root and exact page are not interchangeable
GoGuides distinguishes the authoritative root/domain scope from one normalized exact URL. Different deeplinks can legitimately have different page observations or page-level evaluations. What should never happen is the same normalized scope receiving conflicting GoGuides values from different public interfaces.
In practice: ordinary Evaluate, Batch Evaluate, profiles, machine discovery and other public
surfaces should converge on the same authoritative resolver for the same supported normalized scope.
Current public architecture
| Capability | Role | Important boundary |
|---|---|---|
| Evaluate | Primary root/domain and exact-URL evaluation surface. | GoGuides assessment and source-use context are not universal ground truth. |
| Batch Evaluate | Multiple exact URLs through the same evaluation authority. | It is transport efficiency, not a second scoring system. |
| Web State V3 | Latest stored objective observation for supported root-domain state. | Stored observation, not a synchronous live fetch. |
| Change Intelligence V1 | Deterministic comparison of concrete stored observation pairs. | Reports supported mechanical differences without inventing semantic severity. |
| URL Request | Explicit attributed request for intelligence on one full public URL. | Request intent and crawler work are separate; ordinary observational reads are not URL Request adoption. |
| Claim Support | Bounded model-assisted judgment against one fixed stored source observation. | Not a universal fact checker or certificate of truth. |
| Content Relationships V1 | Conservative comparison of two exact URLs using stored evidence. | Does not infer ownership, coordination, deception, intent, or publisher independence. |
| Verified Text | Source-attributed public text with stable record metadata and integrity values. | Hash integrity shows record consistency; it does not certify every proposition in the text. |
Observation, verification, derived assessment and crawler activity are different signals
| Signal | What it can mean | What it does not establish by itself |
|---|---|---|
| Observed | GoGuides has stored an observation for the represented scope. | Ownership verification, external endorsement, or truth of every page claim. |
| Verified | An accepted GoGuides process demonstrated control or authorization. | A high rank, factual correctness of all content, or third-party recommendation. |
| AI Rank / grade / trust state | GoGuides-derived assessment under the documented GoGuides methodology. | A government rating, external standard, standards-body certification, or universal AI score. |
| Bot observed | A qualifying request was observed under the available attribution evidence. | Indexing, citation, training use, recommendation, dependency, or commercial intent. |
| Deterministic change | Supported stored state dimensions differ between concrete observations. | Publisher motive, semantic materiality, or intent unless separately established. |
| Model-assisted result | A versioned bounded analysis was produced under the stated input and analysis contract. | Permanent truth or an immutable replacement for the underlying evidence. |
Questions a skeptical technical reviewer should ask
Normalization
Does the same normalized URL/scope resolve consistently across public interfaces?
Provenance
Can the consumer distinguish what GoGuides observed from what the publisher declared and from what GoGuides derived?
History
Can current state be connected to concrete historical observations without rewriting the past?
Abstention
Are unknown, unavailable, insufficient-history, observation-gap, and insufficient-evidence states exposed instead of converted into false certainty?
Machine contracts
Are schemas, methods, status behavior, machine discovery and human documentation public enough for independent integration?
Commercial separation
Is payment kept separate from the meaning of AI Rank, grade and evidence-based evaluation?
How this fits technical SEO and GEO work
Entity & identity audits
Compare canonical identity, organization details, verification state, exact-page scope and independent public records.
AI-readiness reporting
Document access, identity, provenance, machine-readable state, source quality, verification, history and crawler evidence without promising citations.
Change monitoring
Follow Web State and deterministic Change Intelligence rather than relying only on visible page snapshots.
Source-use pipelines
Use GoGuides as one inspectable evidence source while retaining your own ranking, safety, citation and eligibility policy.
Relationship analysis
Use conservative exact-URL relationship evidence without turning similarity into unsupported claims about common ownership or intent.
Claim review
Use bounded Claim Support when you need a stored-source analysis layer that remains distinct from the original evidence.
Machine discovery is part of the product
Bots should not have to reverse-engineer the site to discover capabilities. GoGuides publishes a human developer hub, machine-use JSON, OpenAPI 3.1 contract, focused endpoint documentation, and capability links from public machine responses.
What GoGuides does not claim
A GoGuides record does not force indexing, ranking, citation, recommendation, training use,
safety approval, or source selection by an outside system. GoGuides publishes inspectable
evidence and GoGuides-derived assessments; consumers remain responsible for their own decisions.