Andrei

Hello there,

Thanks for reaching out to us!

1.

TP works on a string by string translation, so the whole post content is not translated and stored as one entity, rather it is split into pieces. There are no filters that are triggered when a post is translated. If you have automatic translation on, then the post is translated when then a page containing the post is accessed.

You can retrieve translation of a post content using this custom code. It also translates it automatically if untranslated.

$trp = TRP_Translate_Press::get_trp_instance();
$trp_render = $trp->get_component( ‘translation_render’ );
global $TRP_LANGUAGE;

$content_post = get_post($post_id);
$content = $content_post->post_content; //actual text, it can be post title etc.
$TRP_LANGUAGE = ‘en_US’; // language code of translated language
$translated_custom_content = $trp_render->translate_page( $custom_content );

Original-translated string pairs stored inside TP tables are linked to a particular post ID in wp_trp_original_meta, using the post_parent_id meta key. The original_id column refers to the original_id of the trp_dictionary_lang1_lang2 tables.

2.

Regarding your concern about SEO and duplicate content, this can indeed be a valid concern if a lot of your blog posts are duplicated in as many URLs as there are languages defined. This could potentially impact your SEO ranking due to perceived duplicate content by search engines. However, TranslatePress adds ‘hreflang’ attributes to your pages, which notifies search engines about the different language versions of your page. This should mitigate the risk of SEO penalties for duplicating content across different languages.

3.

Finally, your idea of adding the ‘noindex’ robots meta tag to untranslated posts does sound like a logical approach to avoid these URLs being indexed by search engines. While TranslatePress does not have an automatic feature for this, you may be able to achieve this with custom coding or a SEO plugin that allows for this kind of customization.

Best Regards,

Hello there,

Thanks for reaching out to us!

We tried checking this problem on your website but we could not locate it, would you giving us more details on this topic? Maybe some screenshots?

Looking forward to your reply.

Hello there,

Thanks for reaching out to us!

If TranslatePress detected once these unnecessary, it will again even if you delete those.

In order to delete this strings you can do so by removing their entry from the tables you mentioned. But before doing this please make sure you make a backup and you refer to this article.

Let me know if this works for you!

Best Regards,

Hello,

Thanks for reaching out to us!

I apologize for the inconvenience, it is true that we are aware of this issue and we tried dealing with it multiple times but we couldn’t find a permanent solution.

TranslatePress operates on a unique string by string approach, which means each separate HTML tag within your content is considered an individual string. This method allows for a precise translation of each element, but sometimes may cause deviation from the original sentence structure when HTML tags such as bold and links are present within the text.

One approach would be to wrap the page’s content with a translation block:
https://translatepress.com/docs/translation-editor/#translation-blocks

You have to keep in mind that the entire content will merged into one string, so any changes made to the original text will invalidate your translation.

Kind regards,

Hey there,

Thank you for approaching us with your concern.
​ 
Block Crawlers simply tries to detect if it’s a bot and not automatically translate that particular page. Since bots can be varied, we can’t guarantee all will be detected.
​
In regards to the large amount of POST requests to trp-ajax.php, you might want to try disabling the ‘Dynamic Translation’ from the Advanced settings section. This could potentially resolve the issue.
​
Please let us know if disabling the dynamic translation helps
​
Best Regards,

Hello there,

Thanks for reaching out to us!

Please check the index of your website using https://search.google.com/search-console/welcome Google Search Console. It will give you a clear report as to whether something is not indexed correctly, not a 3’rd party.

Unfortunately we can’t debug search indexing issues as Google only offers that information to site-owners.

I’m not excluding a conflict with our plugin, just saying you need Google Search Console active to properly identify the issues regarding crawling certain URL. There is even a URL checker so you can test if there are problems with a particular URL: https://support.google.com/webmasters/answer/9012289?hl=en ​​​​​​
That being said, if you spot any anomalies, or you get any errors reports in GSC related to the secondary language, then please let us know and send them to us, so we can investigate further.

​Hey there,

Thanks for reaching out to us!

For the time being, we don’t allow custom size flags. You can change them, but they need to be that resolution.
In order to have a crisp flag, you need to upload the exact flag size. Our flags are basically icons and are created small with exact pixels so they look ok at such small resolutions.

Hello there,

Thanks for reaching out to us!

At the moment the implementation of this feature is not a priority for our team but it could be in the near future.

Thank you for understanding!