At a glance
Key Takeaways
- A publish date alone is weak evidence because anyone with editor access can change it. WP ContentLedger records a content fingerprint, linked revisions, and supporting proofs so the history can be checked outside your own database.
- Each check on a certificate stands on its own and proves one narrow thing. A fingerprint covers integrity, a signature ties a record to a site key, and a timestamp sets a time bound, and none of them establish authorship or copyright.
- The machine-readable layer is where provenance starts working for your brand as an entity. JSON-LD, Linkset discovery, and did:web key authorization give crawlers and AI systems structured statements about who published what, in formats they already parse.
- Brand insurance means having evidence in place before your work is questioned. The record can’t stop copying or pay out on a loss, but it lets you answer a copycat, an altered quote, or a client dispute with something checkable.
- WP ContentLedger launches on Black Friday, November 27, 2026. The lifetime deal listed on the product site is $299 once for unlimited eligible sites, with 500 new certificates per site each month.
A publish date is just a field
I’ve spent about two decades publishing things on the internet, and for most of that time I treated the publish date on a post as a fact. It took me an embarrassingly long time to accept what it really is, which is a text field. Anyone with editor access can change it, and nothing on the page tells a reader it moved.
That used to be a trivia point. Then the web filled up. Merriam-Webster named “slop” its 2025 Word of the Year, a word it now uses for low-quality digital content churned out in volume with AI. Graphite’s analysis of Common Crawl pages, reported by Axios in Exclusive: AI writing hasn’t overwhelmed the web yet, found that AI-generated articles briefly outnumbered human-written ones in November 2024 and have run about even since. Roughly half of the new articles in that sample came out of a model.
Here’s what that changes for those of us who do the work the slow way. When anyone can produce a plausible article in thirty seconds, a reader, a client, or an AI system has less reason to take your page at face value. A copycat can republish your piece with an earlier date. A quote can be altered in a screenshot. “Trust me, I wrote this first” was never much of an argument, and it gets weaker as the pile grows.
I’ve been chewing on this problem since 2017, when I was reading Po.et whitepapers and buying POE tokens on the theory that published content would need a provable record. I was right about the problem and early on the solution by most of a decade, which in investing terms is the same as being wrong.
What content provenance can and can’t do
Content provenance is the practice of recording where a piece of content came from and how it changed, so that someone else can check the record. The use cases are well rehearsed by now. It helps people assess altered or fabricated media, gives audiences a reason to trust what they’re reading, lets organizations verify their own publishing assets and spot impersonation, and gives creators documented evidence of attribution when their work is disputed.
I want the caveat up front, because this category attracts overclaiming. Provenance supports verification. It doesn’t prove a piece of content is true, it doesn’t establish legal ownership, and it doesn’t make anyone compliant with anything by default. A record shows what was recorded, by which key, no later than what time. That’s a narrower promise than “proof of authorship,” and it’s the one that holds up when somebody pushes on it.
My own view is that complete transparency is the one position that survives the slop era. I can’t out-shout a million generated pages, and I’m not going to win by adding a “written by a human” badge that anyone can copy. What I can do is publish the record behind my work and let people check it.
What WP ContentLedger records
So I built the thing I wanted. WP ContentLedger is a WordPress plugin that records publication evidence for your content. When you publish an eligible public post or page, it captures the source URL, title, publisher-reported author, publication dates, and a SHA-256 content fingerprint for that version. It then submits the evidence to a certificate repository hosted separately from your site.
When you update the post, the plugin adds a new revision linked to the one before it, and the certificate address stays the same. Earlier records aren’t overwritten. Unpublishing a post or making it private is recorded as a withdrawal event. The result is a history a reader can walk through, where each version points at its predecessor.
Around that core record, the plugin attaches supporting proofs where they’re available. A site-controlled Ed25519 signature ties the record to a key your site holds. An archive reference points to a separate Internet Archive capture of the URL. An optional independent timestamp runs through OpenTimestamps, which anchors a cryptographic commitment in Bitcoin to show the evidence existed before a given point in time. Your article never goes on the blockchain, and neither does your URL or your author details.
Each of those checks is evaluated separately, and the certificate shows a status for each one, either Verified, Local enrollment, or Not evaluated. I care about that design choice more than any single feature. A pending check is displayed as pending, and nothing gets rounded up to a green checkmark.
The outputs you can hand to someone else
A record nobody else can inspect is a diary. Here’s what comes out of the plugin that other people can use.
The first output is the public certificate. Every eligible post or page gets one at a stable address in the WP ContentLedger Certificate Repository, showing the original URL, the reported author and publisher, the recorded revisions, and the result of each check. Anyone can look one up by certificate ID, certificate URL, or the source page URL.
The second is the portable evidence bundle, a ZIP you can export and hand to a client, a platform, or an attorney. It carries the manifests, proofs, schemas, archive references, key history, and checkpoints, along with an integrity inventory of everything inside.
The third is the checker. The WP ContentLedger Package Checker verifies a bundle locally in your browser with nothing uploaded, and it lets you compare the bundle against values you obtained separately, like a package hash or the site’s DID. There’s a desktop checker that works offline too. You can check a bundle without the plugin installed and without asking me.
Underneath those sit the individual proof files, which include downloadable JWS signatures and .ots timestamp proofs, plus site-wide checkpoints with compact inclusion proofs for anyone who wants to audit the whole ledger. On your own site, the plugin publishes a public ledger page with verification records and version history.
Why the machine-readable layer matters most
Here’s where things get fun (well, fun for SEO nerds like me). Everything above is built for a person who wants to check a record. The readers I think about most these days are crawlers and AI systems, and they don’t squint at certificates. They parse structured data.
So WP ContentLedger publishes its provenance in formats machines already understand. Records are exposed as Schema.org JSON-LD and as a Markdown representation. Discovery runs through standard Web Links and a Linkset, the format defined in RFC 9264, Linkset: Media Types and a Link Relation Type for Link Sets, so a crawler landing on a post can find its provenance resources without guessing at URLs. The signing key is authorized through did:web, a DID method that resolves an identifier through your own domain. That ties the key signing your records to the same domain your brand lives on. If you run LLMS Amplifier, there’s an optional integration between the two plugins.
Why does that matter for how your brand is represented as an entity? My working theory in AI Visibility Engineering is that the brands machines describe accurately are the ones that hand them consistent, structured, corroborated statements about who they are and what they’ve published. A provenance record is that kind of statement. It says this publisher, at this domain, with this key, published this content at this URL and revised it on these dates. A certificate hosted on a separate site repeats the claim from a second location. Each one is a small, checkable fact attached to your entity, and they accumulate with every post you publish.
Now the honest part. I can’t promise rankings, AI citations, or an E-E-A-T bump from any of this, and you should be suspicious of anyone who does. Search engines and AI systems decide for themselves how to use these resources. My bet is that as generated content keeps piling up, those systems will lean harder on signals that are expensive to fake, and a signed, timestamped publishing history is expensive to fake. I’m placing that bet on my own sites first.
Why I call it brand insurance
I’ve started describing WP ContentLedger as brand insurance, and I want to be careful with the metaphor. No policy pays out here, and the plugin can’t stop anyone from copying your work. What you get is the thing you always wish you had after something goes wrong, which is evidence you set up beforehand.
Think about the situations where your work gets questioned. A copycat republishes your article and claims it, and you can point to a recorded fingerprint, a revision history, and whatever archive and timestamp evidence exists for your version. Someone circulates an altered quote from your page, and you can compare it against the content captured in your record. An impersonator publishes under your name, and readers have a signed record tied to your site’s public identity to check against. An edit becomes controversial, and you can show how the piece changed through its linked revisions. A client asks what was delivered and when, and you hand over an evidence bundle they can verify without logging into anything.
For agencies, that last one is the sleeper. I run an agency, and a portable record of what we published and when is something I want on every client site. The license covers unlimited eligible sites you own or are authorized to manage, client sites included.
Like any insurance, it has to be in place before the incident. A record that has been accumulating quietly for a year is far more useful than one you scramble to create after the dispute starts. And as with any policy, read the exclusions. A certificate doesn’t establish human authorship, copyright ownership, originality, factual accuracy, or first publication of an idea. A certificate is also no substitute for a backup, because a fingerprint can’t reconstruct a deleted article. It gives you evidence for an argument you’d otherwise have to win on your word alone.
Launching Black Friday 2026
WP ContentLedger officially launches on Black Friday, November 27, 2026. The lifetime deal is $299, paid once, and covers unlimited eligible sites, with each site getting 500 new certificates per UTC calendar month. Revisions and withdrawals on existing certificates don’t count against that allowance. “Lifetime” means the operating lifetime of the product and its service, and I’d rather say that plainly here than have you find it in the terms. There’s a full refund within 30 days, and you don’t have to show a defect to get it.
One more piece of transparency, since that’s the theme. I’d rather you check my work than take my word for it. A handful of practitioners I respect have had early access, and their feedback is on the WP ContentLedger product page. Chris Labatte of SEOBANK singled out the machine-readable outputs and the LLMS Amplifier integration for AI search work, which is the part I’d point you to first as well. Read what they said, then poke at the certificate repository and the package checker and judge the evidence for yourself.
If you want in at launch, get WP ContentLedger here. And if a copycat, an altered quote, or a “who published this first” argument has already landed on your desk, tell me how it went. Those stories will shape what I build next.
Frequently asked questions
Questions, answered
The practical details on what WP ContentLedger records, what its certificates prove, and what the launch deal includes.
What does a WP ContentLedger certificate prove?
It shows that a specific version of your content, identified by its fingerprint, was recorded and passed the checks the certificate lists. It does not establish authorship, copyright ownership, originality, or factual accuracy.
Is my content stored on the Bitcoin blockchain?
No. The optional OpenTimestamps proof anchors a cryptographic commitment derived from the evidence, and your article, URL, and author details stay off-chain.
What happens when I update a post?
The plugin records a new revision linked to the previous one, and the certificate keeps the same address. Ordinary revisions don’t use one of your 500 monthly new-certificate slots.
Can someone verify a record without installing the plugin?
Yes. Certificates are public web pages, and exported evidence bundles can be checked locally with the browser-based package checker or the offline desktop checker.
Will WP ContentLedger improve my rankings or AI citations?
I make no promise on rankings, AI citations, rich results, or E-E-A-T. The plugin publishes machine-readable provenance, and search engines and AI systems decide how to use it.