Which languages to add first

Your site is in one language. FluentC translates into 128+ languages and charges per language, so the question isn't whether you can add one. It's which languages earn their place, and in what order.

You don't need a market study. The answer is usually sitting in tools you already have.

Start with the searches you're already getting

Open Google Search Console and look at the countries report. Countries that send impressions and clicks to a site that isn't written in their language are telling you something: people there are searching, finding you and landing on a page they may not read comfortably.

Then look at the queries. Scroll past the ones in your language. Queries that arrive in Spanish, German or Portuguese are people who typed their own language and got your page anyway. That's the clearest signal you'll find: a search in a language you don't serve, already matching your site. A page in that language would match it better. How assistants and search engines find a site in other languages.

Then what your analytics says

Two reports are worth an hour. The language report is the visitor's browser language, which is the language they read in, not where they happen to be. The location report is where they are. Put them side by side. A country where the browser language and the local language agree is a stronger case than one where they don't.

Look at behaviour too. If visitors from one language leave sooner, or reach a product page and go no further, you may be watching people who would stay if they could read it.

Then where the business already comes from

Search and analytics measure interest. Orders, enquiries and support requests measure people who got through anyway.

• Orders and sign-ups, by shipping or billing country.
• Contact-form messages written in another language.
• Support tickets where someone apologises for their English, or writes in their own.
• Sales calls that needed a colleague to interpret.

A language that already produces business, from a site that works against it, is the one to add first.

Then who can read it

FluentC gives you a machine translation of every page, and you edit the lines that matter in the dashboard. That works better when someone on your side can read the result: a colleague, a reseller, a translator you can call for an hour. A language nobody can check is still worth adding when the data says so. Put it second, behind one you can.

Subdomain or country domain, per market

Each language gets its own address, and you choose the format for each one. A subdomain (es.yoursite.com) is the simpler setup, though it still needs DNS work. A country domain (yoursite.es) gives the strongest local signal and suits larger sites, but it means registering the domain and setting up DNS for it, and it costs the most. A sensible mix is a country domain for the market you're serious about and subdomains for the ones you're testing. The trade-off, laid out.

How to decide

1. List every language that shows up in Search Console queries, analytics and orders or enquiries.
2. Rank the list by where the business already comes from, then by search interest.
3. Move up any language someone on your team can review.
4. Choose subdomain or country domain for each, market by market.
5. Start at the top. Add the rest as the data says so.

After launch

Read the lines that matter in each new language: navigation, product names, prices and the terms around them. What to review first.

Then watch the same reports, with the new address in them. The next language down your list will make its own case the same way, and when it does, add it. The price is flat per site, per language, so adding one is a decision about that language, not a new plan. See pricing.