Cistate Translation Proxy Frequently Asked Questions (FAQ)

What is Cistate Translation Proxy?

What kind of service is Cistate Translation Proxy?

Cistate Translation Proxy is a cloud service that automatically converts existing websites into multiple languages using AI. By using reverse proxy technology to apply translations between your server and users, there is no need to make any changes to your existing site's CMS or server. You can launch a multilingual site in as little as one week.

How does the translation process work?

When a user accesses the translated version of your site, Cistate Translation Proxy retrieves content from your original site in real time and displays it with AI-powered translation and glossary applied. Your original site remains completely untouched.

What is the difference between the Server Version and the Frontend Version?

Cistate Translation Proxy offers two implementation methods: the Server Version and the Frontend Version.

Server Version is assigned a dedicated URL for delivering translated content. On your end, you can implement it simply by setting up the dedicated URL as a virtual directory on your web server (such as Apache). If you are using a CDN such as AWS CloudFront, you can implement it in the same way by setting it as the origin. Since translated pages have their own unique URLs, they are highly effective for SEO and are correctly indexed by search engines as multilingual pages.

The Frontend Version can be implemented simply by inserting a single line of JavaScript tag into your HTML. Since the translation is performed in the browser, it also supports SPAs (Single Page Applications) and content dynamically generated by JavaScript.

It is also possible to implement both in combination. For example, you can flexibly configure the system to apply the server version to static pages for SEO benefits, while using the frontend version for dynamic content areas. When implementing both together, the server version will automatically insert the JavaScript tag for the frontend version, so no additional work is required on your end.

About Implementation and Basic Specifications

How long does it take to implement?

Implementation can be completed in as little as one week. The timeframe may vary depending on the size and requirements of your site, so please contact us for more details.

Can it be implemented without disrupting the design of my existing site?

Yes, it is possible. Cistate Translation Proxy applies translations while maintaining the existing site's HTML structure, minimizing any impact on the design.

Is it compatible with dynamic sites such as SPAs (Single Page Applications)?

Yes, it is supported with the frontend version. Content dynamically generated by JavaScript can also be translated. It can also be used in combination with the server version.

Do I need to migrate my server or make complex changes to implement it?

No, it is not necessary. For the server version, you only need to set up a virtual directory on your existing web server (such as Apache) or configure the origin on a CDN (such as AWS CloudFront). For the frontend version, you only need to add a single line of JavaScript tag. In either case, you can continue using your existing web server or CMS as is.

What preparations are required for implementation?

All you need to launch the translated site is the URL of the site you want to translate. Additionally, when publishing the translated site, you will need to set up the language switch menu on your end.

What are the differences from Google’s website translation?

Google’s website translation (Google Translate widget) is a feature that machine-translates pages within the browser. The main differences between Cistate Translation Proxy and other solutions are as follows.

1. Editing and Saving Translations — With Google Translate, you cannot edit or save translations, but with Cistate Translation Proxy, you can manually edit and save translations using the translation editor.
2. Glossary Registration — The Google Translate widget does not have a glossary feature, but with Cistate Translation Proxy, you can register proper nouns and technical terms in a glossary and have them reflected in the translation.
3. SEO (Search Engine Optimization) — Since Google Translate performs translations in the browser, the translated content is not indexed by search engines. With the server version of Cistate Translation Proxy, translated pages have their own unique URLs, so they are properly indexed by search engines as multilingual pages.

Which languages are supported?

We support a wide range of languages, so there are no languages that cannot be translated. However, translation accuracy may vary depending on the language pair, so please feel free to consult with us.

Can additional languages be added?

You can also add languages later.

Can translated pages be found on Google?

In the server version, each translated page has a separate URL for each language and includes the translated content in the HTML, so Google correctly indexes them as multilingual pages. The hreflang tags are also properly output, so pages that match the user's language will appear in search results.

There is a possibility that the frontend version may also be indexed by Google, but it can be disadvantageous in terms of SEO. In the frontend version, translation is performed using JavaScript in the browser, so the initial HTML contains the original, untranslated content. Google's crawler processes pages in two stages: first, it retrieves the HTML (phase one), and then the rendering of JavaScript (phase two) is deferred until later. As a result, it may take time for the translated content to be indexed, or it may not be indexed at all. Additionally, some search engines other than Google (such as Bing) may not execute JavaScript properly, which can result in the translated content not being recognized.

Is it possible to display translated pages on the same domain as the original site?

Yes, with the server version, it is possible to operate using a subdirectory format (e.g., example.com/en/). By configuring virtual directories on the web server or setting the origin on the CDN, you can deliver translated pages on the same domain as the original site.

Is it possible to hide parts of a page in the translated version?

Yes, it is possible. It is possible to configure certain elements to be hidden on the translated page.

Can sites that require a password for access also be translated?

Yes, it is supported. You can use it with sites that require authentication or in environments with IP restrictions.

However, password-protected pages may contain confidential information such as personal data. With the server version, content is processed via a proxy server, so confidential data will pass through external servers. If this is not desirable from a security perspective, we recommend using the frontend version. With the frontend version, translation is performed in the user's browser, so the page content does not pass through external servers.

You also have the option to exclude highly confidential pages from translation. For optimal security, it is ideal to apply the server version to public pages to ensure SEO benefits, while using the frontend version or excluding translation for pages that require authentication.

The layout broke after translation. What could be the cause?

The main reason is that the length of the text changes due to translation. Normally, if such issues are found during pre-implementation checks, we will adjust the CSS of the translated pages on our end. In some cases, you can also address this by adjusting line breaks in the translation editor.

There are links to external sites. Is it possible to change the destination URL for each language?

Yes, with the link replacement feature, you can set different destination URLs for each language.

About Translation Accuracy and Customization

If there are mistranslations or unnatural expressions, can they be manually corrected?

Yes, you can manually edit and save the AI translation results from the dedicated management screen (translation editor).

Is there a dictionary feature for registering technical terms and proper nouns?

Yes, there is a glossary feature. You can register internal terms, product names, and more, and apply them to translations.

Is it possible to exclude only specific sentences or pages from translation?

Yes, you can set specific pages or certain elements within a page (such as those specified by class) to be excluded from translation.

Can text within images also be translated or replaced?

With the image replacement feature, you can display different images for each language. For information about the automatic translation of text within images, please contact us.

About Pricing and Contracts

Please tell me about the initial and monthly pricing structure.

We offer plans based on the size of your site (number of pages) and the number of translation languages. For details, we will provide a quote, so please contact us.

Does the pricing change based on the number of pages or page views?

The pricing is based on the number of pages (URLs). There are no usage-based charges for page views (PVs).

Is there a free trial period?

Yes, you can use a free trial as a proof of concept (PoC). For more details, please contact us.

Are there any discounts for implementing on multiple sites?

We are also available to discuss implementation on multiple sites and volume discounts.

How can I cancel my subscription, and what happens to my data after cancellation?

Cancellations are processed according to the prescribed procedures. After cancellation, your translation data will be retained for a certain period and then deleted. You can also export your data if needed.

About Security and Support

Will the data I enter be used for AI training?

No, your data will not be used for AI training. Our system is designed with a strong focus on security and privacy.

How is the translation of pages containing personal information handled?

All communications are SSL encrypted and processed securely. However, with the server version, content containing personal information passes through the proxy server, so it may not be suitable depending on compliance requirements. We recommend using the frontend version for pages that contain personal information. In the frontend version, you can configure certain elements to be excluded from translation, and since the translation process itself is not applied to these excluded sections, no personal information will be sent to the translation engine. You can also exclude entire pages from being translated. For more details, please also refer to "Can sites that require a password for access be translated?"

Please tell me about the support system for operation methods and troubleshooting after implementation.

We offer support via email and chat. Our dedicated staff will provide support, including guidance on how to use the system and troubleshooting.

Is it possible to set up an SLA (Service Level Agreement)?

SLA settings are available to meet your requirements, such as for enterprise plans. For more details, please contact us.