Publication details
Record the source URL, title, publisher-reported author, publication dates, and content fingerprints for an eligible version.
WordPress publication evidence
A clear record of what you publish.
WP ContentLedger creates a traceable publishing history for WordPress content. It connects publication details, content fingerprints, and recorded revisions so readers can inspect the evidence behind a page or post.
Certificate repository coming soon.
In developmentIntegrated certificate publishing is coming.
WP ContentLedgerPUBLICATION RECORD
Publication evidence certificate
Building a better record of the published web
RECORD05
example.org/journal/a-better-record
- SOURCE AUTHOR
- Jamie Reed
- SOURCE PUBLISHER
- Fieldnotes Journal
Attribution reported by the publisher
The evidence behind this record
Submission signatureVerified
Manifest digestVerified
Publisher identityLocal enrollment
Independent timestampNot evaluated
REVISION HISTORY030405
Illustrative local record. Each check has its own scope.
01 / The publishing record
Give your publishing history a record people can inspect.
Publishing dates tell part of a story. ContentLedger adds records of the content, its stated source, and its changes, with evidence that can be examined separately.
Revision history
Keep relationships between recorded versions so an update can be understood in the context of earlier evidence.
Separate evidence checks
Connect signatures, archive references, and timestamp proofs where available. A submitted request and a completed check are different things.
Portable evidence
Export supported evidence for inspection beyond the WordPress site. A certificate gives readers an accessible starting point for understanding those records.
02 / How it works
From publication to an inspectable record.
PLANNED INTEGRATION
This is the intended workflow for integrated certificate publishing.
- 01
Publish in WordPress
Publish a public page or post using WP ContentLedger.
- 02
Record the version
The plugin records the supported publication data and content fingerprint. The planned integration submits that evidence to the central certificate repository.
- 03
Inspect the certificate
The repository provides a stable certificate address with source details, recorded revisions, and the results of the checks it has performed.
The integration is being built to add a new certificate revision when supported content or certified metadata changes, while keeping the same certificate address. Delivery and additional proof checks can take time.
03 / The certificate repository
Follow the evidence behind a publication.
The central certificate repository is in development. It will provide public certificate pages for reviewing source details, recorded versions, and available evidence.
certificates.wpcontentledger.com
Certificate repository coming soon.
- Source details & attribution
- A connected revision history
- Results for each evidence check
04 / What the evidence means
Different checks. Different questions.
Understand what each record tells you.
- Content fingerprint
- Do these bytes match?
- Helps check whether a defined set of bytes matches a recorded fingerprint.
- Signature
- Which key signed this?
- Connects a record to a signing key. Identity and authorization require their own checks.
- Independent timestamp
- What time bound is supported?
- A verified timestamp can support a time bound for particular evidence.
- Archive reference
- Is there a separate capture?
- Points to a separate record of the public URL, when available.
A certificate does not, by itself, establish human authorship, copyright ownership, originality, factual accuracy, or the first publication of an idea.
A publisher-reported publication date, the time a repository accepts a record, and an independently verified timestamp are different kinds of evidence.
05 / Questions & answers
A little more on the record.
The practical details behind publication evidence and the project’s development.
Contact Brian about the projectWhat is WP ContentLedger?
WP ContentLedger is a WordPress plugin for recording evidence about published content. It brings publication metadata, content fingerprints, revision relationships, and available supporting proofs into an inspectable history.
What is a publication certificate?
A publication certificate is a public view of a recorded work and its evidence. It can show the original URL, author and publisher as reported by the source, recorded versions, and verification results. The planned central repository gives each work a stable certificate address separate from the publisher’s website.
How do I verify a certificate?
Public certificate verification is in development. When available, the certificate repository at certificates.wpcontentledger.com will let readers inspect records and the checks performed on their evidence.
What happens when I update a post or page?
The integrated feature is being designed to record a new certificate revision when supported content or certified metadata changes, preserving the earlier evidence and the work’s certificate address. Complete update coverage is still being implemented and tested.
Does a certificate prove authorship or ownership?
A certificate records evidence and attributed claims. Hashes, signatures, and timestamps can support particular integrity and timing checks, but they do not independently establish who wrote the content, who owns its copyright, whether it is original, or whether its claims are true.
Is my article stored on the Bitcoin blockchain?
No. When OpenTimestamps is enabled, a cryptographic commitment derived from the evidence is used for timestamping. The article itself is not stored on-chain. A repository receipt, a pending timestamp proof, and an independently verified Bitcoin timestamp are different evidence states.
Is the certificate the same as an archived copy of my page?
No. A certificate presents metadata and evidence about a publication. An archive capture is a separate record of the page. Keeping a manifest or content fingerprint does not, by itself, preserve the complete article or let someone reconstruct it.
Is this an independent third-party authority?
The central repository is intended to host records separately from participating WordPress sites. Separate hosting does not by itself establish independent governance. The service should identify its operator and explain exactly which evidence checks it performs.
What happens if I unpublish a page or make it private?
The planned integration handles these changes as withdrawal events. Public certificate details can be suppressed while permitted audit evidence is retained. Publication, withdrawal, and retention policies will explain what remains stored and visible; withdrawal does not erase every previously distributed copy.
Can evidence be checked without the original WordPress site?
Supported portable evidence exports can be inspected outside WordPress. What can be verified depends on the artifacts included and the verifier used. A content fingerprint alone cannot recreate a missing article, and evidence retention is different from guaranteed permanent availability.
Will this improve SEO or AI visibility?
ContentLedger makes publication evidence easier to inspect and connect to its source. Search engines and AI systems decide whether and how to use those records. The project does not promise rankings, citations, rich results, or an E-E-A-T score increase.
Will I need a second plugin, and can I install this now?
The intended finished product is one WP ContentLedger plugin with integrated certificate publishing. The project is currently in development; public availability, installation requirements, and commercial terms will be announced when ready. Contact Brian about the project.
A record of publication.
Follow the development of WP ContentLedger.
Explore the project and learn how publication records and certificate verification fit together.
About certificate verificationCertificate repository coming soon.
About the project