An alternative to WordProof
By BlockchainSignLast updated
WordProof timestamps the content on your website. It plugs into WordPress, Shopify, Drupal, Joomla, Magento and others, records each publish and revision, and surfaces the result to readers as a trust signal with structured data attached. Millions of articles have gone through it. It is a good product for a specific job — and that job is not ours.
What WordProof does well
WordProof's insight is that a published page has a history, and that history is worth showing. Every time you publish or edit, the plugin timestamps the content and builds a visible record: here is what this page said, and when. Readers get a trust badge. Search engines get structured data.
For a publisher, that is a coherent story. It runs automatically, it requires no thought after setup, it works across most major CMS platforms, and there is a free plan. The company has since expanded into AI-related content products, but timestamping remains the core.
If you run a content site and want provenance visible on the page, WordProof does something we do not do at all.
The different problem
WordProof's model assumes the content is public. It has to be — the whole point is that visitors can see the timestamp on the page. The protection is against someone later disputing what you published or when.
Our customers are usually at the opposite end. The file has not been published and often must not be:
- an engineering design before a patent filing,
- a brand identity before launch,
- a pitch handed to one prospect,
- a deal document under NDA,
- a manuscript before it goes to an agent.
There is no page to badge. What is needed is a dated, tamper-evident record of a file that stays private.
| WordProof | BlockchainSign | |
|---|---|---|
| Protects | Published web content | Any private file |
| Trigger | Automatic on publish or edit | Deliberate, when you choose |
| Installed as | CMS plugin | Nothing — a browser page |
| Visible to readers | Yes, that is the point | No, nothing is published |
| Revision history | Yes, built in | One certificate per version you choose |
| SEO structured data | Yes | Not applicable |
| Verification | Through their verification tooling | Directly on Etherscan, no vendor |
| Pricing | Free plan, then subscription tiers | One-time per certificate |
Where the file goes
This is the question worth asking of any provider, and the answer differs by design rather than by diligence.
WordProof timestamps content that is on your website already, so confidentiality is not a concern it needs to solve. We start from the assumption that the file cannot be shown to anyone. The hash is computed in your browser with the Web Crypto API, and only that 64-character hash is transmitted. There is no upload endpoint for the file, because there is nothing for it to do. You can watch this happen in your browser's network tab, and the free SHA-256 hash generator runs the same code with nothing sent anywhere at all.
They are not mutually exclusive
If you publish and also work on confidential material, using both is entirely reasonable. WordProof handles the pages; a timestamp handles the drafts and the files that never become pages. Neither interferes with the other.
Choose WordProof if
- Your content lives on a website and you want its history visible there.
- You want timestamping to happen automatically on publish.
- You want the SEO structured data that comes with it.
- You are on WordPress, Shopify, Drupal, Joomla or Magento and want a plugin.
Choose us if
- The file is not published and must stay private.
- You want a certificate you can hand to a lawyer, client or insurer.
- You want verification that works on a public block explorer without any vendor.
- You timestamp specific files deliberately rather than a content stream automatically.