--- title: "Multilingual Website Architecture 2026: Subfolders vs Subdomains vs ccTLDs" date: 2026-10-01 author: "Tobias Rast" featured_image: "https://static.pegotec.net/uploads/2026/09/multilingual-website-architecture-2026.webp" categories: - name: "Pegotec News" url: "/category/news.md" --- # Multilingual Website Architecture 2026: Subfolders vs Subdomains vs ccTLDs Most guides frame multilingual website architecture as a search-engine question. Subfolder, subdomain or country domain — pick one, optimize, move on. That framing is wrong in one specific and expensive way. Across Southeast Asia the deciding factor is often **who is legally allowed to register the domain at all**. Consequently, the decision belongs to your corporate structure before it belongs to your SEO plan. ## Multilingual website architecture: four options, no Google preference Google’s own guidance lists four locale URL structures. Those are a country-specific domain, a subdomain on a generic domain, a subdirectory on a generic domain, and URL parameters. Notably, Google marks the parameter approach as not recommended. For the other three, Google states pros and cons rather than a winner. Furthermore, its listed con for country domains is the one this article is about: “Strict ccTLD requirements (sometimes)”. Google even adds the warning directly. Some countries restrict who can use their ccTLDs, so do your research. Almost nobody does that research. Therefore teams choose a country domain on SEO grounds, then discover the eligibility rule during procurement. ## The rule that actually decides it: eligibility sits one level down Here is the finding that reframes the whole decision. In several ASEAN countries the *short* domain is open to anyone in the world, while the *commercial* second-level domain requires a local entity. The restriction is not on the country code. It sits one level down, exactly where teams stop reading. CountryShort formCommercial formMalaysia`.my` — open worldwide`.com.my` — Malaysian-registered entityIndonesia`.id` — open, foreigners included`.co.id` — business identity number (NIB)Singapore`.sg` — open, local contact needed`.com.sg` — ACRA registration or local agentPhilippines`.ph` — open`.com.ph` — **also open**Thailand`.th` — local presence reserved across the namespaceCambodia`.com.kh` — Cambodian legal entity onlyThe Philippines row matters most, because it contradicts what most advisory pages say. dotPH imposes no nationality, residency, local-entity or local-address requirement on `.ph`, `.com.ph`, `.net.ph` or `.org.ph`. Restrictions apply only to `.gov.ph`, `.edu.ph` and `.mil.ph`. Accordingly, treat “you need a local company for .ph” as a myth. ## Singapore: an open domain with a conditional contact Singapore deserves its own note because the rule is procedural rather than absolute. SGNIC’s Rules of Registration open `.sg` to all persons. However, a foreign applicant must appoint a local administrative contact. For `.com.sg` the test is registration with ACRA, Enterprise Singapore or a Singapore professional body. Alternatively, a foreign corporation may duly authorise a local agent. Two clauses deserve attention from anyone planning a launch. A thirty-day clock applies to the “in the process of registering” route. Moreover, SGNIC reserves the right to demand proof of eligibility after a domain is already live, with revocation as the stated consequence. Consequently, an eligibility shortcut is a live operational risk, not a one-time form. ## Thailand and Cambodia are the genuine blockers Thailand applies a blanket local-presence reservation across its namespace. One detail is worth planning around. A foreign trademark owner may register a `.in.th` domain without a Thai branch, but the registration is **held inactive** until a local branch or representative exists. In other words, you can own it and not use it. Cambodia goes furthest. Sub-Decree No. 287 ANKr.BK, dated 31 December 2021, allocates `.com.kh`, `.org.kh`, `.edu.kh` and `.net.kh` exclusively to legal persons established or registered in Cambodia. Additionally, a joint ministerial notification pushed further still, effectively requiring locally registered companies to use the national domain. We could not verify that notification’s exact number from a primary source, so treat the direction as established and the citation as unconfirmed. Either way, Cambodia is the one ASEAN market where the domain choice may not be yours. ## Vietnam changed its rules this year Vietnam is open to foreign registrants, but the filing channel depends on your address. Applicants with a Vietnamese address must file through a domestic registrar, while those with a foreign address use a different route. More importantly, check your source’s date. Circular 48/2025/TT-BKHCN now governs `.vn`, superseding the 2015 circular, and the responsible ministry changed with it. Guidance written before 2026 therefore cites a repealed instrument. This is a recurring pattern in the region, and it is the single most common way domain guidance goes quietly stale. ## A subdirectory does not geotarget anything Here is a widespread misconception worth killing. Google states plainly that language-specific subdomains and subdirectories are *not* used to determine a page’s target audience. You must signal that explicitly instead. The tool teams reach for no longer exists. Search Console’s International Targeting report was removed in August 2022, and Google stated the country-targeting setting had little value. Consequently, for a generic domain there is now no country-targeting switch at all. Hosting location will not rescue you either. Google describes server location as a possible signal but explicitly not a definitive one, and it lists no ranking benefit for in-country hosting. ## The hreflang rules that break implementations Four rules account for most broken hreflang setups. First, annotations require **return links**. Google ignores a claim unless both pages point at each other, which stops third parties declaring themselves your alternate. Usefully, an incomplete set does not void the whole cluster. Second, every set needs a **self-referencing entry**, in all three implementation methods. Third, the three methods — HTML elements, HTTP headers and XML sitemap — are equivalent, and Google states there is no benefit to implementing more than one. Pick one and keep it consistent. Fourth, hreflang does not tell Google what language a page is in. Google determines language from the visible content instead, and it ignores locational meta tags such as `geo.position`. Therefore a correct annotation on a badly translated page fixes nothing. ## One ASEAN gotcha: Filipino has no valid code This one catches teams building for the Philippines. Google accepts only two-letter ISO 639-1 language codes in hreflang. However, the IANA registry records Filipino as the three-letter subtag `fil`, and only Tagalog holds a two-letter code. By Google’s stated specification, then, Filipino cannot be expressed in an hreflang annotation. Teams either use `tl` for Tagalog and accept the imprecision, or serve Philippine audiences in English and target by region instead. Either way, decide deliberately rather than discovering it in a validator. ## Certificates are becoming an automation problem The infrastructure difference between these architectures is growing, and the direction is one-way. The CA/Browser Forum now caps publicly trusted certificate validity at 200 days. That drops to 100 days in March 2027 and 47 days in March 2029. Separate country domains mean separate certificates, and manual renewal stops being viable well before 2029. Subdomains bring their own trap, because a wildcard matches exactly one label. So `*.example.com` covers `sg.example.com` but not `shop.sg.example.com`, nor the bare domain. Rate limits follow the same shape. Let’s Encrypt counts certificates per registered domain using the Public Suffix List, so every subdomain shares one quota. Meanwhile separate country domains each get their own. Accordingly, the architecture you choose sets your renewal automation burden for years. ## The decision sequence 1. **Check eligibility before anything else.** Read the registry’s own policy, not a reseller’s page. Resellers overstate requirements because they sell local-agent services. 2. **Ask whether you need country targeting or language targeting.** These are different problems, and most teams only need the second. 3. **Default to subdirectories.** They consolidate authority, share one certificate and one deployment, and carry no eligibility risk. 4. **Choose country domains for genuine legal or market separation** — a local entity, local invoicing, a regulator expecting a national domain, or Cambodia’s mandate. 5. **Budget the certificate automation** before the 2027 and 2029 validity cuts make it urgent. 6. **Decide who maintains each locale.** The common failure is not architecture. It is one language silently falling a year behind. ## How Pegotec helps We build multilingual platforms across Southeast Asia, including bilingual English and Khmer public-sector portals in Cambodia and a five-language commercial shop in Europe. Consequently, we check domain eligibility during scoping rather than during launch week. If you are planning a market entry and the domain question is still open, [talk to us](https://pegotec.net/contact-us/). Our [multi-language website development](https://pegotec.net/service/websites-development-service/multi-language-websites-development/) work starts with exactly this decision. ## Read next - [Where Your Data Can Legally Live](https://pegotec.net/data-residency-southeast-asia-2026-decision-framework/) — the same jurisdiction-first thinking, applied to hosting. - [CL Cosmetic](https://pegotec.net/portfolio/cl-cosmetic-multilingual-cosmetics-shop/) — a five-language shop built on one domain. - [Schema.org and JSON-LD](https://pegotec.net/why-schema-org-and-json-help-you-win-with-google-seo-and-llms/) — structured data across locales. ## FAQ