About this plugin
HTBD translates supported WordPress content with the Baidu Translate API and persists each translation for reuse. It supports language-specific subdirectory URLs and domain bindings.
The WordPress admin interface follows the current WordPress locale. English is the default. org language packs take priority, with the bundled Simplified Chinese translation used as a fallback when WordPress is set to zh_CN.
Supported values include published titles, content, excerpts, image alternative text, term names and descriptions, and selected SEO fields, for any public post type and public taxonomy selected in the settings. Automatic translation is only scheduled for posts and pages with the publish status. Completed translations are stored in the {$wpdb->prefix}hyx_bd_translations custom database table.
Existing {$wpdb->prefix}btranslate_translations data is migrated when the renamed plugin is activated. Front-end rendering reuses stored values and never calls the translation provider dynamically.
Subdirectory routing supports paths such as /en/example-post/. Domain routing maps configured hostnames to target languages. php or wp-admin through a target-language route are redirected to the corresponding source-site URL while preserving query parameters.
Translation failures are non-fatal and fall back to source-language content.
Singular views print hreflang alternate links for every configured language, and localized sitemaps declare the same alternates. A language switcher is available as the [htbd_language_switcher] shortcode, the HTBD language switcher block, and a classic widget.
Text segments of the same post are sent to Baidu as one multi line request where possible, requests are spaced by the configured interval, and transient provider errors are retried. wp htbd translate, wp htbd translate-terms, wp htbd status, wp htbd export, and wp htbd import are available when WP-CLI is installed.
External Services
HTBD connects to the Baidu Translate Open Platform API, a service provided by Baidu, to translate WordPress content. The plugin cannot generate new translations without this service. A Baidu Translate account, application ID, and secret key are required.
Baidu may apply request quotas or usage charges according to the service plan selected by the site administrator.
The API is contacted by scheduled tasks after a published post or page is saved, after a supported category or tag is created or edited, or after an administrator explicitly queues or refreshes translations. Front-end page views reuse stored translations and do not contact Baidu. The plugin also makes no Baidu request when valid persisted translations are already available, unless an administrator explicitly requests a refresh.
For each translation request, the plugin sends the text being translated, the configured source and target language codes, the Baidu application ID, a random salt, and a request signature. Depending on the content being translated, the text may contain published post or page titles, body text, excerpts, selected SEO title and description values, attached image alternative text, and category or tag names and descriptions.
Standard network information, including the originating server IP address, is also visible to Baidu as part of the HTTPS request. The secret key is used locally to create the signature and is not sent as a separate request field.
HTBD stores the returned translated text in the WordPress database but does not store complete Baidu response payloads. Data sent to Baidu is subject to Baidu’s own terms and privacy practices:
- Baidu Translate API documentation: https://fanyi-api.baidu.com/doc/23
- Baidu Translate Open Platform service agreement: https://fanyi-api.baidu.com/doc/6
- Baidu privacy policy: https://privacy.baidu.com/policy