Google Shopping Feed Optimization Checklist for Fashion Ecommerce

Use this fashion ecommerce Google Shopping feed checklist to verify that the feed represents the exact brand, style, seller, variant, market, and offer a customer can purchase. Review product IDs and item groups, titles, categories, size and color, images, landing pages, price, availability, shipping, localization, source rules, and diagnostics together. Google’s apparel and accessories guidance is a useful reference, but current Merchant Center requirements and source-owner decisions govern the final result.

This checklist is educational and does not guarantee eligibility, placement, or performance. Use how to optimize a Google Shopping feed for fashion ecommerce for context, best Google Shopping feed settings for fashion ecommerce for configuration, and Merchant Center diagnostics when a check fails. Do not use a pass as authorization to change inventory, price, page content, or campaigns without the responsible owner.

Define scope and sign-off ownership

Record account, market, language, currency, channel, destination, seller or brand population, source version, product and variant grain, review owner, reviewer, and reason for the review. State whether this is a launch, seasonal refresh, market expansion, source migration, rule change, incident, or recurring quality review.

Include owned brands, marketplace sellers, private label, resale, rental, made-to-order, footwear, bags, jewelry, accessories, sets, and bundles only if they are in scope. Do not let an editorial collection such as “new season” silently define product category or availability.

Use explicit exception states

Mark each check pass, fail, not applicable, blocked by missing evidence, or not yet verified. For failures, record product or variant ID, seller, market, field, current value, expected value, owner, severity, permitted action, and reviewer. An upload confirmation is not a pass for a page or attribute check.

Identity, brand, seller, and style checklist

[ ] Product IDs are stable, unique, and tied to the commerce source.
[ ] Child or variant IDs remain stable across title, price, and collection updates.
[ ] Item-group IDs include only variants of the same style or product family.
[ ] Brand, manufacturer, retailer, seller, and house-brand meanings are separate.
[ ] Style code, SKU, season, collection, and product type are not confused.
[ ] No row is an orphan, duplicate, or cross-brand item-group join.
[ ] Owned inventory, marketplace, resale, rental, and made-to-order populations are identified.
[ ] GTINs or manufacturer identifiers are valid where supplied and are not fabricated.
[ ] The product is actually offered in the target market and destination.

Inspect one straightforward product and one complex product with many sellers or variants. A catalog can pass an ID uniqueness check while still joining the wrong designer, season, or seller to a child row.

Variant identity checklist

[ ] Color, size, size system, size type, fit, width, length, or other options match the customer selector.
[ ] Variant-specific price and availability are attached to the correct child.
[ ] A family page or variant URL resolves to the same offer represented in the row.
[ ] New, missing, disabled, and sold-out options are distinguished.
[ ] Sets, packs, bundles, and accessories have their own identity when the purchasable product changes.
[ ] Custom, personalized, rental, and resale conditions are visible in the product and page contract.

Title, description, and taxonomy checklist

Review titles and descriptions for each fashion category:

[ ] Brand and product or garment type are clear.
[ ] Style or model is present when it distinguishes the offer.
[ ] Color, size type, size, fit, material, audience, width, length, or quantity appear when relevant and supported.
[ ] Important product facts appear before collection slogans or optional editorial language.
[ ] Titles avoid internal codes, repeated punctuation, all-caps, keyword stuffing, and unsupported urgency.
[ ] Temporary promotions do not remain in persistent titles after their effective period.
[ ] Descriptions explain supported item facts and do not invent sustainability, fit, authenticity, or performance claims.
[ ] Internal product type, Google product category, collection, brand, seller, and custom labels have distinct meanings.
[ ] Dresses, coats, activewear, footwear, bags, jewelry, accessories, sets, and parts are reviewed with relevant attributes.

Use Shopping feed title optimization to review title order and truncation. Use Google product category mapping for ambiguous category branches. Do not fill a missing source value with a plausible phrase just to complete a title.

Evidence for title changes

For each changed title, retain current value, proposed value, page value, selected variant, source, reason, rule version, reviewer, and rollback. Include one long title, one short title, a translated title, a marketplace seller title, and a product with a variant-specific difference in the test set.

Apparel and fashion attribute checklist

[ ] Size value agrees with the page selector.
[ ] Size system and size type are explicit where the market requires them.
[ ] Petite, tall, plus, maternity, youth, infant, adaptive, one-size, and custom products are not flattened into the wrong standard.
[ ] Color values agree with page text, swatches, image, and title.
[ ] Pattern, material, fit, and personalization come from an approved source.
[ ] Footwear width, length, and regional size details are mapped correctly.
[ ] Jewelry metal, length, stone, and quantity describe the actual item.
[ ] Bags, accessories, and replacement parts are not assigned the parent garment’s attributes.
[ ] A localized market uses the right units, size terminology, colors, and page language.

Do not convert a custom measurement into a fixed size or a local size into another system without an approved mapping. Preserve original and converted values for review.

Image and landing-page checklist

Open exact product and variant pages and verify:

[ ] Page works in target market and language.
[ ] Brand, product name, image, and selected variant match the row.
[ ] Color, size, fit, quantity, and configuration are selected or clearly selectable.
[ ] URL parameters, redirects, and canonical behavior do not lead to an unrelated default.
[ ] Main image shows the actual item and variant where required.
[ ] Variant images do not show the wrong colorway, size, or product.
[ ] Images load, are clear, and are not obscured by unsupported promotional overlays.
[ ] Price, currency, sale state, availability, delivery, and purchase controls match.
[ ] Structured data, if present, agrees with the visible product page.
[ ] Seller or fulfillment information matches the submitted offer.

Google’s product-data optimization guidance emphasizes matching submitted product data to the landing page. A feed-row pass is incomplete until the click path and exact option have been checked.

Difficult page states

[ ] Disabled or sold-out swatches are represented accurately.
[ ] Store pickup and regional availability are separated from online delivery.
[ ] Size guides do not change the meaning of the submitted size.
[ ] Personalization fields, custom prices, and delivery dates are visible where relevant.
[ ] Rental, resale, preorder, backorder, and made-to-order pages expose truthful purchase conditions.
[ ] A generic collection page is not used to conceal an unavailable or mismatched product.

Price, availability, shipping, and lifecycle checklist

[ ] Exact variant price is supplied, including size, seller, or configuration differences.
[ ] Currency, decimal format, sale price, and effective dates match page and checkout.
[ ] Inventory source, source time, feed time, and page observation are retained.
[ ] In-stock, out-of-stock, preorder, backorder, rental, and made-to-order states are distinct.
[ ] A product available in one store or country is not represented as available everywhere.
[ ] Shipping service, region, handling, delivery, pickup, exclusions, and seller promise agree.
[ ] Collection changes do not leave discontinued variants available.
[ ] A destination or visibility choice is not disguised as an inventory state.

Use the current availability guidance for supported values and page consistency. See out-of-stock product alerts when the review needs a recurring mismatch signal.

Market and localization checklist

[ ] Account, market, language, currency, and destination are explicit for each source.
[ ] Translated titles and descriptions preserve brand, model, and product identity.
[ ] Color, size, fit, material, units, and measurements use natural target-market terms.
[ ] Size systems are mapped with evidence rather than copied from the source market.
[ ] Product pages and structured data use the same localized values.
[ ] Shipping, delivery, returns, seller, and availability differ by market only when documented.
[ ] A global catalog row is not assumed to be offered in every market.

Do not use a single global feed setting to cover different currencies, delivery contracts, or regional inventory unless the source contract proves they are identical.

Source, rule, and processing checklist

For each feed or transformation, record:

[ ] Primary source and supplemental source ownership.
[ ] Attribute-by-attribute precedence and matching keys.
[ ] Product, variant, seller, market, and language scope.
[ ] Rule condition, target field, source version, effective period, and rollback.
[ ] Input and output values, matched and unmatched rows, changed count, and rejected count.
[ ] Generation, submission, processing, page observation, and checkout timestamps.
[ ] Alert route, diagnostic reference, reviewer, and approval.
[ ] A fallback for missing or stale data that does not invent product facts.

Product feed rules explains why transformations should be narrow and reviewable. Keep title, category, availability, price, shipping, and campaign settings separate. A rule that passes processing but changes the wrong field fails this checklist.

Diagnostics and recovery checklist

When an issue appears:

[ ] Original issue text and scope are preserved.
[ ] Affected products, variants, sellers, markets, and destinations are known.
[ ] Source, feed output, Merchant Center processing, page, structured data, and checkout are compared.
[ ] Root-cause hypothesis is separated from observed evidence.
[ ] The likely owner and smallest authorized correction are identified.
[ ] Before and after values, source versions, and rollback are retained.
[ ] Processed result, diagnostics, page, variant, and customer path are rechecked.
[ ] Result is classified fixed, partial, unresolved, superseded, or unable to verify.
[ ] Any review request follows current guidance and owner authorization.

Use Merchant Center diagnostics to structure this evidence. Do not close an incident because a source uploaded or a warning disappeared from one screen.

Launch and recurring fashion-feed review

For a launch, use the following order:

Approve account, catalog boundary, markets, sources, variant grain, and owners.
Test simple and complex products across brands, sellers, categories, and lifecycle states.
Review generated rows and exact landing pages.
Process the source and inspect diagnostics, warnings, and changed values.
Verify price, availability, images, selectors, shipping, and checkout.
Record the reviewed version, exceptions, evidence, and rollback.

For a recurring review, inspect new and changed rows first, then products with recurring diagnostics, stale data, or market differences. Seasonal reviews should include new collection labels, sale dates, discontinued items, size systems, localized pages, and new sellers. The review cadence should be derived from catalog change risk and owner expectations, not invented as a universal target.

Final sign-off criteria

Sign off only when:

identity, brand, seller, style, and variant relationships are correct;
titles, descriptions, categories, and attributes use supported meanings;
images, pages, selected options, prices, availability, and shipping agree;
localization and lifecycle states are explicit;
sources, transformations, ownership, freshness, and rollback are documented; and
diagnostics and exceptions have evidence and a named next action.

A fashion ecommerce Shopping feed passes when a reviewer can show what each row represents, why its important values are present, and how the customer path was verified. The checklist controls evidence and scope; it does not replace current Google requirements, policy review, or product-owner authority.