Your product feed says size M. Does the link open size S?

The feed says size M. The product page opens with size S selected. The shirt looks identical, so the mistake can survive a quick visual check.

Before changing a price or marking a row as ready, establish which variant the row represents and what its exact submitted URL opens.

Illustrative example, not a customer result. Prepared with AI assistance by Rowmint, the product-data education brand of Mingche Commerce.

A small mismatch that changes the whole comparison

EvidenceFeed rowLanding page at first load
ProductBlue everyday teeBlue everyday tee
VariantTEE-BLUE-MSize S selected
SizeMS

A page showing the right style is not enough to establish a variant match. Google recommends linking to the page with the correct variant already selected. Size and colour information should still be supplied in their appropriate product-data attributes.

A five-minute check for one row

  1. Start from the exported row. Record its ID, intended size, colour and market. Copy the exact link from that row; do not find a similar product through the store navigation.
  2. Open a fresh browser session. Note the option selected before touching the page. A remembered choice from an earlier visit can disguise a bad default.
  3. Check the merchant's source record. Confirm that the row really is meant to describe size M. A familiar filename or image is not proof.
  4. Correct the cause. If the source confirms M, use the store's supported link that opens M. If the row itself describes the wrong variant, correct the source mapping instead. Do not invent a URL parameter and assume the store honours it.
  5. Retest the exact link. Check the selected variant and then its current price and availability. Save the evidence and the time checked.

Choose the next check from what you actually observed

  • The link opens the wrong size: follow the exact-variant URL checklist. Keep the original link and the selected option in your notes before changing a mapping.
  • The correct size opens, but stock differs: use the availability-mismatch walkthrough. Compare the same variant and observation time; another size being in stock does not establish that this one is available.

Both guides are free. A difference is a reason to investigate the current source, not proof that either the file or the page should be overwritten.

What if the store cannot preselect a variant?

Keep that item unresolved and ask the store owner or developer how that storefront supports variant links. Replacing the feed's size with whatever loads first can make the fields look consistent while changing which product is being advertised.

This checklist is practical guidance, not a claim that every step is performed by our free check. Our paid audit has a defined scope, and sampled URLs cannot prove that every page in a catalogue matches. Supported CSV corrections do not edit a live storefront or guarantee platform approval.

Start small: run a free product-page check and review the service scope.

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