Listing rewrite

Listing rewrite produces approval-ready diffs for every editable PDP field: title, bullets, description, JSON-LD. The output is channel-aware — Rufus-tuned for Amazon, Enricher-tuned for D2C and retailer. Nothing ships without an explicit approval, and a human review pane shows the before/after side by side.

What it produces

For every SKU that has a PDP Score recommendation, Listing rewrite generates the actual content the merchant would paste in. Five field types.

• Title — usually two or three variations, brand-name-first by default.
• Bullets — five bullets, structured pattern (spec → benefit → use case where possible).
• Description — plain-prose long description that answers what / who / why in the first three sentences.
• JSON-LD — Product schema with Offer, AggregateRating, BreadcrumbList, FAQPage where appropriate.
• FAQ block — four or more shopper-language Q&A pairs derived from review themes.

Capsule diffs

The capsule is the unit of approval. Each capsule covers one editable field on the PDP. The merchant approves capsules independently — title alone, or title plus bullets, or everything. Capsules carry three pieces of metadata: priority (from PDP Score), effort (estimated minutes), and rationale (the underlying score recommendation it satisfies).

Channel-aware output

The generator branches on channel.

Amazon

Rufus-tuned. A+ content blocks rather than free-form description. Structured bullets in Amazon's expected pattern. Proposed Q&A submissions instead of FAQ schema (Amazon does not surface FAQPage). See Rufus Score.

D2C

Enricher-tuned. Title, bullets, plain-prose description, FAQ block, full Product JSON-LD with Offer / AggregateRating / FAQPage.

Retailer

Enricher-tuned but filtered to fields the retailer exposes (title, bullets, copy modules). No site-level schema or robots.txt recommendations because the merchant has no power over them. See channel-aware scoring.

JSON-LD block

The JSON-LD output is generated from the rewritten content rather than appended afterwards. Concretely: the price, name, brand, and image fields are pulled from the canonical product record; description is the proposed rewrite; AggregateRating is read from the live review platform (Yotpo, Judge.me, Okendo, Trustpilot); FAQPage is built from the proposed FAQ block.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Vornado AC1 air purifier",
  "brand": { "@type": "Brand", "name": "Vornado" },
  "description": "Quiet 200 sq ft air purifier with True HEPA filtration...",
  "image": ["https://example.com/vornado-ac1-1.jpg"],
  "sku": "VRN-AC1",
  "offers": {
    "@type": "Offer",
    "price": "129.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "1247"
  }
}

Approving and pushing

1. Open the capsule queue

   From the PDP Score detail page or from the bulk Listing rewrite view that shows all pending capsules across the catalogue.

2. Review the diff

   The pane shows current value top, proposed rewrite bottom, with highlighted changes. The editor is live — tweak any field before approving.

3. Approve

   One click. The capsule moves to the Approved queue.

4. Push to store

   If a publishing integration is connected (Shopify, WooCommerce, etc.), the Approved queue can push in bulk. Errors are reported per SKU; successful pushes move to History.

Version history

Every approved diff is recorded with timestamp, approver, and an optional reason note. The History view lets you roll back a single SKU or a batch by date range. Rollback fires a new push to the publishing integration restoring the previous values.

Common questions