Separate indexable pages
Each language needs its own URL that search engines can crawl and index. A widget that swaps text on the fly produces one indexable page, so you get no search visibility in the second language at all.
Delhi NCR
Multilingual websites in Delhi done properly, not with a widget.
A translate button is not a multilingual website. It produces nothing indexable, reads as machine output, and earns you no search visibility in the second language.
Overview
What multilingual actually requires
A genuinely multilingual site needs separate indexable pages per language, hreflang tags so search engines serve the right version, a switcher that keeps you on the same page, and copy written in each language rather than machine-translated. A translate widget delivers none of these.
hreflang, configured correctly
Tags telling search engines which version serves which audience, with correct language and region codes and reciprocal references. Misconfigured hreflang is worse than none because it sends conflicting signals.
Written translation, not machine output
Machine-translated pages read as machine-translated to native speakers, and they trigger the quality concerns Google's guidance describes. Professional translation, or someone in-house who writes well in the language.
Keyword research per language
Hindi search terms are frequently not direct translations of the English ones. Translating your English keywords produces pages targeting phrases nobody searches, which is a common and expensive assumption.
A switcher that keeps your place
Switching language should keep you on the same page, not dump you on a homepage. This sounds minor and it is one of the most common complaints from users of bilingual sites.
Priced honestly
A genuinely bilingual build adds real work: duplicate structure, translation, testing in both languages. We price it openly rather than quoting a monolingual number and revising later.
What to avoid
Widget or proper build
| Translate widget | Proper multilingual | |
|---|---|---|
| Indexable pages | One | One per language |
| Search visibility in language two | None | Yes |
| Translation quality | Machine | Written |
| hreflang | Not possible | Configured |
| Cost | Almost nothing | Real work, priced |
| Suits | Convenience for existing visitors | Actually reaching a new audience |
A widget is fine if the goal is convenience for people already on your site. It does nothing if the goal is being found by people searching in another language.
Detail
What to ask before you hire
| The question | A good answer | Walk away if |
|---|---|---|
| Who owns the site and accounts? | You do, in your own name | Accounts in the agency's name |
| How many revision rounds are included? | A number, and what a round means | As many as you need |
| What does month two cost? | A number, before you sign | We can discuss that later |
| What happens if we leave in month three? | You keep everything, no exit fee | It gets complicated |
The revision question is where scope disputes start. Settle it before you sign.
FAQ
Common questions
Is a translate plugin good enough?
Only for convenience. It does not create separately indexable pages, so you get no search visibility in the second language, and machine output reads as machine output to native speakers. If the goal is reaching a new audience, it does not work.
What is hreflang and do we need it?
Tags telling search engines which language version serves which audience. You need them for any genuinely multilingual site, and misconfigured hreflang is worse than none because it sends conflicting signals.
Will translating our site help us rank in Hindi?
Only with separate indexable pages, correct hreflang and genuine keyword research in Hindi. Hindi search terms are often not direct translations, so translating your English keywords targets phrases nobody actually searches.
How much does a multilingual site cost?
A genuine second language typically adds 30 to 40 percent, covering written translation, duplicate page structure, hreflang and testing in both languages. We price it openly rather than burying it.
Should we translate every page?
Not necessarily. Translate the pages that matter to the second-language audience and leave the rest in one language. Partial is fine as long as hreflang correctly describes what exists.
Can we use in-house translation?
Often better and cheaper, if the person genuinely writes well in the language rather than just speaking it. Written translation is a different skill from fluency, and readers can tell.
Next step
Search visibility in language two?
Tell us what the site has to do and we will tell you what a first-time visitor cannot find. If it is not worth rebuilding, that is what you will hear.