AI Catalog Improver

Missing or unclear product facts can make discovery and shopper answers less useful. The AI Catalog Improver drafts product copy and SEO with your brand voice applied, shows you a side-by-side, and - when you approve - pushes the change to your store and re-indexes it.

The copy workflows on this page are review-first: generating a draft does not apply it. Product page Q&A is a separate workflow with its own optional auto-publish setting; review that setting in AI Review.

Where to find it

The improver lives on each product’s detail page - open Catalog → Products, click a product, and scroll to the AI Catalog Improver card. There’s also a cross-store review surface at AI Training → AI Improver for everything waiting on your call (covered at the end of this page).

What it can generate

The Catalog Improver card has four actions. Each one calls the model with the product’s data and your brand voice, then returns a draft you can review:

The approve-and-apply workflow

Generating a draft does not change anything on your store. To go live:

1. Click an action (e.g. Rewrite description).
2. Review the draft. For the description you get a current-vs-AI side-by-side; for SEO you get multiple options to choose from.
3. Save the previous value, then click Apply on the reviewed version. Shopify and WooCommerce have platform write-back paths. Custom-store edits stay local to Zubby; update the authoritative source separately so its next push does not undo the edit. Verify both saved content and indexing before assuming search uses the new copy.

The PDP rewriter (Beta)

Just below the Catalog Improver is the AI PDP rewriter. It produces a single, fuller rewrite of the whole product detail page in one pass: a title, a hook line, a short description, a long description, and a list of benefits. Each field has its own copy button.

The difference from the Catalog Improver: the PDP rewriter is copy-to-clipboard, built for pasting a polished draft into your storefront yourself, whereas the Catalog Improver applies fields directly. Use the PDP rewriter when you want a complete first draft of a page; use the Catalog Improver when you want to update one field at a time and push it live.

Autopilot drafts

Zubby can also draft rewrites for you overnight. When the nightly autopilot has prepared a rewrite for a product, an Autopilot rewrite draft card appears on that product’s page, dated and marked pending. It contains the same fields as the PDP rewriter (title, hook, short and long description, benefits).

You have two choices:

• Approve - applies the nonempty title and the long description (or short description fallback) through the same platform write-back path, then marks the draft live if that flow succeeds. Hook and benefits do not have separate platform fields.
• Dismiss - discards it; the autopilot can regenerate on a later pass.

The AI Improver Inbox

Beyond per-product copy, the AI Improver Inbox (AI Training → AI Improver in the sidebar) is the single queue of every AI suggestion still waiting on you. It groups items into five buckets, each with a pending count:

• Segment ideas - suggested cohorts discovered from eligible store data. Promote to keep or dismiss.
• Content drafts - blog, landing, and campaign drafts from the AI. Star to keep or archive.
• Feedback to review - replies your team flagged as wrong, incomplete, or needing handoff. Resolve so they stop surfacing.
• Demoted sources - products and policies the reranker is currently down-weighting because of negative feedback. A high hit count means the source keeps showing up in failing answers - a strong hint to fix or rewrite it.
• Stale docs - knowledge documents untouched for 90+ days. Confirm they’re still accurate or open to edit.

Worked example: review, apply, and recover

Illustrative staging product: the source says “cotton canvas,” while a draft adds “organic” without evidence. Reject that addition, keep the supported material, and save the previous description before applying. Compare the saved Zubby product, connected platform field, and public page after the theme/cache updates. For custom stores, make the approved edit in your own catalog and push it back through the API.

There is no automatic version-restore control documented here. To undo an applied edit, restore the saved prior value through the supported editor or source platform, then sync and verify. Multi-field approval can partly succeed before a later write fails: inspect title and description separately, keep the draft available, and reconcile the source before retrying. AI service availability, permissions and platform access can block generation or write-back. Use catalog access and an authorized test product before applying to a live catalog.

SEO character counts are editing aids, not Google requirements. Choose accurate page-specific wording; Google can show different titles or snippets, and a rewrite does not guarantee rankings or sales.

Tips & gotchas

• Start with the worst offenders. The catalog page’s “Descriptions missing” counter is the best worklist - those products gain the most from a rewrite.
• Brand voice carries over. The improver writes with the brand voice profile from Settings → Brand Voice(tone, blocked words, do/don’t examples). Fill it in before a big rewrite session and the drafts land much closer to how you actually write. See system prompt & persona.
• Applied copy can still be edited. Pushing a draft live doesn’t lock anything - you can refine it in Shopify or WooCommerce afterward, and the next sync re-indexes your edits.
• Drafts aren’t live until you act. Generating a rewrite or letting autopilot draft one changes nothing on your store until you apply or approve it.

Related

• Catalog & product sync - where product copy is stored and indexed.
• System prompt - define the brand voice the improver writes in.
• Knowledge base - where generated FAQs belong.
• Product recommendations - better copy means better ranking.