Validation evidence

Snapshot: July 17, 2026 · Evidence ID LP-2026-07-17-01

This page records a reproducible release-candidate check on a non-production Shopify development store. It demonstrates the tested workflow; it does not predict rankings, traffic, revenue, or behavior on every theme and storefront. Later deployments do not silently inherit this dated evidence ID.

Protected-store scan

The live workflow evidence in this section was captured against the protected-store sitemap-query release deployed July 17, 2026. The storefront password remained enabled. LinkPatch detected the password page, accepted the password for one scan, established a temporary same-store session in memory, and did not persist the password.

15 storefront URLs discovered.
14 healthy resources analyzed.
4 actionable contextual-link recommendations produced.
Shopify child-sitemap query parameters were preserved during HTTP discovery and stripped only when canonicalizing page URLs for analysis.

Reproducible fixture pairs

A published start page linked to four source guides. Each source contained one natural but unlinked phrase matching a separate target page:

Alpine Trail Gear Guide → Alpine Daypack
Storm Shell Guide → Storm Shell Checklist
Ridge Hydration Guide → Ridge Water Bottle
Compact First Aid Guide → Compact First Aid Kit

Exact apply and guarded rollback

The Alpine recommendation was opened in the review UI, its before and after HTML was inspected, and the individual change was approved. A Shopify Admin API read then confirmed exactly one link to the expected target. Revert restored the stored original: the resulting live hash matched the saved base hash, and the managed target URL was absent.

Immediately before apply or revert, LinkPatch fetches and hash-checks live content. A detected mismatch stops the write. Shopify's native content-update inputs do not expose an atomic version precondition, so this is a pre-write conflict safeguard rather than a content lock. In Shopify's 2026-07 API, the native page, article, product, and collection update inputs have no comparison token. Shopify documents compareDigest for the separate metafieldsSet operation, not for native content body fields.

Automated release gate

A subsequent July 17 release candidate containing the truthfulness, coverage, dependency, and public-discovery changes passed:

261 automated tests across 29 test files.
ESLint and TypeScript checks.
Client and server production builds.
A production dependency audit with zero known runtime findings.
Uncached public checks for legal/support pages, security headers, authentication guards, and unsigned-webhook rejection.

What this snapshot does not prove

It is one controlled development-store corpus, not a representative benchmark of every Shopify store.
The scanner analyzes a bounded sample of up to 100 reachable pages; dashboard link counts describe that sample.
Recommendation usefulness still requires merchant judgment and individual approval.
No search-ranking, traffic, conversion, or revenue outcome was measured or claimed.
Public Shopify App Store review, billing setup, and the reviewer screencast remain separate launch steps.

Questions or reproduction details

See support or email support@leadsfromurl.com. Do not send storefront passwords, access tokens, or customer data.