CoreWeb
12+ languages
Indian-language search
Hreflang
bidirectional or broken
Localise
do not translate

Multilingual & Vernacular SEO

Two related problems. Serving several countries without your markets competing against each other, and reaching the large and growing share of Indian users who search in a language other than English.

Search Engine Optimization

Being found on Google, in AI answers, on maps and in marketplaces.

International
Where multi-market sites break.

The hreflang problem

Hreflang tells Google that several URLs are the same content for different audiences. Done correctly, the right market surfaces for the right user. Done incorrectly — and it very often is — your markets compete, the wrong currency and language appear, and conversion drops for reasons nobody traces back to a tag.

The frequent failures: annotations that are not reciprocal, so Google ignores them entirely. Missing self-references. Region codes used where language codes belong. Hreflang pointing at URLs that redirect. Clusters broken because one market launched late and nobody revisited the others.

Underneath sits a structural decision — subdirectories, subdomains or country domains — that is expensive to reverse. Getting it right at the outset is worth considerably more than fixing tags later.

India
A different problem from translation.

Vernacular search in India

Indian-language search has grown substantially and behaves unlike English search. Queries are longer and more conversational. Voice input is common, which changes phrasing again. And a large share of users type Indian languages in Latin script — transliteration — which your keyword research will miss entirely if you only look at native script.

Machine translation performs badly here. Translated pages read as translated, use terms nobody searches, and rank poorly. What works is establishing what people in that language actually search for, then producing content natively rather than converting English pages.

8 areas
One body of work, not a menu.

All services

What’s included

International architecture

Subdirectory, subdomain or ccTLD decisions with the trade-offs made explicit, since this choice is costly to reverse.

Hreflang implementation and repair

Building or fixing bidirectional clusters, with automated monitoring so a late market launch does not silently break the set.

Market cannibalisation

Diagnosing and resolving cases where your own regional sites compete, most commonly across English-language markets.

Localisation over translation

Keyword research conducted natively per language, so pages target real queries rather than translated English ones.

Transliteration research

Capturing Latin-script variants of Indian-language queries, which conventional keyword tools handle poorly.

Indian-language content production

Native content in major Indian languages, written rather than machine-translated.

Technical language signals

Correct lang attributes, character encoding, script rendering and font loading — unglamorous and frequently wrong.

Geotargeting configuration

Search Console targeting, server location and CDN behaviour, aligned so signals do not contradict each other.

Common questions
Asked on most first calls.

Questions

Subdirectories, subdomains or country domains?

Subdirectories usually, because they inherit domain authority and are cheapest to maintain. Country domains suit strong local brand requirements or legal constraints, at the cost of building authority separately for each. We make the trade-off explicit rather than asserting a rule.

Can we just use machine translation?

For a first pass on low-value pages, sometimes. For commercial pages, no. Translated content targets translated keywords, which are frequently not what people search. It also reads as translated, which affects trust and conversion.

Which Indian languages are worth targeting?

It depends entirely on your customer base and category. Hindi has the largest volume, but Tamil, Telugu, Marathi, Bengali and Kannada dominate in their regions. We size demand per language against your markets before recommending.

How do we know hreflang is broken?

Common signs are the wrong market ranking for a query, or Search Console reporting no return tags. It is one of the first things we check on any multi-market site, and it is broken more often than not.

Do we need separate content per market, or can English serve several?

English often serves several markets, which is where cannibalisation appears. If UK, India, Singapore and Australia all have English pages, hreflang has to be right or they compete. Sometimes consolidation is the better answer.

Next step
We look at your site before the call.

Start with a free audit

An automated crawl plus a 30-minute walkthrough of what we can see from outside your site. If what you need isn’t something we do well, we’ll tell you.