Digital Karma Score
A single 0 to 100 reading of AI readiness and completeness, currently version 8.2. It follows the Digital Karma Federation scoring rules published by digitalkarmaweb.com, the protocol's specification authority. It is an evolving implementation score, not a predictor of rankings or AI citations. See the Experiment Log for what is being observed.
Score components (v8.2)
| Signal | Weight |
|---|---|
| Schema Coverage | 20 |
| Content Freshness | 15 |
| AI Endpoints | 25 |
| Federation Presence | 15 |
| External Links | 10 |
| Technical Quality | 10 |
| Dataset Quality | 5 |
External Links & Authority is defined by the protocol as backlink or domain-authority data from a paid checker API such as Moz or Ahrefs. Krisada chose not to add a paid API for this. The signal is approximated from Google Search Console signals already in the DK Warehouse for domains inside the tracked portfolio, and is unmeasured rather than faked for any domain outside it.
Badges
- Karma Elite 95-100 ... Exceptional, best-in-class implementation
- Karma Pro 85-94 ... High-quality site, strong AI readiness
- Karma Certified 70-84 ... Meets baseline federation quality standards
- Not Yet Certified 0-69 ... Below baseline, missing required signals
Changelog
- v6.1 2026-03-30 ... Protocol history from digitalkarmaweb.com: the original four-file structured AI endpoint baseline, before the federation and constellation layer existed. This site's own dk-rules.json first existed at this version number but implemented a separate rubric rather than this protocol baseline. See the 8.0 entry for why that was corrected.
- v7.0 2026-04-13 ... Protocol history (digitalkarmaweb.com), not a change made on this site: expanded required artifacts from 4 to 6 (added federation.json and llm.txt), renamed the entry badge from Karma Bronze to Karma Certified, and introduced the formal Starter/Certified/Pro/Elite compliance tiers this site now also uses.
- v7.1 2026-04-21 ... Protocol history (digitalkarmaweb.com), not a change made on this site: tightened root discovery file placement rules (robots.txt and sitemap.xml must live at the site root, not under /ai/).
- v8.0 2026-07-30 ... Realigned to the Digital Karma Federation's actual v8.0 protocol (digitalkarmaweb.com is the protocol authority, not this site). Previous v6.1 rules used a different, independently-invented rubric (installation/structure/integrity/connectivity/freshness/discoverability/monetizationReadiness weights, A/B/C/F letter grades, a 3-file required list) that had drifted from what the protocol itself defines. Replaced with the protocol's real 7 signals and weights (Schema Coverage 20, Content Freshness 15, AI Endpoints 25, Federation Presence 15, External Links 10, Technical Quality 10, Dataset Quality 5), all 6 required artifacts, and the protocol's own badge tiers (Karma Certified/Pro/Elite at 70/85/95) in place of custom letter grades.
- v8.1 2026-09-21 ... Protocol history from digitalkarmaweb.com: restored llm.json and ai/llm.json after live crawler demand showed that the retired files were still being requested, then added llms.txt as a standard discovery output.
- v8.2 2026-09-23 ... Added the required rendered-schema.json receipt and now requires a clean, complete rendered Dataset audit before a site can pass the current seven-artifact federation baseline. Restored llm.json, ai/llm.json, and llms.txt outputs are checked as recommended discovery files.
Example scorecards
| Domain | DK Score | Badge |
|---|---|---|
| realseolife.com | 95 | Karma Elite |
| as400software.com | 93 | Karma Pro |
| aihealthcarenow.com | 92 | Karma Pro |
| aimedicinetoday.com | 92 | Karma Pro |
| aisymantix.com | 92 | Karma Pro |