Frequently Asked Questions about Autoglot

• All translations performed by Autoglot are entirely machine-generated. The translation process is carried out automatically by software algorithms without any human intervention, editing, or post-processing.
• Autoglot does not review, monitor, approve, or modify the translated content in any language. The service functions purely as a technical tool that provides automated translation based on the input received.

The quality of NMT (neural machine translation) has increased significantly lately. According to some experts, the leading machine translation providers can show the quality comparable to medium-level professional translators. Moreover, many of these translators also use neural machine translation systems to generate the initial translation and then slightly proofread it. Sounds weird? Add the fact that you will have to pay them 100 times more.

Autoglot provides reasonable quality for the fraction of this cost. And it is fully automated!

• According to numerous tests provided by independent tools, Autoglot does not significantly influence the speed of your sites.
• Moreover, these minor changes may only be noticeable on translated pages. Your original, non-translated pages will not be affected at all.
• The process of automatic translation takes some time. That is why when you first open new pages that have not been translated yet, they might be slow – or even fail to load! Don’t worry, no translation will be lost. Once Autoglot completes the automatic translation process, all translated pages will be served from your local DB without delays.
• Finally, Autoglot supports most of the caching plugins like LiteSpeed Cache, SpeedyCache, W3 Total Cache, WP Fastest Cache, WP Super Cache, WP-Optimize, etc.
• Translated pages are cached by these plugins and delivered to site visitors with increased speed and performance.

When you first open an untranslated page, it might take a bit longer to load. This is normal – it just takes some time to extract the content, send it to our API for translation, and get it back. Once it’s translated, it’s stored in your local database and will load quickly for future visitors, just like any other WordPress page.

Yes, Autoglot supports translation of basic WooCommerce functionality. This includes WooCommerce products, cart and checkout process, including dynamic updates of shopping cart and checkout, and switching between different shipping addresses. In order to prevent excessive expenses, Autoglot will not translate all dynamic messages and emails.

However, please note the following:

• Please use classic cart and checkout pages. New block pages are JavaScript-based and therefore cannot be translated on the server.
• In addition to the words calculated in the Word Counter, please allocate up to 1,000 words per language for translation of cart and checkout pages.
• WooCommerce may show unique dynamic messages for different users. If they have not been shown before, Autoglot will translate them using the translation balance.
• Currently, Autoglot does not translate outgoing emails in order to prevent excess charges.

• We do not require any subscription and monthly fees; you don't need to pay for storage or bandwidth. But you will have to pay for translation – and this is where we cannot offer our service for free because we also have to pay fees to NMT services (neural machine translation providers).
• Moreover, when you register, you will have an initial translation balance that can be used to check the functionality of our plugin.

• Our pricing depends only on your words count.
• We can offer options where you can pay less than $0.0005 per word! This is 200 times cheaper than working with freelance translators.
• For more information, please check our pricing page.

• This is a number of words you can translate. You can check and replenish your translation balance via your control panel using a credit card. For pricing information, please check our pricing page.
• When your blog posts and pages are automatically translated to another language, we will subtract the number of words in your content from your translation balance. For example, if your blog post contains 100 words, we will subtract 100 from your translation balance. If you translate your blog post to 2 languages, we will subtract 200 from your translation balance, etc.
• If your translation balance reaches 0, we will not be able to provide new translation for you until you replenish your balance. However, unlike many other plugins, your previous translations will still be available on your website and will never be disabled until you decide to do so.

• Yes, Autoglot follows all the best search engine optimization practices and creates fully SEO compatible language versions.
• Autoglot will translate all HTML titles, META tags, schema.org markup, take care of all language settings, hreflang tags, etc.
• Autoglot will also update most SEO plugins' sitemap XML files and add new language URLs there. You will not have to modify them manually!

• Yes, Autoglot can translate URLs (inner links to posts and pages). When enabled in Advanced section, Autoglot will translate all WordPress permalinks, e.g. http://site.com/page/ to http://site.com/fr/página/.
• It can also transliterate URLs to URL-friendly format, e.g. https://site.com/page/ to https://site.com/ko/peiji/
• This also includes links in "alternate hreflang" and "canonical" tags, links in language switcher, forms, and sitemaps
• All translated URLs can be modified in Translation Editor
• This can be useful for better SEO, improved conversions, and overall user experience
• Please note, enabling or changing settings of Translation and Transliteration of URLs will affect only URLs that have not been translated yet. If you need to update already translated URLs, you need to modify or delete them in Translation Editor.

Yes, this can be done using our “Links Modifier” tool. This will replace links depending on current language, so you can have a link to site.de on your German pages, site.es on your Spanish pages and so on.

Yes, this can be done using our “Text Replacement” tool. This feature of Autoglot plugin lets you easily change pieces of content on your translated pages. For example, you can change video URLs depending on current language, so you will show different videos in different languages. Additionally, you can localize external links, images, and even your site appearance!

Currently, it is not possible to automatically translate text on images. Even with the latest advancements in AI technologies, the results of this “AI translation” can be unpredictable.

The only way to proceed is manual replacement, and this is what Autoglot can do using the “Text Replacement” module.

This can be done in 3 steps:

1. First, find the original image that needs translation, like this one: http://domain.com/wp-content/uploads/2024/01/logo.jpg
2. Next, download the image, make the necessary changes to the text, and then upload the new, translated image to your site’s Media section. For example: http://domain.com/wp-content/uploads/2025/12/logo-spanish.jpg
3. Open the Autoglot – "Text Replacement" module. Add a new record and give it a name (this is just for your reference). In this tool, you’ll replace a part of the original image’s URL with the new one. In the Original Content field, paste the part of the original URL that should be replaced: 2024/01/logo.jpg. In the corresponding language row, use the New Content field to paste the different part from your translated image’s URL: 2025/12/logo-spanish.jpg

This will ensure that when a visitor switches to the translated language, the system swaps out the original image with your new, translated one.

Yes, you can! Starting from version 2.3.0, Autoglot provides a flexible Translation Editor that lets you manually modify translations. This tool displays all records from translation DB with convenient “search” and “filter by language” functions. There is an option to delete translation records so they will be re-generated. The most important, translation editor comes with a “Quick Edit” button to let a site administrator, translator or proofreader manually adjust and modify the translation.

Yes, starting from version 2.6.1, WP users with “Editors” role can access Translation Editor module and edit/delete translations.

To enable this, please proceed to Advanced settings and under Admin Settings choose “Yes, Editors can edit and delete translations”. Don’t forget to save the settings!

If you’re using a caching plugin or server-side caching in your hosting provider, please start with clearing/purging it. Try refreshing your website page or access it in incognito mode.

You can use a [ag_switcher] shortcode to add a language switcher to your website posts, pages, popups, etc.

Add a "title" argument if you want to set a custom title of this box: [ag_switcher title = "Website Translation"]. Use [ag_switcher title = "_"] for an empty title.

Use a "type" argument in order to select a type of language switcher:

1. [ag_switcher type = "smallflagslist"] – small flags.
2. [ag_switcher type = "flagslist"] – large flags.
3. [ag_switcher type = "languageflagslist"] – list of languages with flags.
4. [ag_switcher type = "languagelist"] – list of languages without flags (default).

Add "hidebox = 1" argument if you don’t need a default widget-like box around switcher: [ag_switcher hidebox = 1].

Yes, you can use the same API key on different websites. These can be your staging and production sites, or even completely different domains.

If you need to activate Autoglot account on another website, simply install and activate the plugin, then use the same Autoglot API key during setup or on the Autoglot settings page.

When you enter your Autoglot API key on a different website, it will link that new site to your existing Autoglot account, allowing you to use your translation balance there.

Please make sure this is secure as there isn’t any way to limit the consumption of translation credits for each individual website.

Sharing API keys with other people isn’t secure and could lead to unexpected expenses. However, if you own all the sites where the key is used, this approach works perfectly.

Alternatively, you can create separate Autoglot accounts for each site and manually transfer translation credits from one account to another via support tickets.

All translation are stored in your local WP database, particularly in [wp_prefix]_autoglot_translations table. In order to move translations from your staging to your production environment, simply move this table to the production DB. In this case, no new API call should be made (this is only valid if the original content is absolutely the same).

Please note, if you set up Autoglot on two separate sites (e.g., your staging and production environments) and translate the same content on both simultaneously, you will use your quota twice (once on the staging site, and then again on the production site).

Think of it like your main post content: if you add content on your staging server and then move that database to your production server, you’ll see it there. If you don’t move the database, you’d have to add the content on both your staging and production servers twice.