Choose the fields
Start with posts, pages, excerpts, SEO content, or other fields your editors already maintain.
WordPress localization
Translate WordPress content without turning publishing into spreadsheets.
Keep the fields your editors use, give important pages a review path, and return approved translations to the workflow that publishes them.
A publishing-friendly flow
Keep WordPress work recognizable from first draft to final locale.
Translate with context
Keep related content together so the translated page still makes sense to the person publishing it.
Review what matters
Route campaigns, policies, support content, and other high-impact pages through approval when needed.
Publish with confidence
Return approved language to the WordPress workflow your team already uses.
What to expect
Know what the workflow includes and what your team connects around it.
Supported by Babelnotch
Translation of the content fields your team selects, with tracked work and an optional review step.
Recommended pattern
Use one page your editors know well to agree on the source fields, review, and publishing handoff.
Optional connection
Reading content from WordPress and writing approved language back are connections your team configures around Babelnotch.
Ready to connect
Start with one page that matters to your audience.
A real page makes it easy to agree on fields, review, and the handoff back to publishing.
Related workflows
Related translation workflows
Strapi workflow
Open Strapi workflowhuman review
Open human reviewdocument workflows
Open document workflowsFAQ
Questions teams ask before getting started.
Can Babelnotch translate custom fields and SEO metadata?
Yes. Treat posts, pages, taxonomy labels, excerpts, slugs, and SEO fields as structured document content.
How should WordPress receive completed translations?
Use polling or a signed webhook callback from an authenticated workflow.
Can reviewers approve WordPress translations first?
Yes. Route campaign, policy, and support pages through review before publish.