A product feed audit is a systematic check of your feed for the errors that cause Google Merchant Center rejections and lost impressions. The good news: you don't need an agency to run one. Most of the problems that quietly drain your Google Shopping performance are structural—missing attributes, mapping mistakes, format mismatches—and you can find and fix them yourself in an afternoon.
This guide walks through exactly what to check, in what order, and where a free audit tool can do the tedious part for you.
Why most feed problems don't need an agency
When products stop showing in Google Shopping or your impressions drop, the instinct is to call in help. But the majority of feed issues aren't strategic—they're mechanical. A missing GTIN, a price in your feed that doesn't match your landing page, an availability value Google doesn't recognize. These don't require an expert to diagnose; they require a checklist and a tool that reads your feed the way Merchant Center does.
Agencies earn their fee on large catalogs, complex multi-channel setups, and ongoing campaign strategy. For a single Shopify, WooCommerce, or BigCommerce store trying to stop disapprovals, that's usually overkill. You can run the same audit they would—you just need to know what they're looking at.
What a product feed audit actually checks
A complete audit covers four layers. Skip any one of them and you'll keep getting surprised by disapprovals.
Required attributes
Every item in your feed needs a baseline set of attributes for Google to accept it: a unique id, a title, a description, a link to the product page, an image_link, a price, an availability value, and a brand. Miss one of these on a product and that product simply won't run. The audit's job is to confirm every item has every required field populated with a valid value—not just present, but valid.
Attribute mapping mismatches
This is where most "invisible" errors live. Your store stores data in its own structure; Google expects a specific structure. The mapping between them is where things break—your "stock status" field maps to availability, your "manufacturer" maps to brand, your variant data maps to size and color. When a mapping is wrong or incomplete, the data looks fine in your store and fails in the feed. Auditing the mapping means confirming each store field lands in the right Google attribute with the right format.
Title and description quality
A title can be technically valid and still hurt you. Google reads titles to decide which searches your product is relevant for, so a title that's missing the product type, brand, or key attribute leaves visibility on the table. The audit checks that titles are descriptive and front-load the important terms, and that descriptions are complete rather than truncated or empty.
Image and identifier issues
Images that are too small, broken links, placeholder graphics, and watermarked photos all trigger problems. On the identifier side, the audit confirms your gtin and mpn values are present and correctly formatted—or, if a product genuinely has no GTIN, that you've handled the identifier_exists attribute correctly instead of leaving Google to guess.
How to audit your feed step by step
Here's the order that finds the most problems with the least effort.
Step 1 — Export and inventory your feed
Start by pulling your current feed exactly as Google receives it. Don't audit your store's product list—audit the feed file itself, because the gap between the two is often where the error is. Count your items and note how many you expect to be live versus how many actually are.
Step 2 — Check required fields
Go attribute by attribute through the required set and confirm every product has a valid value. Sort or filter for blanks. A single column of missing gtin values or empty brand fields will jump out immediately, and these are usually fast fixes once you can see them.
Step 3 — Validate against Merchant Center specs
A value can be present but still wrong: an availability of "available" instead of "in_stock," a price without a currency, a condition Google doesn't recognize. This is the step where you check format and allowed values, not just presence. Google's product data specification lists the accepted values for each attribute—verify yours against it, because these requirements can vary by country and category.
Step 4 — Prioritize errors vs. warnings
Not everything Merchant Center flags blocks a product. Errors stop items from running; warnings reduce performance but keep them live. Fix errors first—they're costing you visibility right now—then work through warnings. Trying to clear every warning before launching anything is how feed audits turn into month-long projects.
When to automate the audit (and when to do it manually)
A manual audit works once. The problem is that feeds aren't static—every new product, price change, and inventory update is a chance to reintroduce an error. Auditing a 50-product feed by hand is reasonable; auditing a 5,000-product feed every time it updates is not.
That's the line. If your catalog is small and changes rarely, a spreadsheet and the steps above will keep you clean. If your catalog is large or updates frequently, an automated audit that scans every product against Google's specs on every update saves you from the disapproval-fix-resubmit cycle that eats hours every week. The manual process teaches you what to look for; automation keeps it from coming back.
Run a free product feed audit
You don't have to do any of this by hand to start. IronFeed's free product feed audit scans your feed against Merchant Center specs and flags the exact attributes that will cause rejections—before you submit. It separates errors from warnings, points to the specific products and fields that are failing, and shows you what to fix first. No agency, no paid plan to start: connect your feed and get the diagnosis.
If you want to understand the layer where most of these errors originate, our guide to attribute mapping and feed error correction goes deeper on the mapping issues this audit surfaces. For the rejection side of the equation, see why products get disapproved in Merchant Center and how to prevent it.