Writing titles that rank

The title is the single most important text field in your listing. It's the primary signal for A10 keyword indexing, the first thing a shopper reads in search results, and the input Rufus uses when answering comparison questions. Getting it right means balancing three things simultaneously: keyword coverage, mobile readability, and trust.

1. Start with the brand name

   Put your brand in the first 1-3 tokens. Brand name must match your Brand Registry enrollment exactly — character for character, including capitalization and spacing. Amazon's algorithm and Brand Registry both use brand name as a trust and filtering signal.

   Example: Knours

2. Lead with the primary keyword

   Immediately after the brand, place the head term from your tier_1 conviction list — the highest-volume, most direct description of what this product is. Don't save it for later. Rufus reads the opening tokens with higher weight than the tail of the title.

   Example: Knours Pore Control Exfoliating Toner Pads

3. Add the product form and defining attribute

   Name the physical form factor and the key differentiating ingredient or feature. Be specific — "PHA-based" is more indexable and more trustworthy than "gentle formula."

   Example: Knours Pore Control Exfoliating Toner Pads | Plant-Based BHA + Algae Extract

4. Include one high-volume modifier

   Size, count, pack, or occasion — something that widens your exact-match reach while answering a comparison-shopping question before the shopper has to click through. Numbers use numerals, not words: "90 Count" not "Ninety Count."

   Example: ... | 90 Count, 175ml

5. Close with a short benefit phrase

   Use the remaining budget (up to character 200) for a concise outcome or audience qualifier. This is the part most visible on desktop and least visible on mobile, so it should reinforce rather than lead.

   Example: ... | For Sensitive and Oily Skin — Refine Texture, Tighten Pores

6. Check the character budget in the RankASIN editor

   The Title field shows a CountBar with two markers:

   • 80 characters — mobile cutoff. Everything before this line is what most shoppers see without tapping.
   • 200 characters — hard limit. The bar uses amber coloring below 75% usage to encourage you to use the full budget.

   Aim for 180-200 characters on desktop to maximize keyword coverage, but verify that the first 80 characters read cleanly as a standalone sentence on mobile.

Common mistakes

Keyword stuffing. Stringing synonyms together wastes the title's ability to convert. "Exfoliating Toner Pads Exfoliator Peeling Pads Face Scrub" indexes more terms but reads like spam. Rufus penalizes listings where title, images, and bullets don't feel coherent.

ALL CAPS words. Amazon flags and sometimes auto-edits titles with all-caps words outside of abbreviations like "BHA" or "AHA." Use Title Case.

Punctuation beyond commas, hyphens, and pipes. Banned characters include ! $ ? _ { } ^ ¬ ¦. Restricted characters (~ # * < >) are only allowed in measurement or ID contexts.

Ampersands instead of "and." Write out "and" unless & is part of your brand name.

Promotional phrases. "Best Seller," "Hot Item," "#1," "Free Shipping," "Award-Winning" — all banned. Amazon's algorithm treats them as noise; Seller Central may auto-suppress listings that include them.

Repeating words beyond twice. Amazon's title rules prohibit any word appearing more than twice (excluding articles, conjunctions, and prepositions). The RankASIN editor flags repetitions in the title CountBar guidance.

What happens after save

When you save a title edit in RankASIN, the listing editor starts a 5-second debounce timer. After that window closes with no further edits, the classification engine re-runs for this ASIN — re-evaluating keyword classes based on the updated copy. If you added a tier_1 keyword to the title, terms that were previously "opportunity" may get reclassified because their path to the listing is now established.

Amazon re-indexes the live listing within 24-48 hours. Test after the indexing window closes, not immediately after upload.