What an Adobe Commerce product data audit should cover
Adobe Commerce and Magento catalogs can use attribute sets, configurable products, store views, websites and channel exports. A useful audit follows a product’s data from admin attributes to the rendered product page and then into the feed or discovery channel that consumes it.
1. Review attributes and attribute sets
Check that important product facts use appropriate attributes with consistent codes, labels, scope and value types. Confirm the right attribute set is assigned to each product family and that key customer-facing attributes are enabled for storefront display where needed. Adobe documents how to add product attributes and how attribute sets define available product fields.
2. Test configurable products and store views
For configurable products, verify that the parent and each simple child have the expected identifiers, option values, images, price and salability. Test that selecting a child updates the storefront display. Compare values across relevant store views and currencies so localized pages and feeds do not present stale or conflicting details.
3. Match the page, schema and export
Compare visible product facts against Product and Offer structured data and the channel export. Check URL, title, image, SKU or GTIN where applicable, price, currency, sale dates and stock status. Confirm that an export maps the intended source attribute and includes the correct website or store-view values. Google’s Product structured data documentation describes supported product markup; valid markup can make a page eligible for certain appearances, but does not guarantee them.
4. Check indexing and product-page quality
Confirm that the canonical product URL is accessible, indexable when intended, returns the correct status, and provides distinct useful content. Check for duplicate URLs, layered-navigation parameters, empty descriptions, missing images, and variant pages that cannot be understood without client-side interaction.
5. Prioritize fixes by scope and impact
Start with a cross-category sample. Group repeated issues by attribute, product type, store view, and feed mapping so the team can fix the source once instead of editing products one by one. Recheck representative products after deployment and monitor whether the correction survives scheduled exports.