Onboarding Guide

Troubleshoot your feed

Next: Overview of Merchant Center'southward product information specification

Troubleshoot your feed [hero image]

At times, you may need help troubleshooting your feed. Our goal is to provide answers to specific problems that you might encounter when using feeds and Google Merchant Center.

Review feed processing results

You're able to review the results of all feed processing for file-based or Google Canvass-based feeds. To find the results:

  1. Sign in to your Merchant Centre business relationship.
  2. From the navigation bill of fare, click Products, and so click Feeds.
  3. Click the primary or supplemental feed proper noun you lot'd similar to review.
  4. Review the results:
    • Properties: Includes fundamental feed properties, which vary depending on the input method of the feed. Hither, you tin detect attributes such equally input method, timezone, filesize, detected delimiter (if applicative), and more.
    • Attributes: Your feeds need to adhere to the product data specifications for the programs you're opted into. In this section, you can review all of the attributes we found in your feed, including those attributes which are recognized and map to the feed specification, and besides unrecognized attributes which exercise not match 1 listed in the product data specification. Y'all may review the list and use tools such as feed rules to tell Merchant Center which unrecognized attribute yous would like to apply to populate a Google aspect. For example, yous may want to use "product proper name" in the championship [title] attribute.
    • Processing data: In this section, y'all can review the corporeality of items found in your feed, besides as those with any detected item issues. Review the list of detail issues to understand how many items in your feed are impacted, including examples and links to documentation to address the issue.

If your account has been disapproved and your feeds seem to exist correct, delight view consolidated issue reporting for the Shopping product data across your business relationship, feeds, and items in the "Diagnostics" folio, located under "Products".

Notation: Processing simply checks for basic file and data issues. To see all issues, get to Diagnostics.

Troubleshoot your feed | Feed creation issues [icon] Feed creation issues

  • Forgotten attribute: Your feed may be missing a required attribute. The ID [id] attribute is one of the about commonly forgotten attributes, and so e'er cheque it kickoff.
  • Wrong formatting: Click any of these links for example files that bear witness what a feed should look like in these formats.
    • Tab delimited (.txt)
    • RSS 2.0
    • Cantlet i.0
  • Nosotros currently don't let feeds in .xls format. If you created a feed in .xls format, learn how to catechumen it to a .txt file.

Troubleshoot your feed | Feed registration issues [icon]Feed registration issues

  • Country of sale: Specify the primary location where your items are sold. For instance, if you specify "United states of america" as your land of sale, this indicates that your items are available for buy in the The states. The product data uploaded to a selected land must run across the requirements for that country, including the feed specifications and policies.
  • Multiple countries: Specify multiple countries of sale if yous sell the aforementioned production in multiple countries. Ensure your products meet the requirements for each state, including the feed specifications and policies.
  • Information feed file name: RSS and Cantlet files should end with an .xml extension. Filenames that don't end with any extension will be processed every bit a tab-delimited file by default and should end with (.txt). Remember that we do not have files in Excel format. See converting your spreadsheet for aid.
  • When using filename extensions like .zip or .gz, you lot must ensure that the file is compressed because our system assumes that the file is compressed. Uploading an uncompressed file in this case may cause feed failure. Please make certain that the compressed archive contains exactly one file.

Please note, when editing your data feed settings we recommend yous leave "autodetect" equally the selected option unless a specific problem needs to be addressed.

Troubleshoot your feed | Formatting issues Formatting issues

  • Text or tab-delimited
    • If you lot are using previously formatted text (annihilation with line breaks or quotations), make sure your feed has quoted attributes turned on.
    • Make sure that your columns (tabs) with the required attributes correctly match all the items; oftentimes there volition be either an extra tab or a missing tab.
    • If you're using Google Sheets, the Google Merchant Center add-on can assist y'all validate your data.
  • XML
    • You cannot include un-escaped special characters like "&".
    • Your aspect names may not contain capital letters, any capitalization in your attribute names should be removed. For example, the title [championship] aspect should be entered equally <title>, instead of <Title>.
    • Incorrect encoding sometimes occurs. Be sure to encode your file in the accepted formats.

Troubleshoot your feed | Upload issues [icon]Uploading problems

  • Your feed may exist too large for the upload method you're using.
    • Directly upload files must exist less than 4 GB in size. (If you're encountering an "oops" message from this method, please wait a few hours and try over again.)
    • SSH File Transfer Protocol (SFTP) and File Transfer Protocol (FTP) files must be less than 4 GB in size.
    • Files set for scheduled fetches must be less than 4 GB in size.
  • Commonly, automatic uploads fail because:
    • The URL used for scheduled fetch is roboted or does not have permission settings for Merchant Eye to download the data feed.
    • The URL used for scheduling is not working or redirects to a folio that doesn't comprise the data feed.
  • Compressed files must exist smaller than 500 MB.

Hither are some of the most common errors encountered using SFTP and FTP.

Consequence Solution
Server non found mistake

For FTP, verify you lot're signing on to ftp://uploads.google.com. If you're using an FTP client, remove ftp://; and use uploads.google.com.

For SFTP, verify y'all're signing on to {sftp username}@partnerupload.google.com with a specified server port of 19321. If yous're using an SFTP client, you may need to prefix the host proper noun address with the 'sftp://' protocol (for case, sftp://partnerupload.google.com).
Username or countersign incorrect Click here for help with SFTP and FTP login issues.
"Tin't build information connection" or "FTP folder mistake" You will need to upload using passive FTP.
"Filename not allowed" error Ensure that your filename does non contain spaces. The name of your file should exactly match the name of the filename you registered in your account.
You don't have a information feed registered with this name Ensure that the name of the file you lot're submitting via SFTP or FTP exactly matches the file proper name provided when registering your data feed.
"FTP connection reset by peer" error The Internet connexion to our FTP server was lost. Please endeavor uploading your file again. If your file is nether 200 MB in size, you can likewise upload your file directly through the Google Merchant Eye data feeds page. If your file is larger than 200 MB, attempt splitting your information feed into multiple files smaller than 200 MB. The smaller file size will permit you lot to upload your files through your dashboard.

For specific issues with SFTP and FTP non answered within this page read this article.

If you created your feed using i of the upload methods and would like to review it during your investigation, follow these steps to download it. Notation that there is no file to download for Content API feeds.

  1. Sign in to your Merchant Center account.
  2. Select Products from the left-paw navigation carte, then click Feeds.
  3. Under the "Feed" column, click the feed name.
  4. Under the "Processing" tab, click the iii-dot icon 3 dot icon on the far correct.
  5. Select the option to Download file.

Notation that only users who belonged to the merchant account at the time the file was uploaded have the correct privileges to download the feed.

You'll be able to download a CSV study detailing processing errors and warnings later on yous've uploaded your feed. When a report is available, you'll see an option to download the report in the feed summary folio side by side to the "Download file" button. The written report will contain identifying data for errors at the height, followed by a table with details on individual items and their feed errors and warnings. Please notation that the report volition just be available for xiv days after you've uploaded your feed and volition only particular up to 100,000 errors and warnings combined.

You may also be able to use feed rules to right missing or incorrectly formatted attributes in your feed without editing its content.

Was this helpful?

How can we improve information technology?