Domains and Routing
A domain name is a unique address that serves as an identifier for a specific website on the internet. It is used to locate and access websites, and typically consists of a name (such as google) and a domain extension (such as .com) separated by a dot.
When setting up new localized sites with Glopal we will automatically create a subdomain on a shared glopalstore.com domain, giving you the ability to access your localized sites before selecting a routing strategy.
Your options
Custom Domains
Combination of top-level domain names and subdomains, each having one localized site.
Low Complexity
DNS - Using CNAME records
Custom Paths enterprise only Multiple localized sites on a single domain, under different path prefixes (sub-folders).
High Complexity
To have localized sites appearing on the existing domain next to the existing content, additional configuration with CDN or hosting provider is required to implement “traffic split” delegating only specific paths to Glopal.
If source site has no paths (www.example.com): fr.example.com, www.example.de
If source site has paths (www.example.com/us): fr.example.com/fr, www.example.de/de
Localized sites on the existing domain, next to the existing content on www.example.com/us: www.example.com/fr, www.example.com/de
Multiple localized sites on a new domain: www.example.be/fr, www.example.be/nl
Comparing your options
When comparing the use of multiple domain names, subdomains, and paths for localization efforts on your website, consider the following factors:
Speed to market: Think about the speed at which you would like to adopt the Glopal technology. There is an impact on timelines in executing a more complex custom path routing strategy.
Branding and Identity: Multiple domain names allow for completely separate branding and identities for each localized version, while subdomains maintain the main domain branding to some extent, and custom paths keep the main brand identity intact.
SEO and Ranking: Each option can impact SEO differently. Multiple domain names may require separate SEO efforts for each domain, while subdomains and custom paths benefit from the established authority and backlinks of the main domain.
Maintenance and Management: Multiple domain names require separate registrations and management, while subdomains and custom paths allow for centralized maintenance under a single domain.
User Experience: Consider how each option affects user experience. Multiple domain names can create confusion, while subdomains and custom paths provide a more seamless user experience by keeping visitors on the main domain.
Cost: Registering and maintaining multiple domain names can be costlier compared to subdomains, which is a more cost-effective option.
Technical Considerations: Evaluate technical requirements and constraints for each option, such as DNS setup, server configuration, and security reviewing.
Your Glopal Plan: The custom paths solution is reserved for enterprise plans only.
Ultimately, the choice depends on your specific needs, resources, branding strategy, and target audience. Consider the pros and cons outlined above to make an informed decision that aligns with your localization goals.
Custom Domains
Having a single domain name per country allows a company to target specific local audiences, improve search engine visibility, build trust and credibility, comply with local regulations, create localized marketing campaigns, and provide a seamless customer experience.
Using a subdomain instead of top level domains can have advantages such as maintaining brand consistency, centralized management of the domain, ease of implementation, and cost-effectiveness, as it avoids the need to register and maintain multiple domain names.
Subdomains are the cheapest implementation method as it does not require additional domains or a special plan. The major cost in this method is simply the time used to input the DNS updates.
In case your source content has path prefixes (eg. www.example.com/en), localized site on a separate domain will inherit the same structure. For consistency, Glopal can remap your content prefix to match localized content (eg. if using subdomain, /en can be remapped to /de as in de.example.com/de).
In implementing a multi-domain strategy, each domain or subdomain is capable of hosting a single localized site only (tailored to a specific language and currency). However, it is still possible to offer content in various languages via country selector (cookie method). When users visit the site, they will first be directed to the default content. From there, if enabled, they can have the option to switch to another language using the country selector. This choice will be stored, ensuring a personalized experience during subsequent visits.
Who localizes like this?
| Source URL | UK | France | Swiss | |
|---|---|---|---|---|
google.com | google.co.uk | google.fr | google.ch | |
Amazon | amazon.com | amazon.co.uk | amazon.fr | amazon.ch |
prettylittlething | www.prettylittlething.com | - | www.prettylittlething.fr | www.prettylittlething.ch |
Boohoo | www.boohoo.com | - | fr.boohoo.com | ch.boohoo.com |
Setup instructions
Custom Paths
enterprise only Custom paths when localizing a website allows for central management, consistent branding, consolidated SEO efforts, cost-effectiveness, and simplified implementation and maintenance compared to managing separate domain names for each localization.
Using custom paths it is possible to set multiple localized sites (targeting different markets, each with its own language and currency) on the same domain.
Currently this feature is limited to enterprise plans only.
Note:
Custom Paths require the URL structure on the target to remain the same as on the source. We are unable to remove or add additional paths - however we can rename the path to match the target country, language and currency. Read more in the limitations section “Can I remove/add a directory to a URL?”
If you’re setting up a new domain to fully delegate to Glopal where sites will appear under custom paths, we can handle the setup of the splitting of traffic.
To have localized sites appearing on the existing domain next to the existing content, additional configuration with CDN or hosting provider is required to implement “traffic split” delegating only specific paths to Glopal. Having multiple localized sites appearing on the existing domain, next to your existing content, is not compatible with some SaaS products like Shopify where “traffic splitting” can not be configured.
Setup instructions
Who localizes like this?
| Source URL | UK | France | Swiss | |
|---|---|---|---|---|
Nike* | www.nike.com/* | www.nike.com/gb/ | www.nike.com/fr/ | www.nike.com/ch/ |
Mango | shop.mango.com/es | shop.mango.com/gb | shop.mango.com/fr | shop.mango.com/ch-fr |
*Nike uses paths for localized websites, but doesn't include a prefix in the URLs for its primary market. To have localized sites with custom paths with Glopal, we need to define additional source content that aligns with the need to neither add nor remove path components. This extra source content may stay invisible to site visitors, being accessible only to Glopal.
Limitations
Can I remove/add a directory to a URL?
We are unable to remove or add additional directories to the URL structure, however, we are able to replace any directory name with other terms.
In case your source content has path prefixes (eg. www.example.com/en), localized site on a separate domain will inherit the same structure. For consistency, Glopal can remap your content prefix to match localized content (eg. if using subdomain, /en can be remapped to /de as in de.example.com/de).
| Source URL | UK | France | |
|---|---|---|---|
One directory | www.example.com/us/ | uk.example.com/loremipsum/ | www.example.fr/fr/ |
Two directory | www.example.com/us/shop/ | www.example.co.uk/en/store/ | www.example.fr/fr/boutique/ |
Last updated