Title: TradeGear – AI Translation & Multilingual Customer Assistant Author: vonblanc1 Published: ଅକ୍ଟୋବର 9, 2026 Last modified: ଅକ୍ଟୋବର 9, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/tradegear.svg) # TradeGear – AI Translation & Multilingual Customer Assistant By [vonblanc1](https://profiles.wordpress.org/vonblanc1/) [Download](https://downloads.wordpress.org/plugin/tradegear.0.13.4.zip) * [Details](https://ory.wordpress.org/plugins/tradegear/#description) * [Reviews](https://ory.wordpress.org/plugins/tradegear/#reviews) * [Installation](https://ory.wordpress.org/plugins/tradegear/#installation) * [Development](https://ory.wordpress.org/plugins/tradegear/#developers) [Support](https://wordpress.org/support/plugin/tradegear/) ## Description Bring your business to the world: your whole site in your customers’ languages, served from your own server, with an assistant that answers from what you already publish. TradeGear translates your WordPress and WooCommerce site with AI and answers your visitors’ questions in their own language, using an assistant grounded in the content you already publish. Your site stays where it is; translation and your assistant are managed from one dashboard. #### Your whole website, in a familiar language * Visitors choose their language from a switcher on your pages, and translated pages are served from a local translation store on your own server. * Language links and translated sitemaps — WordPress’s own, Yoast SEO’s or Rank Math’s — help each language get found. * Protect brand names and key terms, set preferred translations, and review and improve wording from your dashboard. * Test mode and search-engine indexability are controlled from WordPress, so you can preview a language before customers see it. * Turn languages off with a retention period, or clear a translation batch explicitly. #### Your knowledge, ready for their questions * An optional assistant answers from the public content you choose — pages, products and policies — in the visitor’s language. * It links back to the page an answer came from. * Public content only. Private pages, password-protected content, drafts, hidden products and customer accounts stay out of the knowledge base. * Works with or without WooCommerce; product details, prices and availability sync only when you enable it. #### How it works 1. Create a TradeGear account and add your website to your workspace. 2. Install this plugin and pair it with the code from your dashboard — there are no API keys to copy or paste. 3. Choose your languages in the dashboard, then optionally enable the assistant and knowledge synchronization. #### Plans The plugin is free software. A Free plan includes 3,000 translated words a month; translation and AI customer support together start at $19/month, billed monthly in US dollars. Current plans and allowances: https://app.tradegear.org/translations A TradeGear account is required for the hosted translation and assistant features. Activation alone does not enable translation, launch chat or send knowledge to TradeGear— those features start only when a site administrator configures and enables them. The optional “Powered by TradeGear” link is off by default and can be enabled or disabled in Settings > TradeGear, independently of the plan. See “External services and privacy” below for exactly what leaves your site and when, and the FAQ for what happens when you deactivate. #### External services and privacy This is a client for an external service, not a locally running AI model. Its hosted endpoints are https://app.tradegear.org (translation API, account dashboard and embedded chat page) and https://assistant.tradegear.org (connection, knowledge synchronization and assistant API). Advanced settings also support an administrator’s own deployment; its operator’s policies then apply. The plugin communicates with these services as follows: * Connecting: when an administrator submits a connection code, the plugin sends the code and site origin to the assistant service. The service verifies domain control using a temporary public challenge on your site, then returns site-scoped credentials. Those credentials remain on the WordPress server. * Account navigation: opening the dashboard or signup link sends your public website origin and WordPress setup URL to the TradeGear website so it can prefill the domain and offer a return link. No connection code or stored credential is included. This navigation hint is retained in the browser tab for up to 24 hours and can be dismissed with “Use a different website”. * Translation: when translation is enabled, the plugin sends extracted page text, selected attributes/metadata, page URLs, source/target languages and the site identifier to the translation API. It polls for translated text and account language settings using the site’s credential. Account-setting refreshes also communicate with that API once configured. Checkout and WordPress administration, login and REST API paths are excluded by default. Form labels, headings, button text and input placeholders are translated like any other page text; text typed into a field is not sent. Style, code, preformatted, textarea, noscript, SVG, iframe and template content is skipped, while string values inside page scripts can be collected. Account and order pages are not excluded automatically, so add a path exclusion for any page that shows a person their own information. When a language is added, cleared or restored, the plugin also asks for the text of the website’s public pages in the background — the home page, pages, product and post categories, products, posts and other public content, up to 1,000 pages, fetched from the site itself — so they are translated before a visitor opens them. TradeGear can also ask the website to do this again for a language; the plugin then reports to the translation API how it went: the language, the number of pages and whether it finished. This counts toward the word allowance. The sd_translate_warm_limit filter changes the number of pages; returning 0 turns it off, and pages are then translated when first visited. * Knowledge synchronization: only after enabling it, the plugin periodically sends public pages and/or published, catalogue-visible products to the assistant service. This includes titles, descriptions, URLs, prices and stock status. It excludes drafts, private/password-protected content, hidden products, configured page exclusions and WooCommerce cart, checkout and account pages. Updates and removals are synchronized. The regular check is weekly, with changes queued for earlier synchronization through WordPress cron. Switching knowledge synchronization off asks the assistant service to forget everything this website sent it. * Chat: opening the launcher loads the hosted TradeGear chat page in an iframe. Sending a message forwards the message, requested language, random visitor/session identifier and request identifier through WordPress to the assistant service. The iframe receives normal browser network information, including the visitor’s IP address. The plugin does not send the WordPress administrator key, orders or customer records to the chat page. * SEO verification: only when requested by an administrator, the plugin fetches the site’s own pages, robots.txt, feed and sitemaps to report translation/SEO problems. It follows redirects only when they stay on the site. * Deactivation: switching the plugin off sends the site identifier and a short reason (deactivated or uninstalled) to the translation API, and switching it back on sends the same two fields with reason activated. Nothing else is included— no page text, no visitor data and no credentials beyond the site’s own. The service uses it to pause or resume this website, including its billing. Local cookies: tradegear_lang remembers the selected language for 30 days; tradegear_test authorizes a test-link visitor; tradegear_assistant_visitor is a signed, random assistant session cookie lasting up to seven days. Local hashed rate-limit counters protect chat. Site owners should describe the enabled services and cookies in their site’s privacy notice. AI answers and translations can be inaccurate; review important business content. Service information and account signup: https://app.tradegear.org/translations Privacy policy: https://app.tradegear.org/translations/privacy Service terms: https:// app.tradegear.org/translations/terms Contact: info.tradegear@gmail.com ## Installation 1. Install TradeGear from your WordPress dashboard or upload tradegear.zip, then activate it. 2. Open Plugin setup on the Plugins screen (or Settings > TradeGear), then choose Create a TradeGear account. Already registered? The plugin’s Settings link opens your TradeGear dashboard, asking you to sign in if needed. 3. Register your publicly reachable HTTPS site in the dashboard. The plugin pre-fills the website address. On its website card, choose Connect this website and copy the code. 4. Choose Return to WordPress setup and submit the code under Connect to TradeGear. Your WordPress server must be reachable by the service to verify ownership. For WordPress installed in a subdirectory, start from Plugin setup so TradeGear remembers the correct admin address. 5. Choose your site languages in the account dashboard, start with local test mode, and enable live translation when ready. 6. Optionally enable the shop assistant and knowledge synchronization. Review the external-service disclosure before enabling them. ## FAQ ### Does this work without an account? The hosted features need a TradeGear account, site connection and applicable allowance. Installing the plugin does not create an account or start a subscription. ### Is there a free plan? Yes. The Free plan includes 3,000 translated words a month. Paid plans add more languages and allowance and include the AI customer assistant; translation and AI support together start at $19/month, billed monthly in US dollars. Current plans and allowances: https://app.tradegear.org/translations ### What does the assistant know about my business? Only the public content you enable. Knowledge synchronization sends published pages and catalogue-visible products — titles, descriptions, URLs, prices and stock status— and excludes drafts, password-protected content, hidden products, your configured page exclusions, and WooCommerce cart, checkout and account pages. You choose which pages are included and whether products sync, and removals are synchronized. The assistant answers from that content and links back to the page it used. Nothing is sent until an administrator enables knowledge synchronization, and switching it off asks the assistant to forget what it was given. ### Where are translated pages served from? From a local translation store on your own server, so serving a translated page does not wait on a live request to TradeGear. The dashboard is where translation is reviewed and managed. ### Do I need API keys or service URLs? No. A single connection code retrieves this website’s translation, chat and knowledge- sync credentials after domain verification. Languages and plan settings refresh automatically every five minutes when WordPress cron runs, even with translation serving off. The setup page shows the connection state, the features this website shares, and when knowledge was last synchronized; synchronization runs on its own schedule and cannot be started by hand. Reconnect with a fresh code to renew service addresses or keys; individual keys are never shown. Custom deployments can define TRADEGEAR_MANUAL_CONNECTION as true in wp-config.php to show manual connection fields, and may set TRADEGEAR_* constants (engine URL, token, mode, languages, assistant keys) in wp-config.php or a must-use plugin; the SD_TRANSLATE_* and SD_ASSISTANT_* names earlier releases documented still work. The plugin never loads a PHP file from the uploads directory. Leaving manual mode off preserves previously saved credentials. The full operator page a custom deployment shows also offers Refresh account settings. ### Does adding a language translate pages nobody has opened yet? Yes. The plugin asks for the whole website in the new language in the background, most important pages first (home, pages, categories, then products and posts), and collects the translations as they are finished. It runs from WordPress itself, in short steps, so it never slows a visitor’s page. On a Free plan the allowance can run out before every page is done; the rest are then translated as visitors open them once the allowance renews. See the sd_translate_warm_limit filter above. ### Does it work with page caching? Yes. A translated page that is still waiting for part of its text is sent with no- cache headers and marked DONOTCACHEPAGE (also honoured by batcache and LiteSpeed Cache), so a page cache stores it only once it is fully translated. ### Is WooCommerce required? No. Public-page translation and assistant knowledge work without WooCommerce. Catalogue synchronization requires WooCommerce. ### Can I upgrade from SD Translate? Yes. Internal option names, REST routes and hook names keep their sd_translate prefix to preserve connections and stored translations; 0.13.0 renames the translation tables in place and keeps every row. Deactivate SD Translate before activating the canonical TradeGear package. Deactivation preserves data. A compatibility upgrade ZIP with the old directory name is also available from the project build script. Keep only one copy active. ### What happens when I deactivate or delete the plugin? Deactivation removes scheduled jobs and stops the plugin’s local features, and it tells TradeGear that this website has left. The service then pauses the site: it stops serving translations and assistant answers for it and stops synchronizing its knowledge, and it pauses subscription billing, so an invoice raised while the site is paused is voided rather than charged. Nothing is erased and the subscription is not cancelled — settings, local translation tables, remote translations and remote business knowledge are all retained. Activating the plugin again reports the website as back and resumes both on the same credentials, so there is no re-pairing. Deleting the plugin reports the same thing once more and erases nothing either. Manage remote data and billing in your TradeGear dashboard. Back up your database before manually deleting retained sd_translate options or the tradegear_translations / tradegear_meta tables (named sd_translations / sd_meta before 0.13.0; an upgrade renames them and keeps every row). ### How do I get help? Email info.tradegear@gmail.com, or post in this plugin’s support forum on WordPress. org. The settings page has the same Contact link. ### Does it work with Yoast SEO or Rank Math? Yes. When one of them serves the sitemaps, each language’s sitemap at /es/sitemap_index. xml (for Spanish) lists that language’s pages, and the SEO verification checks those sitemaps. ### Are developer files or credentials included? No. The distribution includes the PHP source, readable JavaScript/CSS, this readme and the GPL licence. Tests, private configuration and credentials are excluded. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “TradeGear – AI Translation & Multilingual Customer Assistant” is open source software. The following people have contributed to this plugin. Contributors * [ vonblanc1 ](https://profiles.wordpress.org/vonblanc1/) [Translate “TradeGear – AI Translation & Multilingual Customer Assistant” into your language.](https://translate.wordpress.org/projects/wp-plugins/tradegear) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/tradegear/), check out the [SVN repository](https://plugins.svn.wordpress.org/tradegear/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/tradegear/) by [RSS](https://plugins.trac.wordpress.org/log/tradegear/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.13.4 * Installing or activating the plugin no longer changes any address on your site. Language addresses such as /es/ are handled only while translation is live, or in test mode for you and test-link visitors. Before, a fresh install answered every /es/ address with the untranslated page, which could take those addresses over from another translation plugin. * Yoast SEO and Rank Math sitemaps list translated pages under their language again; 0.13.3 served them unchanged. * SEO verification follows the redirect Yoast SEO and Rank Math put on WordPress’s sitemap, reads each language’s first sitemap of pages, and reports every address the site does not serve instead of leaving it out of the report. Each line is named after what it checks. * TradeGear can ask the website to warm a language again: the plugin runs its usual warm-up and reports back when it is done. * A Contact link on the settings page: info.tradegear@gmail.com. #### 0.13.3 * Requires WordPress 6.9 or later. Translated pages and the language switcher now go through WordPress’s own template output buffer instead of a buffer the plugin opened itself. * WooCommerce cart fragments and notices are translated through WooCommerce’s own filters, and translated sitemaps through WordPress’s sitemap entry filters, instead of rewriting the finished response. A sitemap made by another plugin is served as it is under a language prefix. * The debug overlay’s styles are an enqueued stylesheet instead of a style element written into the page. #### 0.13.2 * Switching Business knowledge off now withdraws what the assistant was given, as the privacy policy says, instead of only stopping updates: the assistant is asked to forget this website’s content once, and asked again until it confirms. A website that never shared anything sends nothing, and one that switched it off before this release has its content withdrawn after updating. The settings page says whether the content has been forgotten yet. #### 0.13.1 * A translation written back into structured data (JSON-LD) or another inline script now has its angle brackets escaped, so text containing “” can never close the script element early, whatever slash style the page’s own block uses. #### 0.13.0 * Every class, function, cookie, query parameter, cron interval and database table now carries the tradegear prefix (the WordPress.org directory requires a unique prefix). The translation tables are renamed in place on upgrade with every row kept; the sd_translate option and hook names are unchanged, so nothing needs re-pairing. * Configuration constants are read by their TRADEGEAR_* names; the SD_TRANSLATE_* and SD_ASSISTANT_* names still work. The optional PHP overrides file in the uploads directory is no longer loaded — define the constants in wp-config.php or a must- use plugin instead. * Deleting the plugin from the WordPress.org package no longer fails on a missing file. * The language switcher’s style and script are enqueued as files instead of written into every page; every attribute the plugin writes into a page (language codes, canonical, hreflang and Open Graph URLs) is escaped at output; the language and test cookies are marked Secure on HTTPS sites. * Table creation no longer runs on every admin request, only until the schema version is recorded. #### 0.12.1 * The whole-website translation keeps collecting while the translation service is still working through the pages, instead of stopping after 40 minutes. It gives up only when nothing has moved for 15 minutes; anything left then arrives with the regular five-minute check. #### 0.12.0 * Adding, clearing or restoring a language now translates the whole website in the background instead of waiting for each page’s first visitor, who used to read it in English. Each page is rendered once for every new language, and the plugin collects the translations as they are finished rather than waiting for its five-minute check. * A translated page still waiting for part of its text is no longer stored by page caches (no-cache headers, DONOTCACHEPAGE, batcache and LiteSpeed Cache), so a cache cannot keep serving it half in English. #### 0.11.4 * Switching off both the catalogue and pages under Assistant knowledge now clears what the assistant knows about the website, instead of leaving it answering from content the shop has withdrawn. Content that disappears while a source is still switched on is still never pushed as an empty snapshot. * A visitor asking in a language the assistant no longer answers in (one just removed in the TradeGear dashboard) is told so and pointed to the shop, instead of being told the assistant is temporarily unavailable and asked to try again. #### 0.11.3 * A product review, or any form, sent from a translated page now reaches WordPress: links and redirects to WordPress’s own scripts (wp-comments-post.php and the like) and folders never carry the language, whatever the saved link exclusions say. #### 0.11.2 * Translated pages no longer add the language to links into wp-content, such as a product image’s full-size view, which then failed to load. * The mini-cart and other WooCommerce cart updates on a translated page now arrive in that page’s language instead of the website’s own, and a cart shown on one language’s pages is no longer replayed on another’s. * The language menu and the test link keep a website’s port, so a shop served on a non-standard port stays on itself. * When the shop’s plan no longer covers the assistant, visitors are told to contact the shop instead of being asked to try again. #### 0.11.1 * The settings page now says when TradeGear no longer accepts this website’s connection because it was disconnected or replaced in the dashboard, and tells you to connect again with a new code. A service outage is no longer reported the same way. * If TradeGear still has the website paused after the plugin was switched back on, the next automatic refresh asks it to resume, instead of leaving the site paused until the plugin is switched off and on again. #### 0.11.0 * Switching the plugin off now tells TradeGear that this website has left: the service pauses the site and pauses subscription billing, so an invoice raised while it is paused is voided rather than charged. Activating the plugin again reports the website as back and resumes both on the same credentials, with no re-pairing. * Deleting the plugin reports the same departure once more. Nothing is erased either way — settings, translation tables and remote knowledge are all retained. * Correct this readme and the WordPress privacy-policy text, which both previously said deactivation did not affect a subscription. * Rewrite the description and FAQ to explain what the plugin does, what the assistant uses, and the Free allowance and paid plans, and add a Screenshots section. #### 0.10.0 * Rename the plugin and canonical distribution to TradeGear while preserving existing settings and data. * Add service disclosures, licence metadata, safer input handling and prepared database identifiers. * Make the public credit link a local opt-in, off by default. * Link Settings to the hosted dashboard and guide signup back to the WordPress connection form. * Simplify setup around one connection code, hide manual credentials by default and report authenticated account-setting refreshes. * Replace the settings page with one connection panel, three feature controls and collapsed advanced options; a page save can no longer set a credential. * Check knowledge synchronization weekly instead of twice daily, and remove the manual synchronization control and its endpoint. Content changes still queue an earlier automatic update. * Report the last synchronization, its document count and the next scheduled check on the settings page. * Link the account page, privacy policy and service terms from the settings page, and correct the translation disclosure in this readme. ## Meta * Version **0.13.4** * Last updated **23 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.9 or higher ** * Tested up to **7.1.3** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/tradegear/) * Tags * [chatbot](https://ory.wordpress.org/plugins/tags/chatbot/)[customer support](https://ory.wordpress.org/plugins/tags/customer-support/) [multilingual](https://ory.wordpress.org/plugins/tags/multilingual/)[translation](https://ory.wordpress.org/plugins/tags/translation/) [woocommerce](https://ory.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://ory.wordpress.org/plugins/tradegear/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/tradegear/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/tradegear/reviews/) ## Contributors * [ vonblanc1 ](https://profiles.wordpress.org/vonblanc1/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/tradegear/)