Do not add an undocumented provider-key constant

POM Translate defines no public wp-config.php constant for an arbitrary machine-translation provider key. Adding a guessed constant does not connect another service and creates an unsupported secret-management path.

Use the POM AI license controls supplied by the product for built-in machine translation. Keep any credentials for an external editorial system in that system, outside POM Translate and outside visitor-facing WordPress output.

Never put a provider credential in:

  • a URL or query string;
  • browser JavaScript;
  • a registered translation string;
  • post metadata intended for translation;
  • plugin source or a public documentation file;
  • an import or export payload.

If custom code needs to detect whether the built-in workflow is available, design it to fail safely and leave the original content unchanged. Do not read private license storage or depend on internal client classes.

See Let POM AI manage service authorization for the supported setup.

Understand the machine-translation integration boundary
Previous
Write crawler rules
Next