Product feed audit in 5 easy steps

May 28, 2026

Reading Time - 16 min

Amy Bateson

Amy Bateson

Author

If your product listings are not driving enough revenue, the problem is often your data. Poor titles, wrong categories, and missing attributes reduce visibility, clicks, and conversions.

Even a small error rate, such as 5–10% of products with bad or missing data, can affect a large portion of your catalog.

A product feed audit helps you quickly identify and fix these issues.

In this guide, we walk through the steps to audit your product feed so your data is clean, complete, and ready to drive better results.

Key Takeaways

  • A product feed audit helps you identify issues that directly affect visibility, clicks, and conversions, especially missing data, weak titles, and incorrect categories.
  • Focus on fixing mandatory issues first in the Quality step, since these can block products from appearing in Google Merchant Center and other channels.
  • Most feed issues are fixed either with rules (for cleanup and enrichment) or by correcting the source data in your import.
  • Accurate mapping, identifiers (GTIN/EAN), categories, and attributes are critical for product approval, matching, and performance.
  • Always verify the final output in Preview before export to ensure your feed is formatted correctly and ready for the channel.

How to audit your product feed with Channable in 5 steps

With a product feed optimization tool like Channable, you can audit a product feed directly within the channel setup to see how your data is mapped, transformed, categorized, and validated.

In practice, feed management in Channable is done in four main areas:

  • The Mapping step, to see how internal fields are linked to channel fields
  • Your Rules, to fix missing, inconsistent, or misformatted data at scale
  • The Categories step, to make sure products are assigned to the right channel categories
  • The Quality and Preview steps, to spot issues and verify the final output before export

Let’s take a look at each of these steps in detail below.

Step 1: Review issues in the Quality step

By this point, your product data is already imported into Channable, and you have a feed set up for your channel. Now you can use the Quality tab to review and fix any issues in your feed before sending it to the channel.

This is where you get a clear picture of your feed health. You can see which feed issues are affecting your product data, which products are at risk, and which problems need attention first.

Each issue is labeled as:

  1. Mandatory issues are problems that can stop products from being accepted or shown at all, such as missing required fields, invalid GTIN/EAN values, or duplicate IDs. These should always be fixed first.
  2. Recommended issues don’t always block products, but they hurt performance or limit visibility. For example, missing brand, weak titles, or incomplete attributes. Fixing them usually improves relevance and click‑through.
  3. Optional issues are minor improvements or nice‑to‑have fields. They are useful if you want to fully optimize your feed, but they are not urgent during the first audit pass.

Meta product feed quality issues screen

Focus on these steps:

  • Import your product data into Channable, then select the channel you want to sell on
  • Open that Channel’s feed and go to the Quality tab
  • Review the list of issues flagged based on your imported data and the channel’s requirements
  • Check the severity of each issue: Mandatory, Recommended, or Optional
  • Start with Mandatory issues, since these can block products from appearing in Google Merchant Center, Google Shopping, or other channels
  • Expand each issue to understand what is wrong and which products are affected
  • Note the type of problem before you fix it, such as missing data, invalid values, duplicate identifiers, or field mismatches
  • Recheck the Quality tab after each round of fixes in the next step

For example, if product titles, brands, or product descriptions are empty, that usually indicates missing data in your source feed. If global trade item numbers such as GTIN or EAN are duplicated or invalid, those products may not be accepted.

If a required field is not mapped correctly, your product details may not meet the channel's requirements.

Step 2: Fix data with rules or import changes

Once you know what’s wrong from the Quality tab, you fix it in one of two places:

  • In the Rules tab, where you can clean or enrich product data
  • In the Import setup, when the source data itself is missing or wrong

Fix issues using rules (inside your feed)

Use Channable rules when data exists but needs cleaning, formatting, or adjustment.

Go to the Rules step in your feed and:

  • Click + Create rule
  • Add an IF condition to target the issue, for example:
  • Title is empty
  • GTIN is not valid
  • Price is less than 0

Add a THEN action to fix it, such as:

  • Copy a value from another field
  • Set a default value for missing data
  • Clean text (for example, remove HTML from descriptions)
  • Exclude products that should not be exported

Save the rule and apply it

Then return to the Quality tab and check whether the issue is resolved.

Price-based exclude rule

💡 Use rules when:

  • The data exists in another field
  • Values need cleanup or formatting
  • You want a scalable fix across many products

Fix issues in the import source

Use import changes when the data itself is wrong or missing at the source.

Go to your import settings and:

  • Open Setup → Import → [your import] → Edit mapping
  • Check if the field is mapped correctly to the right source field
  • If the data is missing or incorrect, fix it in your source (spreadsheet, feed file, or webshop)
  • Save your changes

Then return to the Quality tab and verify the issue is gone.

💡 Use import fixes when:

  • The data doesn’t exist anywhere in your feed
  • Identifiers like GTIN or EAN are invalid
  • Core product details, such as price, brand, or product categories, are incorrect

Step 3: Verify required field mapping

Mapping connects your product data to the fields required by each channel, such as Google Merchant Center or Google Shopping feed. If a required field is not mapped, your products may not be listed at all.

Go to the Mapping tab in your feed and review all fields marked Mandatory.

For each field, check three things:

  1. A valid Internal field is selected
  2. The mapped field contains data
  3. The values match the format expected by the channel

If a mandatory field is missing, create or fix it in your import first, then map it.

After making changes, save your mapping and go back to the Quality tab to confirm the issue is resolved.

💡 A quick way to think about it:

  • Field is not mapped → the channel cannot read your data
  • Field is mapped, but values are wrong or empty → the product may still be rejected

A simple example is availability in a Google Shopping feed. Availability is a required field, so you need to ensure Google can read the correct stock status for every product.

To check this:

  • Open the Mapping step
  • Find the mandatory field availability
  • Map it to the internal field that stores stock status, such as stock_status
  • Check that the values in stock_status use valid Google values, such as in_stock, out_of_stock, preorder, or backorder

If stock_status is empty for some products, fix that first with a rule (for example, set availability to out_of_stock when stock is empty).

Meta feed mandatory field mapping

💡 The same pattern applies to other required fields:

  • Missing brand → map a valid brand field
  • Missing GTIN/EAN → map a valid identifier field
  • Missing description → map your description field

Step 4: Improve identifiers, categories, and attributes

Mapping alone doesn’t fix weak data. A field can be mapped correctly and still contain the wrong identifier, the wrong category, or incomplete attributes. That will still limit visibility, approvals, and performance.

Start with identifiers. Fields such as ID, GTIN, and EAN must be valid and unique. If the same value appears more than once, or if variants share an identifier when they shouldn’t, products can be rejected or matched incorrectly.

Check for issues like:

  • Duplicate IDs
  • Duplicate GTIN or EAN values
  • Invalid GTIN or EAN values
  • Variants using the same identifier

If the problem is in the source data, fix it in the import. If duplicate items need to be cleaned up within the feed, use rules where appropriate. If an identifier is invalid and cannot be fixed, exclude the affected items if needed.

Next, review your categories in the Categories step. This is where you check whether products are assigned to the right category. If items are uncategorized, too broad, or clearly in the wrong place, channels may not understand them properly.

Channable helps in two ways here:

  • Manual categorization gives you more control when products need a closer review

  • AI product categorization can automatically match products to likely categories. It can infer missing attributes from the product data you already have, which is useful when details like color, material, or size exist somewhere in the data but are not properly structured.

Smart product categorization summary

Step 5: Check output in Preview & export

By now, you have reviewed issues, fixed the data, verified your mapping, and improved key fields. Now you need to confirm that the exported output looks right.

Go to Feeds → [Your feed] → Preview.

From there, work through these checks:

  • Open the Overview tab if you want to copy the feed URL
  • Open the XML/CSV/JSON Preview tab to inspect the actual exported output
  • Download the feed as XML or CSV if you want to review it outside Channable

If you are working with a marketplace setup, the Preview step also shows mapped attributes, item-level errors, and product details before export.

Product table with empty quantity fields

To review this properly:

  • Use the error filter to show only problematic items
  • Search for a specific product if you want to inspect one item closely
  • Click an item to open its detailed preview
  • Check any red-marked fields or error labels
  • Use View in build or Categories to jump back and fix the issue

This step is important because it shows you the output as the channel will receive it. A field may look fine earlier in the build, but the preview will show whether it exports in the correct format and with the correct value.

If you’re using a Shopping Ads generator, click Reload preview after making changes. This runs a dry run and refreshes the preview without sending anything live.

Once the preview looks correct and the remaining issues are resolved, your feed audit is complete.

💡 See how TITUS used Channable as a central feed hub to scale 100,000 SKUs across 7 markets while cutting manual fixes. Read the case study.

Product feed audit best practices

A good product feed audit should help you find the issues that affect visibility, clicks, conversions, and campaign efficiency.

Start with diagnostics and product categorization

A product feed audit starts where the data lives: in your Merchant Center diagnostics and feed tool, not in the campaign dashboard. The first step is to pull a clear view of product status and group items by approval status, missing required attributes, and error type so you know exactly where the biggest delivery risks are.

This gives you a clear order of priority. Fix disapproved products and missing required fields first, then move on to optimization issues like titles, attributes, and categories.

Validate feed data against the website and tracking

At a minimum, you want to compare titles, descriptions, GTINs, brand names, prices, and availability in the feed with what users actually see on the product page.

Pricing mismatches, outdated stock status, or incomplete descriptions can quietly hurt both compliance and conversion. In parallel, you should validate product IDs and variant IDs across your feed, your attribution platform, and analytics.

Fix identifiers, attributes, and taxonomy for better matching

This means filling in GTINs wherever possible, standardizing brand names, and cleaning up product types so they map accurately to Google Product Categories. It improves how platforms understand your catalog and reduces the risk of disapprovals due to ambiguous or incomplete data.

You should also review attributes like color, size, material, gender, age group, and compatibility. These details help platforms understand what each product is and match it to more relevant searches.

Taxonomy matters here, too. If your product type is too vague or mapped to the wrong category, your products may show for weaker queries or miss better opportunities. The goal is to make your feed easy for both platforms and shoppers to understand

Rebuild titles around organic search intent

Use search term data, product performance reports, and high-intent keywords to understand how people describe your products. Then rebuild titles using a consistent structure that includes the most useful product details.

For example, a weak title like “Running Shoes Model X” gives platforms very little to work with. A clearer title, like “Nike Men’s Running Shoe - Black/Red - Sizes 8-12,” includes the brand, product type, gender, color, and size range.

A title structure usually includes details such as:

  • Brand name
  • Product type
  • Key feature
  • Gender or audience
  • Size, color, material, or compatibility

Review product clustering and variant structure

Check whether your product variants are grouped correctly. Products that belong under one parent should stay together, while genuinely distinct products may need to be split.

Pay close attention to naming consistency across variations. If the same product family uses different naming patterns, platforms may struggle to understand how the items relate to each other.

During this step, decide:

  • Which variants should remain under a single parent
  • Which products should be split into separate listings
  • How product names and IDs should stay consistent across variants
  • Whether variant-level performance data is being grouped correctly

Connect the feed to profitability and bidding strategy

Not every product deserves the same visibility or budget. Some products may drive revenue but have weak margins. Others may have strong profit potential but poor visibility because they are not labeled correctly.

Use custom labels to segment products by margin, seasonality, stock status, price tier, product priority, or performance group. This gives your bidding strategy better inputs and helps budgets move toward products that actually support business goals.

For example, custom labels can help you separate:

  • High-margin products
  • Low-margin products
  • Bestsellers
  • Overstocked products
  • Seasonal products
  • New arrivals
  • Products with strong ROAS or POAS potential

Without this segmentation, campaigns may push spend toward products that look good on revenue but underperform on profit.

Run regular audits before major changes or promotions

Google recommends submitting new product data three to five business days before a launch or sales event so there is time for processing and review. This makes pre-promotion audits especially important.

A practical audit schedule could look like this:

  • Weekly: Check Merchant Center diagnostics for disapproved products, warnings, and eligible products
  • Monthly: Review query-level performance in Google Ads and assess how feed attributes affect CTR, CPC, and conversion rates
  • Quarterly: Review taxonomy, title frameworks, competitor positioning, and product segmentation

Common product feed audit mistakes

Here are the most common mistakes to avoid:

Treating the feed like a static catalog

Many teams build their feeds based on the internal catalog structure rather than on how users search for and compare products. This leads to clean-looking data that performs poorly. Product names, categories, and attributes might make sense to your team, but that does not mean they help ad platforms understand user intent.

The result is a feed that may be technically valid but does little to help algorithms understand which products should win auctions, receive budget, or be surfaced for high-intent queries.

Ignoring attribution and tracking in feed audits

A feed audit shouldn’t stop at Merchant Center diagnostics or feed tool errors. You also need to check whether your product IDs and variant IDs align with your tracking, analytics, and attribution setup.

For example, a product may receive traffic in the ad platform, but the conversion may be credited somewhere else. Or worse, it may not be credited properly at all.

This creates a major optimization problem. Your team may increase spend on products that appear to perform well but are not actually driving profitable conversions. At the same time, other products may receive insufficient funding because their performance signals are broken or incomplete.

Treating “approved” as “optimized”

Approval in Google Merchant Center only means your products meet the basic requirements to be shown. It doesn’t mean your feed is ready to perform well.

A product can be approved and still have weak titles, missing attributes, vague product types, poor images, incomplete identifiers, or thin descriptions. These gaps can limit visibility, reduce click-through rates, and weaken campaign performance.

Auditing in silos instead of as a cross-functional effort

Feed quality is shaped by how products are structured on the website, how attributes are managed, how campaigns use the data, and how performance is tracked.

When teams audit the feed in isolation, they usually fix the visible errors but miss the root cause. For example, a disapproved product may point to a missing field, but the real issue could be inconsistent product setup at the source. A weak-performing product may look like a campaign problem, but the feed may be missing the attributes needed for better matching.

The goal is to review the full product data flow, from the source catalog to the final channel output.

Make product feed optimization part of your workflow

Product data changes constantly, and even small issues can affect visibility, clicks, and conversions if they are left unchecked.

That’s why feed optimization needs to be part of your regular workflow. Channable helps you do this at scale. You can use Rules to clean and enrich product data, run Quality checks to catch errors early, and manage mapping and categorization so your feed meets channel requirements.

Channable makes it easier to keep your product data accurate, consistent, and ready for channels like Google Shopping and marketplaces.

Amy Bateson

Amy Bateson

Author

Amy Bateson is a Product Marketing Manager at Channable for Channable Insights and Channable AI solutions. She helps eCommerce teams by shaping the go to marketing strategy, guiding product adoption, and highlighting how data and AI can transform everyday workflows for digital marketers and online retailers. She's able to bring her deep product expertise to help present products and features that resonate for clients.

Product feed audits FAQs

How often should you audit your product feed?

You should audit your product feed at least once a month and more frequently if your catalog, pricing, or inventory changes often or before major campaigns.

What are the most common product feed errors?

The most common product feed errors include missing data, invalid or duplicate GTIN or EAN values, incorrect mapping, weak product titles, and mismatches between feed data and your website.

What happens if a required field is missing in my feed?

If a required field is missing, the product may be rejected or not shown on the channel, especially in Google Merchant Center and Google Shopping.

Can I use one feed for multiple channels in Channable?

No, you cannot use a single feed for multiple channels in Channable. Each channel has its own feed because every platform has different requirements. For example, Google Shopping requires fields like GTIN, availability, and Google’s category structure, while Meta uses different attributes and formats. So you would create one feed for Google Shopping and a separate feed for Meta inside the same project. Both feeds use the same imported product data, but you configure mapping, rules, and categories separately for each channel to match its requirements.

Stay ahead of the curve

As we keep on improving Channable, we would like to share the latest developments with you.

First name

Last name

Company email *