Your content deserves more than an editable date field. WP ContentLedger creates a portable, tamper-evident publishing history for eligible WordPress content—combining verified web archives, canonical manifests, site-controlled signatures, Bitcoin-attested timestamp proofs, machine-readable provenance, and independently verifiable evidence.
Plugin walkthrough video coming soon
A WordPress publication date is useful, but it can be edited. A web archive can show that a URL was publicly accessible, but it does not identify the author. A content hash can reveal whether something changed, but it needs an independent timestamp to establish when that version already existed. WP ContentLedger brings those layers together in one automated workflow.
Each recorded version produces a deterministic manifest containing its URL, claimed author and publisher, dates, version relationships, and SHA-256 fingerprints. WP ContentLedger then submits the eligible public URL for independent archiving and, when enabled, attaches OpenTimestamps proofs and a site-controlled Ed25519 signature. The resulting evidence is published through a transparent public ledger that can be inspected and independently verified.
For original research, expert contributions, reviews, datasets, news, and high-value evergreen content, readers and machines can follow the evidence from the current page to its archived snapshot, manifest, signature, timestamp proof, and recorded version history.
Creates a deterministic manifest for each recorded version and connects individual records to a signed, timestamped site-wide history.
Submits eligible public content to the Internet Archive, manages retries and rate limits, and verifies a working Wayback snapshot before publicly listing it.
Uses OpenTimestamps to create externally anchored time evidence for an exact manifest digest without publishing the page or manifest on-chain.
.ots proofs connected to the exact manifest SHA-256Signs exact manifest digests with Ed25519, publishes key authorization through did:web, and keeps the resulting evidence useful outside WordPress.
Turns preservation history into a connected public resource for readers, crawlers, LLMs, researchers, and independent tools.
Runs quietly in the background while giving site owners complete control over what is recorded, archived, and displayed.
“Add a customer quote about creating a credible publication and revision history without adding work to the editorial process.”
Customer nameWebsite or company
“Add a customer quote about using verified Wayback captures to preserve research, original data, or evergreen content.”
Customer nameWebsite or company
“Add a customer quote about the value of downloadable content receipts and independently verifiable timestamps.”
Customer nameWebsite or company
“Add a customer quote about the public Content Ledger strengthening transparency, citations, or publisher trust.”
Customer nameWebsite or company
$00one-time
Unlimited use on sites you own
Lifetime updates
Automatic archive submission and verification
Downloadable OpenTimestamps proofs and Bitcoin attestations
Protected signing keys, portable evidence bundles, and standalone verification
Public ledger, JSON-LD, Markdown, Linkset, and LLMS Amplifier integration
Email support
30-day money-back guarantee
Secure checkout. Delivery upon payment confirmation.
WP ContentLedger creates corroborating evidence that a specific canonical manifest existed no later than an externally anchored timestamp and that a public URL was captured by the Internet Archive. Ed25519 signatures associate manifest digests with a site-controlled key, while version chains and checkpoints document relationships among recorded versions. These records strengthen provenance but do not independently determine legal authorship, copyright ownership, factual accuracy, or first publication.
No. OpenTimestamps submits a privacy-protected cryptographic commitment derived from the manifest and combines it with many other commitments before a shared result is anchored through Bitcoin. Your article, URL, author information, and credentials are not placed on-chain. WP ContentLedger can identify a Bitcoin block-header attestation in the completed .ots proof; independent blockchain verification requires a compatible OpenTimestamps client and trusted Bitcoin node.
When eligible content is materially updated, WP ContentLedger can create a new record instead of overwriting the earlier one. The new manifest references its predecessor, producing a tamper-evident version chain. Site-wide checkpoints can then commit those records to a signed and timestamped aggregate history.
No Bitcoin wallet or OpenTimestamps account is required. You provide your own Internet Archive credentials for authenticated submissions, select eligible content types, and optionally generate a site signing key. WP ContentLedger protects stored credentials and signing material, provides recovery tools, and handles background submission, proof upgrading, signing, and verification.
No plugin can guarantee rankings, citations, or a direct E-E-A-T boost. WP ContentLedger makes preservation and provenance evidence more transparent and machine-discoverable through a public archive, Schema.org JSON-LD, Markdown, Linkset data, standard Web Links, and optional LLMS Amplifier integration. These resources improve discovery and correlation, but each search engine and AI system decides how—or whether—to use them.
Yes. Portable evidence bundles contain the exact manifests, JWS signatures, .ots proofs, archive references, schemas, key history, checkpoints, and integrity inventory needed for independent inspection. A standalone verifier can recalculate digests and evaluate the evidence without requiring WordPress or trusting the originating database.
WP ContentLedger provides preservation, integrity, site-key attribution, and timestamp evidence. It does not provide legal advice or independently establish human authorship, copyright ownership, factual accuracy, first publication, or permanent archive retention. WP ContentLedger is not affiliated with WordPress, the Internet Archive, or OpenTimestamps.