Overview
A product feed audit helps ecommerce teams catch catalog problems before products reach shopping engines, social catalogs, marketplaces, or internal merchandising systems. Juno reviews feed structure, field coverage, malformed values, broken links, variant issues, and storefront mismatches.
The output is a feed audit table plus a short report. Each finding includes the affected field or product, severity, sample evidence, and the recommended fix, so feed cleanup does not turn into a guessing game.
Why you should catch feed issues before channels do
Product feeds are boring until they are expensive. A missing image, invalid price, duplicate id, bad availability value, or mismatched product URL can quietly block distribution or send shoppers to the wrong experience.
Google Merchant Center documents required and recommended feed attributes in its product data specification. Those rules are only part of the story, though. The feed also needs to match the live storefront closely enough that shoppers and platforms trust it.
Juno keeps the audit read-only by default. It identifies blockers, quality gaps, and sample storefront mismatches before anyone starts editing exports.
Step-by-step
- 1Confirm the feed source, destination standard, market, currency, and whether variants need special handling.
- 2Profile the feed format, row count, required fields, duplicate ids, price patterns, availability values, and product links.
- 3Check field coverage for titles, descriptions, images, price, sale price, brand, category, product type, and variant attributes where relevant.
- 4Verify a small sample of in-stock storefront URLs for broken links, unrelated redirects, price mismatch, or availability mismatch.
- 5Prioritize findings by syndication risk, affected product count, revenue relevance, and effort.
- 6Produce the audit table and a concise feed readiness brief.
Frequently asked questions
Will Juno rewrite my feed?
No. The default playbook is an audit. A corrected feed export should be a separate, explicit follow-up.
Which feed destinations can this support?
It can start from a general merchant-readiness check, then adapt to Google Merchant Center, Meta catalogs, marketplaces, or internal storefront feeds when you provide the target.
How many product URLs are checked?
The default pass checks a small representative sample so critical mismatches surface without turning the audit into a full crawl.
