Skip to content
All articles
Web Development9 min read

Nepali language website or app: Unicode, fonts and search

What adding Nepali to a site or app takes: Unicode Devanagari, a font for conjuncts, separate URLs with hreflang, search, and an owner for each language.

EK

EK Ra Sunya team

EK Ra Sunya Inc.

A Nepali language website needs four things that a translated menu doesn't give you. The text has to be stored as Unicode Devanagari, not typed in a legacy font. The site needs a web font that renders Devanagari conjuncts properly. Each language needs its own URL, marked with lang and hreflang. And someone has to own keeping the Nepali and English versions in step after launch.

The first three are setup work. The fourth decides whether your Nepali pages are still accurate a year from now.

Does your business need a Nepali language website at all?

Only if a real part of your audience will read the Nepali version, and you can keep it maintained. A half-translated site, where the menu is in Nepali and the pages underneath are in English, is worse than an honest English-only site. Google's guidance on multilingual sites says that translating only the boilerplate while keeping most of the content in one language gives users a poor experience.

Before you start, list the pages a Nepali-first customer actually needs: services, prices, how to order, contact, terms. Translate those properly and leave the blog in English if you must. Bilingual means every page you offer in Nepali is complete, not that every page exists in both.

What does "Unicode Devanagari" mean, and why does it matter?

Nepali is written in Devanagari, and Unicode gives Devanagari its own range of characters. The Unicode Standard's chapter on South Asian scripts places the main Devanagari block at U+0900 to U+097F and names Nepali among the languages written with it.

Text typed with a non-Unicode legacy font is a different thing. It only looks like Nepali because the font draws Devanagari shapes; the characters stored underneath are not Unicode Devanagari. That causes problems that are easy to miss in a demo:

  • It breaks without the font. Copy the text into an email, a search box or a phone that lacks that font, and the reader sees Latin gibberish.
  • Search can't find it. Someone typing Nepali on a Unicode keyboard is searching for Unicode characters, and legacy-font text doesn't match them.
  • Screen readers and translation tools can't read it. They see the stored characters, not the shapes.

If your existing brochures, notices or price lists were typed in a legacy font, convert them to Unicode before they go anywhere near the website. Check the converted text by eye, especially conjuncts, because a conversion error reads as a spelling mistake. Serve every page as UTF-8, which W3C's guidance on choosing an encoding says is the one to use for web content.

Which Devanagari font should a website use?

Use a web font that covers the Devanagari block and renders conjuncts correctly, and test it with your own text. Unicode doesn't give conjuncts their own characters. The Unicode Standard says rendering software must map combinations of characters to the right conjunct glyphs in the font, and when a font lacks a conjunct, the fallback is a visible virama (the small slanted stroke under a consonant). A font with thin Devanagari support will show those strokes in words where a Nepali reader expects a joined form.

When you choose a Devanagari font for your website, check these:

CheckWhy
Covers U+0900 to U+097FMissing characters fall back to another font, mid-word
Renders the conjuncts in your actual copyBroken conjuncts read as spelling mistakes
Has a weight that pairs with your Latin fontMixed-script lines (prices, brand names) look stitched together otherwise
Loads only the subsets you needFewer font bytes, faster first paint
Licensed for web useFree to download is not the same as licensed to embed

Test with a real paragraph of your own copy, not Devanagari placeholder text, so you see the conjuncts you actually use.

How should the English and Nepali pages be structured for Google?

Give each language its own URL, such as /en/services and /ne/services, and link them to each other. Google recommends different URLs for each language version rather than switching language with cookies or browser settings, and it advises against automatically redirecting visitors by language, because that can stop users and search engines from seeing all versions.

Then add two kinds of markup:

  1. The lang attribute. W3C's internationalization guidance says to always declare the default language on the html element, so a Nepali page starts with <html lang="ne">. ne is the ISO 639-1 code for Nepali. If a Nepali page quotes an English product name or a sentence, wrap it in an element with lang="en". This is also an accessibility requirement: WCAG 2.2 success criterion 3.1.1, Language of Page, is Level A, and the declared language lets screen readers use the right pronunciation. We cover the rest of that list in our website accessibility checklist.
  2. hreflang links. In Google's documentation on localized versions, each language version must list itself as well as every other version, and if two pages don't point to each other, the tags are ignored. Add an x-default entry for the page people should see when neither language matches, often the English version or a language chooser.

Google also says it doesn't use hreflang or the lang attribute to detect a page's language. It reads the content. So a page marked ne that is mostly English is still an English page to Google. The markup only tells Google which pages are alternates of each other.

How do input, search and numerals work in Nepali?

Input. Make sure every form accepts and stores Unicode: names, addresses and messages typed in Devanagari should come back exactly as entered, in the admin panel, the export file and the confirmation email. A database or email template set to an old encoding will turn it into question marks.

Search. If your site or app has its own search, test it with Devanagari queries before launch. Decide early whether a search for an English product name should also find the Nepali page, and whether customers who type Nepali in Latin letters should get results. Unicode's FAQ on Indic scripts also notes that sort order should follow the language, not raw code point order, which matters for any alphabetical list in Nepali.

Numerals. Devanagari has its own digits, at U+0966 to U+096F. W3C's gap analysis for Devanagari says Latin numerals are generally acceptable in Devanagari text, while some sites prefer Devanagari numerals for readers who only read that script. Pick one rule per field and apply it everywhere. Phone numbers, prices and order numbers that customers will type back into a form are safer in the digits your forms accept. The same gap analysis raises script-aware number and date inputs as missing pieces, so test any numeric field a Nepali user fills in. Dates are their own topic; if you need Bikram Sambat, plan it as a separate feature.

Who keeps the two languages in sync?

The risk is simple: someone updates the English price, nobody updates the Nepali page, and the two now disagree. Settle these before launch:

  • One named owner for each language. Not "the marketing team". A person who signs off Nepali copy and knows when it changed.
  • A rule for what happens when English changes. Either the Nepali update ships at the same time, or the Nepali page shows that it is out of date until it does.
  • Content in fields, not pages. In a CMS, keep each language as a field on the same item, so an editor sees both and can't publish one silently. This is one of the questions to ask when comparing platforms, as in our Next.js vs WordPress comparison.
  • Human review of any machine translation. A machine draft is a start. A Nepali speaker who knows your business should read every customer-facing line, especially prices, terms and anything legal.

For a mobile app, the same rules apply to strings in the app. Keep them out of the code in translation files, give a Nepali reviewer a way to see them in context, and test every screen in Nepali, because a Nepali string can be longer or shorter than its English version and break a layout that looked fine.

Frequently asked questions

Can I just add a Google Translate widget instead?

You can, but a widget that translates in the browser doesn't give you separate Nepali URLs that search engines can index, and the translation isn't reviewed. For customer-facing pages with prices or terms, a reviewed translation on its own URL is the safer choice.

Do I need a separate domain for the Nepali version?

No. A language folder on the same domain, such as /ne/, gives each language its own URL, which is what Google asks for, and hreflang links the folders together.

Can old documents typed in a legacy Nepali font go on the site as they are?

Not as text. Convert them to Unicode first, then check the result by eye. Uploading them as images or PDFs in a legacy font leaves them unsearchable and unreadable to screen readers.

Planning a bilingual site or app

Our web development team builds websites and web applications, and our mobile development team builds Flutter and React Native apps. The checks above are the ones to raise with any team you hire. If you're deciding how much of your site to offer in Nepali, tell us what you have now and who will maintain it.

Have a project in mind?

Let us help you build something scalable, fast, and built to last.

Start a conversation