A personal website for translators and interpreters

Search "translator website" and count how many results open with a paragraph about a lifelong love of language before mentioning what the person actually translates, from what, into what. That paragraph is not wrong to include eventually. It is wrong to include first, because the buyer reading it — an agency project manager scanning forty tabs before lunch, or a company that needs a contract translated by Friday — has one question on arrival: does this person work in my pair, in my direction, and do they know this subject. Everything else is decided after that, and most translator sites answer it third or fourth, buried under biography.

The fix is not complicated, but it runs against the instinct to lead with personality on a personal site. A translator's site is closer to a specialist's site than a portfolio site: state the pair, the direction, the specialism and the turnaround in the first screen, and let the rest of the page do the work of building trust rather than establishing eligibility. Buyers who can't confirm eligibility in the first few seconds leave and never find out how good the translation itself would have been.

For a solo translator, the fastest honest route to that first screen is reach: it builds a page from a CV in about twenty seconds and can be live at a free yourname.joinreach.app subdomain in under two minutes, turning the job into editing a draft rather than staring at an empty template. One limit is worth flagging immediately: it makes exactly one page in one language, no switcher, no second version — a real constraint for a profession built around working across languages, covered below.

Pair and direction, stated the way your reader expects

"Fluent in English, French and German" tells a buyer almost nothing useful, because professional translation runs in one direction by convention: into your native or dominant language, not out of it. A translator who lists three languages without saying which way the work flows is asking the reader to guess whether they translate French into English, English into French, or claim to do both — and the honest answer, for nearly everyone, is that quality drops sharply outside the native-target direction.

State it as a pair with a direction, not a list: "English to German, native German speaker" or "FR–EN, EN–FR (native English)" if you genuinely work both ways. Put it in the first screen, ideally in the first line under your name, because it is the single fact that determines whether the rest of the page is relevant to the person reading it.

Direct clients and agencies read this line differently. A direct client is usually thinking in terms of their own pair without the professional vocabulary — "I need this contract translated from German" — so the line needs to be legible to someone who has never heard the term "target language." An agency project manager reads the same line as a filter against their own database fields: source, target, native variant. Write it so both readings work: plain language first, the standard abbreviation second, not instead.

Specialism and the certifications that actually carry weight

After the pair, the second thing a buyer checks is whether you know their subject. "General translation" as a specialism is not a specialism; it tells a legal client nothing about whether you know the difference between a warranty and a guarantee clause in their jurisdiction, and it tells a pharmaceutical client nothing about whether you've ever translated a package insert under a regulator's house style. Name the two or three domains you actually work in — contracts and corporate law, clinical trial documents, technical manuals for industrial machinery, literary fiction — and be specific enough that a buyer in that field recognises the vocabulary as real rather than aspirational.

Certifications matter here, but which ones matter depends entirely on the market you're selling into, and this is where translator sites either overclaim or underclaim. A sworn or certified translator status recognised by a court in one country carries no weight in another, and stating it without the jurisdiction reads as confused or misleading to a buyer who checks. If you hold a certification tied to a specific court, ministry or professional body, name the body and the country next to it — "sworn translator, appointed by the Regional Court of [city]" does real work; "certified translator" alone does not, because certified by whom is exactly the question a legal or medical buyer needs answered before they can use the document at all.

Agency and direct client: different evidence, one page

Most advice about audience on a personal site assumes you should pick one. Translation is one of the few professions where the two realistic audiences want genuinely different proof, and building separate pages for each is more work than the difference justifies — one well-organised page can serve both if you're honest about what each one is scanning for.

An agency project manager wants operational facts fast: pair, direction, specialism, CAT tool compatibility, typical daily output in words, availability. They are not reading your bio for personality; they are checking whether you fit an open slot they're staffing right now, often against a dozen other profiles the same afternoon. Put these facts in a scannable block, not a paragraph.

A direct client wants reassurance instead of specifications, because they usually can't evaluate translation quality themselves — that's the entire reason they're hiring you. What reassures them is evidence of judgment: a short explanation of how you handle a document with unclear terminology, testimonials that describe an outcome rather than generic praise. The operational block satisfies the agency reader in ten seconds; the reassurance underneath it satisfies the direct client who scrolls further. One page, ordered so the fast reader gets what they need up top and the slower reader finds more as they go, does the job of two audiences without doubling the site.

Rates: publish a range, not silence

The instinct to hide pricing entirely and force every enquiry through a contact form is understandable — every project is different, and a fixed number invites arguments about documents you haven't seen. But silence has a cost too: it filters nobody out, so you spend time quoting clients whose budget was never close to what the work requires.

A published per-word range, or a stated minimum charge for small jobs, does the filtering for you before the enquiry arrives. It doesn't need to be exact — "typical rates run from X to Y per word depending on subject and turnaround, minimum charge Z for short documents" gives a real buyer enough to self-select, while leaving the actual quote to depend on the document itself. Agencies in particular expect this; many won't open a conversation with a translator whose range isn't stated anywhere, because their own budgeting process needs a number before they can staff a project.

One site, one language — or two, deliberately

The multilingual question deserves a straight answer rather than the usual dodge. Most translator sites should not exist fully in two languages, because maintaining two complete, current versions of a site is real ongoing work, and a stale second-language version — old rates, an outdated specialism list — actively damages the impression you want to make in that language.

The more sustainable version is asymmetric: a short version in the language of the clients you're recruiting (often English, since it functions as the trade's working language for many pairs), and a fuller version in the language you think and write in professionally, usually also the direction you translate into. A German-to-English translator whose real writing voice is English can afford a shorter German landing section and a full English site, because that split matches how the work actually flows. Maintaining equally deep versions in both languages is the plan that quietly stops happening after the first few months.

This is exactly where the reach limitation flagged earlier bites: it publishes one page in whatever language the CV was written in, with no language switcher and no second version to add later. For a translator who has decided the asymmetric two-language approach above is right for them, that's a real blocker, not a minor inconvenience — worth knowing before you upload a CV and build a page you'll want to duplicate a week later.

Sample translations and the confidentiality problem

Showing translated work is the strongest form of proof available to a translator, and also the hardest to produce honestly, because most real work is covered by a confidentiality agreement. Removing the client's name from a contract doesn't solve this if the subject matter — a specific merger, a named product, a dispute with identifiable parties — still points back to who it was written for. Anonymising a document properly usually means changing more than the header, and by the time enough detail is altered to be safe, the sample may no longer represent the actual work faithfully.

The more defensible approach for most translators is a constructed sample: a short passage written or selected specifically to demonstrate the skill — handling a technical term correctly, preserving tone in a literary excerpt, matching a legal register — without being drawn from any real client engagement. Label it as a sample rather than implying it's client work, and pair it with a testimonial or a case description that talks about the kind of project rather than the specific one, if a past client is willing to give you that much without naming themselves.

None of this is unique to translators, but it lands harder here than in most fields, because the entire product is text, and text is exactly what confidentiality agreements are written to protect. The profession-wide patterns behind this piece — what belongs above the fold, how specialism proof differs by field — are covered in personal websites by profession, and the same audience split shows up in a different form for consultants building a personal site, where credential-versus-track-record plays out over a career rather than a single job.

For translators who arrived from another career, the pair-and-specialism framing above still applies, but the credibility problem is different: a former lawyer now translating legal documents needs to state the career change plainly rather than let a buyer wonder why a legal background appears in a translator's bio. That framing problem is covered in personal websites for career changers.