A real Amazon US listing build: one prompt in, five minutes later a complete, editable document with title, bullets, description, A+ copy and backend keywords.
This article records a real Amazon US listing build: from entering a single request to receiving an editable document with all five parts — title, five bullets, Description, A+ copy and backend keywords — in about 5 minutes.

*02 Figure 1 — Submitting the request*
Project background
Writing a listing is one of the most frequent daily tasks for cross-border sellers, and the title, five bullets, A+ copy and backend keywords of a single listing need repeated polishing. Completing a full listing by hand, including competitor research, usually takes 4-5 hours. With Talos, this run produced a five-part US listing in about 5 minutes.

*03 Figure 2 — It does the work*
The challenge
The difficulty of a listing concentrates in three places. First, competitor research means going through pages one by one and noting down their title structure and how they write their bullets. Second, the copy has to be organised around Amazon's search logic, with core terms up front and long-tail terms moved down into the backend fields. Third, every field has a hard limit: a 200-character title and 250 bytes of backend keywords, and anything over fails to go live. Generic AI tools return broad marketing paragraphs whose format and length you cannot control, and you do not get fields you can paste straight into the backend. The goal here was a five-part listing document ready to publish.

*04 Figure 3 — The delivered output*
Method
Step 1: State the product information, competitor links and output requirements in one go
The core of the prompt is putting the selling points, the competitors to reference and the output format into the same paragraph. This is the full prompt used:
I need an Amazon US listing for a portable blender.
Selling points: USB-C charging, 18oz, BPA-free, built-in sip lid, dishwasher safe.
Look at how these two competitors write their titles and bullets before you start:
- https://www.amazon.com/dp/B0C2FF74J6
- Category search page (pick more yourself): https://www.amazon.com/s?k=portable+blender
Produce, following Amazon's search logic: title, five bullets, Description, A+ copy, backend keywords.
Requirements: the title must not be keyword-stuffed and must read smoothly; each bullet covers exactly one concrete selling point; keywords must cover both core and long-tail terms.
Output one md file with all five parts.
The prompt contains four key elements:
Clear product information: five selling points listed one by one, so nothing needs a follow-up question. Specific references: both a competitor detail page and a search page were given, with the instruction to look before writing. Fixed output structure: all five parts named at once, so the resulting document maps directly onto the backend fields. Format constraints in place: no keyword stuffing in the title, one point per bullet, layered keywords — all three requirements stated outright.
Step 2: Talos handles the research and writing
After receiving the request, Talos runs the following process automatically:
- Fetch competitors: read the specified competitor detail page and extract its title structure and bullet approach
- Add the search page: pull several more competitor titles from the category search page and summarize high-frequency and long-tail terms
- Summarize the conventions: compare the two typical approaches and settle the trade-off between title readability and keyword density
- Produce section by section: write the title, bullets, Description, A+ copy and backend keywords according to search logic
- Self-check hard limits: verify title character count and backend keyword byte count, rewriting anything over the limit
The whole run takes about 5 minutes.
Step 3: The output structure
Talos outputs a Markdown document with all five parts, plus competitor observations and a list of items still to be filled in.
| Part | Content |
|---|---|
| Competitor observations | A breakdown of how Ninja (B0C2FF74J6, Amazon's Choice, 14,000+ reviews) writes its title and bullets, plus a summary of high-frequency terms on the search page |
| Title | 180 characters, with the core term Portable Blender for Shakes and Smoothies up front, readable as a full sentence |
| Five bullets | One selling point each: USB-C charging, 18oz capacity, BPA-free, built-in sip lid, dishwasher safe |
| Description | Plain text, mapping directly to the backend Product Description field |
| A+ copy | Six standard modules, each with an image placeholder plus heading and body text |
| Backend keywords | Two versions: a full version at 246 bytes and a de-duplicated version at 215 bytes, both under the 250 limit |
The key constraints sit inside the copy itself: the title is held to 180 characters to leave headroom, both backend keyword versions are labelled with their byte counts, and each bullet makes only one point. The document ends with an items-to-fill list that leaves parameters such as battery life in cups and motor speed blank rather than inventing numbers.
Results
| Metric | Manual | Talos | Change |
|---|---|---|---|
| Total time | 4-5 hours | About 5 minutes | About -98% |
| Competitor research | Page-by-page reading, manual notes | Fetched and summarized automatically | — |
| Content coverage | Mainly title and bullets | Title, bullets, Description, A+, backend keywords | More complete |
| Output format | Split across documents and the backend | A single md file with all five parts | — |
| Reusability | Start from zero each time | Prompt saved and reused | High |
Talos completed everything from competitor research to five-part copy in about 5 minutes and produced a listing document that can go straight into the backend, with a 180-character title and 246 bytes of backend keywords, both within the platform's publishing limits.
Business impact
For seller teams that need to launch new products in batches, the value of this workflow accumulates:
One-off production: compressed from 4-5 hours to 5 minutes, sharply lowering the cost of producing a single listing. Repeat production: once the prompt is saved as a template, switching products means replacing the selling points and competitor links, so the marginal cost is very low. Information quality: competitor conventions are fetched and read by the tool, reducing the bias of summarizing from memory. Format compatibility: the output is structured md whose five parts map directly onto backend fields, with no second pass of splitting required.
Repeatable takeaways
- List the selling points one by one: the more specific they are, the less the five bullets blur together; one point per bullet is what makes each one targeted.
- Give competitor links so the tool looks first: saying "look at these competitors before you start" stays closer to how the category is actually written than letting the tool imagine it.
- Name the output format once: put the five fields — title, bullets, Description, A+, backend keywords — into the prompt and skip the back-and-forth later.
- Save the prompt for reuse: keep a validated prompt as a template and change only the selling points and competitor links when the product changes.
FAQ
Q: Can a listing written with Talos go live as is?
A: The format maps directly onto the backend fields, and punctuation, character counts and byte counts are within the limits. We recommend a manual review of the product specifications before publishing, especially measured data the tool did not have.
Q: How long does a complete listing take?
A: About 5 minutes in this case, covering the whole process from competitor research to five-part copy. The time depends mainly on the number of competitors and how complete the information is.
Q: Where does Talos look for competitor information?
A: It reads the competitor links and category search page provided in the prompt and fetches the titles and bullets publicly shown on those pages. You can specify which links to look at in the request.
Q: Does this method work for other products?
A: Yes. The core is a structured request made of "product selling points + competitor links + output fields"; for any product in any category, you replace those three parts and reuse it.
Screenshot checklist (delete before publishing)
Delete this section before publishing. The first two are required.
| # | Section | What to capture | Framing notes | Suggested filename |
|---|---|---|---|---|
| 1 | Project background | New session on the Talos home screen | Widen the window; no customer or product names in the sidebar session list | usecase-listing-01-home.png |
| 2 | Method, step 1 | The session box with the prompt entered | Full prompt visible, send button inside the frame | usecase-listing-02-prompt.png |
| 3 | Method, step 2 | A session mid-run | Show competitor page fetching and file generation; mask the account and credit balance | usecase-listing-03-running.png |
| 4 | Method, step 3 | The generated md document | All five parts visible, with the character/byte labels on the title and backend keyword sections readable | usecase-listing-04-md.png |
| 5 | Results | Editing that file in a local editor | Cursor placed in the title or a bullet to show it is editable | usecase-listing-05-edit.png |