What does Merchant Feed Audit check?

It fetches a public merchant feed, parses product rows, and compares feed price, currency, and availability with public product-page signals visible to crawlers and agents.

How much does it cost?

The audit costs 0.25 USDC on Base via x402 or the non-x402 Base USDC transaction-hash checkout.

Preflight Google Merchant Center price mismatches before they become disapprovals.

If the feed says one price, the landing page says another, and structured data lags behind the theme, crawlers and commerce agents see weak product evidence. Devryno checks the public feed against public product pages before you submit or resubmit.

Audit sample feed Preview feed rows free Free preview landing Pay with Base USDC See sample JSON See sample feed Share kit Diagnostic order Example cases OpenAPI

ProblemFeed, theme markup, JSON-LD, Open Graph, visible price, and variants can drift apart after price or market changes.

Paid checkGive Devryno a public product feed URL. It parses rows and checks page evidence for price, currency, and availability.

OutputJSON verdict, row-level mismatches, evidence sources, and the next repair step. Pay by x402 or with a normal Base USDC transaction hash.

Paid call

GET https://devryno.com/pay/merchant-feed-audit?url={public-product-feed-url}&limit={1-10}

Price: $0.250 USDC on Base via x402, or 0.25 USDC through the non-x402 wallet checkout. The endpoint supports public Google Merchant/RSS/Atom/CSV/TSV feeds and checks up to 10 rows.

Not ready to pay yet? First call the free parser preview: GET https://devryno.com/free/merchant-feed-preview?url={public-product-feed-url}&limit={1-3}. It confirms the feed is public and shows parsed rows, but it does not check product pages.

What it catches

Feed price differs from JSON-LD Offer price.
Feed currency differs from Open Graph product currency.
Feed availability differs from structured availability.
A product URL points to a variant/default page whose visible price is not the submitted feed price.

Devryno is not affiliated with Google. This is a public-page/feed preflight and does not guarantee Merchant Center approval; it helps catch mismatches before crawlers or agents quote them.

What to check first when the warning is vague

Public Shopify and Merchant Center threads keep circling around the same operational question: the warning says price mismatch, but the slow part is deciding which layer is wrong. Devryno's audit is shaped around that diagnostic order.

Feed row: submitted price, currency, availability, sale price, and variant URL.
Landing page: first visible price, default variant, subscription/compare-at/sale presentation, region or currency redirects.
Machine-readable page data: Product/Offer JSON-LD, Open Graph product price tags, microdata, canonical URL, noindex/robots reachability.
Timing: feed sync delay, recent theme/app changes, and whether crawlers have recrawled the repaired page.

For a compact list of synthetic-but-realistic mismatch examples, see Merchant Feed Audit example cases.

Why this maps to Merchant Center pain

Google documents inaccurate price issues when feed data and landing-page data disagree, and also describes structured data conditions crawlers rely on for matching product data. Devryno does a small public preflight over those same practical surfaces: feed rows, landing-page price/currency/availability signals, and Product/Offer markup.