7 Google Merchant Product Data Issues to Check First

 

7 Google Merchant Product Data Issues to Check First

Your product can look perfectly normal in your online store and still have problems in Google Merchant Center.

The reason is simple: Google does not look at only one piece of information.

It can compare your submitted product data with your landing page, structured data, price, availability, product identifiers and variant information. When those signals disagree, products may become limited, display incorrectly or require additional attention.

Google itself notes that inaccurate, missing or conflicting product information can lead to disapprovals, limited eligibility or incorrect product displays.

Before changing your entire product feed, start with these seven areas.

1. The Price in Your Product Data Does Not Match the Page

Price mismatches are one of the first things worth checking.

The price submitted for a product should match the price shown on its landing page, in its structured data and during checkout.

For example, imagine your product data says:

29.00 USD

but the landing page currently shows:

34.00 USD

That inconsistency can create a problem even if both values were correct at different times.

Google's product data requirements state that submitted price and currency should match the landing page, structured data and checkout.

The important question is not only:

“Is my feed price correct?”

It is:

“Do all of my product data sources agree right now?”

2. Availability Is Out of Sync

A similar problem happens with inventory.

Your submitted product may say:

in_stock

while the product page says:

Sold out

Or the page may show the product as available while your submitted data still says:

out_of_stock

Google expects availability information to match the landing page, checkout experience and supported structured data.

Stores with frequently changing inventory should pay particular attention to this.

A perfectly formatted feed can still become inaccurate if the underlying information is stale.

3. The Product URL Opens the Wrong Variant

Variants create another common source of confusion.

Imagine a product feed row describes:

Blue T-shirt — Medium — $25

but the submitted URL opens the page with:

Red T-shirt — Large — $30

The product exists.

The URL works.

But the evidence no longer clearly matches the exact offer described in the product data.

For products with variants, Google recommends using variant-specific landing page URLs and grouping related variants correctly with attributes such as item_group_id.

This is why checking only whether a URL loads is not enough.

You also need to ask:

Does this URL represent the exact variant submitted?

4. Your Structured Data Disagrees With What Customers See

Structured data gives machines a clearer description of a product and its offer.

For example, a page may contain structured information for:

  • price

  • currency

  • availability

  • condition

But structured data is useful only when it agrees with the visible page.

Google states that structured data should match the values shown to customers. It also uses structured data for features such as automatic item updates.

That means a page can visually show the correct price while still sending an older price through its markup.

From a shopper's perspective, everything may appear fine.

From a machine-readable data perspective, it may not be.

5. Variant Attributes Are Missing or Inconsistent

If you sell products with different colors, sizes, materials or other options, each variant needs to be represented clearly.

Google specifically identifies incorrect or missing variant attributes as a source of Merchant Center problems.

For relevant variants, attributes can include:

item_group_id, color, size, material, pattern and other product-specific values.

One important mistake is treating several variants as if they were one identical product.

Another is assigning variant information that does not match the landing page.

Good variant data should make it possible to understand exactly which product configuration each row represents.

6. Product Identifiers Are Missing, Wrong or Invented

Identifiers such as GTIN can help distinguish one product from another.

But incorrect identifiers can be worse than leaving information unresolved.

Google lists incorrect GTIN information among common product-data issues.

If a product has an official identifier, use information from a reliable product or manufacturer source.

Do not invent a GTIN simply to fill an empty field.

The goal is not to make every cell look complete.

The goal is to make the submitted information accurate and defensible.

7. Your Feed and Website Have Slowly Drifted Apart

This final problem is broader than a single field.

Stores change constantly.

Prices change.

Inventory changes.

Descriptions get edited.

Variants are added.

URLs move.

Promotions begin and end.

A product data file that was accurate when exported may gradually stop matching the live store.

Google's landing-page requirements make clear that important product information on the destination page should correspond with the submitted product data.

So product-data quality is not only a formatting problem.

It is also a synchronization problem.

What Should You Check First?

Do not immediately rewrite your entire catalog.

Start with a small sample of real products and compare the most important signals:

product → exact URL → exact variant → price → availability → structured data

If those already disagree on a few sampled products, you have evidence that a wider catalog review may be useful.

If they agree, you have eliminated several common sources of uncertainty before making unnecessary changes.

Check Three Product Pages Before Auditing the Whole Catalog

Mingche offers a free, read-only Product Page Check for three distinct product URLs from the same store.

The check looks at public-page signals including readable price, availability, variants and structured data.

You do not need to upload your full catalog, and the check does not modify your website. It is a small sample rather than a full Google Merchant audit.

Start with three products and find out whether the data on your pages is telling a consistent story.

[Start the Free Product Page Check →]https://www.mingcheip.com/start?utm_source=chatgpt.com

Important note

A product-data check or correction cannot guarantee approval, inclusion, ranking, traffic or sales on Google. Google makes its own eligibility and policy decisions. The purpose of an audit is to identify evidence-backed issues and help merchants understand what may need attention.

Comments

Post a Comment

Popular posts from this blog

Before you upload a product feed: check the row, the variant and the page

A product file can look tidy and still describe the wrong offer. The useful question is whether each row points to the product a customer can actually buy, at the price and availability you submitted. Start with a copy of your catalog export. Keep the original and record when it was exported. The following is a short review workflow for English product data and US-dollar offers. It is a starting point, not a complete Merchant Center compliance checklist. First confirm which file you are checking A current-looking spreadsheet can still cover only a selected set of products, or differ from the file Merchant Center last received. Keep the export time and the source version with your notes. Working from Shopify: use the export selection and coverage checklist to distinguish the rows you selected from the full catalogue. A Shopify export is source evidence, not automatically a ready-to-upload Google feed. The file looks right but an issue remains: check the last file Merchant Center ac...
Read more
Image
  Merchant Center Says “Missing Brand” — Should You Use Your Store Name? You open Merchant Center and see: Missing brand The obvious fix seems easy. Your store is called: YourStore So you type: Brand: YourStore Save. Done? Not necessarily. The brand field is supposed to describe the brand of the product , not simply the company selling it. That distinction matters. Before changing hundreds of products, I would first figure out which of these situations you are actually in: You sell another company's product. You manufacture the product yourself. You sell a private-label product. The product genuinely has no recognized brand. Those four situations should not automatically receive the same value. First: Ask Who Actually Branded the Product Imagine your store sells a pair of Adidas shoes. Your business is called: YourStore The correct brand is not: YourStore It is: Adidas because that is the product brand shoppers recognize. Google's current brand specification says the value sho...
Read more

Before importing a repaired product CSV, ask for the change log

A repaired CSV should come with an explanation of what changed. Otherwise, you are being asked to upload a file without knowing whether it fixed a formatting problem or silently guessed a product fact. Keep the original export. Before importing any proposed replacement, review a change log that lets you trace a changed field back to the same product and its evidence. This is an illustrative workflow, not a customer case study or a promise that every field can be repaired. Prepared with AI assistance by Rowmint, the product-data education brand of Mingche Commerce. Three rows, three different decisions Example issue Evidence available Appropriate next step A field contains accidental surrounding spaces The receiving field's rules and the intended value are known Propose a supported formatting correction; show old and new values A product identifier is missing No manufacturer record supplied Request the source identifier or relevant product evidence; do not invent digits The lin...
Read more