01
Deterministic preflight
49 documented row and feed-level rules with stable IDs, severities, affected rows, and correction guidance.
Browser-local Google Merchant feed QA
Validate the feed. Control the release.
Declare what a release is authorized to change, then run 49 deterministic checks, enforce safety policy, inspect material drift, and create a hash-bound decision another person can independently rerun—without uploading either file.
Files stay in your browser No account or channel connection No AI in the validation path CSV, TSV, RSS/XML, Atom/XML
Optional product analytics are off by default. Feed data is never included. You can enable or manage the pseudonymous measurement separately.
Privacy controlsRelease Gate · product v1.3.0
Turn a feed correction into a release decision.
Declare what the release is meant to change, then compare the approved baseline with the candidate. FeedGuardrail tests actual drift against that contract and an inspectable safety policy before returning pass, review, or block.
- Declared change contract catches technically valid but unauthorized edits
- Versioned profiles, editable limits, and portable JSON controls
- Price, availability, identity, schema, inventory, and field drift
- Field-by-field operator ledger plus raw-input hash-bound evidence
SHA-256 identifies the exact local file bytes used. It does not prove who made a file, certify compliance, or guarantee Google approval.
The approved version before this release.
The version being evaluated for release.
Allows content and destination fields, but expects no product additions or removals.
Define the authorized scope
Blocks removals, large price changes, and candidate errors; requires review for warnings and any availability drop. Best for guarded production releases.
Customize the exact limits
Private: file contents and hashes stay on this device.
Independent local verification
Received an evidence pack?
Choose a v3 evidence HTML or JSON file plus the exact baseline and candidate feeds. FeedGuardrail verifies both hashes and reruns the recorded change contract, rules, safety policy, drift analysis, and gate decision in this browser.
Unsigned evidence: nothing is uploaded. Verification proves a byte-for-byte match to the recorded hashes and a reproducible decision only—not authorship, authorization, certification, provenance, or Google approval.
Creates a synthetic evidence pack and both tiny example feeds on this device, then reproduces the result automatically.
The difference is the workflow
Not another pass/fail feed checker.
A single scan finds today’s defects. FeedGuardrail turns the next export into a governed release: what was fixed, what drifted, which thresholds were crossed, and whether the candidate should pass, wait for review, or be blocked.
02
Declared change contract
Records the fields and catalog volume authorized to change, then calls out valid-looking edits that occurred outside that scope.
03
Safety policy and operator ledger
Enforces integrity checks and editable limits across price, availability, identity, inventory, schema, and field drift—then exports normalized field changes for uniquely matched products.
04
Independent verification
Exports a privacy-minimized record bound to both file hashes, the exact contract, ruleset, policy, drift, and decision for recipient-side reruns.
Single-file preflight
Need to check one feed first?
Run the same deterministic rule engine on one export. Use this for diagnosis; use Release Gate above when a baseline exists and the change itself needs approval.
Single-file diagnosis
Check a product feed
↑Drop a feed here, or choose a fileCSV, TSV, or XML · up to 25 MB, 100,000 rows, 500 columnsChoose product feed
Files stay on this device. Desktop recommended for large catalogs.
Proof over promises
Inspectable release quality.
FeedGuardrail publishes what it checks, which release produced the result, where the product’s limits are, and how its evidence can be reproduced.
Read the methodology and full rule catalog →Versioned rules
google-merchant-online-product-data-2026-09-09.1
Private processing
Feed contents, filenames, hashes, IDs, and values are not uploaded.
Deterministic engine
The same inputs and ruleset reproduce the same comparison; no AI model decides findings.
Published operating limits
Up to 25 MB, 100,000 rows, and 500 columns per file, with explicit evidence and contract size limits.
Useful, not vague
Know what broke, where, and how to fix it.
The report groups repeat problems, identifies affected rows and product IDs, and explains the correction in plain language. Download a corrections CSV or a self-contained client summary.
Illustrative report preview
sample-spring-catalog.csv · 2,418 products
ErrorMissing required identifiersGTIN, MPN, or identifier_exists needs attention38 rows
ErrorInvalid sale priceSale price is not below the regular price17 rows
WarningTitles likely to be truncatedImportant attributes appear after 70 characters64 rows
01
Add a feed
Choose a Google Merchant CSV, TSV, RSS/XML, or Atom/XML export. Credentials are never required.
02
Declare the intended change
Choose or customize a portable contract for allowed fields, product-count limits, and review-versus-block enforcement.
03
Gate the release
Compare baseline and candidate feeds against the declared scope and safety policy, inspect drift, and export a reproducible release record.
Troubleshooting library
Fix the issue behind the diagnostic.
Practical guides grounded in Google’s product-data documentation, with clear boundaries around what a local file check can and cannot prove.
Browse the complete guide library →Current access
Free, browser-local, and ready to use.
No checkout, trial clock, account, ad-platform connection, or feed upload. Run a preflight or policy-based release gate whenever you need one.
Available now
- ✓ 49 sourced single-feed checks
- ✓ Portable change contracts and safety policies
- ✓ Deep drift plus operator change ledger
- ✓ Independently reproducible evidence v3
Built for controlled handoffs
Give an operator the exact contract and policy, give a reviewer the exact inputs and evidence, and preserve a deterministic record of why the release passed, required review, or was blocked.