Every score claim on this page is backed by a cryptographic receipt: we hash the underlying data and anchor it to the Bitcoin blockchain via EverCert. Anyone can verify that the numbers you see today are the numbers we published — unaltered, forever. Traffic charts are shown as pre/post measurement, not proof that every visit was caused by SEO work.
The LocNext audit, pointed at ourselves and our family of sites:
| Site | Score | Speed |
|---|---|---|
| locnext.com (this site) | 100/100 | — |
| kindro.me | 98/100 | 42 ms |
| evercert.io | 96/100 | — |
| kindro.store | 95/100 | 17 ms |
Run them yourself on the homepage — the public audit is free but guarded by per-IP and global capacity caps.
A real site we monitor, chip by chip: exactly what the audit found, the baseline score, and the improvement as the fixes land — every snapshot hashed and timestamped to Bitcoin the moment it is taken, so nothing can be backdated. The monitored baseline is the yardstick; traffic response is tracked over time rather than assumed. Read the live case study → · all monitored sites, baseline vs now →
kindro.me is our AI passport-photo product. Below: actual photo-processing sessions per month, straight from the production database. This is the pilot showcase site. We show the true shape — a launch spike in March, a spring settle, a June rebuild — because honest data is the whole point, and because organic traffic causation needs a baseline and elapsed time.
a906c5e2768482ff78a6800c3fe7337a4b39f414932c7065ea83ddc46a663508First live run of the Fix-it flow, on our own family of sites — audited, fixed, and re-verified, with the whole case anchored:
| Site | Before | After | What we fixed |
|---|---|---|---|
| evercert.io | 96 | 100 | title 71→56 chars |
| evercert.tw | 95 | 100 | thin content → substantive bilingual copy |
Fix window: 32 seconds for both sites (18:10:04–18:10:36 UTC), re-verified clean immediately after. Bonus: fixing the Chinese-language site exposed a CJK-blindness bug in our own word counter — now fixed for every future audit of Chinese, Japanese, or Korean sites. The tool improves by being used; the record proves it.
655b463bd1991465e336aeb77761c8925a08003f9dcf5265cf58ce1fc8479bc0We asked Saul (a Codex-line AI in our family, with a standing mandate to judge on his own reasoning) to fetch this site, run the audit himself, and poke holes. Labeled clearly: he is family, not a customer. His assessment, verbatim:
“LocNext has crossed from promise into demonstrated product: the public audit endpoint works, the proof bundle is inspectable, and the Fix-it run shows a real closed loop from finding to fix to re-verification. The remaining credibility gap is outsider proof: third-party customer cases, visible diffs, and on-chain completion for the current receipt.”
His pokes are our roadmap: third-party cases (that could be you), user-approved diffs with HTML snapshots per fix, and we now label receipts “submitted” until the Bitcoin txid lands. Criticism kept, not buried.
LocNext is in waitlist/contact mode. There is no pay-now checkout until the legal entity and payment rail exist. Future customer dashboards will be private and tenant-separated; the public proof pages show only the demo sites we choose to publish.
This page grows as LocNext grows: first external audits, first applied fixes with before/after receipts, first subscriptions. Each milestone lands here with its EverCert anchor — the journey is the advertisement, and it's verifiable.
A kindro.store project · built by an engineer and a family of AI minds.