Content provenance
A public, timestamped record of what this website published and when, so anyone can check that a page is the one we published.
How it works
Every day an automated job fetches /okf/manifest.json, which lists the SHA-256 hash of every file in our knowledge bundle: company facts, leadership, products, customer stories and every published guide. It saves the manifest and what changed to a public GitHub ledger, timestamps both files with OpenTimestamps (anchored in the Bitcoin blockchain), and submits changed pages to the Internet Archive.
Latest run
- Date: 2026-11-20
- Files recorded: 155 (0 changed since the previous run)
- Spot-check mismatches between served bytes and manifest: 0
- Proofs still waiting for Bitcoin confirmation: 2
- Pages archived this run: 0, still queued: 0
Verify a page yourself
- Hash the page as served today:
curl -s https://www.locafy.com/okf/company/locafy.md | shasum -a 256 - Find that hash in the ledger to see when it was first recorded.
- Install the client (
pip install opentimestamps-client) and runots verifyon that day’s.otsproof.
A proof reads “Pending confirmation” for a few hours until it is committed to a Bitcoin block. A file that has been altered fails verification.
Timestamp certificates
Our main service pages, customer stories and cornerstone guides also carry a third-party certificate from ScoreDetect. Each one records the SHA-256 of the page’s knowledge-bundle file on the SKALE blockchain, so it should match the hash in our manifest. A changed page gets a new certificate version that links to the previous one.
- /blog/aeo-vs-seo (bundle file, version 1): certificate, transaction
- /blog/geo-vs-seo (bundle file, version 1): certificate, transaction
- /blog/local-seo-guide (bundle file, version 1): certificate, transaction
- /blog/local-seo-pricing (bundle file, version 1): certificate, transaction
- /blog/optimize-for-chatgpt (bundle file, version 1): certificate, transaction
- /blog/what-is-answer-engine-optimization (bundle file, version 1): certificate, transaction
- /case-studies/air-sense-environmental (bundle file, version 1): certificate, transaction
- /case-studies/clubbys-pest-control (bundle file, version 1): certificate, transaction
- /case-studies/everlift-garage-doors (bundle file, version 1): certificate, transaction
- /case-studies/pauls-gutter-cleaning (bundle file, version 1): certificate, transaction
- /case-studies/precision-mobile-tinting (bundle file, version 1): certificate, transaction
- /case-studies/sure-roy-painting-decorating (bundle file, version 1): certificate, transaction
- /products/proteus (bundle file, version 1): certificate, transaction
- /services (bundle file, version 1): certificate, transaction
- /services/ai-seo (bundle file, version 1): certificate, transaction
- /services/answer-engine-optimization (bundle file, version 1): certificate, transaction
- /services/local-seo (bundle file, version 1): certificate, transaction
What this does and doesn’t prove
It proves that the exact bytes existed no later than the attested time and were served at the recorded URL. It doesn’t prove that the content is true, who wrote it, or legal ownership. The hashes are unsigned: anyone can recompute them from the public URLs. More about these files: AI info.