The honest answer for most Chennai businesses is no, not yet. That is not a comment on the language. It is that a second version doubles the content you maintain, and a neglected Tamil section that goes stale does more harm than never having built it.
There are clear cases where it is obviously right, though, and they are worth recognising.
When it is worth it
- Your customers genuinely search in Tamil. Look in Search Console under Queries for Tamil-script terms already reaching you. If they are there, demand is proven rather than assumed.
- The subject matters too much to get wrong. Healthcare, legal and financial services, where a patient or client understanding the detail in their first language is not a nicety.
- You serve areas outside the metro. Tamil-language search behaviour is markedly stronger outside central Chennai.
- Your competitors have done it and rank for those terms. That is demand somebody else has already validated for you.
When it is not
- B2B and professional services, where the working language is overwhelmingly English.
- You cannot commit to maintaining it. A Tamil page describing a service you stopped offering is a liability.
- You were planning to machine-translate it. More on that below.
- Your English site is not finished. Fix the primary version before duplicating its problems.
Do not machine-translate it
Automatically translated pages published without human review are explicitly the kind of thing Google’s spam policies name. Beyond the policy risk, machine Tamil reads as machine Tamil to a Tamil speaker, and the credibility you were trying to build is what you lose.
Machine translation as a first draft that a fluent person then rewrites is fine. That is a workflow. Publishing the raw output is not.
Implementing it so the two do not compete
- 1Give each language its own URL. A subdirectory such as /ta/ is the simplest and works well. Do not swap the language with a cookie on the same URL, because Google will only ever index one version.
- 2Add hreflang tags. Every page points at itself and at its counterpart, using ta-IN and en-IN, and the reference must be reciprocal or it is ignored.
- 3Add an x-default pointing at the version to serve when no language matches.
- 4Set the html lang attribute correctly on each version. It is one attribute and it is routinely wrong.
- 5Translate the metadata too. A Tamil page with an English title tag will not rank for Tamil queries.
- 6Include both versions in the sitemap.
- 7Let people switch manually, and remember the choice. Never auto-redirect on IP, which strands crawlers and annoys bilingual users.
What it costs
Roughly half again on top of the original build, not double. The structure, design and code are reused; the content, translation and testing are not. The ongoing cost is the one people underestimate: every future edit is now two edits, forever.
A maintained Tamil site beats an unmaintained one, and no Tamil site beats an abandoned one.
A cheaper middle path
Translate the pages that carry the decision, not the whole site. The service page for your main offering, the contact details and the directions. Three well-made Tamil pages that stay accurate are worth more than forty that rot.
