by aipogeo 1 (0 reviews)

Aipogeo Context Translate

Name: Aipogeo Context Translate
Author: aipogeo

Translate your site with an AI that reads the whole page first, then fix whatever it got wrong before your visitors see it.

Aipogeo Context Translate ranks #59,820 among WordPress.org plugins with 1+ active installations, is #483 of 776 in the Language Tools category, a 1/5 rating from 0 reviews, and was last updated Sep 24, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v2.3.3 Current Version v2.3.3

Updated 2 days ago Last Update on 24 Sep, 2026

Refreshed 14 hours ago Last Refreshed on

#483 of 776 in Language Tools Actively maintained

View on WordPress.org

Rank

#59,820

— No change

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

282

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

46,883

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #59,820

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.3.3
Last Updated: Sep 24, 2026
Requires WP: 6.7+
Tested Up To: 7.1
PHP Version: 8.0 or higher
Author: aipogeo

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

AI localization multilingual translation

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Translate Wordpress with GTranslate

TranslatePress - Translate Multilingual sites with AI Translation

Connect Polylang for Elementor

100K+ installs

#293

WPML Multilingual & Multicurrency for WooCommerce

100K+ installs

#324

View all Language-tools plugins

Frequently Asked Questions

Common questions about Aipogeo Context Translate

The bundled php-ai library supports OpenAI, Claude, Gemini, DeepSeek and OpenRouter. Pick a model and the plugin works out which one you mean; if you

yourself. If your server cannot reach the provider directly, there is a proxy setting.

In their own table, keyed by the source text and the language pair. A string that shows up in your header on every page is stored once, not once per page. Deactivating the plugin leaves your content exactly as it was.

script and style are skipped, along with WordPress core endpoints and static assets. Add the not-translate class to anything else you want left alone, or not-translate-url on a link to keep that address as it is.

The AI knows nothing about your business unless you tell it. Under Translation Settings > Translation prompt, add the names that must stay as they are, for example under "Notes": Never translate or transliterate these names; copy them exactly as written: Acme Cloud, AC-200. Two other tools help when a name still slips through: the not-translate class keeps a whole element away from the AI, and per-language replacement rules (Languages screen) can fix the result. A rule has no idea of context and is applied to every translated text of that language, so use it sparingly and only for distinctive names. The Help screen has examples and the risks. Translations that are already stored are not redone; edit or delete them under Translation Data and translate the page again.

Under Settings > Front end > Switcher styles, pick one of: Plugin default – the bundled stylesheet. My own CSS – an editor opens with the default styles filled in; change

database and printed inline, so plugin updates never overwrite it. No styles – nothing is loaded and your theme styles the switcher from scratch. Your theme then also handles floating the switcher and showing the menu only while .is-open is set; docking the switcher into a theme element with Container ID is usually the simplest way to go. Developers can do the same in code: add_filter( 'apgt_enqueue_switcher_styles', '__return_false' ); apgt_switcher_css filters the custom CSS, and `apgt_switcher_languages` filters the list of languages the switcher shows. These class names are stable and will not be renamed: Root: #apgt-language-switch, .apgt-switcher Elements: .apgt-switcher-btn, .apgt-switcher-current, .apgt-switcher-caret, .apgt-switcher-menu, .apgt-switcher-item, .apgt-switcher-flag States: .is-active on the current language, and .is-docked, .is-open and .is-flipped (menu opens towards the left) added by the script The switcher also fires bubbling DOM events on #apgt-language-switch: apgt:ready, apgt:docked, apgt:open and apgt:close.

Yes. Turn off "Show the language switcher" in the settings and call apgt_get_switcher_languages() in your template. It returns the same data the built-in switcher uses: the source language first, then every target language the current visitor can see. Each item has iso, label (the language's own name), url (this page in that language), hreflang, flag (a data URI) and active. Call it while the page is being rendered, not earlier than template_redirect.

A translated page is only served once enough of it has stored translations (Settings > Front end, "Serve the translated page once coverage reaches", 100% by default). Below that the source page is shown, so half-translated pages stay out of search indexes. Only what visitors can see counts; text that appears only in JSON-LD structured data does not hold a page back. Every response on a language URL carries an X-APGT-Status header that says

X-APGT-Status: source; coverage=97%; required=100%. Check it with curl -sI https://example.com/es/ | grep -i x-apgt. If it says source, run "Translate all" for that language to fill the gaps.