How to translate XML feeds?

Summary

With Clonable, you can translate XML feeds (usually product or shopping feeds) so you can use them in channels like Google shopping. In this guide you’ll learn how to upload a feed, choose which fields get translated (to control costs), how URLs are handled, and how to keep feeds updated manually or automatically.

XML feed translations are billed separately

FAQ

Can Clonable translate XML shopping feeds?

Yes, Clonable can translate XML feeds (often product feeds) for your Clone.

Do URLs in my feed get updated to the clone domain?

Yes, Clonable replaces your original domain with the clone domain automatically and uses existing URL translations.

How long does the first translation take?

It can take hours for large feeds (thousands of products), because feeds have lower priority than web pages.

Can I exclude fields like price from translation?

Yes, you can disable translating (and optionally exclude the field entirely) to reduce costs.

⏱️ **Reading time: **6-8 minutes

What XML feeds are used for
Add and translate an XML feed
Translation time
Exclude fields to reduce cost
URLs in the feed
Update an existing feed
Automatic updating
Where to find the translated feed
Examples and use cases

What XML feeds are used for

XML feeds are often shopping feeds that list products (titles, descriptions, prices, links, images, etc.). Translating them helps your products show up in other languages and regions, for example in google shopping.

XML feed translation is billed separately from normal page translations, so always review the cost estimate before you commit a big feed.

Add and translate an XML feed

You add feeds from the Clonable backend.

Steps:

Open the control panel: <#>
In the left menu, click E-commerce > XML feeds
Upload your XML file
Clonable will show an estimated cost and start translating after you confirm

XML

If you upload a second version of the same feed later, Clonable won’t charge again for segments that have not changed.

Translation time

Feeds are translated with a lower priority than web pages. Combine that with large product catalogs, and the first translation can take a while (hours for thousands of products is normal).

If your feed is huge, start by translating only the fields you actually need (usually title and description).

Exclude fields to reduce cost

Not every field should be translated (price, ids, tracking parameters, and links are common “don’t touch” fields).

In the feed field list you can control two things:

Translate: whether clonable translates that field
Include: whether the field is present in the translated feed at all

Example:

Translate enabled for title and description
Translate disabled for price and links
Include disabled for fields you do not want in the translated output

Changing these settings later is done by re-uploading the feed and adjusting the checkboxes again.

URLs in the feed

Clonable automatically replaces your original domain with the clone domain in the translated feed.

Example (original feed):

<product>
  <title>Example product</title>
  <price>12,50</price>
  <product:url>https://www.clonable.net/products/example-product</product:url>
</product>

Will be translated as:

<product>
  <title>Voorbeeld product</title>
  <price>12,50</price>
  <product:url>https://www.clonable.nl/producten/voorbeeld-product</product:url>
</product>

This also includes the url translations, which ensures that you don't get 301 redirects from the feed. The feed will not create new url translations, but only use existing url translations.

If you use a subfolder clone, Clonable will automatically include the subfolder in the urls of the feed.

Other domains in the feed

Clonable leaves other domains in your feed alone by default. This has the effect that if you use another domain for your product urls, you have to replace it separately with a substitution rule.

Updated on: 06/02/2026

Was this article helpful?

Thank you!