Manage your WordPress Translation Workflow
WordPress is the most popular web content management system in the world, used by 35% of the websites. To easily manage the translations of multilingual websites, site owners and content managers can use the LocHub WordPress connector.
The LocHub WordPress connector allows content managers to select the WordPress content that needs to be translated, create a translation job, send it to any Language Service Provider and publish the translated content, all from within the LocHub interface. In addition, LocHub reports in real-time on the status of your translation job(s).
After the connector configuration (which required minimal developer skills), LocHub pulls content from WordPress, allowing content managers to easily select the WordPress content that needs to be translated, set the automation rules and send it for translation to any LSP or directly to MT.
The connector supports the translation of pages, posts and even content created via Custom Post Types. Watch the video below to get an impression on how it works.
- Seamless exchange of contents between WordPress and LSP;
- Contents are pulled from WordPress and pushed into translation automatically;
- Scalable automation, fully automate content flows and still keep the option to manually create a project;
- Automatically publish translated content once it is returned;
- No manual file export or handling required;
- Freedom of choice – work with your preferred LSP.
- Content Managers can manage the complete translation process within the LocHub environment;
- Localization Managers can check status of translation;
- Supports preview.
Watch in action?
In this video, we demonstrates how to translate Wordpress content with LocHub and its Wordpress connector. We will translate several blog posts from English to German, Dutch and French using LocHub WordPress connector.
- Installation of LocHub
- Configuration of WordPress connector
- Wordpress 4.7 and higher
Find Answers to Your Questions
We submit whatever AEM supports and is selected at project creation: assets, pages, l18n dictionaries and tags.
Yes, it does. For example, by transferring the html of a page as long as the content owner allows for it.
The content manager would create a new project to translate the new page version or the updated page.
No, there is no limit and no noticeable slowdown.
Our connector transfers pages or assets, depending on what the content manager decides to be translated via AEM function. LocHub submits the whole page, it will be the translation memory to identify the specific segment that needs to be updated.
The status in AEM will be updated. In addition, the content manager / localization manager can access the project overview in LocHub for more details.
There is a page view function in AEM that the content manager can use to sign-off the page before publishing (no connection to the translation memory). LocHub also supports in-context review function on TMS side.
Request a quote
Fill out the form and we will contact you as soon as possible.