feedlinter
Audit my feed

WooCommerce feed fix

Set identifier_exists to No in WooCommerce Feeds

Selling products without a GTIN or MPN? Give Google the right signal without inventing barcodes, editing PHP or changing your WooCommerce catalogue.

Loading verification

Audits up to 10,000 products. No account or credit card required.

✓No WordPress code changes✓Variant-level XML processing✓No fabricated GTIN values
Feed diagnosis

WooCommerce feed

61/100

Identifier warning

42 products affected

!GTIN field is empty
!MPN field is empty
!identifier_exists is missing

Feedlinter rule

<g:identifier_exists>no</g:identifier_exists>

Why Google flags these products

No barcode does not mean bad product data. Google still needs an explicit signal.

WooCommerce stores selling handmade goods, custom furniture, private-label clothing or one-off products often have no EAN, UPC or other GTIN to export. Many feed plugins leave the identifier fields blank without explaining why. Google Merchant Center can then interpret the record as incomplete rather than genuinely identifier-free.

The correct response is not to invent a barcode. For products that truly have no GTIN and no manufacturer part number, Google supports identifier_exists set to no. That tells Merchant Center the identifiers do not exist, instead of suggesting the feed simply forgot them.

Feedlinter processes the XML after WooCommerce generates it. Your catalogue, theme and checkout stay untouched while the outgoing advertising feed gets a consistent identifier rule.

  1. Audit

    Find identifier gaps

    Scan up to the first 10,000 records in the public WooCommerce XML and count variants where both GTIN and MPN are empty.

    Free audit: first 10,000 records

  2. Transform

    Apply identifier_exists=no

    Enable the rule to add the flag to records that contain neither identifier. Feedlinter does not generate fake barcode data.

    Conditional XML rule

  3. Publish

    Give Google a stable feed URL

    Use the Feedlinter proxy URL in Merchant Center and keep it refreshed as your WooCommerce catalogue changes.

    2, 4 or 12 refreshes daily by plan

Better product data means fewer disapprovals, steadier campaigns and more room to scale.

Built for Google Merchant Center

Pricing

Simple pricing for every catalog.

Pay for processed products across your account. Every plan includes unlimited domains.

1,000 SKU
1 000 SKU250,000 SKU

The prices below include each plan’s base SKU allowance. Additional SKUs are sold in packs of 1,000.

Core

Recommended

$9.99/ month

1,000 SKU total · included

  • 2 source feeds
  • 1,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 2 daily refreshes per feed
  • Google Merchant Center

Omnichannel

$29.99/ month

10,000 SKU total · included

  • 6 source feeds
  • 10,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 4 daily refreshes per feed
  • Google Merchant Center
  • Meta / Facebook Catalog
  • OpenAI / ChatGPT

Scale

$59.99/ month

30,000 SKU total · included

  • 20 source feeds
  • 30,000 SKUs included
  • $2.00 per additional started 1,000 SKUs
  • Unlimited domains
  • 12 daily refreshes per feed
  • Google Merchant Center
  • Meta / Facebook Catalog
  • OpenAI / ChatGPT

1 SKU = 1 processed product record in a feed. The same product in two feeds counts twice. When you exceed your allowance, we email you and allow 24 hours to correct it before adding SKU packs to your invoice.

Not ready to subscribe? Run a free instant audit →

Frequently asked questions

The details, without the fine-print fog.

Everything you need to know before running your first product feed audit.

Still have a question? Talk to us

When should identifier_exists be set to no?

Only when a product genuinely has no GTIN and no MPN assigned by a manufacturer. Do not use it to hide identifiers that exist but are missing from WooCommerce.

Does Feedlinter create GTIN or EAN codes?

No. Fabricating identifiers can create worse Merchant Center problems. Feedlinter checks the fields already present and applies identifier_exists=no when the configured rule matches.

Do I need to edit functions.php?

No. Feedlinter transforms the exported XML outside WordPress, so the workflow does not require PHP snippets or theme changes.