CryptoMeter docs
v1.0.0
Get help
● Set up · Make it yours

Customization
texts, signals, language.

What you can change without code and 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. Everything in the first column is changed in the CryptoMeter admin, without code; the filters named in the second column are optional, for developers who want to go further:

WhatHow
Which bots are allowed or blockedBots & rules (presets, intents, per-bot exceptions, custom user agents), cryptometer_bots
Text blocked bots seeSettings → Access rules → Blocked bots (HTTP 403)
Licensing signalsSignals; cryptometer_content_usage, cryptometer_license_xml
/llms.txtSettings → Content & discovery; cryptometer_llms_txt
Monetize texts402 message, service name, badge (style .cryptometer-badge in your theme), cryptometer_license
Admin languageTranslation

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 readable, unminified bundle in assets/app/ with npm install and then npm run build inside admin-app (@wordpress/scripts, Node.js 20 or newer; on Windows use WSL or Git Bash). You only need this if you change the source. The build was run for this release on 2026-10-20.

Settings, General tab: protection switch, referral counting and the log retention field
Settings → General. Protection off means the plugin only logs and never blocks.

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.

  1. Open the .pot file in Poedit or a plugin such as Loco Translate and create a translation for your language.
  2. Save it as cryptometer-<locale>.po / .mo (for example cryptometer-de_DE.mo). The admin app additionally needs WordPress's JSON translation file for its script, which Loco Translate or wp i18n make-json creates from the .po file.
  3. 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.