Create & Publish
Content Translation
Localize a page for a new language and market with the keywords researched in that market and hreflang checked on the way out — not a word-for-word translation of what already ranks somewhere else.
No credit card required
In your own words
Ask it like this
Content Translation is not a screen to configure. It is a conversation — these are the prompts the app itself suggests.
- Audit hreflang on my homepage
- Map keywords for a new language market
- Translate and localize a key landing page
What you get
The work comes back finished
Content Translation returns something you can act on the same day, not a dashboard to interpret on your own.
Keywords researched in the market
The phrase people actually search in the target country, which is often not the translation of the phrase that works in English.
Localised, not converted
Currency, examples, units and idiom adjusted for the market, so the page reads as though it was written there.
Hreflang checked
The tags that tell Google which version belongs to which market, validated for the return-link and self-reference errors that quietly break the whole set.
How it works
Three steps, and you are done
Content Translation runs the same way everything else here does — one workspace, one conversation, and nothing published behind your back.
Connect your website
One workspace per site. It crawls what you have, learns what the business does, and — if you connect Google Search Console — starts from your own measured performance rather than from market averages.
Ask for the job
Pick the skill or let Auto route it, and describe what you want in a sentence. It buys the data it needs from DataForSEO and Ahrefs instead of estimating it, and reads the live results for the terms in question.
Review, then decide
The findings land in chat and are saved to the project, so the next question builds on them. Nothing reaches your site unless you approve it — the only thing that can publish is an article, to a CMS you connected.
Under the hood
The numbers are bought, not guessed
Everything Content Translation tells you traces back to a source you can name.
- DataForSEO — in-market keyword data
- Live crawl and hreflang inspection
- Live Google SERP in the target locale
Included in every plan. There is no separate vendor account to connect and no usage bill on top of the subscription — where a figure is an estimate rather than a measurement, the answer says so.
Questions
Frequently asked questions
Which languages are supported?
Each project is set to one content language and market at setup, chosen from a full BCP-47 locale catalogue — en-US, de-DE, uk-UA and so on. Research, SERP data and articles all follow that setting.
Why not just use a translation tool?
A translation gives you the same page in another language. It does not tell you that the term with the volume in Germany is a different word, that the SERP there rewards a different page type, or that your hreflang tags are pointing at each other incorrectly.
What are the most common hreflang mistakes?
Missing return links between versions, a page not referencing itself, wrong or invented region codes, and hreflang pointing at URLs that redirect. Any one of them makes the whole cluster unreliable, and none of them shows up as an error anywhere in your CMS.
Can one project target several markets?
A project is one website and one market. For a second market, create a second project — that keeps the keyword research, the SERP data and the memory for each market separate, which is what makes the advice specific.
Keep looking
The rest of the employee
Content Translation is one job out of fourteen, and they all share the same context about your website.
See all features