Well-formed XML
Unclosed tags, invalid nesting, broken entities and document-level parse errors.
FeedScore separates syntax blockers from product-data problems. That makes it clear whether the file cannot be parsed, individual items are malformed, or the catalog is technically valid but commercially incomplete.
Unclosed tags, invalid nesting, broken entities and document-level parse errors.
Encoding declarations and the namespaces required by the chosen feed structure.
Consistent item or entry nodes and repeated attribute patterns.
Empty, missing or malformed core product fields.
Duplicate identifiers plus invalid or inaccessible product and image links.
Content, identifier, price, availability and taxonomy coverage after parsing.
Fix blockers first, then catalog-wide patterns, and leave isolated optimization opportunities for last.
FeedScore reads the public URL and records access, status and file-level signals.
The validator checks structure first, then evaluates values product by product.
The report combines repeated failures so you can fix the export logic once.
A file can be perfect XML and still contain missing GTINs, weak titles, invalid prices or broken image URLs. FeedScore combines XML validation with catalog-level commerce checks.
The planned parser covers common XML product-feed structures, including RSS-style item lists and Atom-style entries. Final format coverage will be documented when the production parser is connected.
Yes. XML syntax is only one layer. Attribute requirements, values, website data, account settings and policies can still cause warnings or disapprovals.
Yes. The full report is designed to list issue counts and export the product identifiers or rows affected by each check.
No. FeedScore analyzes the source and explains what to fix. It does not rewrite or upload your feed.
Our public guidance is checked against first-party documentation. FeedScore adds independent data-quality checks and does not represent a platform approval decision.