Install the current Store release
Add the published extension from the Chrome Web Store. No Merchant Center login or broad browsing permission is requested.
Chrome extension · Current Store version 0.1.8
Find which product-data layer disagrees. Verify the repair.
Merchant Match Preflight compares one selected Shopify or WooCommerce product variant across three layers: the visible page, product structured data, and one optional local feed row. It identifies supported price, sale-price, currency, and availability conflicts, then lets you rescan after correction to verify whether the mismatch disappeared.
Free to install. No Merchant Center credentials, account access, or catalog crawl. Product and feed contents remain local.
Release status: Version 0.1.8 is the current public Chrome Web Store release. It adds deterministic handling for Google's eligible public UnitPriceSpecification current-price model. Its permissions and privacy boundary are unchanged.
Install → fixture → scan
Reach a known result before using a live store.
The controlled path separates installation trouble from extraction trouble and produces a reproducible first report in about three minutes.
Open the fictional fixture
Use the stable public product and one-row sample feed before scanning any client or live-store data.
Scan the current tab
Reproduce the known price and availability findings, then use the same workflow on an authorized product page.
Diagnostic guides
Choose the exact Merchant Center symptom.
Each guide uses one bounded comparison and a reproducible fixture. No Merchant Center login or full-catalog scan is required.
Task-specific guide →
Five causes of a visible-price vs JSON-LD mismatch
Trace the selected variant, current price, currency, and Offer object before changing the feed.
Task-specific guide →Validate a sale price before Merchant Center recrawls
Check the live sale state across the page, structured Offer, and one local feed row.
Task-specific guide →Shopify is in stock, but Merchant Center says out of stock
Separate storefront, selected-variant, structured availability, and feed-row state before changing inventory data.
Task-specific guide →WooCommerce shows the wrong variation price
Check whether the selected variation is being compared with a parent, default, or lowest-price Offer.
Task-specific guide →Rich Results Test passes, but Merchant Center reports a mismatch
Use the exact live variant and feed row to identify what a structured-data validation result does not compare.
Choose the shortest valid path
Verify the workflow before using client data.
Both paths start with the stable fictional fixture and keep page, product, and feed contents on the device.
First-use path →
Run a controlled first scan in about three minutes
Install the current Store release, open the fictional fixture, reproduce the expected findings, and confirm that the report workflow works before using a live store.
Agency path →Use the client-safe agency install kit
Standardize setup, one-row feed comparison, local report handling, and the fix-and-rescan loop across stores or client accounts.
User-initiated accessThe extension reads only the product page you choose to scan
Product data stays localPage, structured-data, and feed contents are not transmitted
Measurement is optionalConsent-based pseudonymous telemetry is off by default
Actual extension workflow
One current page. Three compared layers. One verified repair loop.
Unlike a file-only validator, MMP checks whether the selected live variant, structured product data, and optional matching feed row agree. It does not validate a complete feed or guarantee Merchant Center approval.
Open one product page
Select the exact Shopify or WooCommerce product variant you want to check, then open the extension from the Chrome toolbar.
Scan the current tab
A user-initiated scan reads supported visible product fields and Product or ProductGroup structured data from that page.
Add one feed row if needed
Optionally paste or import one local CSV, TSV, or JSON row for the same selected variant. No Merchant Center login is required.
Fix, rescan, and export
Review field-level findings, correct the source data, and run a repair scan to verify whether the supported mismatch was resolved.
Illustrative extension output
Locate the conflicting layer. Correct it. Verify the rescan.
This fictional example demonstrates the report structure. It is not customer evidence and does not imply Merchant Center approval.
MMP-SAMPLE · BLUE / LARGE
2 critical findingsDemo running shoe
FieldVisible pageStructured dataFeed row
Price$79.00$89.00$79.00
CurrencyUSDUSDUSD
AvailabilityIn stockIn stockOut of stock
Next action
Align the Product Offer price and confirm which availability state is authoritative for the selected variant. Then scan again.
Supported boundary
Preflight findings, with explicit limits
Unsupported, ambiguous, and low-confidence pages return a non-pass state rather than a clean result.
Supported price, sale price, currency, availability, title, brand, SKU, GTIN, MPN, and selected-variant conditions.
Compact scan evidence is retained for up to 30 days, capped at 50 records, and can be exported or cleared at any time.
The extension does not inspect Merchant Center account state, checkout behavior, policy status, or every possible storefront.
Problem evidence
Why this comparison exists
Category evidence supports the workflow. It does not prove demand for this exact extension or guarantee that every mismatch will be detected.
Primary source ↗Google: troubleshoot price and availability mismatches
Google says product-source, landing-page, and structured-data values should agree.
Primary source ↗Google: Product structured dataPrice, availability, and variants are represented in Product and Offer markup.
Primary source ↗Google: structured-data testing toolsRich Results Test and Schema Markup Validator validate markup, not a locally supplied feed row.
Published on the Chrome Web Store
Validate the relationship between sources—not only the feed file.
Install the current Store release, scan a supported Shopify or WooCommerce product page, and export a local report for the fix-and-rescan loop.