Add a language
Map your approved translations to the right pages, menus, forms and templates. Agree publishing steps and a clear fallback for missing translations.
MULTILINGUAL WORDPRESS · UK & EUROPE
Multilingual WordPress
development.
One website. More people reached.
Give customers the right language version and your team a practical way to manage it. Add a language, repair an existing setup or plan a migration using content supplied or approved by your team.
Based in Istanbul. UK working-day overlap. Suitable projects worldwide.
A CONNECTED CUSTOMER JOURNEY
01 / YOUR APPROVED CONTENTPages, products & navigation
LANGUAGE AService pageContent · URL · metadata
LANGUAGE BEquivalent pageContent · URL · metadata
↔ Language switching keeps the page context
START WITH THE CHANGE YOU NEED
Add a language.
Fix the experience.
A useful language version connects the pages, navigation and enquiry or buying journey. The work can start with a focused set of pages.
Fix an existing setup
Investigate broken switching, missing content, mixed-language screens or inconsistent SEO settings in your current WordPress installation.
Move with a URL plan
Review the current language relationships and dependencies, then test a scoped plugin or site migration on staging before release.
Connect the store journey
Check product details, attributes, cart, checkout and customer emails in the agreed languages. Confirm pricing and currency requirements separately.
CONTENT AND IMPLEMENTATION
Your language team.
A workable publishing system.
You supply or approve the translations. I build the technical setup and work with your team on how content moves from draft to release.
- 01
Review the current site
Confirm languages, priority pages, editors, plugins and the problem to solve. Identify missing content and access needs.
- 02
Agree the map and scope
Define equivalent pages, URL changes, publishing responsibilities, integrations and the first release.
- 03
Build and review on staging
Implement the agreed workflow and test with approved content. Your language reviewers check wording and context.
- 04
Launch and hand over
Check the live routes and deliver setup notes, dependency details and editor guidance. Agree who handles future changes.
CHECKS THAT SUPPORT THE CUSTOMER JOURNEY
From the search result
to the right page.
Language and search signals
Review indexable URLs, canonical signals, metadata and sitemaps. Map equivalent pages with valid hreflang and reciprocal references.
Navigation and conversion
Test language switching, menus, internal links, forms and agreed store screens. Make missing-language fallbacks understandable.
Layout and ongoing use
Check long labels, approved fonts, RTL where needed and mobile templates. Review caching and performance across representative languages.
SCOPE & PRICING
Start with a review.
Get a defined GBP proposal.
The estimate follows your current setup, language count, templates, content readiness and integrations. A language addition and a complete migration need different scopes.
Share your project brief ↗What the proposal covers
Deliverables, any paid investigation, licences, milestones, feedback rounds, launch checks and initial support.
What to send
Your URL, current language plugin, target languages, a sample of the problem, content status, budget range and deadline.
What your team provides
Approved content and a language reviewer. Translation writing, market research and continuing site care are separate responsibilities to agree.
PUBLIC PRODUCT WORK
Explore Simple Multilang.
A WordPress language-management product built here. Review the product and documentation as one example of the work.
The choice for your project follows its editing workflow and dependencies. Existing WPML or Polylang installations can be reviewed before considering a different approach.
Explore Simple Multilang ↗BEFORE YOU START
Practical questions.
Do you provide the translations?
Your team or translation agency supplies and approves the content. I handle the WordPress implementation, content mapping and technical checks. We agree who reviews language quality, terminology and market-specific wording before publishing. Translation writing is not included in this service.
Can you fix our existing WPML or Polylang site?
Yes. Share the URL, current plugin and an example of the problem. I review page relationships, language switching, URLs, cache behaviour and the publishing workflow before recommending a repair or migration. A rebuild is only proposed when the existing setup cannot meet the agreed needs.
Which multilingual plugin should we use?
The choice follows your content, editors, theme, integrations and support requirements. I review WPML, Polylang or a multisite approach against those needs. A custom implementation needs a clear reason and an agreed maintenance plan. Licence and translation-service costs are identified in the proposal.
Can we add one language first?
Yes. Start with the pages needed for a useful customer journey: entry pages, key services or products, navigation and contact or checkout. We agree what happens when a page has no equivalent translation. Further languages can be planned once the first workflow is working.
Will our existing URLs and rankings be preserved?
The plan records current URLs and identifies which can stay. Where a URL must change, relevant redirects, internal links, canonicals and language references are reviewed. Search performance can change after a migration, so launch includes agreed checks and a monitoring plan.
What does hreflang do?
Hreflang helps Google understand equivalent pages for different languages or regions. The implementation checks language codes, page relationships and reciprocal references. It does not guarantee a ranking or replace useful local content, crawlable pages and consistent canonical signals.
Can you support a multilingual WooCommerce store?
Yes, after reviewing the actual extensions and selling workflow. The scope can include translated product pages, attributes, cart and checkout labels, emails and account screens. Language, currency, pricing, tax and payment behaviour are separate requirements to confirm.
Do you support right-to-left layouts?
RTL layout work can be scoped where needed. We check text direction, mixed-language content, navigation, forms, icon placement and the agreed mobile templates with approved content. Language review remains with your team or linguist.
How much does the work cost and how long does it take?
You receive a scoped GBP proposal after the initial review. The number of languages, pages and templates, content readiness, current plugin setup and integrations affect cost and timing. The proposal defines any paid investigation, licences, milestones, feedback rounds and support responsibilities.
How do we keep translations up to date after launch?
We agree who updates the source content, who receives changes and who approves each language version. Handover includes the publishing steps, plugin dependencies and technical checks. Ongoing site care or SEO work can be scoped separately.
YOUR NEXT STEP
Show me where the
language journey breaks.
Share your site and the change you need. I will review the brief and outline a suitable next step.