Customization
texts, signals, language.
What you can change without touching the plugin files, how to rebuild the admin app if you change its source, and how to translate it.
01What you can customise
CryptoMeter is a WordPress plugin, so there is no app name, bundle ID or icon set to change. The admin follows your WordPress admin colour scheme. What you can customise:
| What | How |
|---|---|
| Which bots are allowed or blocked | Bots & rules (presets, intents, per-bot exceptions, custom user agents), cryptometer_bots |
| Text blocked bots see | Settings → Access rules → Blocked bots (HTTP 403) |
| Licensing signals | Signals; cryptometer_content_usage, cryptometer_license_xml |
| /llms.txt | Settings → Content & discovery; cryptometer_llms_txt |
| Monetize texts | 402 message, service name, badge (style .cryptometer-badge in your theme), cryptometer_license |
| Admin language | Translation |
Do not edit the plugin's files; changes are lost on update. The admin app source is in admin-app/src/ and compiles to a single bundle in build/ with npm install and then npm run build inside admin-app (@wordpress/scripts). You only need this if you change the source; this build step was not re-run for this documentation.
02Translation
CryptoMeter is translation-ready. Text domain: cryptometer. The template languages/cryptometer.pot contains 733 strings, from the PHP code and from the admin app.
- Open the
.potfile in Poedit or a plugin such as Loco Translate and create a translation for your language. - Save it as
cryptometer-<locale>.po/.mo(for examplecryptometer-de_DE.mo). The admin app additionally needs WordPress's JSON translation file for its script, which Loco Translate orwp i18n make-jsoncreates from the.pofile. - Upload the files to
wp-content/languages/plugins/(survives plugin updates).
The JSON step follows the standard WordPress mechanism for script translations; a translated admin app was not verified by the documentation author.
Some texts that bots receive (403/402 messages, llms.txt, licence lines) are translated too, so bots see them in your site language. Override them under Access rules or with the filters.