ProofRank

The description states that ProofRank is:

• A technical inspection tool for website migrations or cleanups.
• A local, read-only Codex plugin that imports exported data from various sources (GSC, GA4, WordPress, sitemap, crawler, etc.).
• A system that:
  • Normalizes URL identities without discarding source provenance;
  • Verifies that the declared starting scope matches inventory by SHA-256;
  • Checks full HTML for every active page in scope;
  • Reports evidence conservatively (broken, noindex, schema, duplicate, reachability, overlap, link-opportunity);
  • Emits a machine-readable decision.json contract with either WITHHOLD or READY_FOR_HUMAN_REVIEW.

It also includes:

• A Guarded Release Contract in decision.json;
• A dashboard that shows owner/release explanation and technical evidence ledger;
• No API keys or third-party packages required for demo.

The tool is described as offline, read-only, and not connected to production systems.

Claim: ProofRank is a local, read-only plugin.

Evidence: The write-up explicitly says it does not perform OAuth, call live APIs, control crawlers, or write to production. It uses offline adapters and deterministic Python tools.

The author positions ProofRank as a solution to the problem of false completeness in SEO evidence during website migrations:

“Unsafe automation does not remove work; it creates review, risk, and cleanup.”

It is described as turning this issue into an enforceable product rule:

“no whole-site graph conclusions until the declared starting scope is bound to evidence and every active in-scope page has usable HTML.”

The evolution of the claim appears to be from a personal workflow to a reusable plugin, with Codex used to refine design and test automation.

Claim: ProofRank prevents “false green” outcomes.

Evidence: The write-up contrasts an incomplete case (7/11 identities present) that still fails even if all observed pages have HTML, versus a complete case that passes.

The description states two main user groups:

• Site owners, who want to ask SEO specialists or developers to prove that valuable pages haven’t disappeared.
• Technical teams, who use it as a local, read-only Codex plugin.

It is not clear whether ProofRank targets agencies, internal teams, or individual practitioners. The tool is described as being used in large-scale WordPress migrations, but no specific customer segments are named.

Claim: Site owners and technical teams.

Evidence: The write-up describes the product’s use for both site owners and developers, especially in migration contexts.

There is no evidence of a business model or pricing structure. The tool is described as a plugin built with Codex, and it is not presented as a commercial offering.

Claim: Not evidenced.

Evidence: No mention of monetization, subscriptions, licensing, or pricing.

The project is described as:

• Built using Python, Codex, and various tools like Playwright, JSON, CSV, HTML, CSS, XML, GitHub Actions.
• A deterministic system that uses SHA-256 to bind inputs.
• A read-only plugin, not connected to production.
• Includes offline adapters, regression tests, CI, secret scanning, and a dashboard.

Claim: Technical delivery is offline, deterministic, and reproducible.

Evidence: The write-up says it uses standard Python libraries, does not call live APIs, and includes CI, regression tests, and secret checks.

There is no evidence of traction or adoption. The project is described as a personal workflow turned into a plugin, with only synthetic fixtures and sanitized private data used for demonstration.

Claim: Not evidenced.

Evidence: No customers, revenue, usage metrics, or public adoption are mentioned.

The description does not mention competitors or similar tools. It is unclear whether ProofRank is positioned against existing SEO tools, migration platforms, or workflow automation systems.

Claim: Not evidenced.

Evidence: No competitive landscape or comparison to other tools is provided.

• The tool is described as a read-only plugin, not a commercial product. This raises questions about its scalability and path to market.
• It is not connected to production systems — this may limit its utility in real-world workflows.
• There is no evidence of monetization, customers, or traction — suggesting it’s still in early development or prototype stage.

Inference: The tool may not be ready for commercial use without further development or integration into larger platforms.

Evidence: The description says it's a plugin, not a service, and lacks any indication of real-world deployment or monetization.

1. What is the intended user base beyond the author’s personal workflows?
2. Is there a plan to make this available beyond a local plugin or read-only tool?
3. How does ProofRank integrate into existing migration or SEO workflows?
4. Are there any plans for authentication, production integration, or API access?
5. Has it been tested in real-world scenarios beyond the synthetic and private examples provided?