Google Shopping Feed Optimization Checklist for Furniture Stores

Use this furniture-store Google Shopping feed checklist to verify that every row describes the exact item or configuration a customer can buy, including dimensions, material, finish, included components, price, availability, image, and delivery. Review the product source, generated feed, Merchant Center result, landing page, and checkout together. Google’s product-data guidance is a useful reference, but current requirements and the store’s product and fulfillment owners determine the final decision.

This checklist is educational and does not guarantee eligibility, placement, delivery, or sales. Use how to optimize a Google Shopping feed for furniture stores for context, best Google Shopping feed settings for furniture stores for configuration, and Merchant Center diagnostics when a check fails. A checklist result is not permission to change prices, inventory, pages, freight, or campaigns without authority.

Define scope and sign-off

Record account, market, language, currency, channel, destination, source version, product population, product or configuration grain, catalog owner, fulfillment owner, reviewer, and reason for review. State whether the work covers a launch, supplier migration, seasonal refresh, freight change, rule change, market expansion, or incident.

List in-scope families such as sofas, chairs, tables, beds, mattresses, desks, storage, outdoor furniture, lighting, rugs, décor, replacement parts, room sets, or services. Keep room collections and design styles separate from product category. Decide how showroom-only, local pickup, stocked, made-to-order, preorder, backorder, and discontinued items are handled.

Use pass and exception states

Mark each check pass, fail, not applicable, blocked by missing evidence, or not yet verified. For an exception, record product or configuration ID, field, current value, expected value, source owner, severity, permitted action, reviewer, and next step. A source upload confirmation is not proof that dimensions or delivery are correct.

Product and configuration identity checklist

[ ] Product IDs are stable, unique, and owned by the catalog source.
[ ] Configuration or child IDs remain stable when price, finish, or collection changes.
[ ] Item-group relationships connect variants of the same product family only.
[ ] Brand, supplier, retailer, room collection, style, and product type have separate meanings.
[ ] Models, SKUs, included components, and package quantities are not confused.
[ ] Sets, bundles, modular products, replacement parts, and services have the correct identity.
[ ] No row is duplicated, orphaned, or joined to an unrelated configuration.
[ ] The offer is actually available in the target market and destination.
[ ] Manufacturer identifiers are valid where supplied and are not fabricated or reused across unrelated products.

Inspect one simple item and one configurable item with multiple finishes, dimensions, orientations, or packages. Identity can look correct at the parent level while a child row points to the wrong page or inherits the wrong price.

Configuration checklist

[ ] Size, width, height, depth, orientation, finish, material, color, quantity, and included components match the customer selection.
[ ] Configuration-specific price and availability are attached to the correct child.
[ ] Modular, extendable, adjustable, and personalized products expose the chosen result.
[ ] Room sets and bundles describe exactly what is included.
[ ] Optional assembly or installation is not silently included or excluded.
[ ] Base-product pages are not used for a premium configuration without a clear selection path.

Dimensions, materials, and attribute checklist

[ ] Width, height, depth, weight, seat count, capacity, or mattress size have defined meanings.
[ ] Assembled dimensions are separate from packaged or shipping dimensions.
[ ] Units are explicit and correctly localized for the target market.
[ ] Dimensions match the product page and the selected configuration.
[ ] Material and finish values come from an approved product or supplier source.
[ ] Veneer, solid wood, engineered wood, metal, glass, textile, leather, and synthetic distinctions are supported.
[ ] Named finishes and colors agree with swatches, images, titles, and page copy.
[ ] Missing dimensions, capacities, materials, or safety claims are visible rather than guessed.

Do not infer a material from a product name or styled image. Preserve source and converted dimensions where a market mapping is used, and retain the evidence for rounding or unit conversion.

Dimensions evidence

For each changed dimension, record source, source version, current value, proposed value, unit, assembled or packaged meaning, product or configuration ID, reviewer, and page observation. A dimension should be tested on a representative product that has a variant selector and a product with a recent supplier update.

Title, description, and taxonomy checklist

[ ] Title identifies brand or maker, product type, model, and important configuration facts.
[ ] Size, finish, material, shape, capacity, quantity, or orientation appears when it distinguishes the item.
[ ] Titles do not rely on room labels, design slogans, internal SKUs, or temporary promotions.
[ ] Descriptions use supported construction, care, assembly, included-component, and delivery facts.
[ ] Unsupported solid-wood, natural-fiber, capacity, safety, or certification claims are absent.
[ ] Internal product type and Google product category are separate.
[ ] Sofas, chairs, tables, beds, mattresses, desks, storage, outdoor furniture, lighting, rugs, décor, and parts are reviewed by relevant family.
[ ] Room, style, price band, and collection labels are not substituted for product category.
[ ] Sets and replacement parts have the category and identity of what is actually sold.

Use Shopping feed title optimization when product facts are available but the order is unclear. Use Google product category mapping when the item has ambiguous category branches.

Title change evidence

Keep current title, proposed title, page title, selected configuration, source, reason, transformation version, reviewer, and rollback. Test a simple chair, a large sofa, a configurable table, a set, a part, and a product with a long material or finish name.

Image and landing-page checklist

Open exact product and configuration URLs and verify:

[ ] Page loads in the target market and language.
[ ] Product name, brand, model, image, and selected configuration match the row.
[ ] Dimensions, finish, material, quantity, included components, and options are visible or selectable.
[ ] URL parameters, redirects, and canonical behavior do not choose an unrelated default.
[ ] Main image represents the item clearly, not only an ambiguous styled room.
[ ] Variant image represents the exact finish, color, or configuration where available.
[ ] Accessories shown in an image are clearly included or excluded.
[ ] Price, currency, sale, availability, lead time, freight, and purchase controls agree.
[ ] Structured data, if present, matches visible product values.
[ ] Mobile selectors and long pages do not hide the configuration or delivery promise.

Google’s product-data guidance stresses matching submitted data to landing pages. A source pass is incomplete until the exact furniture page and option have been checked.

Difficult page states

[ ] A finish, orientation, size, extension, or bundle is selected or clearly identified.
[ ] Out-of-stock configurations are not represented as purchasable.
[ ] Showroom, local pickup, and online delivery states are distinct.
[ ] Made-to-order or long-lead pages show a truthful delivery expectation.
[ ] Assembly, installation, freight, or room-of-choice services are represented accurately.
[ ] A room-set image does not imply that unpurchased décor is included.

Price, availability, shipping, and delivery checklist

[ ] Price is for the exact configuration and included components.
[ ] Currency, decimal values, sale period, and checkout price agree.
[ ] Inventory source, source timestamp, feed timestamp, and page observation are retained.
[ ] In-stock, out-of-stock, preorder, backorder, made-to-order, and showroom-only states are separate.
[ ] Lead time matches the page and fulfillment source.
[ ] Freight, handling, delivery area, pickup, assembly, and exclusions match the customer promise.
[ ] Regional inventory is not confused with online inventory.
[ ] 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 stale configurations need recurring monitoring.

Market, unit, and localization checklist

[ ] Account, market, language, currency, destination, and delivery region are explicit.
[ ] Dimension units and conversions have an approved mapping and retained source value.
[ ] Product type, material, finish, and color terms are natural in the target language.
[ ] Page, title, structured data, and variant fields use compatible localized values.
[ ] Freight, pickup, room delivery, seller, and availability differ by market only when documented.
[ ] A product not sold in a market is not copied into that market as available.
[ ] Local or showroom availability is keyed separately from online offers.

Do not use a single global shipping or availability setting when freight, units, or product pages differ by market.

Source, rule, and processing checklist

For each source and transformation, verify:

[ ] Primary and supplemental sources are named with owners.
[ ] Attribute precedence and matching keys preserve product and configuration grain.
[ ] Scope includes market, language, seller, product family, and destination where relevant.
[ ] Rules have conditions, target fields, source version, effective period, and rollback.
[ ] Derived values are labeled and do not invent dimensions, materials, capacity, or lead time.
[ ] 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 provides a framework for narrow transformations. Keep title, category, image, price, availability, shipping, and campaign settings separate. A rule that processes successfully but changes the wrong field fails this review.

Diagnostics and recovery checklist

When a problem appears:

[ ] Original issue text and scope are preserved.
[ ] Affected products, configurations, markets, sellers, and destinations are known.
[ ] Source, generated row, Merchant Center processing, page, and checkout are compared.
[ ] Observed evidence is separated from the root-cause hypothesis.
[ ] The likely owner and smallest authorized correction are identified.
[ ] Before and after values, source versions, and rollback are retained.
[ ] Processed result, diagnostics, selected configuration, image, price, and delivery 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 the incident. Do not close it because a feed upload succeeded or one warning disappeared without verifying the customer path.

Launch and recurring furniture-feed review

For a launch or major catalog change:

Approve catalog boundary, configuration grain, sources, markets, fulfillment, and owners.
Test simple, configurable, bundled, local, made-to-order, and large-item cases.
Review generated rows, images, exact pages, dimensions, and selected options.
Process the source and inspect diagnostics, rejected rows, changed values, and source freshness.
Verify price, availability, freight, delivery, pickup, assembly, and checkout.
Record source version, exceptions, evidence, approval, and rollback.

For recurring review, inspect new and changed products first, then recurring dimension, page, price, inventory, and freight failures. The review cadence should be derived from catalog and fulfillment change risk, not invented as a universal target.

Final furniture-feed sign-off

Sign off only when:

item and configuration identity is stable;
dimensions, units, materials, finishes, and included components are supported;
titles, categories, images, pages, prices, availability, and delivery agree;
market and local context is explicit;
sources, rules, ownership, freshness, and rollback are documented; and
diagnostics and exceptions have evidence and a named next action.

A furniture-store Shopping feed passes when a reviewer can prove what the customer will receive, which dimensions and configuration apply, what the delivered offer means, and how the page was verified. The checklist is a control for evidence and scope, not a shortcut around current requirements or owner approval.