A multilingual site for Indian languages works for users, search engines and AI crawlers when each language has its own URLs, every page declares its language with the lang attribute and hreflang, fonts load only the scripts a page needs, text is stored in UTF-8, numbers and dates follow each language’s conventions, and search handles both native and Roman script. This guide covers the technical setup for Hindi, Marathi and other Indian languages in Next.js and Laravel, including right-to-left support for Urdu.
URLs and language declaration
- Use language subfolders, such as /hi/ and /mr/, on one domain.
- Set the lang attribute on the html element: hi, mr, ta, ur and so on.
- Link equivalent pages with hreflang, including x-default, and never auto-redirect by browser language. See implementing hreflang in Next.js.
- Provide a visible language switcher with real links to the equivalent page, not just the home page.
Fonts for Indian scripts
Load fonts per script with unicode-range, so a Hindi page downloads the Devanagari font and an English page does not:
@font-face {
font-family: "Noto Sans Devanagari";
src: url("/fonts/noto-sans-devanagari.woff2") format("woff2");
font-display: swap;
unicode-range: U+0900-097F, U+1CD0-1CFF, U+A8E0-A8FF;
}
body { font-family: "Your Latin Font", "Noto Sans Devanagari", system-ui, sans-serif; }
Self-host the fonts, load only the weights you use, and test that conjuncts and matras render correctly on budget Android phones.
Right-to-left languages
For Urdu, set dir=”rtl” on the html element for those pages, and use CSS logical properties (margin-inline-start instead of margin-left) so layouts mirror correctly.
Numbers, dates and currency
new Intl.NumberFormat("hi-IN", { style: "currency", currency: "INR" }).format(150000);
// "₹1,50,000.00" with Indian digit grouping
new Intl.DateTimeFormat("mr-IN", { dateStyle: "long" }).format(new Date());
Format on the server so the HTML crawlers receive is already correct.
Translations in the application
Next.js
Use a [lang] route segment, load translation files per locale in server components, and generate metadata and alternates per language. Libraries such as next-intl handle messages and formatting.
Laravel
// lang/hi.json { "Book an audit": "ऑडिट बुक करें" } {{-- in Blade --}} <a href="{{ route('contact', ['locale' => app()->getLocale()]) }}">{{ __('Book an audit') }}</a>
Set the locale from the URL prefix in middleware, not from the browser’s language alone.
Search on multilingual sites
- Normalise Unicode text (NFC) before indexing and searching.
- Support Roman-script queries for Indian-language content, for example with transliteration or embeddings that handle both scripts. See semantic site search.
Sitemaps and structured data
- Include all language versions in the sitemap with alternates.
- Output structured data in each page’s language, with the same organisation details.
- Set the inLanguage property on articles.
Test
- View source: correct lang, hreflang and canonical on each version.
- Check fonts render on real devices and that only needed fonts load.
- Run our AI crawler access checker on each language version.
Frequently asked questions
Native script or English slugs in URLs?
Both work. English or transliterated slugs are easier to share and type; native script URLs are more readable to native speakers. Be consistent.
Should we use a translation plugin that translates on the fly?
Client-side translation widgets do not create indexable pages. Use server-rendered translated pages with their own URLs.
How do we handle content that exists only in English?
Do not create empty or machine-filled language pages. Link to the English page, and add hreflang only for real equivalents.
Sources
- Google Search Central, “Managing multi-regional and multilingual sites”
- MDN Web Docs, Intl API, unicode-range and CSS logical properties
- Laravel documentation, localization