Technical setup for the partner program
This section explains how the technical setup of Clonable works and what to consider when implementing Clonable for your clients. It covers topics such as DNS configuration, website performance, SEO elements and compatibility with different platforms. The answers below help you understand how Clonable integrates with existing websites and how to configure Clones correctly. If you encounter technical issues that cannot be resolved through configuration, the Clonable team can provide additional support.
Do you need to modify code on the source website?
Usually not. In most cases Clonable is implemented through DNS configuration, a plugin or a small server adjustment. This means the original website does not require major code changes. The exact setup depends on the platform and project.
How does the DNS configuration work?
Clonable is typically connected through a DNS configuration. You create a CNAME record that points to the Clonable servers. Clonable then serves the translated content of the website through this connection. This allows the Clone to operate alongside the original website.
Does Clonable support subfolders such as /en/?
Yes. In many cases Clonable can serve translated versions of the website within subfolders such as /en/. This is achieved through a reverse proxy configuration. For some custom systems additional configuration may be required.
What happens to dynamic content such as shopping carts?
In most cases dynamic elements such as shopping carts and checkout processes continue to function normally. Occasionally certain scripts may need to be adjusted or excluded. Creating a demo Clone usually reveals quickly if additional configuration is required.
How does Clonable handle forms on the website?
Forms are generally copied as part of the Clone. Form labels and field names can be adjusted to match the translated language. If necessary, form behaviour can also be modified through the editor.
Does Clonable affect website speed?
The impact on website speed is usually minimal. Clonable uses caching and edge technology to deliver content efficiently. In most cases visitors will not notice a difference in loading performance.
Are internal links automatically adjusted?
Yes. Clonable automatically rewrites internal links so visitors remain within the correct language version of the website. This ensures consistent navigation within the Clone.
Can external scripts such as Google Analytics still be used?
Yes. External scripts such as Google Analytics, Google Tag Manager and other tracking tools usually work without issues. If necessary, scripts can be adjusted so that performance can be measured per language or region.
How does Clonable handle hreflang tags?
Clonable automatically generates hreflang tags for both the original website and the Clone. These tags are added to the page source to indicate the correct language and regional versions. This helps search engines understand the relationship between the different language versions of the website.
Are meta titles and meta descriptions translated?
Yes. Clonable translates SEO elements such as meta titles and meta descriptions that appear in the <head> section of the page. These can also be edited or optimised when needed.
Does Clonable generate an XML sitemap for the Clone?
Yes. Clonable automatically generates an XML sitemap for the translated version of the website. This helps search engines discover and index the pages of the Clone correctly.
Is there a risk of duplicate content?
No. Because the content is translated and hreflang tags are used, search engines recognise the pages as language-specific versions. This allows each version of the website to be indexed correctly for its target region.
Updated on: 16/03/2026
Thank you!