A website with a few pages in two languages can be run by one careful editor. A site with hundreds of pages in six languages cannot. Pages change daily, editors come and go, and no one is quite sure which version is current. Translation workflow management gives website teams a clear route for every page.
What a workflow really is
A workflow is the agreed path a piece of content takes from source to live page. It names the steps, the people and the deadlines.
If the path lives only in people's heads, it breaks when they are away. Writing it down and building it into a system fixes that.
Map your pages first
List the page types on your site: product pages, blog posts, help articles, legal pages and landing pages. Each type has different needs for speed and quality.
This list becomes the base for your workflows.
Choose the right system
A translation content management system brings files, memory, glossary and review into one place. Look for connectors to your CMS and clear status views.
Avoid tools that need manual exports for every page.
Triggers for new content
Decide when translation starts: on publish, on approval or on request. Automatic triggers prevent forgotten pages.
Manual requests work for rare content, but not for daily updates.
Detecting changes
Pages change after launch. The system should detect edited sentences and send only those to translators.
This saves money and keeps languages in sync.
Roles and responsibilities
Editors create content, translators adapt it and reviewers approve it. Name an owner for each language and for the process as a whole.
Clear owners reduce delays and confusion.
Deadlines and priorities
Not all pages are equal. Mark urgent pages, such as promotions, and give routine pages a standard turnaround.
Dashboards show what is late or at risk.
Memory and glossary
Navigation, footers and recurring phrases appear on every page. A shared memory translates them once and keeps them consistent.
A glossary keeps product names and key terms the same everywhere.
Content structure
Keep headings, links and formatting safe during translation. The system should show translators only the text, not the code.
Test a sample page to confirm that layout survives.
Context for translators
Screenshots, page previews and short notes help translators choose the right word. This matters most for buttons and short headings.
Better context means fewer questions and fewer corrections.
Review and approval
Local reviewers should check key pages in context before they go live. Changes should be tracked and comments kept in one place.
Set a deadline for review so pages do not wait for weeks.
SEO fields
Titles, descriptions and slugs need translation too. Follow good practice from sources such as content management system translation to keep search value across languages.
Include these fields in every workflow.
Handling media and downloads
PDF files, images with text and videos need their own steps. List them and decide who updates them.
Missing media is the most common reason for half translated pages.
Quality checks
Automated checks catch broken links, missing tags and number errors. Human review covers tone and brand fit.
Track recurring issues and fix them at the source.
Machine translation rules
Decide which pages may use machine drafts and which need full human work. Document the rules inside the system.
Make sure reviewers know when they are editing a draft.
Some page types should never rely on a machine draft alone. Clinical and patient-facing content is the clearest example, because a small wording error can change dosage instructions or consent language. Teams handling that material often turn to medical translation services with trained reviewers who check every term against approved sources. Building that specialist step into the workflow protects readers and keeps the organization compliant.
Version control
Keep a clear record of which source version each translation matches. This prevents mismatches after quick edits.
A good system shows differences between versions.
Working with external partners
Invite agencies and freelancers into the system rather than sending files by email. They use your memory and glossary and deliver in the same place.
You keep all assets even if you change partners.
Reporting
Reports show volume, turnaround, cost and savings per language. They help you plan budgets and staffing.
Review them monthly with your team.
Open resources
Open communities share useful ideas on localization workflows, such as the Mozilla localization resources pages that explain how large projects manage translation.
Borrow what fits your own team.
Security and access
Unpublished pages are confidential. Limit access by role and project, and check who can publish.
Review permissions when team members change.
Training
Short sessions for editors and reviewers prevent most mistakes. Provide a one page guide with screenshots.
Update it when the workflow changes.
Common mistakes
Skipping context, forgetting media and having no owner for each language are the usual problems. A checklist helps.
After each big launch, hold a short review and improve the workflow.
Launching a new language
Adding a language is a project of its own. Start with the most visited pages, test the workflow, then extend to the rest of the site in stages.
Announce the launch internally so support and sales teams are ready for new questions.
Final advice
Good workflow management makes translation routine. Map your pages, automate the repeating steps and give people clear roles, and your website will stay consistent in every language.