2fox4oliver

Von Oliver Deppe von <a href="https://www.2fox4.de/" rel="nofollow ugc">2FOX4</a>.
2FOX4 Translate to English translates your German WordPress website into English using professional translation APIs. It automatically detects the visitor’s browser language and serves translated content under SEO-friendly <code>/en/</code> URLs.
Translations are stored as native WordPress posts and pages, ensuring full compatibility with SEO plugins like Yoast SEO and RankMath, XML sitemaps, Open Graph tags, and social sharing.
Key Features:
<ul>
<li>Native WordPress Storage — Translations are real WordPress posts/pages, fully compatible with SEO plugins, sitemaps, and the WordPress ecosystem.</li>
<li>Automatic Language Detection — Detects the browser language via the <code>Accept-Language</code> header and redirects non-German visitors to the English version.</li>
<li>Three Translation Providers — Choose between DeepL, OpenAI (GPT-4o), or Google Cloud Translation. Switch providers at any time.</li>
<li>SEO-Friendly URLs — Translated pages live under <code>/en/</code> (e.g., <code>/en/about-us/</code>) with proper <code>hreflang</code> tags and canonical URLs.</li>
<li>Admin Translation Editor — Side-by-side view with the German original (read-only) and the English translation (editable). Review and refine machine translations before publishing.</li>
<li>Translation Workflow — Four-step status system: Draft, Machine Translated, Reviewed, Published.</li>
<li>Language Switcher — Use the <code>[translatetoenglish_switcher]</code> shortcode to display a DE/EN toggle with flag icons anywhere on your site.</li>
<li>Staleness Detection — Automatically detects when the German source content has changed and marks the translation as outdated.</li>
<li>Hidden in Admin — English translations are hidden from the normal Posts/Pages lists to keep your admin clean. Manage all translations via the dedicated 2FOX4 Translate to English menu.</li>
<li>Extensible Architecture — Hooks and filters allow developers to add custom providers, modify translations, and control behavior.</li>
</ul>
Supported Content:
<ul>
<li>Posts</li>
<li>Pages</li>
</ul>
How It Works:
<ol>
<li>Install and activate the plugin.</li>
<li>Go to 2FOX4 Translate to English > Settings and enter your API key for your preferred provider.</li>
<li>Open any post or page and click “Translate Now” in the TranslateToEnglish metabox.</li>
<li>Review the translation in the side-by-side editor and publish it.</li>
<li>Visitors with a non-German browser language are automatically redirected to the <code>/en/</code> version.</li>
</ol>
<h3>External Services</h3>
This plugin connects to third-party translation services to provide its core functionality. No data is sent to any service until you configure an API key and actively trigger a translation. The plugin sends your page titles, content, and excerpts to the selected provider for translation.
DeepL API
When DeepL is selected as the translation provider, your page content is sent to DeepL’s translation servers for processing.
<ul>
<li>Service: <a href="https://www.deepl.com" rel="nofollow ugc">https://www.deepl.com</a></li>
<li>Terms of Use: <a href="https://www.deepl.com/en/pro-license" rel="nofollow ugc">https://www.deepl.com/en/pro-license</a></li>
<li>Privacy Policy: <a href="https://www.deepl.com/en/privacy" rel="nofollow ugc">https://www.deepl.com/en/privacy</a></li>
</ul>
OpenAI API
When OpenAI is selected as the translation provider, your page content is sent to OpenAI’s Chat Completions API.
<ul>
<li>Service: <a href="https://openai.com" rel="nofollow ugc">https://openai.com</a></li>
<li>Terms of Use: <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">https://openai.com/policies/terms-of-use</a></li>
<li>Privacy Policy: <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">https://openai.com/policies/privacy-policy</a></li>
</ul>
Google Cloud Translation API
When Google Translate is selected as the translation provider, your page content is sent to Google’s Cloud Translation servers.
<ul>
<li>Service: <a href="https://cloud.google.com/translate" rel="nofollow ugc">https://cloud.google.com/translate</a></li>
<li>Terms of Service: <a href="https://cloud.google.com/terms" rel="nofollow ugc">https://cloud.google.com/terms</a></li>
<li>Privacy Policy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
</ul>
PayPal (Donate Link)
The plugin readme contains a donate link to PayPal (paypal.com/paypalme). Clicking this link opens the PayPal website in the user’s browser. No data is sent to PayPal by the plugin itself.
<ul>
<li>Service: <a href="https://www.paypal.com" rel="nofollow ugc">https://www.paypal.com</a></li>
<li>Terms of Service: <a href="https://www.paypal.com/de/webapps/mpp/ua/useragreement-full" rel="nofollow ugc">https://www.paypal.com/de/webapps/mpp/ua/useragreement-full</a></li>
<li>Privacy Policy: <a href="https://www.paypal.com/de/webapps/mpp/ua/privacy-full" rel="nofollow ugc">https://www.paypal.com/de/webapps/mpp/ua/privacy-full</a></li>
</ul>

2FOX4 Translate to English

Automatically translates your German WordPress website into English using DeepL, OpenAI, or Google Translate APIs with full SEO support.

Yard | Digital Agency

Mike van den Hoek

This plugin registers secure API endpoints that allow you to request translations directly from DeepL without exposing your Deepl API-key. These endpoints are only accessible when a valid nonce is provided. When providing translations to website visitors, you can configure which languages are supported for translation.
<h3>Caching Mechanism</h3>
Each object that is translated will store its cached translation in the <code>wp_postmeta</code> table within the database. This caching mechanism ensures that translations are efficiently reused, reducing unnecessary API requests to DeepL and saving costs.
<ul>
<li>Serving Cached Translations: If a cached translation is newer than the <code>post_modified</code> date of the object, the cached version is served.</li>
<li>Fetching New Translations: When the <code>post_modified</code> date of the object is more recent than the cached translation, a new translation is fetched from DeepL. Once retrieved, this translation is immediately cached for future use.</li>
<li>Cache Authorization: Only logged-in users with the <code>edit_posts</code> capability (or a custom capability configured via the <code>yard::deepl/cache_capability</code> filter) are permitted to create new cache entries. Requests from users without this capability will still return a translation from DeepL, but the result will not be stored in the cache.</li>
</ul>
This approach minimizes the number of API calls to DeepL, ensuring translations are kept up to date only when necessary.
<h4>Admin: Cache Metabox</h4>
A metabox labeled Yard DeepL is displayed on the edit screen of supported post types (default: page). It provides two options:
<ul>
<li>Disable translation cache: When checked, the cache is bypassed for this object. Useful for posts with dynamic content that should always be translated fresh.</li>
<li>Clear translation cache: When checked and the post is saved, all cached translations for this object are deleted.</li>
</ul>
<h4>Admin: Translation Cache Column</h4>
A Translation cache column is added to the post list screen of all supported post types. Its purpose is to notify editors which posts should be cached as soon as possible to avoid unnecessary DeepL API costs.
<ul>
<li>Green badge per language (e.g. NL, EN-US): a valid, up-to-date cached translation exists for that language. Visitor requests are served from cache at no cost.</li>
<li>Grey badge with a count per language (e.g. EN-US 42): no cache exists for that language and visitors have triggered that many live DeepL API calls. Hovering the badge shows the full count as a tooltip. These posts are the most urgent to cache.</li>
<li>—: the post has never been requested for translation, or caching is disabled for this post.</li>
</ul>
The uncached call count is only incremented for visitor requests (users without cache-write capability) and is automatically reset per language once a cache entry is stored. Posts with the Disable translation cache option enabled are excluded from the column entirely.
<h3>External Services</h3>
This plugin connects to the DeepL API to provide translations for content.
<ul>
<li>Service: DeepL API (https://www.deepl.com)</li>
<li>Purpose: To translate text from one language to another based on the provided target language.</li>
<li>Data Sent: Text content for translation, the target language code, and the DeepL API key (handled securely and never exposed to users).</li>
<li>Conditions: Data is sent when a request for translation is initiated.</li>
<li>Privacy Policy: <a href="https://www.deepl.com/privacy" rel="nofollow ugc">DeepL Privacy Policy</a></li>
<li>Terms of Service: <a href="https://www.deepl.com/pro-license" rel="nofollow ugc">DeepL Terms of Service</a></li>
</ul>
<h3>Usage</h3>
<h4>Security</h4>
The API endpoints registered by this plugin are secured using a WordPress nonce. The nonce is passed to the front-end using the <code>wp_localize_script</code> function and is stored in a global JavaScript object <code>ydpl</code> which contains the following properties:
<ul>
<li><code>ydpl_translate_post_id</code>: The ID of the post to be translated.</li>
<li><code>ydpl_rest_translate_url</code>: The URL of the API endpoint for translation requests.</li>
<li><code>ydpl_supported_languages</code>: The list of languages supported for translation.</li>
<li><code>ydpl_api_request_nonce</code>: The nonce used for API validation.</li>
</ul>
When making requests to the API, ensure that the nonce is included in the request headers. The header should be named <code>X-WP-Nonce</code>, and it should contain a nonce created with the <code>wp_rest</code> action (available via <code>ydpl.ydpl_api_request_nonce</code> on the front-end).
Rate limiting: Unauthenticated requests (or requests from users without the cache capability) are limited to 3 requests per 60 seconds per IP address. Authenticated users with the required cache capability (default: edit_posts) are exempt from this rate limit.
Cache capability: Only users with the <code>edit_posts</code> capability can trigger cache creation. This can be customized using the <code>yard::deepl/cache_capability</code> filter.
<h4>Example</h4>
Request:
<pre><code>var xhr = new XMLHttpRequest();
xhr.open('POST', ydpl.ydpl_rest_translate_url, true);

// Set request headers
xhr.setRequestHeader('Content-Type', 'application/json');
xhr.setRequestHeader('X-WP-Nonce', ydpl.ydpl_api_request_nonce);

// Handle response
xhr.onreadystatechange = function () {
 if (xhr.readyState === 4 && xhr.status === 200) {
 console.log('Translation:', JSON.parse(xhr.responseText));
 } else if (xhr.readyState === 4) {
 console.error('Error:', xhr.statusText);
 }
};

// Prepare and send the request body
var data = JSON.stringify({
 text: ["Look another test"],
 target_lang: "DE"
});

xhr.send(data);
</code></pre>
Response:
<pre><code>[
 {
 "text": "Look another test!",
 "translation": "Sehen Sie sich einen weiteren Test an!"
 }
]<h3>Filters</h3>
</code></pre>
* <code>yard::deepl/cache_capability</code> (default: <code>edit_posts</code>) — The WordPress capability required to create cache entries. Users without this capability receive translations but results are not cached. 
* <code>yard::deepl/cache_metabox_post_types</code> (default: <code>['page']</code>) — Post types on which the Yard DeepL cache metabox is displayed. 
* <code>yard::deepl/disable_cache_metabox_post_types</code> — Deprecated. Use <code>yard::deepl/cache_metabox_post_types</code> instead.

Yard DeepL

This plugin registers secure API endpoints that allow you to request translations directly from DeepL without exposing your DeepL API-key.

2FOX4 Translate to English vs Yard DeepL