Audit product feed and schema mismatches by variant
Compare Merchant Center, Product schema and visible page values without treating harmless formatting as a failure.
- Works in
- ChatGPT, Claude, Gemini
- You need
- Merchant Center export · Product schema export · Visible page values
- Written for
- product feed audit prompt
Most mismatch reports produce noise because punctuation gets the same red flag as the wrong price. This prompt uses statuses that preserve that difference and assigns each problem to the system that should own the repair.
Compare these three sources one sellable variant at a time: feed, Product
structured data and visible landing page.
Match identity first using ID, SKU, GTIN, MPN, brand and variant group. Then
compare URL, title, price, currency, availability and condition.
Return a table with feed value, schema value, page value, status and owner.
Status must be EXACT, ACCEPTABLE PRESENTATION DIFFERENCE, STALE, WRONG
VARIANT, or MISSING. Rank identity and purchase-condition errors first.
Never invent a missing value or assume which source overrides another.
Feed: [FEED]
Schema: [SCHEMA]
Page values: [PAGE]What to change
Everything in square brackets is yours to replace. Nothing else needs editing.
[FEED]- A feed export with identifiers and offer fields.
[SCHEMA]- Parsed JSON-LD values by product URL.
[PAGE]- Visible values from the same live URLs.
How to run it
- 01Sample important variants
Start with top sellers, sale items and recently changed stock.
- 02Resolve identity first
Do not compare prices until the rows describe the same variant.
- 03Fix the source system
Correct the catalogue or integration rather than patching one export.
Questions people ask
Should feed and schema titles match exactly?
Not always. Presentation can differ while the product and variant remain consistent. Identity, price and availability mismatches are more urgent.
Unsubscribe in one click. We never pass your address on.