How To Plan Ahead For Content Updates?

Content_Update

One thing to remind you: your website is a living entity on the internet. Every update you make influences its interaction with visitors, customers, and search engines. And yes, a static website without any updates may be viewed by the mentioned search engines as dead. Simply put, if you update your website often enough with high-quality content, your advances towards the search engines may be finally returned. More Keywords = More Content = Frequent Indexing = Organic Curve Rising.

Deal with it! In fact, we assume that you already have dealt with it, just now you are searching for the sensible way to plan all of that. And we will help you with it.

Meet Your New Friends: Continuous Translation

These are two terms that will truly unlock your imagination from monolingual boundaries because when used together, they allow for ridiculously easy maintenance of multilingual website content. 

Continuous Translation is an idea derived from cloud computing – Continuous Integration in particular. The latter aims to provide updates to apps and cloud services without disrupting continuity of service (often advertised as 100% uptime). In the localization world, downtime would mean that a particular interface element, like a menu item, or web page as a whole, let’s say a blog post, wouldn’t be available in one of the many languages offered to users. Continuous Translation prevents that from happening. 

There’s a basic “Sync” principle behind it. Regardless whether you use Over The Air translation or GitHub/BitBucket based versioning, the “Sync” mechanism crawls all of your new content on a schedule and compares it against its previous version. It then checks whether translations are available or not. And yes – it’s able to identify which sentences in particular need to be translated – it doesn’t matter if it’s simply a small change on your website!

…and Translation Memory.

Translation Memory is essentially the database against which the “Sync” changes are being checked. 

Every sentence ever translated into any language is indefinitely stored in the Translation Memory and is readily available to pull up when it appears again in new content. If new, fresh material is added to the site, the Translation Memory isn’t carrying its version, then the difference will be noticed and Continuous Translation will be put to use to fill the gap. This will happen both for new original content and whenever adding a new language to your website’s language stack. 

Each language has its own Translation Memory. The more you use it, the smarter it gets, and the more human translations you can use completely free of charge. Some of our customers who deployed global strategies are seeing a 50% decrease in translation spending, simply after being with us for a couple of months. After all – web content tends to be repetitive (with a few exceptions).

TranslateAndPay
See What We Did Here? 😉

Human Translator Issue

Budget-wise, in case you were wondering, charges may apply as human translation has a per-word cost. Each new word should be considered an expense multiplied by the number of languages you maintain. But you know what? Machine Translation is built into many systems, including ours. You can quickly fill in the blanks using Google Translate until you get approval for an extension of your localization budget. And if the Machine Translation works fine, it can be merged with your Translation Memory to be re-used, free of charge.

So… How Should You Plan For Content Updates?

First of all, make sure you deeply understand that the underlying, original content version – it will be used as a basis for every other language! With Continuous Translation and Translation Memory in place, working in the background, automatically and completely self-reliant, you DO NOT HAVE TO plan ahead.

Just Go With Your Creative Flow!

Gosia Szaniawska
Written By:

Gosia loves copywriting and product translation. Additionally, is content marketing and lolcats junkie.

Add a Comment

Your email address will not be published. Required fields are marked *