Google Merchant Center XML Feed Errors: Fix All Issues 2026

XML feed errors in Google Merchant Center stop your products from appearing in Shopping ads. After auditing thousands of merchant feeds, the same categories of errors come up repeatedly. This guide covers every common XML feed error, what causes it, and exactly how to fix it.

Why XML Feed Errors Matter

Google Merchant Center reads your product data from a feed file, whether you submit it as a plain text TSV, a Google Sheets export, or an XML file. XML is the most structured format, which makes it both the most powerful and the most sensitive to errors. A single malformed tag or missing required attribute can cause Google to reject individual products or, in the worst case, fail to process the entire feed.

Unlike policy violations, feed errors are purely technical. You can fix them without writing an appeal. But the longer they persist, the more product disapprovals accumulate, and that affects your Shopping campaign performance directly.

The Most Common XML Feed Errors

1. Unescaped Special Characters

XML requires that certain characters be escaped using HTML entities. If your product title includes an ampersand written as a bare "&" character (without the semicolon), the XML parser throws an error and rejects the item. The same applies to angle brackets and apostrophes inside attribute values.

The fix is to replace these characters with their XML-safe equivalents: "&" becomes "&amp;", "<" becomes "&lt;", ">" becomes "&gt;", and "'" becomes "&apos;" when inside attribute values. Most feed generation plugins handle this automatically, but custom-built exporters often miss edge cases.

2. Missing Required Attributes

Google Merchant Center requires a minimum set of attributes for every product: id, title, description, link, image_link, availability, price, and condition (for used or refurbished items). If any of these are absent from an XML item entry, GMC disapproves that product with a "missing required attribute" error.

Check the Processing tab in your feed details. GMC lists which attribute is missing for each affected product ID. Patch the missing values in your source data and re-upload. If your catalog management system is not exporting a required field, map it manually in the feed settings under Attributes in Merchant Center.

3. Malformed or Non-HTTPS Product URLs

Every link and image_link value in your XML feed must be a fully qualified HTTPS URL. Relative URLs like "/products/red-shoes" fail validation. HTTP URLs (without the S) also fail, because Google requires secure landing pages for all Shopping products. URLs with spaces or unencoded characters also break XML parsing.

Encode all URLs before inserting them into the XML. Spaces must become %20, and special query string characters must be percent-encoded. If your store platform generates URLs with trailing spaces or double slashes, your exporter needs to sanitize those before output.

4. Incorrect Character Encoding

Your XML feed must declare its encoding in the XML declaration at the top of the file: <?xml version="1.0" encoding="UTF-8"?>. If your file is declared as UTF-8 but actually saved in ISO-8859-1 (common with Windows-based systems), non-ASCII characters like accented letters or currency symbols will produce byte-sequence errors that corrupt the entire feed.

Always save your XML file with UTF-8 encoding explicitly selected in your text editor or export script. In Python, use open(filename, 'w', encoding='utf-8'). In PHP, set the mb_internal_encoding to UTF-8 before any string operations that feed into your XML output.

5. Namespace and Schema Violations

Google's XML feed format uses a specific namespace declaration. If your feed wraps product data in custom namespaces or uses non-standard tag names, GMC cannot parse the product entries correctly. The root element must be <rss version="2.0"> with the Google namespace, and each product entry must use <item> tags with attributes prefixed correctly with "g:" for Google-specific fields like g:price, g:availability, and g:id.

Compare your feed structure against Google's official XML feed specification. The most common mistake is omitting the "g:" prefix on Google-specific fields, or accidentally duplicating tags within a single item entry.

How to Validate Your XML Feed Before Submission

Before uploading to Merchant Center, run your feed file through a local XML validator. The free W3C Markup Validation Service accepts XML file uploads and flags syntax errors with exact line numbers. Fix every error it reports, then re-validate until the file passes clean.

After the syntax check, use Google's Feed Rules tool within Merchant Center to preview how attributes will map to your products. This catches semantic issues, like a price field containing a value formatted incorrectly (missing currency code, wrong decimal separator for the target country), before they cause disapprovals at processing time.

If you manage a large catalog (10,000+ products), consider setting up automated pre-submission validation as part of your feed generation pipeline. A simple Python script using the xml.etree.ElementTree library can check for required attributes and flag encoding issues before the file ever reaches Google's servers.

Fixing Disapprovals Caused by XML Errors

Once your feed errors are fixed, you do not need to wait for the next scheduled fetch. Go to Products > Feeds, select your feed, and click "Fetch now" to trigger an immediate reprocessing. GMC will process the corrected feed within 24 to 72 hours and restore approved status to the affected products.

If your feed errors were severe enough to drop your active product count below a threshold Google considers significant, pair the feed fix with a quick GMC suspension checklist review to confirm no policy issues have been flagged alongside the technical problems. Feed errors and policy issues sometimes appear together, and fixing only the feed while leaving a policy problem unresolved means your products stay disapproved for a different reason.

For accounts that have already been suspended, fixing feed errors is a required step before submitting an appeal. A feed with active errors signals to reviewers that the account is not ready for reinstatement. Complete the full suspension fix process first, then appeal once the feed passes clean.

Find Every Feed Error in Your Account

Our audit tool scans your Merchant Center account for XML feed errors, missing attributes, encoding issues and product disapprovals. Get a full report in minutes.

Run Free Audit

Preventing XML Feed Errors Long-Term

The most reliable prevention is to build validation into your feed generation process rather than catching errors after the fact. Set up a pre-upload script that checks for required attributes, validates URL format, and confirms UTF-8 encoding on every file before it goes to GMC. Schedule this to run before every scheduled feed fetch.

Also monitor the Processing tab in Merchant Center at least weekly. Google's feed processing can introduce new error categories when they update their product data specification, and catching a new error type early prevents it from accumulating across your entire catalog. Subscribe to Google Merchant Center policy update emails so you hear about specification changes before they affect your disapproval rate.

If your feed error rate is zero but products are still disapproved, the issue has shifted from a feed format problem to a policy violation. Those require a different resolution path than technical feed fixes.

Frequently Asked Questions

What causes Google Merchant Center XML feed errors?

XML feed errors are usually caused by invalid characters (like unescaped ampersands), missing required attributes such as id, title, link, price or availability, malformed URLs, or incorrect encoding. Even a single invalid character can make the entire feed unprocessable.

How do I find XML errors in my Google Merchant Center feed?

Go to Products > Feeds in Merchant Center, click your feed, then open the Processing tab. GMC lists every error with the affected item ID and the specific attribute that failed. You can also download the feed as a file and validate it with an XML validator tool before uploading.

Can XML feed errors cause a Google Merchant Center suspension?

Feed errors themselves rarely cause a full account suspension. They cause product disapprovals, which reduce your eligible product count. However, if a high percentage of your products disappear due to feed errors and you also have policy issues, the combination can accelerate a suspension review.

How quickly does Google reprocess a fixed XML feed?

After you upload a corrected feed or trigger a manual fetch, Google typically processes it within 24 to 72 hours. You can track the processing status in the Feed details page. Products that pass validation move back to an active state, usually within the same processing window.