Ecommerce & Marketplace · THE NO-PANIC PLAN
Preflight a Google Merchant Center product feed before submission
A feed can be valid CSV and still contain wrong product facts, unsupported identifiers, or prices that do not match the store. This preflight keeps the original export intact, checks the current Google Merchant Center requirements for the intended country and product type, and sends the final decision through Merchant Center’s own diagnostics. Nirmion’s local tools help inspect user-supplied fields; they do not certify or submit the feed.
MISSION Prepare and review a Google Merchant Center product data export against the current target-market specification, source-of-truth product facts, and Merchant Center diagnostics before relying on the feed.
Review a product feedTHE REAL-WORLD BIT
What happens outside this browser tab?
Define the target country, language, destination, and catalog owner; consult the current Google product data specification; preserve an immutable export and verify field mappings; inspect feed health locally; reconcile product identifiers, variants, price, availability, and landing pages to the authoritative store; submit through Merchant Center and resolve its diagnostics; then record the accepted feed version and recheck cadence.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Set the feed destination and the person who owns product facts
Write down that this feed is for Google Merchant Center, the target country or countries, language, online or local destination, currency, and the catalog export date. Name the owner for product identity, price, availability, shipping, images, and policy questions; these fields may have different systems of record. Confirm whether the file includes variants, used or refurbished items, regional prices, or products with destination-specific requirements. Keep the feed owner and an authorized Merchant Center administrator in the review. Do not reuse a passing rule set from another country or program without checking its requirements. Google’s specification marks attributes as required, optional, or conditional depending on product type and target markets, so the target context must be decided before checking individual rows.
- 02
Map source columns to the current Merchant Center attributes
Download or open Google’s current product data specification for the feed’s target. Create a mapping from each source column to the exact Merchant Center attribute name and format; mark required, conditional, optional, unused, and owner-confirmation fields separately. Product Attribute Mapper can help organize merchant-supplied fields into a reviewable mapping, but it does not decide Google eligibility or replace the destination specification. Check variant relationships such as item group identifiers, color, and size when relevant. For product identifiers, use the manufacturer-assigned GTIN, brand, or MPN only when it is genuine and available; Google specifically warns not to guess or substitute an internal SKU for an assigned product identifier. Flag unmapped fields and uncertain values for the catalog owner rather than inventing data to fill blanks.
- 03
Preserve the original export and inspect its structure
Save an unchanged, dated copy of the source export and record its source system, export time, delimiter, encoding, worksheet or file name, row count, and intended import method. Work on a separately named copy. Confirm the header row is present, each record has the expected number of fields, identifiers are not silently converted to numbers, and prices, currencies, URLs, booleans, and availability values retain the documented formats. Check for blank IDs, repeated IDs, malformed links, formula cells that were not exported as values, and unexpected extra columns. Do not remove suspicious rows or rewrite product facts during a technical preflight; mark them for owner review. Keep any customer, supplier, or commercially confidential data in approved storage and send only the necessary catalog fields to a tool.
- 04
Run a local feed-health review and inspect every flagged rule
Use Catalog Feed Health CSV Analyzer on a copy of the product export only after checking its current input instructions and deciding that the file contains no data you should not provide. Review its field-health findings against the target specification: distinguish a missing required value from a conditional attribute that does not apply, and distinguish a format warning from an incorrect product fact. Product Attribute Mapper can help document an approved field mapping, but the catalog owner must confirm every mapping. Save the tool output with the exact input version and date if it is useful for review. A clean local result means only that the selected checks found no issue; it is not proof that Google accepts the feed, every policy is met, or a product is eligible to show.
- 05
Compare submitted facts with the live product page
For a representative sample of products and every flagged exception, compare the feed’s title, identifier, price, currency, availability, variant, image, and product URL with the authoritative catalog and live checkout path. Confirm the selected variant is the one shown after opening the URL; a parent item page that defaults to a different size or color can mislead a reviewer. Google requires product data to align with the landing page and, for price and availability, the checkout experience; update the source of truth and regenerate the feed rather than patching a stale export. If inventory, regional price, or stock changes frequently, confirm the update cadence and regional setup with the Merchant Center owner. Record the sampled IDs and comparison date so a second reviewer can reproduce the check.
- 06
Submit through Merchant Center and resolve destination diagnostics
An authorized administrator should submit or refresh the correct data source in Merchant Center using the planned method. Then open the account’s current Diagnostics or issue-details area, review affected items and examples, and distinguish account-level, data-source, and item-level issues. Fix the upstream catalog or mapping when appropriate, regenerate the export, resubmit, and confirm that the particular issue is no longer reported. Google’s troubleshooting guidance points users to data-source attributes and item issue details; a local analyzer cannot see account diagnostics or verify live acceptance. If a warning depends on policy, destination, or product eligibility, use Google’s current documentation or support route and the responsible merchant reviewer instead of changing factual data just to suppress the warning.
- 07
Archive the accepted version and set a change-triggered review
Record the submitted file version or data-source update time, target country and program, row count, source-system export, unresolved warnings, approving owner, and any corrective changes. Keep the original, reviewed copy, and destination outcome linked under the organization’s retention rules so the team can explain which product data was submitted. After updates, inspect a small set of live products and confirm that the intended variant, price, availability, and landing page appear as expected. Recheck the specification when Google announces an update, when the feed destination or country changes, or when the catalog schema changes; do not assume a past approval applies forever. Google publishes dated specification updates, so include a “last checked” date and owner in the feed review record.
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-10