Can the feed be processed?
The scanner enforces public HTTP/HTTPS access, content type, redirects, timeouts, transfer and decompression limits, encoding and safe XML rules.
Validate whether your product feed can be processed reliably and whether individual product records contain consistently structured values.
The scanner enforces public HTTP/HTTPS access, content type, redirects, timeouts, transfer and decompression limits, encoding and safe XML rules.
XML requires safe, well-formed product nodes. CSV requires a supported delimiter, unique non-empty headers and consistent parseable rows.
Rules cover IDs, content length, URL syntax, price with currency, availability, brand, GTIN/MPN and category presence.
The audit groups repeated failures and detects duplicate product IDs without retaining the full 100,000-product catalog in memory.
| Layer | Validation | Audit |
|---|---|---|
| File | Fetch, content limits, encoding and parsing | Records the technical evidence behind the result |
| Structure | Recognizable XML nodes or CSV columns | Measures recurring gaps across parsed products |
| Values | Expected representation of supported fields | Completeness and issue severity |
| Outcome | Can the source be processed reliably? | What should be fixed first, and on which rows? |
Need catalog-wide prioritization rather than only technical validation? Read the complete product feed audit guide.
A source-file validator cannot see destination policies, account settings or review outcomes.
The current scanner does not crawl every landing page to compare live price and availability.
A correctly formatted identifier or category can still be factually wrong and require human verification.
Product Feed Scan parses public XML and CSV feeds incrementally, applies versioned rules to supported fields and groups failures by impact. It does not predict platform policy decisions, modify feeds or guarantee channel approval.
Yes. A parseable file can still contain missing IDs, weak descriptions, invalid product URL syntax, malformed prices or incomplete category data.
No. The current rules validate whether supported URL values are present and syntactically use HTTP or HTTPS. They do not crawl every product and image URL.
Encoding is detected strictly first. Isolated invalid bytes in explicitly identified UTF-8 XML may be replaced with U+FFFD within a configured recovery limit and are always reported as a high-severity warning.
No. The source must be publicly reachable without credentials, cookies or authorization headers.
Scan a public XML or CSV feed, review the free score and unlock the complete private report only if you need every affected product.