Attribute coverage: the 41% to 96% figure

Our homepage says catalogs arrive at 41% attribute coverage and leave enrichment at 96%. This page defines the metric, shows where the two numbers come from, and explains how to run the same count on your own feed in an afternoon.

What the metric counts

Attribute coverage is the share of key Merchant Center fields that are filled and valid across every product in a feed. We count the fields that drive matching and filtering: color, size, material, pattern, gender, age group, and a category assigned to a leaf of Google's taxonomy rather than a top level.

The 41% is the median coverage of catalogs when they first connect to Cobiro. The 96% is the median for the same catalogs after enrichment has run and the review queue has been cleared. Individual feeds land higher or lower, and apparel usually arrives lowest because it has the most attribute slots to leave empty.

Why coverage decides visibility

Google's guidance for Merchant Center is direct: providing all relevant attributes increases a product's chances of showing for the most relevant queries. Every blank field is a filtered search the product cannot appear in. A search for a red cotton dress never surfaces a dress whose color and material columns are empty.

Complete data also cuts disapprovals. A large share of Merchant Center rejections trace back to missing or contradictory fields, and a product stuck in review earns nothing while it waits.

Measure your own feed in an afternoon

Export the feed, count the non-empty values per column, divide by the number of products. That is the whole method. Run it before enrichment and after, and you have a before-and-after nobody can argue with. Cobiro shows the same count per catalog in the dashboard, so the numbers on this page are ones you can reproduce on your own data.

What enrichment will not touch

The AI fills in what it can see and read: color, material, pattern, category, fit. It never invents identifiers. GTINs, brand names and prices come from your data or not at all, because a wrong guess there is a policy violation rather than a blank field.