Google Shopping Feed Optimization Checklist for Jewelry Stores

Use this jewelry-store Google Shopping feed checklist to prove that each row represents the exact piece, material, stone, size, quantity, condition, and customer offer. Review IDs, item groups, titles, categories, metal and stone evidence, images, pages, price, availability, delivery, market context, source rules, and diagnostics together. Google’s product-data guidance is a useful reference, while current requirements and jewelry-owner evidence govern the result.

This checklist is educational and does not guarantee eligibility, authenticity, approval, or sales. Use how to optimize a Google Shopping feed for jewelry stores for context, best Google Shopping feed settings for jewelry stores for configuration, and Merchant Center diagnostics when a check fails. Do not treat a pass as permission to change material claims, price, inventory, pages, or campaigns without authority.

Define scope and sign-off ownership

Record account, market, language, currency, channel, destination, source version, product population, piece and variant grain, catalog owner, jewelry or compliance owner, fulfillment owner, reviewer, and reason for review. State whether this covers a launch, collection refresh, material-source change, market expansion, personalization flow, incident, or recurring quality review.

List in-scope rings, earrings, necklaces, bracelets, watches, body jewelry, charms, loose stones, sets, personalized pieces, fashion jewelry, fine jewelry, vintage, resale, repaired items, and replacement components. Keep collection, occasion, and style labels separate from product identity and evidence.

Use explicit exception states

Mark each check pass, fail, not applicable, blocked by missing evidence, or not yet verified. For each exception, record piece or variant ID, field, current value, expected value, source owner, severity, permitted action, reviewer, and next step. A processed source is not a material or page pass.

Piece, variant, pair, and set identity checklist

[ ] Piece IDs are stable, unique, and tied to the catalog source.
[ ] Variant IDs remain stable through price, collection, and description changes.
[ ] Item groups connect only variants of the same piece or product family.
[ ] Brand, maker, model, SKU, collection, condition, and product type are separate.
[ ] One piece, pair, pendant with chain, gift set, box, charm, and replacement component have correct identity.
[ ] Included quantity and components are explicit.
[ ] No row is duplicated, orphaned, or joined to a different stone, metal, or size.
[ ] Manufacturer or maker identifiers are valid where supplied and are not fabricated.
[ ] The offer is actually available in the target market and destination.

Inspect a single item and a complex variant family with size or personalization. A parent-level check can pass while one ring size or earring pair points to the wrong page or quantity.

Variant checks

[ ] Ring size, chain length, bracelet length, metal color, stone, engraving, and quantity match the selector.
[ ] Variant-specific price, image, availability, condition, and lead time are attached to the right child.
[ ] A pair is not represented as one piece, and a single piece is not represented as a pair.
[ ] Sets, bundles, loose stones, and replacement parts describe what is actually sold.
[ ] Custom and made-to-order options have explicit purchase and delivery behavior.

Material, stone, size, and evidence checklist

[ ] Metal, purity, plating, tone, finish, stone, treatment, and count come from an approved source.
[ ] Gold tone, plated, simulated, lab-created, natural, and solid-material meanings are not conflated.
[ ] Stone size, metal weight, dimensions, ring size, chain length, and units are defined.
[ ] Ring-size system and local measurement conventions are explicit.
[ ] Certification, authenticity, origin, hypoallergenic, safety, and treatment claims have evidence.
[ ] Condition such as new, fine, fashion, vintage, resale, estate, repaired, or refurbished is sourced.
[ ] Missing material, stone, purity, authenticity, or size evidence remains visible rather than guessed.
[ ] Converted or localized values retain original source and mapping evidence.

For each changed material or stone value, retain source, source version, piece or variant ID, current and proposed values, reviewer, page wording, and permitted claim. Do not infer a high-value fact from a product name or image.

Title, description, and category checklist

[ ] Title identifies brand or maker, piece type, model or style, and meaningful material or stone detail.
[ ] Ring size, chain length, pair count, quantity, or configuration appears when relevant.
[ ] Titles avoid unsupported “solid,” “genuine,” “certified,” “authentic,” or “hypoallergenic” claims.
[ ] Titles do not rely on occasion, collection, internal SKU, keyword stuffing, or expired promotion.
[ ] Descriptions use supported material, stone, purity, treatment, care, condition, quantity, and delivery facts.
[ ] Product type and Google product category have separate meanings.
[ ] Rings, earrings, necklaces, bracelets, watches, charms, stones, sets, parts, and boxes are reviewed by actual item sold.
[ ] Fashion, fine, vintage, resale, custom, and repaired populations are scoped separately when evidence differs.

Use Shopping feed title optimization for title order and page agreement. Use Google product category mapping for ambiguous pieces, sets, and components.

Title evidence

For each changed title, retain current and proposed values, page title, selected option, source, reason, rule version, reviewer, and rollback. Test a ring, earring pair, necklace, custom pendant, set, and a product with a named metal or stone.

Image and landing-page checklist

Open exact piece and variant pages and verify:

[ ] Page works in the target market and language.
[ ] Piece, brand, model, image, metal, stone, condition, and selected option match the row.
[ ] URL parameters and redirects do not select another size, metal, or default piece.
[ ] Main image represents the actual item and included quantity.
[ ] Variant image shows the submitted stone, finish, color, or size.
[ ] Styled imagery does not imply that unpurchased pieces are included.
[ ] Price, currency, sale period, availability, lead time, delivery, and purchase control agree.
[ ] Structured data, if present, matches visible values.
[ ] Mobile selectors and personalization flows expose the same offer.

Google’s product-data guidance emphasizes matching submitted data to landing pages. A source pass is incomplete until the exact jewelry page and option are checked.

Difficult page states

[ ] Out-of-stock sizes, stones, and metal options are not presented as available.
[ ] Pair, set, pendant-and-chain, and included-quantity meanings are visible.
[ ] Custom, engraved, made-to-order, preorder, and backorder pages show truthful timing.
[ ] Vintage, resale, repaired, and fine-jewelry condition and documentation are clear.
[ ] Local pickup and insured online delivery are distinct.
[ ] Certification or authenticity wording is supported by the page and source.

Price, condition, availability, and fulfillment checklist

[ ] Exact piece, size, stone, metal, quantity, and custom option price is supplied.
[ ] Currency, sale price, effective period, and checkout agree.
[ ] Condition, warranty, authenticity documentation, and included items match the page.
[ ] Inventory source, source timestamp, feed timestamp, and page observation are retained.
[ ] In-stock, out-of-stock, preorder, and backorder states are distinct.
[ ] Insured shipping, signature, pickup, region, handling, and exclusions match the customer promise.
[ ] A showroom or supplier item is not represented as an online purchase without evidence.
[ ] A destination choice is not disguised as an inventory state.

Use the current availability guidance for supported values and consistency.

Market and localization checklist

[ ] Account, market, language, currency, destination, size system, units, and delivery area are explicit.
[ ] Brand and piece identity are preserved through translation.
[ ] Metal, stone, purity, treatment, authenticity, and certification terms are reviewed locally.
[ ] Ring, chain, and bracelet units use target-market conventions.
[ ] Page, title, structured data, variant, warranty, and delivery use compatible local values.
[ ] A global purity, authenticity, price, or shipping claim is not copied without evidence.

Source, rule, and processing checklist

For each source or transformation, verify:

[ ] Catalog, maker, supplier, compliance, supplemental, inventory, pricing, and fulfillment ownership is named.
[ ] Attribute precedence and matching keys preserve piece and variant grain.
[ ] Product, market, language, condition, seller, and destination scope is explicit.
[ ] Rules have conditions, target fields, source version, effective period, and rollback.
[ ] Derived values do not invent metal, stone, purity, authenticity, size, condition, or availability.
[ ] Input, output, matched, unmatched, changed, rejected, and unchanged rows are retained.
[ ] Generation, submission, processing, page, and checkout timestamps are available.
[ ] Alert route, diagnostic reference, reviewer, and approval are recorded.

Product feed rules explains how to keep transformations narrow. Keep title, category, material, stone, size, image, quantity, price, condition, inventory, shipping, and campaign settings separate.

Diagnostics and recovery checklist

When an issue appears:

[ ] Original issue text and scope are preserved.
[ ] Affected pieces, variants, pairs, sets, markets, suppliers, and destinations are known.
[ ] Source, generated row, processing, page, structured data, and checkout are compared.
[ ] Observed evidence is separated from the root-cause hypothesis.
[ ] Catalog, product, compliance, pricing, inventory, fulfillment, or account owner is identified.
[ ] Before and after values, source versions, and rollback are retained.
[ ] Processed result, selected option, image, material, stone, size, quantity, condition, price, and availability are rechecked.
[ ] Result is fixed, partial, unresolved, superseded, or unable to verify.
[ ] Any review follows current guidance and owner authorization.

Use Merchant Center diagnostics to structure the evidence. Do not close an issue because a feed uploaded or a warning disappeared without checking the exact piece and customer path.

Launch and recurring jewelry-feed review

For a launch or major catalog update:

Approve product families, piece and variant grain, sources, markets, evidence owners, and fulfillment.
Test simple, sized, custom, set, high-value, resale, and localized products.
Review generated rows, images, exact pages, selected options, and claims.
Process the source and inspect diagnostics, rejected rows, changed values, and freshness.
Verify material, stone, size, condition, price, availability, insured shipping, and checkout.
Record source version, exceptions, evidence, approval, and rollback.

For recurring review, inspect new and changed pieces first, then recurring material, size, page, price, inventory, condition, and fulfillment failures. Derive cadence from product and source change risk rather than inventing a universal interval.

Final jewelry-feed sign-off

Sign off only when:

piece, variant, pair or set, brand, maker, condition, and included-item identity is stable;
material, stone, purity, size, quantity, category, title, and image values are supported;
pages, prices, availability, lead time, delivery, and checkout agree;
market, size, language, authenticity, and claims context is explicit;
sources, rules, ownership, freshness, and rollback are documented; and
diagnostics and exceptions have evidence and a named next action.

A jewelry-store Shopping feed passes when a reviewer can show what piece is sold, what material and quantity are supported, which option the customer receives, and how the page was verified. The checklist controls evidence and scope; it does not replace current requirements or jewelry-owner approval.