The Listing Editor
Four tabs — Editor, Strategy, History, Preview — with inline guidance and AI-powered refinements.
The Listing Editor is where keyword research becomes actual words on the page. Select an ASIN from the left rail, and the editor loads that ASIN's current baseline copy, classification state, and strategy brief. Four tabs give you different views into the same listing.
Editor tab
All editable fields, organized into sections matching the Amazon flat file structure:
- Title — The
item_namefield, labeled "Title" in the editor. CountBar shows your character budget with an 80-character mobile cutoff marker and encourage-full-use coloring (amber when the field is under 75% used, green at 75% and above). Aim for 150-200 characters to maximize keyword coverage while keeping the first 80 crisp. - Bullets — Five fields (bullet_point_1 through bullet_point_5), each with its own CountBar. 200-character target, 500-character maximum.
- Description —
product_description, 2,000 characters. Indexed by A10, read by Rufus as a deep context source. - Backend keywords — The five
generic_keywordsfields. Each shows a byte count, not a character count — they differ for accented characters and symbols. The total byte budget across all five fields is 249 bytes. - Images — Imported as read-only references. URLs are displayed for review but are not editable through RankASIN.
Critical fields that always appear: Even if your imported flat file didn't include certain columns, the editor always renders the five bullets, item_name, product_description, and all five generic_keywords fields. These are defined as always-present in the field definitions and won't disappear due to an incomplete import.
Auto-save on blur: Changes are saved when you move focus out of a field (on blur), not on keystroke. The editor uses defaultValue — not controlled state — so typing doesn't trigger re-renders. After save, a new draft row is written to listing_drafts.
5-second classification recompute: After each blur-save, a 5-second debounce timer starts. When the timer completes with no further edits, the keyword classification engine re-evaluates all keyword classes for this ASIN based on the updated copy. If you added a tier_1 keyword to the title, opportunity keywords that were waiting for that term to appear in copy may reclassify.
Strategy tab
The ASIN's strategy brief — your written positioning, customer questions, and audience notes. This tab is where you set the context that drives AI generation.
- Positioning — One sentence about what this product is, does, and who it's for.
- Customer questions — The specific shopper queries this listing should answer. The classification engine uses this list when scoring proven vs. opportunity keywords.
- Audience notes — Freeform context about the target buyer, their objections, and what they care about.
Saving a strategy update triggers the classification engine immediately.
History tab
Every time you save a field, RankASIN stores a versioned snapshot in listing_versions. The History tab shows the version timeline with:
- Version number and timestamp
- Description of what changed (you can add notes)
- Diff view — side-by-side comparison of any two versions
- Comment thread — threaded comments on each version for team review
History is append-only. You can reference old versions and restore from them, but the version record itself is not editable.
Preview tab
A rendered approximation of how this listing appears in two contexts:
- Search result card — title (first ~80 characters), main image thumbnail, price, and star rating as they would appear on the search results page.
- Detail page — a simplified PDP rendering showing the full title, bullets, and description in the layout Amazon uses on desktop and mobile.
The preview is an approximation — Amazon's actual rendering varies by category, device, and A/B test assignment. Use it to sanity-check mobile truncation and bullet front-loading, not as a pixel-accurate mockup.
The Title field in the Preview tab shows exactly where the 80-character mobile cutoff falls. If your primary keyword isn't visible before that cutoff, rearrange the title.