Baltics · EU, euro, Schengen
SEO audit for websites in Lithuania
Lithuania’s SEO problems are mostly small details: surnames that change with gender, nine accented letters and Polish and Russian minority audiences that are concentrated in particular regions.
The notes below are written for a site aimed at Vilnius, Kaunas, Klaipėda or the Lithuanian diaspora.
Lithuania at a glance
- Languages and hreflang codes
- Lithuanian
lt-LTState language and the default for local sites - Polish
pl-LTMinority language, especially around Vilnius - Russian
ru-LTSpoken by a sizeable minority and by many older users - English
en-LTB2B, startups and tourism
- Lithuanian
- Script
- Latin with nine accented letters: ą, č, ę, ė, į, š, ų, ū and ž.
- Domain
- .lt is the country code.
- Native name
- Lietuva
- Currency
- Euro (EUR), since 2015
- Calling code
+370- Postcode
- ‘LT-’ plus 5 digits
e.g. LT-01100 (Vilnius) - EU, EEA and Schengen
- EU member since 2004, euro area member, and part of Schengen since December 2007.
Market notes for Lithuania
Surnames that change with gender: author pages and Person schema
Lithuanian surnames usually carry gendered endings. A man might be Kazlauskas, his wife Kazlauskienė and an unmarried woman Kazlauskaitė. For SEO this matters wherever you publish bylines: author pages, team profiles and Person markup. Write each person’s name exactly as they use it, keep the spelling identical between the visible byline, the author page and the schema, and link their profiles with sameAs.
Searchers also use the forms that fit the sentence, because Lithuanian is an inflected language. Do not rewrite names into a ‘neutral’ form for the sake of a keyword, since it makes the page look careless to native readers.
Nine accented letters and the ogonek family
Lithuanian uses ą, č, ę, ė, į, š, ų, ū and ž. Four of them (ą, ę, į, ų) carry an ogonek, a small hook that is easy to lose in a broken encoding. Make sure your CMS, database and feeds are UTF-8 end to end, and spot-check titles after any import.
For ASCII slugs, beware of collisions: ę and ė both become ‘e’ under a naive mapping. Either keep UTF-8 slugs, which Google encodes in links, or define one explicit mapping and use it in every language version.
Polish and Russian pages, and why pl-LT is not pl-PL
Polish and Russian are spoken by sizeable minority communities in Lithuania, and Polish is especially associated with the Vilnius region. A pl-LT page says ‘this Polish page is for people in Lithuania’: it should show Lithuanian prices, delivery and contact details. If you also sell into Poland, build a separate pl-PL version with Polish-market content, not a copy of the Lithuanian Polish page.
As with every other language version, each one needs its own URL, native-quality titles and descriptions, and reciprocal hreflang. A thinly translated page for a minority audience can cost more in trust than it earns.
One regional site or three national ones?
If your services are identical across the Baltics, a single English page with a plain en tag is the most efficient. If copy, prices or regulations differ by country, give Lithuania its own lt-LT pages and a .lt domain or an /lt/ folder, and link the Estonian and Latvian versions with hreflang. The .lt domain is a strong local signal, so use it when Lithuanian customers are the priority and avoid it for pages meant for the other two countries.
Copy-ready examples for Lithuania
Both snippets use placeholder data. Replace the domain, name, street, phone number, coordinates and prices with your own before you publish them.
hreflang tags
This set covers 4 versions (lt-LT, pl-LT, ru-LT, en-LT) plus an x-default. Put the same full set in the <head> of every language version, each page listing itself too; Google ignores pairs that do not link back.
<link rel="alternate" hreflang="lt-LT" href="https://example.lt/lt/" />
<link rel="alternate" hreflang="pl-LT" href="https://example.lt/pl/" />
<link rel="alternate" hreflang="ru-LT" href="https://example.lt/ru/" />
<link rel="alternate" hreflang="en-LT" href="https://example.lt/en/" />
<link rel="alternate" hreflang="x-default" href="https://example.lt/en/" />LocalBusiness JSON-LD
The postcode follows the Lithuania format (‘LT-’ plus 5 digits) and the telephone starts with +370. Use the most specific business type that fits, and keep every detail identical to your footer, contact page and map listing.
{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"name": "Example Studio Vilnius",
"url": "https://example.lt/lt/",
"image": "https://example.lt/images/storefront.jpg",
"telephone": "+370 5 000 0000",
"priceRange": "€€",
"address": {
"@type": "PostalAddress",
"streetAddress": "Pavyzdžio g. 1",
"addressLocality": "Vilnius",
"postalCode": "LT-01100",
"addressCountry": "LT"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 54.6872,
"longitude": 25.2797
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "09:00",
"closes": "18:00"
}
]
}What the audit looks at
What the audit checks for Lithuania
UTF-8 and ogonek letters
We check the charset declaration and flag titles where ą, ę, į or ų have turned into question marks or plain vowels.
hreflang across lt-LT, pl-LT, ru-LT and en-LT
The audit verifies reciprocal links, valid ISO codes and that x-default points at a real selector or default page.
Person and Organization schema
We check that author names match between byline and markup, and that required properties are present.
Canonicals on translated pages
Each language version should canonicalise to itself, so the Polish and Russian pages remain eligible to appear in search.
Questions about SEO in Lithuania
How should I write Lithuanian surnames in author markup?
Exactly as the person writes them, including the gendered ending, and identically in the byline, the author page and Person schema.
Do I need a Polish version in Lithuania?
Only if you have customers among the Polish-speaking minority, mostly around Vilnius, and can maintain good Polish copy. Use pl-LT for that, and a separate pl-PL page if you also sell in Poland.
Should a Lithuanian postal code include LT-?
Use the form shown by Lithuania Post and your Google Business Profile, commonly LT-01100, and keep it identical across your site and listings.
Which hreflang code is right for Lithuanian?
lt-LT for Lithuanian aimed at Lithuania, or plain lt for Lithuanian readers anywhere, such as the diaspora.
Is Lithuania in the euro area?
Yes, since 2015. It is also an EU member since 2004 and in Schengen.
Need a hand with Lithuania?
If your Lithuania audit turns up work you would rather hand over, two teams stand behind this tool. Nomor (nomor.tech) is our software development company and Limi Creatives (limicreatives.com) is our marketing company. Send us your report and tell us which market you are working in.
Nomor
Our software development company. Nomor designs and builds the software and websites behind this tool, including the audit engine, the PDF report and the pages you are reading. It is the right place to start for custom development, performance work and technical fixes.
Limi Creatives
Our marketing company. Limi Creatives is a creative agency that runs SEO, paid ads, content, social media and video for brands. It is the right place to start when you want help turning audit findings into traffic and enquiries.