A switch, not a page address
The language changes on screen, and the address does not.
What we do about it
A stable address per language, with the text in the page itself.

A real page for each language, so Google can find it. Not a button that swaps the words after load.
Request this workIs this you?
These are common reasons a business looks at this work.
The language changes on screen, and the address does not.
What we do about it
A stable address per language, with the text in the page itself.
The grammar is fine, and the search is wrong.
What we do about it
Research in that language, then a person edits what you sell. We do not publish raw machine text.
The new page points its main address back at English.
What we do about it
Each language points at itself. Language tags connect the versions.
The homepage is translated, and the page that sells is not.
What we do about it
Sales pages, the menu, and the form first. The old articles later.
They land in one language, and the form is in another.
What we do about it
The path after the visit stays in that language.
The work
A language is a set of searches, not only a translation. The page has to exist, answer the search, and give a next step in the same language.
The kind of work this usually covers.
A path per language that returns the translated page, not a script that swaps the words after the load.
What people type in that language. It is often not the English keyword translated.
Service, product, and campaign pages rewritten. A person who can read the language checks the claims.
Menus, buttons, errors, and the thank-you page. A translated top section with an English form loses the lead.
Each version points at the others, both ways, including a default you chose on purpose.
The French page is the main address of the French page.
Links in the text stay inside that language. No accidental jumps to English.
Language addresses sent to Google as their own set, so Google is not guessing.
A whole blog run through a translator on day one. That fights the pages that sell, and it reads like nobody wrote it.
Approach
Start with the pages that sell. Give them an address, a real search, and a human edit. Add more only after those versions can rank.
Timing and the final list of what is included go in the proposal, before any work starts.
Tell us the jobExamples
A translated blog and an English checkout is how multi-language sites fail.
Service, product, and campaign pages. These should rank and bring in the sale or the booking.
Menus, forms, errors, and the thank-you page.
Names, units, and examples a reader in that language believes.
After the sales pages exist, so they do not outrank what you sell by accident.
A good fit
The same kind of work can help a shop, a clinic, a factory, a school, or an office. Fit depends on the business.
Where it shows up
Business types
The team
These are the roles on the project. One person may cover more than one.
Why us
If Google cannot open it, it cannot rank.
We look up how people search, then we write.
A machine may draft. A machine may not publish.
The form speaks the same language as the search result.
Before you call
Each language becomes a set of real pages Google can list, aimed at the searches in that language, with tags that connect the versions. SEO means helping those pages show up on Google.
Only if it creates stable page addresses and puts the text in the page itself. A tool that swaps the words after the page loads is not a search setup.
We start with the pages that rank and sell, plus the menu and the form. Translating everything on day one usually means nothing is good.
A person who can read it, against what you sell and the facts. Unchecked machine text does not go live.
They should not, if the main addresses and language tags are right. The usual failure is pointing the new pages back at English.
This is language. Country search is the market, including money and which country page should win. A site often needs both.