# Amazon Listing Optimizer

> Checks your live listing for suppression triggers first, then rewrites title, bullets and backend terms — using only words Amazon hasn't already indexed.

- Agent: Claude Code
- Plan: Starter (1 vCPU, 2 GiB RAM, 10 GiB disk)
- Forks: 0 · Stars: 0
- Creator: https://www.jurniti.com/creator-ca0ff2
- Tags: amazon, claude-code, copywriting, e-commerce, ecommerce, listings, marketplaces
- Requires config (you provide): ANTHROPIC_API_KEY
- Skills: amazon-listing-optimizer

**To fork:** open https://www.jurniti.com/templates/amazon-listing-optimizer and use the Fork action — it starts a Stripe Checkout for a new VM seeded with this template's persist disk (same flat plan price, no fork fee).

## README

# "BEST SELLER — FREE SHIPPING" in the title is a suppression

You paid for a listing rewrite. It came back with promotional language Amazon
suppresses for, an eco-friendly claim nobody substantiated, and backend keywords that
repeat every word already in your bullets.

A suppressed listing earns nothing. And the backend field — the one genuinely free
lever you have — was spent on words Amazon had already indexed.

## The compliance pass runs first, on what's already live

Before writing a word, it checks your **current** listing against the known
suppression triggers: promotional language in the title, restricted claims (medical,
curative, FDA-adjacent, unsubstantiated "eco-friendly", safety), competitor brand
names, contact details or URLs, unsubstantiated superlatives.

A suppression risk already published matters more than a better bullet — and most
sellers have never had theirs checked.

## Backend keywords: only words that appear nowhere else

Amazon indexes your whole listing, so repeating a word from your title or bullets in
the hidden search-terms field **buys nothing**. Neither does your brand name, your
ASIN, commas, or both the plural and singular of one stem.

So terms are generated **only** from words appearing nowhere else in the listing — and
you get the byte count.

## Bullets are objection handlers, not feature lists

Five bullets in a fixed order: *does it fit / will it last / is it right for me / what's
included / what happens if it's wrong.* Each led by a capitalised phrase, because
buyers scan bullets on mobile.

## It won't invent a spec

Missing materials, dimensions, counts or certifications come back as
`[SPEC NEEDED: what]`. On Amazon an invented spec is both a suppression risk and a
returns problem.

## Every change carries its reason

One line per element on what changed and why. A rewrite you can't evaluate is one you
won't ship.

## What you supply

Your own Claude Code login, plus your current listing in `~/amzlisting/exports/`.

**Tell it the category** — title limits and restricted claims differ by category, and
guessing produces a suppression. **Paste your reviews** if you have them; the five
objections your bullets need to answer are already written there.

No Seller Central connection, which is also why nothing can publish.

## Where this stops

It drafts copy to paste. It does not connect to Seller Central, edit a listing, or
submit a flat file.

It has no keyword tool, so no search-volume or ranking claims. And the compliance pass
**flags known triggers** — it cannot promise a review outcome.

Verified on build: the skill, the working tree, the `NEVER_PUBLISH` guard, all five
compliance rules, the backend-waste rules and the bullet structure are present on a
fresh fork. Running it on your own listing is yours to do.