WooCommerce Google Shopping Feed Not Working? Here’s How to Fix It

If your WooCommerce Google Shopping feed isn’t working, it’s usually due to issues like incorrect product data, missing attributes, or feed configuration errors. You can quickly fix this by checking your Google Merchant Center, validating the feed setup in your CTX Feed plugin, and ensuring all required fields meet Google Shopping feed standards.

You’ve set up your WooCommerce store. Connected it to Google Shopping. Hit “upload.”

But your products? Nowhere to be seen.

No ads. No traffic. Sales? Poof.

It’s maddening.

Google Shopping drives over 85% of eCommerce clicks for retailers—yet 7% of all product feeds get flat-out rejected for critical errors. Your feed fails, and your visibility flatlines.

Here’s the gut punch:

• Half of you (48%!) are fighting invalid GTIN errors.
• 44% hit policy violations that freeze your feed.
• 40% get slapped for “promotional overlays” on images.

One misstep, and Google hides your products. No explanations. Just silence.

This guide fixes that.

We’ll troubleshoot your WooCommerce Google Shopping feed not working like a pro, covering why it broke, how to fix it in minutes, and ways to bulletproof it.

Let’s get started.

Top 7 Google Shopping Feed Not Working + Fixes

You can come across several WooCommerce Google Merchant Center feed issues if you haven’t created the feed properly or haven’t perfectly done WooCommerce Google Shopping feed optimization.

The key is to find out the problems on time and improve WooCommerce product feed quality accordingly. To find the errors or issues for the reasons WooCommerce Google Shopping feed not working,

• Go to Google Merchant Center Next and navigate to Your Business > Products > Needs Attention. Formerly, it was called Diagnostics.

Let’s explore some of the most common WooCommerce Google Shopping feed errors and how to fix them.

1. “Feed Not Syncing” Error

What’s happening: You update products in WooCommerce, but nothing changes in Google Merchant Center.

Why it happens: Often, your scheduled task (cron job) didn’t run, or your server cut off the process before it finished.

How to fix the WooCommerce feed not syncing with Merchant Center:

1. Run a manual sync via WP-CLI – this bypasses cron and forces an immediate update.
2. Check your server’s timeout and memory limits; ask your webhost to raise them if needed, so large feeds can finish exporting.

Simple Solution: If you’re using the CTX feed WooCommerce Google Shopping plugin, click “Regenerate” on your Google for WooCommerce feed settings page (CTX Feed > Manage Feeds) to trigger a full rebuild without waiting for the next schedule. This should immediately fix this WooCommerce Google Shopping feed not working error.

2. Price & Availability Mismatches

When Google sees a different price or stock status in your feed than on your site, it flags those products—and often disapproves them outright.

Why this happens:

• Currency conversion errors. If you use a multi‑currency plugin or switcher, your feed may export the base price (e.g. USD) while your store shows a converted price (e.g. EUR). Merchants on WordPress.org report that disabling the switcher often clears the mismatch error immediately.
• Caching plugins. Aggressive page or object caching can serve an out-of-date feed file to Google, so even after you update a price or stock level, Merchant Center still sees the old data.

How to fix it:

• Align your decimals. In WooCommerce > Settings > General, set “Number of decimals” to 2 so prices export exactly as Google expects (e.g., 19.99, not 19.9).
• Exclude your feed from caching. In your caching plugin’s settings (WP Rocket, W3 Total Cache, WP Fastest Cache, etc.), add your feed URL (usually /feed/google_product_feed/ or similar) to the “never cache” list. This ensures Google always fetches the latest data.
• Use a plugin that supports multi-currency feed generation. CTX Feed Pro is compatible with all popular multi-currency plugins and allows you to generate multi-currency feeds. As a result, your customers will see their preferred currencies across all your channels.

By matching your site’s live prices and stock levels exactly in your feed, you’ll avoid WooCommerce Google feed price mismatch and WooCommerce Google feed availability error flags—and keep your products live in Google Shopping.

3. Missing GTIN/MPN Attributes

Google uses unique product identifiers like GTIN (Global Trade Item Number) and MPN (Manufacturer Part Number) to match your items with existing catalog data. We have already mentioned WooCommerce Google feed invalid GTIN MPN is one of the most common errors resulting in rejection.

• What are GTIN and MPN?
  • GTIN is the number printed below a barcode on retail products (UPC, EAN, ISBN, etc.). Google requires a valid GTIN for any product that already has one, so it can verify exactly what you’re selling and avoid duplicate listings.
  • MPN is the code assigned by the product’s manufacturer. If your item doesn’t have a GTIN (for example, a store‑brand or handmade product), Google asks for both MPN and Brand instead.
• Why WooCommerce alone can’t help
  Out of the box, WooCommerce product pages don’t include fields for GTIN or MPN. Adding them manually means writing custom code or installing an extra custom‑fields plugin, and then mapping those fields into your feed. That can get technical fast, especially if you have dozens or hundreds of products.

How to Fix It with CTX Feed

No PHP snippets or custom‑field plugins required to fix this WooCommerce Google Shopping Feed not working error. CTX Feed comes packed with Google’s identifier fields right into its settings panel:

1. Enable the fields
   • In your WordPress dashboard, go to CTX Feed > Settings.
   • Click the Custom Fields tab.
   • Toggle on GTIN, MPN, or any other identifier you need, then click Save.

2. Enter your values
   • Open any product from Products > All Products and inside the edit window, scroll to Product Data > Inventory > CUSTOM FIELDS by CTX Feed.
   • Type in each product’s GTIN or MPN value and update the product.

3. Automatic feed inclusion
   • CTX Feed will now pull those custom‑field values into your XML/CSV feed automatically—no extra mapping steps needed.
   • When Google fetches your feed, it sees the correct identifiers and stops disapproving for missing GTIN or MPN.

With CTX Feed handling the heavy lifting, you get full compliance with Google’s product‑identifier requirements in minutes, no coding required to fix the WooCommerce Google Shopping feed error.

4. Image Link Failures (HTTPS / 404 Errors)

If Google can’t fetch your product images, those items get disapproved, and without pictures, your Shopping ads won’t show.

How to spot this WooCommerce Google Shopping feed not working problem:

• Bulk image‑URL checker—tools like Screaming Frog SEO Spider let you crawl your store and sort by “Status Code” to find 4xx errors on image URLs. Simply run a site crawl, switch to the “Images” tab, sort by status, and flag any URLs returning 404 or other errors.
• Merchant Center diagnostics—in the Google Merchant Center “to Your Business > Products > Needs Attention” page, filter by “image_link” issues to see exactly which SKUs are failing.

Common causes:

• HTTP > HTTPS mismatches. If your site enforces SSL but your feed still lists http:// URLs, Google’s crawler will refuse the insecure links.
• Deleted or moved files. When you delete images from your Media Library—or change their folder structure—old URLs break.
• Unsupported formats or bad filenames. Google only accepts JPEG, PNG, GIF, BMP, TIFF, WebP images, or filenames with special characters can be rejected.
• Promotional overlays. If an image has price badges or text on top of the product, Merchant Center flags it as a policy violation.

How to fix it:

• Enforce HTTPS site-wide.
  • In WordPress > Settings > General, ensure your “WordPress Address (URL)” and “Site Address (URL)” both use https://.

• Install a plugin like Really Simple SSL or add a redirect rule in your .htaccess to forward all http:// requests to https://.

• Clean up your Media Library.
  • Use the “Regenerate Thumbnails” plugin to rebuild missing sizes and repair broken paths.
  • Delete unused or broken attachments in Media > Library, then re-upload if necessary.
• Bulk‑replace old URLs in your feed.
  • If you migrated to HTTPS, add a search‑and‑replace rule in your feed plugin (or use the Better Search Replace plugin) to swap http:// for https:// across all image_link fields.
• Remove overlays & convert formats.
  • Replace any images containing promotional text or stickers.
  • Convert unsupported formats (e.g. WebP) to JPEG or PNG before uploading.

By crawling for broken links, enforcing SSL, and cleaning up your library, you’ll eliminate WooCommerce Google feed image link errors and keep your listings live and compliant.

5. Products Stuck in “Pending Initial Review”

When you first upload your products, Google holds them in a “Pending Initial Review” state while it checks that your data and website meet its policies. If this status drags on—especially beyond the expected 3–5 business days—it can stall your entire Shopping campaign.

What Google is checking:

1. Website claim & verification. You must both verify and claim your site URL in Merchant Center so Google knows you own the domain.
2. Shipping settings. For countries that require it, you need shipping rules defined at the account or item level.
3. Feed setup. A correctly configured product feed targeted to your country is required.
4. Business contact info. Your Merchant Center account needs a verified phone number and postal address.
5. Tax settings (US only). If you sell in the United States, set up tax rates at the account or item level before products can be reviewed.

Why delays happen:

• Missing or incorrect settings. Forgetting to claim your domain or leaving shipping rules blank blocks the review from even starting.
• Policy violations. If Google finds disallowed content—banned words in titles, promotional overlays on images, or forbidden products—it pauses approval until you fix the issue.
• Frequent feed resubmissions. Every time you upload a new feed, the clock resets. If you schedule daily fetches, your items may never get past “Pending.”

Checklist for faster approval:

• Verify & claim your website: In Merchant Center, go to Settings > Business information > Details > Your online store, then click the Confirm Online Store button and follow the verification steps.

• Set up shipping: Under Your Business > Shipping and returns, add a shipping service that matches what you charge on your site.

• Configure your feed properly: Make sure your feed is live, targets the correct country, and uses the right file format (XML, CSV, TXT).
• Confirm contact details: In Settings > Business information, double‑check your business address and phone number are marked “Verified.”
• Limit resubmissions: Switch your fetch schedule to weekly or monthly during the initial review period so you don’t keep restarting the process.

If your products stay in “Pending Initial Review” for more than a week after completing these steps, reach out to Google Merchant Center Support for a manual review. Once approved, your items will move to “Approved” or “Eligible”, and your ads can start running.

Keeping this checklist in order ensures your feed sails smoothly through Google’s initial inspection—and into shoppers’ search results.

6. XML / CSV Formatting Errors

Your product feed file must follow Google’s exact syntax rules. Even a single stray character can break the entire import, so it pays to validate and clean your feed before you hit “Upload.”

Common Triggers:

• Special characters. Smart quotes (“ ”), em‑dashes (—), and other Unicode symbols often sneak in when you copy‑paste product titles or descriptions. These characters can break XML parsers or throw off CSV column alignment.
• Encoding mismatches. If your server exports the feed in UTF‑8 but your CMS or plugin saves it as ISO‑8859‑1 (or vice versa), you’ll see garbled text or an “Invalid character” error.

How to catch them:

• Google Feed Rules in Merchant Center. Under Settings > Data Sources, you can preview your file and spot formatting errors before Google even tries to process it. Look for red flags like “unexpected token” or “malformed XML.”

• External validators. Tools such as XML‑sitemaps.com’s XML validator or free CSV linting sites let you upload your feed and run a full syntax check. They’ll highlight exactly which line and column contain the problem, so you can jump straight to the fix.

Fixing the issues:

• Normalize your quotes and dashes. Search your feed file (or use a mass‑find tool) to replace smart quotes with straight quotes, and convert em‑dashes to a simple hyphen (-).
• Enforce UTF‑8 encoding. In your FTP client or hosting control panel, ensure the feed file is saved as UTF‑8 without BOM. If you see a Byte Order Mark (BOM) at the start of your XML, remove it—Google’s parser hates hidden characters.
• Clean up unexpected tags. Sometimes plugins inject HTML comments or analytics tags into your feed. Scan for <!– or <script> snippets and strip them out so only valid <item>, <g:price>, and other Google tags remain.

CTX Feed’s automatic fix

CTX Feed supports a number of formats, including CSX, XML, TXT, etc. It includes built-in encoding correction—every export is forced to UTF-8, and common problematic characters are sanitized on the fly.

It means you no longer need to wrestle with your server settings or open your feed in a text editor. Just generate the feed, run it through Google’s Feed Rules once, and you’re ready to go.

By validating early, cleaning your syntax, and relying on CTX Feed’s built‑in encoding safeguards, you’ll avoid the dreaded “Malformed XML” or “Invalid CSV” WooCommerce Google Shopping feed not working errors—and keep your product updates flowing smoothly.

7. Category & Attribute Mapping Conflicts

Every WooCommerce store has its own category structure. For example, you might list a product under:

/ Clothing / T-shirts

But Google Shopping expects a different taxonomy for the same product:

/ Apparel & Accessories / Clothing / Shirts & Tops /

This mismatch creates a problem. If your products are placed in the wrong category—or have no category at all—Google Merchant Center will flag them, leading to disapprovals or poor visibility.

This is where Category Mapping comes in. It ensures your store categories align with Google’s official taxonomy so your products show up in the right place for the right audience.

How to Fix It with CTX Feed

The good news? You don’t need to manually rewrite your categories or edit your feed file. CTX Feed makes this simple:

1. Go to CTX Feed > Category Mapping.
2. Click New Category Mapping.
3. Select your target merchant (in this case, Google Shopping).
4. On the left, you’ll see your existing WooCommerce categories. On the right, search and select the closest Google Shopping categories.

5. Save your mapping.

Once done, CTX Feed will automatically replace your WooCommerce categories with the appropriate Google categories whenever you generate or update your feed.

Note: For a complete category mapping and Google Shopping WooCommerce integration, check out this article.

Mapping Other Attributes

It’s not just categories. Google also requires other key attributes like:

• Product Type (g:product_type)
• Condition (g:condition)
• Brand, MPN, GTIN

With CTX Feed, you can map attributes as well.

1. Go to CTX Feed > Attribute Mapping.
2. Click Add New Rule and choose your WooCommerce attribute (e.g. your existing category path or custom field like “Season”).
3. Map it to product_type (select g:product_type in CTX).
4. Save your rule and regenerate the feed.

Now your custom values—such as “Clothing > Women’s > Summer Dresses”—will correctly appear in the product_type field in your feed.

8. Invalid Price, Description & Image Errors

When your feed file has missing or malformed data—like blank prices, no descriptions, or broken image links—Google will flag those items and won’t show them in Shopping ads.

• Why it happens:
  • You copy a description that’s too short or dumps HTML tags, making Google reject it.
  • An image URL in your feed doesn’t match what’s in your Media Library, causing a 404.
  • A product is missing a price field or uses a non‑numeric character, so Google can’t read it.
• How to fix it:

• In Google Merchant Center > Your Business > Products > Needs Attention, download the CSV report of errors.
• Open the CSV, correct each row so that:
  • Price is a valid number (e.g. 29.99), with no currency symbols or commas.
  • Description is plain text, between 1 and 5,000 characters, no HTML tags.
  • image_link points to a live URL ending in .jpg, .png, or .gif.
• Re‑upload the fixed file (or reconnect your feed URL) and re‑run Diagnostics to confirm the issues are cleared.

CTX Feed Pro Easy Fix

Use the Filters to exclude incomplete products automatically—those missing price, description, or image—so they never make it into your feed. Just check the boxes for “Remove Empty Price Products,” “Remove Empty Description Products,” or “Remove Empty Image Products” when you build your feed.

9. Out‑of‑Stock & Sale‑Price Mismatches

If you run a sale on your WooCommerce site but your feed still shows the old price (or lists out‑of‑stock items as available), Google will disapprove those listings—or worse, show wrong information to shoppers.

• Why it happens:
  • Your sale campaign ends, but the feed doesn’t update to remove the sale_price or update the price.
  • Products go out of stock, yet your feed continues to list them as “in stock.”
• How to fix it:

• In Merchant Center ‘Needs Attention’, look for “price mismatch” or “availability error.”
• If you’re manually updating feeds, download the error CSV, correct the price and availability columns (instock, outofstock, preorder), then re‑upload.
• For sale campaigns, include the sale_price_effective_date field with start/end timestamps (e.g. 2025-07-01T00:00:00/2025-07-07T23:59:59).

CTX Feed Pro Quick Fix

• Exclude out‑of‑stock products automatically by ticking the “Remove Out Of Stock Products” filter.
• Auto‑fetch sale dates by adding sale_price_effective_date attribute in your feed config window, and the plugin pulls your WooCommerce sale start and end dates straight into the feed so Google always has the right price window.

Wrap Up

Fixing a WooCommerce Google Shopping feed not working issue doesn’t have to feel like wrestling with code all day. By walking through diagnostics in Merchant Center, validating your product data, and making sure your categories and attributes line up with Google’s requirements, you can get your products back in front of shoppers quickly.

Remember these key takeaways:

1. Diagnose first—use Merchant Center’s ‘Needs Attention’ tab to pinpoint exactly what’s wrong.
2. Clean your data—check prices, descriptions, images, and identifiers so everything meets Google’s specs.
3. Map smartly—align your WooCommerce categories and attributes (like product_type) with Google’s taxonomy to avoid “required attribute” errors.
4. Automate with CTX Feed—use its built-in tools (Force Regenerate, Custom Fields, Advanced Filters, Attribute & Category Mapping) to handle common fixes without extra plugins or code.

Once your feed is healthy, set up a regular audit routine—weekly or monthly—to catch any new issues before they impact your campaigns. With your feed running smoothly, you’ll unlock better visibility in Google Shopping and keep your ad spend working harder for you.

Got questions on WooCommerce Google product feed troubleshooting or still stuck? Drop a comment below or reach out to us—let’s get your products back online and selling!