Do not trust this page.
Verify it.
Every page on this site is hashed when it is built, and the manifest of those hashes is sealed into an append-only transparency log that is witnessed by nine independent parties and signed with post-quantum cryptography. You can check all of it yourself, right now, without trusting us and without an account.
Ready. Enter a path and verify.
Try it on any page. The hash check runs in your browser using WebCrypto: no request to us is trusted.
Four layers, each checkable
Every page is hashed at build time
When this site builds, it computes a SHA-256 of each page's plain-text version and publishes the list at /transparency.json. We hash the text rather than the HTML, because HTML churns with asset filenames on every deploy while the words stay the same. The hash moves only when the content moves.
transparency.json →The manifest is sealed into a transparency log
Those hashes are folded into one manifest hash, and that value is sealed into an RFC-6962 Merkle transparency log: the same append-only structure Certificate Transparency uses to keep certificate authorities honest. The receipt, including the inclusion proof, is published at /attestation.json.
attestation.json →The log is witnessed, not self-certified
A log you sign yourself proves nothing: you could show one history to one reader and a different history to another. This log's tree heads are co-signed by an independent nine-witness panel and are only accepted at a six-of-nine quorum. Each witness recomputes the root itself and refuses to sign a root that does not match.
the witness registry →The signatures are post-quantum
Witness co-signatures are composite: ML-DSA-65, the NIST-selected lattice signature, alongside classical Ed25519. Composite means both must hold, so the receipt survives a future break of either one. A signature is a promise about the future, which is precisely why it should not depend on a single mathematical assumption.
the current tree head →What this does not prove
A cryptography word in a marketing sentence is one of the easiest ways to imply more than you have. So, plainly: this proves content integrity and provenance. It proves the words you are reading are the words we published, and that the manifest was sealed into a witnessed log at a known time.
It proves nothing about rankings, nothing about whether our advice is right, and nothing about the quality of the writing. A verified page can still be wrong. We are not claiming quantum-beacon binding either, because the beacon was reporting stale when this build ran, and a feature you cannot demonstrate on the day you claim it is a feature you should not claim.
The point is narrow and worth it anyway: most claims on most agency sites cannot be checked at all. These can.
Machine-readable, by design
An AI agent reading this site does not want our layout. It wants the content and a reason to believe it. Both are published as data. Every page has a plain-text twin at /<path>.md, and any agent that sends an Accept: text/markdown header gets that twin instead of the HTML, which is ordinary HTTP content negotiation rather than a bespoke AI file. Every HTML response also advertises its twin in a Link header, so an agent can find it with a single HEAD request instead of parsing the page.
The provenance is data too. /transparency.json is the hash manifest, /attestation.json is the signed receipt with its inclusion proof, and /AGENTS.md describes the handshake in one page. An agent can fetch the twin, recompute the hash, check it against the manifest, and verify the receipt against a public endpoint, without any of it depending on our good behaviour.
Questions about proving any of this
What the cryptography does, what it does not, and how to check it without trusting us. Answered directly.
JAMIE KLONCZ · SEO AGENCY NAPLES ONLINE Pick a question on the left, or search above. You will get the direct answer, the way an answer engine would give it.