Trigger translation manually

  • Resolved marcoverheiden1

    (@marcoverheiden1)


    10 months, 1 week ago

    Hi,

    Is there a way in TranslatePress to trigger the machine translation of all untranslated content manually?

    I read in your documentation it is only triggered upon second reload of a page. It means the full site must be browsed by a human visitor twice before it is machine-translated. This is fine for small sites, but there are also large sites that have landing pages a user doesn’t normally visit, only through search engines. If those pages aren’t translated, they aren’t indexed by search engines, and therefore the landing pages do not get translated. Do you see my point?

    Isn’t there a way or command with which TranslatePress is triggered to translate all untranslated content up to that point (i.e. without manually visiting a page twice)?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Where excatly did you read we are translating at the second load of a page? You can send us a link.
    Those apply only for gettext and slug translation. Gettext and slugs load before our own plugin. So the way our plugin is constructed, they get applied on the second load of the page.
    Translation API calls are time-consuming. TP tries to perform a single call right before the end of the execution. This is why gettext and slugs are not translated on the first time the translated page is loaded. Slugs translations would be needed early in the execution.
    More than that, TP doesn’t translate slugs of other languages when loading current language. So accessing default language English, will not result in using the Translation API for other languages.
    What you can do is install WP Super Cache (even if you don’t need it) because it has a preload caching function. This means it should try and access all website pages and create a caching page for them — reaching the translations for slugs also, even if for new stations this could be difficult to use. Keep in mind that this is just a suggestion, not sure if will have the desired effect.

    The rest of the content, the regular one, is translated when the user access that page first time in different language, so there is’ no’t necessary any second load of the page here.

    Also, regarding indexing, we’re clearly defining the language and offer the alternative languages in the HTML, so google should know these are not duplicate content pages, but translated versions. Once the pages will be translated, the google will adjust the information automatically.

    Best Regards,

    Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Since 5 days have already passed without getting any reply from your side,I will close this thread and mark it as “Resolved”.

    If there’s anything else, let us know!

    Kind Regards,

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Trigger translation manually’ is closed to new replies.