Commerce Readiness
Audit your WooCommerce catalogue against the product data AI shopping agents need — images, prices, descriptions, identifiers.
Commerce Readiness
AI shopping agents don't browse your storefront. They read structured product data and match it against what the shopper asked for. A beautiful product page with a missing GTIN and a two-line description is invisible to them.
Contexta → AI Visibility → Commerce Readiness audits every published product against the fields those agents rely on.
It costs nothing to run
This audit is fully deterministic: it reads your live WooCommerce data directly. No AI calls, no API cost, no tokens. Run it as often as you like.
What it checks
Eight checks per product:
| Check | Why it matters |
|---|---|
| Image | No image, no listing — this is the hardest requirement |
| Price | Agents filter and compare on price constantly |
| Description | Thin descriptions give an agent nothing to match against |
| Short description | Used as the summary in comparisons |
| Category | Determines whether you appear for a product type at all |
| GTIN / EAN / barcode | The universal identifier agents use to match products across sellers |
| Brand | Brand-filtered queries are extremely common |
| Weight | Feeds shipping estimates, which affect purchase decisions |
Each product gets a 0–100 readiness score, and the catalogue gets an overall score.
Reading the results
- Catalogue readiness — your overall score and how many products have issues
- Most common data holes — the single fix that would improve the most products; usually the best place to start
- Products to fix, worst first — a ranked list, each row linking straight to that product's edit screen
Click a product, fill the missing field, save, re-run the audit. There is no import or mapping step.
Requirements
The audit appears when a product catalogue is detected on the site. With no product post type present, Contexta tells you rather than showing an empty screen.
Large catalogues are audited in batches; the screen shows how many products were covered so a partial audit is never mistaken for a complete one.
Customising the checks
If your shop keeps a field somewhere Contexta cannot see — GTINs in a custom plugin, weights in a shipping integration — a noisy check can be switched off:
// Drop the weight check from the audit.
add_filter( 'rm_commerce_checks', function ( $checks ) {
return array_diff( $checks, [ 'weight' ] );
} );
Valid check names: image, price, description, short_desc, category, gtin,
brand, weight.
Related filters — rm_commerce_audit_limit and rm_commerce_field_threshold — are covered
in Developers.
Where to start on a big catalogue
- Images first. A product without one is effectively not for sale to an agent.
- Then prices, for the same reason.
- Then GTINs, which are what let an agent recognise your product as the same item a shopper saw elsewhere.
- Descriptions and the rest afterwards — those improve ranking among matches rather than deciding whether you match at all.