ANot added
Merchant feed
CSV, TSV, XML, RSS, or Atom-style product feed
or paste data
Private browser-based product data audit
Merchant Feed, Page, and Product Schema Consistency Checker
Match products across two or three supplied sources and see exact disagreements in price, sale price, currency, availability, identifiers, variants, quantity rules, and canonical URLs.
What this proves: which supplied values disagree and how records were matched. What it does not prove: which source is correct, Merchant Center approval, indexing, or rankings.
Add data → Map fields → Configure → Analyze → Review → Export
1Add two or three sources2Confirm field mapping3Set matching rules4Review evidence5Export fixes
Processed locally in your browser. Your files are not uploaded. A normal refresh clears the input and results.
1. Add product sources
Add any two or all three. CSV/XML feeds and crawl files use column mapping; JSON-LD and saved HTML are mapped automatically.
BNot added
Landing page or crawl extraction
Crawl CSV/TSV, saved HTML, or HTML ZIP
or paste crawl data / HTML
Optional visible HTML selectors
For saved HTML only. Supports a simple tag, #id, .class, or exact [attribute='value'] selector.
CNot added
Product schema
Extracted Product JSON or saved product HTML
or paste JSON-LD / extracted CSV
2. Configure matching and comparison
Defaults use exact normalized prices and exact identifiers. No source is assumed correct.
Add and map at least two sources.
Preparing local analysis…
3. Review consistency evidence
| Priority | Product | Issue and evidence | Match basis | Next action | Detail |
|---|
Product match table
Source presence, match method, confidence, and issue count for every base product.
| Product / variant | Match method | Confidence | Sources present | Issues | Compare |
|---|
4. Export evidence and remediation
Issue exports use the active search and filters. CSV cells are protected against spreadsheet-formula injection.
Draft corrected-feed candidate
Select fields to copy from the nominated authoritative source. This creates a draft only and never changes the original file.
How the comparison works
Auditable matching
Records are matched by your ordered identifiers: item ID, SKU, GTIN, MPN plus brand, canonical URL, or product URL. Every result names the match basis and confidence.
Exact decimal evidence
Prices use decimal arithmetic rather than binary floating point. Ambiguous separators, ranges, bulk quantities, and aggregate offers are labeled instead of silently guessed.
Source-neutral findings
The checker shows every supplied value side by side. It does not claim that the feed, page, or schema is automatically correct.
Supported checks
- Regular and sale prices
- Currency consistency
- Availability and condition
- SKU, GTIN, MPN, and item IDs
- Variant groups and attributes
- Minimum quantity and multipack
- Unit-pricing measures
- Canonical and product URLs
- Duplicate Product nodes and offers
- Missing, extra, and ambiguous products
Important limitations
- The tool does not fetch live URLs or inspect Merchant Center data.
- Visible HTML price extraction requires a supported simple selector; generic price guessing is intentionally excluded.
- Only valid JSON is parsed. JSON-LD comments, trailing commas, or JavaScript expressions are reported and skipped.
- AggregateOffer ranges are not treated as a specific variant price.
- Tax, member, subscription, coupon, bundle, and shipping terms require explicit mapped fields and human interpretation.
Frequently Asked Questions
Does this tool upload my merchant or product files?
No. Pasted and selected files are parsed in a Web Worker in your browser. The tool does not send file contents, product URLs, identifiers, prices, or issue examples to the application server or analytics services.
Which file formats are supported?
You can use CSV, TSV, XML or RSS-style product feeds, crawl extraction CSV files, Product JSON-LD JSON files, individual saved HTML files, or a ZIP containing saved HTML files. Add any two or all three source types.
Does a mismatch prove which source is wrong?
No. The checker preserves each source value and explains how records were matched. You can nominate an authoritative source to prioritize remediation, but you should verify the intended product data before changing a feed, page, or schema.
Can it fetch live product pages or connect to Merchant Center?
No. This local MVP does not fetch URLs, connect to Merchant Center, change a feed, or prove policy approval. It only compares files you supply.
How are ambiguous prices and product matches handled?
Values such as 1,299 require you to confirm the decimal convention. Product collisions are shown with candidate records so you can select a match or exclude the ambiguous record before rerunning the comparison.
What are the browser limits?
Each source supports up to 100,000 parsed products and 25 MB of text. ZIP files can contain up to 250 HTML files, with safety limits on individual and expanded file size. Split larger datasets and compare them in batches.
Reviewed Jun 2026 · Sources and limitations
Review details: 2026-06-10 · Marc LaClear · v1.0
Reference sources:
- Google Search Central documentation
- Google Search Central crawling and indexing docs
- Google structured data guidelines
- Schema.org vocabulary
- MDN Web Docs for HTTP and HTML references
Known limits:
- Checks are based on publicly fetchable HTML, response headers, and browser-side input. They do not use private Google Search Console, analytics, or ranking data.
- Scores and warnings are diagnostic aids, not guarantees of ranking improvement or Google indexation.
- Pages blocked by robots.txt, login walls, bot protection, heavy JavaScript, or network timeouts may return incomplete results.
- Validate critical fixes with official Google tools such as Search Console, Rich Results Test, Lighthouse, and your own crawl data.