Automated Web3 SEO that anyone can verify
Web3 visibility without the manual audit: an engine scores your project from public on-chain and on-page data, the result can be registered on-chain so nobody can edit it, and the protocol signs with post-quantum cryptography.
Why the usual approach does not scale
- The tools look at the wrong layer. A keyword tool measures blogs and shops. A protocol lives on-chain: contracts, holders, liquidity, explorers. That data is invisible to a classic SEO suite, so the number it gives you is only half the picture.
- An audit is a claim, not a proof. Whoever reads a PDF in six months has to trust the document. A hash registered on-chain can be re-checked by anybody, forever, without trusting the author.
- A proof signed today has to survive tomorrow. Everything signed with an elliptic-curve key is collectible now and forgeable later. That is why the signatures here are post-quantum.
What runs automatically
Five steps. The first two are free and need nothing; the last three are optional and you sign them yourself.
- 01
Analyze
Paste an EVM address (wallet, token, NFT collection, DEX or bridge) or a plain URL. No account, no login, no wallet needed. The network is detected from the address itself.
- 02
Score
The engine reads public data — on-chain signals plus the on-page signals the target publishes — and returns one deterministic score with its breakdown. Same input, same number: it can be re-run and checked by anyone.
- 03
Register on-chain
Optionally sign a transaction to register the certificate hash. From that moment the record is immutable: it cannot be edited later or quietly replaced.
- 04
Mint the badge
If the score is 70 or above, you can mint a soulbound (SBT) badge on your own wallet. It is not transferable, so it cannot be bought or moved to another project.
- 05
Verify
Anybody can check a certificate: re-run the same target (the score is deterministic), read the on-chain registration in the explorer, or open the IPFS copy of the JSON and PDF.
Quantum-safe by design, not as a badge
The protocol signs with ML-DSA-65 (FIPS 204), the post-quantum signature standard, in production. The practical reason is what the industry calls harvest now, decrypt later: an adversary can copy encrypted or signed data today and break the weak signatures years later, when quantum machines are good enough.
The second half of the problem is crypto agility: being able to swap the cryptography without rebuilding the whole system — and, above all, without invalidating the proofs already issued. A visibility score is only useful if its proof still holds in ten years.
None of this makes a project itself safe. It is about the integrity of the record: the technical documentation has the details, and the Web3 SEO guide explains how the visibility side works.
Deterministic
Same target, same score. That is what allows a third party to reproduce it instead of trusting you.
Immutable
Once registered on-chain, the certificate cannot be edited or quietly replaced.
Publicly verifiable
Anyone can check it: re-run the target, read the explorer, or open the pinned copy.
No manual work
No report to wait for, no consultant in the loop, nothing to chase by email.
Who it is for
Protocol and dApp teams that want a number they can show instead of describe. NFT collections that need to be found. DAOs that have to earn attention for their governance. And agencies that prefer to hand over an on-chain proof rather than a PDF nobody can check later. If you already have a website and a contract, you already have everything needed to start.
Frequently asked
Is this automated, or is a person writing an audit?
How is this different from a normal SEO tool?
Do I need a wallet? Is it free?
What does "quantum-safe" mean here exactly?
Is the score a security audit or financial advice?
Which networks are supported?
Start with the free score. It takes one address or one URL.