Skip to main content

Technical error when uploading the feed

What to do when your product XML feed fails to upload or the app shows an error: how to find and fix the problem quickly.

Written by Saša Kučerová

Step 1: Check the feed URL in your browser

Before looking for the error in the app, open your feed's URL directly in your browser (Chrome, Firefox or Edge).

What you should see: XML code that starts with something like <?xml version="1.0"?> or <rss version="2.0">.

What it means if you see something else:

  • Blank page or 404 error → the URL is wrong or the feed doesn't exist

  • Login screen → the feed is password-protected; it must be publicly accessible

  • Text in CSV or HTML format → you used a link to the wrong export type; you need XML

  • XML with a list of page addresses (tags <urlset> and <loc>) → it is the website's sitemap, not a product feed

  • The file downloads instead of displaying → it may work, but verify the format (must be XML)

The feed URL must start with https://. We don't download feeds from addresses starting with http://, and the upload fails; in Settings you'll see Please use a URL that supports the HTTPS protocol. Most feeds also work over https, just change the address.


What a feed URL looks like and what it doesn't

This is what a feed URL looks like (examples from our platform guides):

  • Shoptet: https://www.mystore.com/google/export/products.xml?hash=YOUR-HASH

  • WebAreal: https://www.mystore.com/fotky12345/xml/google_nakupy.xml

  • Upgates: https://www.mystore.com/feed-google-merchant.xml

  • Eshop-rychle: https://www.mystore.com/feed/google-shopping.xml

  • Webnode: https://www.mystore.com/rss/pf-google.xml

  • WooCommerce (Product Feed PRO plugin): https://www.mystore.com/wp-content/uploads/woo-product-feed-pro/xml/….xml

  • ByznysWeb: https://www.mystore.com/erp/impexp/googlenakupyexport/download

  • Unas: https://shop.unas.hu/admin_export.php?shop_id=…&format=google_product_feed

The URL differs by platform and doesn't have to end with .xml. It often contains words like google, feed, xml, export, merchant or products, sometimes with a long code. It can also be on another service's domain, for example when you edit your feed in Mergado (feeds.mergado.com/…). What matters is that it leads to a product export for Google Shopping.

This is not a feed URL:

  • https://www.mystore.com: the store's homepage

  • https://www.mystore.com/sitemap.xml: the website's sitemap, a list of pages, not products

  • https://www.mystore.com/shoes/mens-sneakers: a regular category or product page

  • a link to your store admin that requires logging in

  • an export for Heureka or Zboží.cz: it is XML, but in a different format than we need


What a correct XML feed should look like

Below you can see what a product XML feed in Google Shopping format looks like. Each product is in a separate <item> block, with the required fields inside it. Your feed doesn't have to look exactly the same; what matters is that it contains these fields in the correct structure:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0">
<channel>
<title>Your store name</title>
<link>https://www.myshop.com</link>

<item>
<g:id>12345</g:id>
<g:title>Women's winter down jacket, black, size M</g:title>
<g:description>Warm down jacket with a hood, water-resistant, ideal for cold weather.</g:description>
<g:link>https://www.myshop.com/womens-winter-jacket-black-m</g:link>
<g:image_link>https://www.myshop.com/images/jacket-black.jpg</g:image_link>
<g:price>99.90 EUR</g:price>
<g:availability>in_stock</g:availability>
<g:brand>ExampleBrand</g:brand>
<g:gtin>8594001234567</g:gtin>
<g:condition>new</g:condition>
</item>

<!-- each additional product is again a separate item block -->

</channel>
</rss>

Watch out for: values like in_stock and the field names (g:id, g:title…) are written exactly like this, in English. The price must include the amount and the currency (99.90 EUR) and must match the price on your website.


Step 2: Most common causes and how to fix them

Possible cause

Solution

The feed is not accessible (most common cause). The feed either doesn't exist at all, or the site has bot protection, so our app can't reach it when loading.

Make sure the feed URL works and is publicly accessible even without logging in. If the site uses bot protection (e.g. Cloudflare or captcha), ask your developer to add an exception for feed access.

A different address was entered instead of the feed (common mistake). For example the website's sitemap (often sitemap.xml) or the store's address. The app then says "We couldn't find any products in the feed".

Neither a sitemap nor the store's address is a product feed, they contain no product data. In your store's admin, find the export in Google Shopping (XML) format and enter its link, see Step 3.

The feed is not in XML format. The app only accepts XML in Google Shopping format.

In your store admin, look for an export in Google Shopping (XML) format and use its link. Note: feeds for Heureka or Zboží.cz are not compatible; we need the Google Shopping format.

Required fields are missing or have the wrong structure.

Check that the feed contains the fields id, title, description, price, availability, link, image_link. Fill in any missing data in your store admin or with your developer.

The feed URL can't be loaded. The link is wrong or doesn't contain XML data.

Open the URL in your browser (see Step 1). If nothing shows up, the URL is probably wrong. Copy it again directly from your store admin.

The feed is too large.

Contact customer support, or exclude from the feed the products you don't want to use in advertising.


Step 3: Where to find the feed on your platform

If you don't know where to find the feed URL in your admin, follow the steps for your platform:

Platform

Where to find the feed

Shoptet

Connections → XML feeds → Google Shopping. If the feed is secured, add ?hash=YOUR-HASH to the end of the URL (Connections → XML feeds → Security) and make sure the first checkbox under Security is unticked.

Eshop-rychle

E-shop → Export → Product export → Google Shopping → Generate feed (the URL appears at the bottom).

WebAreal

E-shop → Export → Product export → Google Shopping → Generate (URL under "Generated feeds list").

Upgates

Add-ons → Google (activate the add-on) → Google Shopping section → activate the product export → feed URL.

FastCentrik

Settings → Tools settings → XML feeds → Google feed.

ExitShop

Stores → your store → XML outputs → XML feed for Google Shopping.

Webnode

Store settings → Product comparison sites / Product feed → Google Merchant Center → activate (the feed is generated).

ByznysWeb

Settings → Product comparison sites → Google Merchant Center → activate for your language version → "Show URL".

Unas

Settings → External connections → Price comparison export, Feed → Google Product Feed. Enter IP 64.227.71.84, save and copy the URL (processing up to 24 h).

WooCommerce

No native XML export; create the feed with a plugin (Product Feed PRO, CTX Feed or Google Product Feed) → feed URL.

Shopify

After connecting your store through the Tanganica app, you don't need a feed. With manual setup, create the feed, for example, in the Feedyio app, see Connecting Your Shopify Store.

PrestaShop

No native XML export; create the feed with a Google Shopping feed module → generated URL.

OpenCart

Extensions → Extensions → Feeds type → Google Shopping extension → generated URL.

AdobeCommerce

No native XML export; create the feed with an extension from the Adobe Commerce Marketplace (product feed) → feed URL.

Wix

No native XML export; create the feed with an app from the Wix App Market (Google Shopping feed) → feed URL.

Squarespace

No native XML export; create the feed via GoDataFeed (Squarespace Extensions) → Google Shopping feed → Create feed URL.

Shoprenter

No direct XML export. Export TSV (Marketing → Automatic product sharing → Google Shopping) and convert it to XML using Mergado.com.

Other platform

Look in the Export, Google Shopping, XML feeds or Product exports section.

Menu names may differ slightly depending on your platform's interface language.


Step 4: The feed uploaded, but products don't appear

If the app confirmed the feed upload but you don't see anything in the Products section:

  • Make sure your advertising credit is topped up and at least one campaign is switched on. The feed is only processed when you have credit and at least one campaign switched on, even if the feed URL is correct and worked before. After topping up, the feed is processed the following night, and your campaigns switch on automatically once it is done.

  • Wait 24–48 hours, processing the feed and syncing products takes a while

  • Check Products → Product status, there you'll see how many products were processed and whether they're approved

  • Product approval takes 3–5 days after the first feed processing

  • If more than 5 days have passed and products are still missing, our team will check it


The “Product feed processing is paused” message

The app shows this message in two cases: you have no advertising credit, or you have credit but all your campaigns are switched off. Your products are then not updated and the date of their last update stays the same. It is not processing in progress that you just need to wait for.

What to do:

  • If your credit has run out, top it up in the Top Up Credit section.

  • Switch on at least one campaign in the Campaigns section.

  • We process the feed once a day, overnight, not right after you top up or switch a campaign on. If you top up or switch a campaign on during the day, your products are updated the following night and the message disappears the next day.

  • If the message is still there after that, we'll check it for you.


Still stuck?

We'll gladly look at your feed and help get it working. Please have ready:

  • The URL of your feed

  • The name of your platform / e-commerce solution

  • A screenshot of the error message (if you have one)

Did this answer your question?