Are the translations made by a translator included in the word quota?
Nope, the word count limit is only for automatic Neural Machine Translations. A translator can manually edit automatic translations with no limit.
Nope, the word count limit is only for automatic Neural Machine Translations. A translator can manually edit automatic translations with no limit.
Every plan and its translation quota is associated with one domain. Though, you can subscribe to an unlimited number of plans for multiple websites with one Linguise user account (if you have many clients, for example). If you are representing a web agency and want to translate 3 websites or more, we can generate a discount for you. Just use the contact form here to get in touch, we’ll do the rest.
That’s possible in the first step of the website domain registration or afterward using a content exclusion rule. For example, it’s possible to exclude a blog translation in one or several languages by adding an exclusion rule by URL like www.domain.com/blog/* You can find more information in the documentation here >>
Yes, an active plan is required to give translations to your customers. The translations are stored on a Linguise cache server and in a remote database. Every time a new content or a new part of an existing content is detected on the website, it will go through the translation API. That’s why an active plan is required.
When you reach the number of words translated included in your plan, the new translations will stop, the existing ones will continue to be served to your users. Your translation quota can be checked from the Linguise admin dashboard.
Yes, the trial can be used for each new domain registered, even if you have several domains under the same user account. Consider it as a 1-month free advantage.
Yes, absolutely and there’s no limit on the number of page views. During the 1st month of the trial, you can translate up to 600 000 words, that is the PRO quota plan. The amount of translated words of your website can be checked anytime from your Linguise dashboard.
You can have several domains (websites) managed by one account. But each domain and subdomains translations are billed separately.
That depends on the number of languages you want to use. Translation quota is calculated as following: (Number of word in the original language X Number of translated languages) – The translation exclusions Whenever you reach more than 600 000 words, the UNLIMITED plan is the solution as you don’t have to worry about word count, it’s unlimited.
If you cancel your subscription (or just don’t activate a subscription), your translations will stop to be served to your website visitors. If you reactivate it, they’ll be back online. I know it may not be an easy decision to translate with an entirely new system. This is why we are offering a 30-day trial with no commitment required. We also offer dedicated support if you need any assistance.
Yes sure, we do have a coupon for non-profit and educational entities. Please use the contact form to get in touch with our team.
The unlimited (large) subscription cannot be used with the trial. That’s because the major cost of the service is the amount of Neural Machine Translation API we pay for and the Large plan has no limit. What is recommended is using the trial with a few languages and limiting the translation to a certain part of your content, using a global rule. You can, for example, exclude your blog pages from translation. Here is a documentation about how to add rules: Exclude pages from translation using URLs
Yes, we are using Stripe payment processor where your card information will be stored automatically. Then your subscription will be renewed automatically. You have to edit if one information in card is changed only
We have not planned to make any prices change in the future for several reasons. The translation API market prices have been very stable the last 5 years or so. Also the way we store and avoid useless content to be translated are going in this way too.
Your site will not be translated anymore if your subscription is expired. That means all your translated content won’t be served to your visitors. That’s because the major cost of the service is the amount of Neural Machine Translation API we pay for, and once the translation is made it has to be stored and served from our servers. Linguise is based on a SaaS model (Software as a Service). Do you need more time to decide, like 10 more days? We can reactivate it, or you can also subscribe and get your translation back. Le us know and we
If you upgrade to a new plan, we will apply a prorated price.It means that you will be refunded for the time you did not spend on the current plan, and you will only pay for the remaining time on the new plan. In any case, during the upgrade process you will have a summary of the upgrade, and you’ll see all the information you need before confirming your upgrade.
You can update your billing information through the dashboard Using the menu: Home > Billing details Once updated, you can download again your invoices by clicking your credit card number. I have attached a screenshot to help: https://drive.google.com/file/d/1Lc7BeoSRHnBKbw4bl7Qu6DUvbtby2pfb/view?usp=sharing Detailled documentation here: https://www.linguise.com/documentation/debug-support/billing-edit-credit-card-info-and-invoices/
When Linguise is activated all your website content is translated but not a contact form? This is probably due to the fact that the form content is loaded asynchronously using AJAX, therefore, Linguise cannot get the content to translate it. What’s the solution? The solution to that depends on the CMS and the contact form extension you have, but if the form provider is using this method, there’s probably a setting to disable it. On WordPress, here’s a non-exhaustive list of the contact plugins that work with Linguise or have an option to disable asynchronous loading: Gravity forms Formidable Forms
In DIVI builder, you have the option to make some content different for mobile, tablet and desktop. In DIVI builder, you have the option to make some content different for mobile, tablet and desktop with tabs above the content. When using it, your content updates when you change the device, are made in the code with .json. This is an issue for the live translation because we cannot intercept the content loaded in AJAX. What’s the solution? The solution is to duplicate the DIVI module and use the DIVI visibility setting. This is also the best solution for the SEO
If it’s not working at all, it could be due to a caching service that prevent our script to be called (like Varnish, Cloudflare, WP Rocket, WP Speed of Light, …). If Linguise is not called, it will not be able to redirect the user. Redirections are only applied with new visitors, in non multilingual pages. If the visitors loads directly a translated page it means that he wants a translated version. We don’t redirect him in this case. We also don’t redirect when the visitor navigate under your site and has already loaded a page. If you’re testing redirection make
Reset password tokens have an expiration time of one hour. Please try to reset your password again and reset your password with the new token within the hour.
You can check the variable $_SERVER[‘HTTP_LINGUISE_ORIGINAL_LANGUAGE’] if it’s not defined, you are under your default language. Otherwise, it will contain the current translated language.
First, replacements or ignore rules will only be applied to new generated urls.It’s necessary to avoid 404 pages on old urls that could hurt SEO. You’ll have to update the urls directly in the Linguise dashboard and create your redirection rules in your .htaccess file. Now, about the rules not applied in html content, it could be due to the local cache.You can clear the local cache in the extension settings in the admin side of your website.Just press the “Clear cache” button and it should be good.If you have other cache services in front of your website, like Cloudflare,
It may be because your content is inline HTML, like <span>Hello<span>World</span></span>. Therefore, Linguise consider it as an inline content, and tries to apply the correct span tags in the translation where the terms may not be at the same position. It can then render tags a bit differently than it was at first. If you rely on it for your positioning, it may change how it’s displayed. There are two options to fix it: You update the original content to block elements where you visually want block elements (replace some spans with div of p) You can add a rule
Unfortunately Linguise is not able to translate dynamic content. It has to see the actual html content in the page you’ve loaded. It requires a custom development for each plugin that uses Ajax request. We’ve done some integration, like WooCommerce and emails translations but unfortunately we can’t do integration with all existing extensions.
All errors code: https://www.linguise.com/documentation/debug-support/wordpress-plugin-error-codes/ Error: Translation not allowed Linguise do not allow your domain to make translation. Please verify that you’re not in one of these cases : Your trial is expired You have reached your translation quota You don’t have a valid subscription for this domain Error: Content type not translatable This error is returned when a translation is tried on a content that is not an HTML document. For example, when you try to translate an XML page.
Sorry but Linguise cannot “translate” images in multilingual. This is a feature we’ve planed to implement with the possibility to update an image URL per language. Though, if you can write few lines of PHP code, we can provide a script that would help you to do that.
There are around 84 languages available. You can check the language list here: Languages available Note that for better SEO optimization, at the beginning of the translation, it’s better to focus on the most important the time search engine crawler proccess all the new pages. Also it’s better to start with the languages that are better in a business perspective.
Linguise provides multilingual content that should be indexed automatically in all search engines, like any other website pages because the we respect all the SEO international content standard. Though, to accelerate or improve the process we recommend to: Connect your website to the Google Search Console and submit multilingual sitemaps Make a regular check for any coverage issue in the Google Search Console Exclude pages with poor content from the robot.txt Analyze your multilingual traffic in Google Analytics Improve neural translations on important pages with a human translator Linguise SEO details: https://www.linguise.com/grow-your-audience-with-seo-optimized-translations/ More info on Google Search Central: https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites
Yes sure, any CDN will work with Linguise translation. The only modification you need to make is with Cloudflare WAF system if it has been activated. To return translation, Linguise translation needs to make a call to its own script on your server. You have to whitelist your website IP in the WAF rules.
If you have a message saying the translation is reached, by email or on your Linguise dashboard, the translation will not work anymore. If you’re using the trial, the maximum quota of translation included in the trial plan, 600 000 words. You should have received an email notification about that @80% and @100% of the translation quota reached. If you want to continue to serve translations to your customers on a long-term basis, we recommend activating a subscription. If you wish to test a bit more of the service, you can contact the customer service.
Linguise will only be able to translate iframes on the same domain. As it has only access to your domain’s content, it won’t translate iframes from third-party websites.
The domain registered in our database is www.domain.com and the CMS in use is WordPress. When trying to translate indeed that your pages are returning a 404 error. The usual causes to check first is that the URL rewrite is properly activated on your system. In WordPress you can find the setting in Settings > permalinks Moreover, please ensure that other translation plugins are disabled in your website. Some of our competitors add their own code in the .htaccess file, please also verify that your .htaccess file has no redirection from other plugins. If you prefer you can provide your
Linguise has a specific integration for the most popular CMS like WordPress or Joomla but it can be installed easily on all website systems based on PHP. Check the integration tested and documented: https://www.linguise.com/integrations/ Check the general PHP install documentation: https://www.linguise.com/documentation/linguise-installation/install-linguise-on-any-website-that-runs-php/
Yes, this option is available in our WordPress and Joomla extensions. You’ll find it in the advanced settings under the name “Browser language redirect”, just enable it and now users should be redirected depending on their browser language.
It could be the language [is/is not] added. Have you check if the language in the plugin and the linguise dashboard are matching… For example if a language is only added in the plugin and not in the Linguise dashboard then the language flag will be displayed but you will not be able to translate in this language.
The international language tag for czech is /cs not /cz even if I understand it can be confusing. Unfortunately, it can’t be changed as it’s an international standard. More information about language tag here: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
You can update the meta tags in the live editor accessible from your Linguise dashboard. That’ll redirect you to your wesbite frontend in edition mode. Clicking on the {} button will display the meta editor. Documentation about the live editor is here: https://www.linguise.com/documentation/edit-translation-with-rules/edit-translations-using-the-frontend-editor-tool/
Translations are stored in our database. We also keep a version of the most translated page in our caching system to serve the content to your visitors the most quickly we can. It has the double advantage of saving your server resources and being able to process complex tasks on the translated content such as translation global replacement rules.
When a visitor submits a search request from your website in a translated page, Linguise will first translate the search request. For example, the visitor search for Bonjour in a French page, then Linguise will translate Bonjour to Hello and then will make the request to the original website. The request to the original website is like if your visitor was searching for Hello on your website without translation. Then the search request is returned in the translated language, here it would be French. Note that the search feature is implemented wor WordPress native search, Joomla and WooCommerce.
Linguise is only able to translate content actually served by your server. It’s not able to translate JavaScript content which is generated on the fly. You can check the content of your original page by opening the source code of your page. Just hit the CTRL + U keys on your keyboard at the time and it should display the source code. If in the code you don’t see the your terms in plain html, it means that Linguise won’t be abl to see it too.
You can copy this CSS rule in your custom CSS file or in the advanced settings of Linguise plugin: .linguise_switcher_dropdown li.linguise_current { border: none! important; }
This problem is usually due a cache issue, the page is loaded in cache instead of a dynamic version with the editor. Do you know what king of speed optimization you have on your website (a cache extension, a Varnish or Cloudflare caching system)? You can try to disable it temporarily and try again? It will help to identify the issue.