Practical scope and examples
What this XML tool accepts
This tool accepts UTF-8 RSS 2.0 with one channel and Google Merchant namespace fields, or a products root containing product records. Prefix spelling does not identify a field: the Google namespace URI does. Atom feeds and arbitrary XML schemas are rejected instead of being silently interpreted as Merchant feeds.
Upload, inspect and compare
Upload a file up to 10 MiB with at most 5,000 products. The same baseline engine checks IDs, titles, descriptions, prices, availability, URLs and GTIN checksums. Row numbers refer to logical product records, starting at 2; they are not XML source line numbers. Download the report for every finding.
Preserving your XML
Selected safe edits can be exported as XML, CSV or XLSX. XML output preserves namespace URIs, product attributes, channel metadata and unmapped elements. Prefix spelling, comments and whitespace formatting may change. Complex or repeated attributes stay in the XML and cannot be automatically edited. A CSV projection cannot represent every nested XML structure.
Safety and limits
DTDs, entities and external references are rejected. Parsing never fetches remote resources. File size, depth, element count, attribute length and product limits prevent excessive work. Safe formatting changes do not invent prices, stock or identifiers. Your original bytes remain available separately; the corrected XML is a new serialization.
Before submitting to Google
A clean file-level report is not approval. Check destination rules, shipping, tax, product policies and the consistency of your live landing pages and images. A valid GTIN checksum does not prove GS1 assignment. Repeated identifiers and structured fields may still need specialist review. Use the full analyzer when you need its complete filtering and pagination.