Results & Case Notes

What was observed, diagnosed, shipped, and learned.

Visibility work should leave a decision trail. These reports and case notes show the starting evidence, the weak layer, the work completed, what changed, and what remains uncertain.

View the Sample Snapshot

The proof inventory separates illustrative material from verified work and does not imply a client outcome.

Proof needs context, not a vanity chart.

Market benchmarks

Original Recommendation Gap reports using real prompts, businesses, public surfaces, and a published methodology.

Audit examples

Anonymized or approved examples showing how a vague visibility problem became a prioritized roadmap.

Shipped work

Implementation notes showing what changed across technical SEO, service pages, schema, internal links, profiles, citations, or source footprint.

Current Proof Inventory

Three honest assets, with the boundary stated on each one.

The sample is fictional. The two case notes describe verified changes to owned products, not client rankings, lead growth, or causal marketing outcomes.

Illustrative audit example

Sample AI Visibility Snapshot

A fictional, clearly labelled example showing the evidence, diagnosis, and next-decision format.

Not a client result · Not a ranking claim · No outcome attribution

Open the labelled sample

Shipped work · Verified owned-product note

Public build metadata boundary

All declared public manifests pass the allowlist and recursive boundary scan with zero rejected fields in the current release.

Context: Base2026 publishes machine-readable manifests for its public research product.
Observed problem: Earlier public manifests serialized machine-local build paths that were not useful to visitors.
Evidence: The release audit found path-shaped values in two served manifests and recorded the affected public fields.
Diagnosis: A build-time object was being serialized instead of an explicit public schema.
Work shipped: The exporter was replaced with field allowlists and a recursive path-leak rejection gate.
Measured change: All declared public manifests pass the allowlist and recursive boundary scan with zero rejected fields in the current release.
Limits / uncertainty: This proves the declared manifest boundary, not the absence of every possible security issue elsewhere.
Next decision: Keep the gate release-blocking whenever the public manifest schema changes.

Inspect the public product

Shipped work · Verified owned-product note

Sitemap admission governance

The current Base sitemap contains 1,734 approved URLs and zero archive/noindex admissions.

Context: Base2026 keeps useful provenance records public while excluding noindex archives from discovery sitemaps.
Observed problem: The prior Base sitemap included 199 provenance archive URLs carrying a noindex contract.
Evidence: The route ledger separated normal public Sources from archive and future/private cohorts.
Diagnosis: Archive existence and sitemap admission had been treated as the same policy decision.
Work shipped: Sitemap generation now requires explicit approved admission in addition to a valid canonical and indexable page state.
Measured change: The current Base sitemap contains 1,734 approved URLs and zero archive/noindex admissions.
Limits / uncertainty: This is a release-governance result. It does not claim a ranking, traffic, or revenue lift.
Next decision: Measure qualified discovery and product activation separately from URL count.