Google Ads guide

Best Google Shopping Feed Settings for Online Stores

The best Google Shopping feed settings for an online store preserve the exact sellable item from source to selected landing page: stable product and variant keys, product type, options, title, image, price, currency, availability, shipping, market, structured data, and checkout. Configure product-level identity separately from variant-level offers, trace every export transformation, and verify the rendered customer path instead of relying on a synchronization status.

This page is educational and does not promise Google approval, traffic, conversion, or a particular platform feature. Start with Google’s product-data guidance, then assign catalog, platform, export, inventory, pricing, fulfillment, market, and compliance owners. Related work is covered in how to optimize a Google Shopping feed for online stores, Shopping feed title optimization, and product feed rules.

Define account, market, and source scope

Record account, domain, country or region, language, currency, channel or export method, destination, online or local program, catalog population, source type, schedule, version, freshness, reviewer, and rollback. State whether the source is a platform channel, app, API, custom feed, supplemental source, or combination. Do not assume every connector maps products, variants, images, inventory, or markets identically.

Use the primary catalog for population and stable identity. Use page and structured product data for rendered selection; inventory and pricing systems for offers; fulfillment for delivery; and approved supplemental data for enrichment. Name owners for product and variant IDs, options, titles, images, price, stock, shipping, and market values.

Set field precedence

Catalog may own product name, brand, product type, collection, and product ID. Variant data owns variant ID, options, SKU, identifier, image, price, inventory, and child-specific content. The page owns selected state and customer path. Inventory owns availability, pricing owns price, and fulfillment owns delivery. Document conflicts instead of silently taking the newest value.

Configure product and variant identity

Use stable keys through packaging, pricing, content, inventory, and collection changes. Decide which options create distinct feed rows:

  • size, color, width, material, flavor, scent, finish, or capacity;
  • pack count, weight, dimensions, model, compatibility, or included quantity;
  • subscription term, refill, bundle, pair, case, replacement part, or condition;
  • market, language, currency, or regional offer where the product differs materially.

Keep family grouping and product description separate from variant-level offer data. A parent handle, URL, collection, or title is not a substitute for a variant key. A default option should not make every child identical or available.

Match the exact page state

For each variant, define product ID, variant ID, URL, selected option, title, image, product type, category, price, currency, availability, shipping, market, structured data, and checkout behavior. A family page is acceptable only when the submitted child is selected or clearly selectable and page facts change with it. Test default and non-default variants on mobile.

Set titles, descriptions, and categories

Build titles from product and variant facts: brand, product name or type, model, material or key attribute, option value, size or quantity, and other facts that distinguish the offer. Use Shopping feed title optimization for order and clarity, then compare the title with the selected page.

Keep SKU, collection, campaign, audience, routine, and temporary promotion separate from identity. Descriptions can state supported materials, dimensions, ingredients, use, care, compatibility, included quantity, condition, subscription context, and delivery. Do not infer claims from tags, collections, custom fields, or export labels unless the source and market support the exact wording.

Review the Google product category against the item sold. An accessory, refill, replacement part, bundle, pair, case, or subscription should not inherit the parent’s category, image, quantity, or offer without review.

Keep transformations auditable

Separate title, product type, category, brand, options, description, image, price, sale price, inventory, shipping, URL, and page transformations. Do not use a title rewrite to solve a missing variant value. Record original, transformed, processed, and rendered values.

Configure images, options, and landing pages

Use an image that represents the exact variant when color, material, size, pack, or configuration changes the buying decision. Add supporting images for package quantity, dimensions, included components, compatibility, or labels. Lifestyle images are context, not a substitute for product evidence.

Set the page to expose the same child as the feed. Compare product and variant IDs, URL, selected option, title, description, product type, category, image, structured data, size, color, material, pack, quantity, ingredients, compatibility, price, stock, shipping, add-to-cart, subscription, and checkout.

Test parent and child behavior

Open a family page, select a non-default option, reload the URL, and use a mobile viewport. Confirm that selection persists and that title, image, structured data, price, availability, and add-to-cart state describe it. Test one available and one unavailable child; the parent should not conceal the difference.

Set price, inventory, and lifecycle states

Assign price, sale price, currency, condition, quantity, availability, handling, and delivery from authoritative store and fulfillment sources and retain timestamps. Use Google’s availability guidance for in stock, out of stock, preorder, and backorder. A supplier or warehouse state is not automatically an online offer in the selected market.

Define settings for new products, new variants, packaging changes, price changes, sale periods, seasonal items, subscriptions, refills, bundles, pairs, cases, preorder, backorder, discontinued variants, out-of-stock children, local-only inventory, and unchanged controls. Preserve stable IDs and history. Do not mark every variant available because one location has stock.

If an item should not appear in a destination, use the approved product or destination mechanism rather than a false availability value. Compare one-time and recurring quantity, price, delivery, and cancellation context at checkout. Check whether the page sells one unit, case, pair, bundle, refill, or subscription.

Configure markets, shipping, and localization

Record target country or region, language, currency, unit system, domain or market context, shipping service, handling time, tax or delivery context, pickup, and exclusions. An online store can have different inventory, price, translation, and delivery by market.

Localize product and option wording naturally while preserving source values and identifiers. Review ingredients, materials, claims, sizes, units, pricing, availability, returns or delivery language, structured data, and page behavior for the selected market. Do not copy global claims, certifications, health, safety, or shipping promises into every market without evidence. Separate online, local, warehouse, and tester inventory.

Control transformations, rules, and supplemental sources

Document the primary catalog, platform, export or channel, app or API transformation, supplemental source, inventory source, pricing source, fulfillment source, market source, and page source. Include matching key, target field, condition, precedence, market, language, version, effective period, freshness, and rollback. Product feed rules may normalize approved values, but they must not invent product identity, variant options, ingredients, compatibility, price, inventory, shipping, or claims.

Keep original, transformed, processed, and rendered values visible. A title transformation that adds a size must use the exact variant. A supplemental source that changes a product option must match product and variant keys. If an export and page disagree, retain the exception and route it to catalog or commerce rather than silently overwriting the customer path.

Assign diagnostic ownership

Route product or variant identity and option issues to catalog; claims, ingredients, or regulated wording to the responsible reviewer; stock to inventory; price to pricing; delivery to fulfillment; export, selector, structured-data, or page issues to commerce; and account issues to the Merchant Center owner. Use Merchant Center diagnostics to locate issues, then reproduce the selected-market page path.

An alert should include product ID, variant ID, market, source timestamp, issue reference, observed values, and permitted next action. “Processed” does not prove that the submitted option, image, price, or availability is what the shopper can purchase.

Test settings before activation

Build a matrix across products with one variant, many variants, size and color options, material or flavor options, pack or quantity options, bundles, subscriptions, refills, accessories, replacement parts, and market-specific offers. Include products whose default page option differs from the submitted child. Vary price, sale state, inventory location, language, currency, image, and shipping.

Include new product, new variant, package change, price change, sale period, seasonal item, subscription, refill, bundle, preorder, backorder, discontinued variant, out-of-stock child, local-only inventory, and unchanged controls. Compare source, export, processed feed, selected page, image, title, options, structured data, price, availability, shipping, add-to-cart, and checkout. Retain changed, rejected, unmatched, and unchanged results.

Verify the deciding store setting

For size or color, verify option value, image, price, and URL. For a bundle or pack, verify included quantity. For a subscription, verify cadence and recurring offer. For a market, verify currency, language, inventory, delivery, and structured data. For an app or API transformation, verify the rendered page, not only the export result.

Review common online-store setting mistakes

Avoid:

  • one parent product row for every variant offer;
  • using handle, collection, SKU, or title instead of a stable variant key;
  • hiding a material size, color, material, flavor, pack, compatibility, or subscription option in a parent;
  • allowing the default page variant to replace the submitted child;
  • applying one image, price, inventory, or shipping value to every variant without evidence;
  • marking every child available because one location or supplier has stock;
  • copying tags, metafields, claims, ingredients, certifications, or market values globally;
  • treating an app export, channel sync, or processing confirmation as proof of page and checkout correctness;
  • changing a shared transformation without reviewing the affected product and variant population.

Online-store settings checklist

Before sign-off, confirm:

  1. Account, market, language, currency, channel, destination, product population, and sources are explicit.
  2. Product and variant keys, options, handles, titles, categories, images, quantities, and condition are stable.
  3. Export transformations, structured data, price, inventory, shipping, and page state are traceable.
  4. Exact page option, price, availability, subscription, bundle, and checkout agree.
  5. Online and local inventory, market translations, units, and delivery context are separated.
  6. Rules, supplemental sources, freshness, diagnostics, ownership, review, and rollback are documented.
  7. Single-variant, multi-variant, bundle, subscription, refill, accessory, and market edge cases have been tested.

The settings are ready when a shopper can identify the exact online-store variant and see its current offer on the matching page. Keep uncertain option, quantity, inventory, market, claim, and delivery values visible as exceptions; a synchronized export is not proof of a correct customer path.