Writing the description — the long-form field that has become the listing's backup channel

Before writing a single character of the description, accept what it has become. It is no longer the second sales surface a shopper meets after the bullets — it is an extension, a backup channel for cases where the visible parts of the listing didn't fully match what the shopper expected. The hotel-booking analogy makes the shift concrete: most shoppers pick a country, a star rating, "all-inclusive", look at a few photos and book. A small minority wants to know about dress codes, vegetarian options, the second breakfast and which spirits are included in all-inclusive. The description is the field that has to satisfy that shopper — without being so noisy that the first group disengages.

For pure search-visibility purposes, the description's weight is small enough to deprioritise in the planning. That doesn't mean the field is skippable. It means you stop treating it as a sales-deck slot and start treating it as a tightly formatted backup field.

What HTML Amazon still tolerates — and what it doesn't

The starting rule applies to the description and to bullets alike: no JavaScript, no DHTML, no arbitrary HTML, no UTF-8 special characters, no emoji. Plenty is currently tolerated on the platform, but Amazon can shut any of it off with a single rule change — do not build the description on tags you have no right to use.

The tags that genuinely work, today, are a small set:

  — a line break. Use two in a row ( ) for a blank line between sections.
 — paragraph. Use it for short logical paragraphs rather than as a big-spacing hammer.
 — bold. Use it on the opening 2–4 words of a feature line, the same way the bullets use an eye-catcher.
 and  — italic. Use sparingly for emphasis inside a sentence, not as a styling flourish.
<ul> and <li> — unordered list with bullet markers. A nested <ul> inside a list item even produces the secondary sub-bullet style (the outlined / hollow marker), which is useful when a feature has a small group of qualifiers.

That's effectively the full toolbox. Numbered lists work in some categories, but the unordered list is the workhorse — and the only formatting that reliably renders the way you wrote it across mobile and desktop.

The worst case: a single unbroken wall of text

The single biggest failure mode in this field is the giant uninterrupted paragraph. Shoppers don't read it. The information you spent time writing disappears between "Customers also searched for" and the sponsored ad rail underneath. It doesn't matter how good the copy is — if it arrives as one block, it isn't perceived.

Any HTML-structured layout beats an unstructured block. But "any HTML" isn't the bar; the bar is a description that respects how the eye reads on a screen.

The white-space rule: break every ~160 characters

The white-space theory is the one heuristic worth memorising for this field. Roughly: the absence of elements draws attention in the opposite direction. If the right side of the description has a large empty area while the left side runs solid text, the eye gets pulled left and the right-hand copy is never registered. On a typical Amazon description column, that means a line that runs for the full column width is read; a line that wraps awkwardly and leaves a deep right-hand gap is half-read.

The working rule that comes out of this: insert a at roughly 160 characters — about the halfway point of the available line on a standard desktop description column. The result is a description that reads in tidy two-line chunks rather than as a frayed paragraph, with an <ul> list pulled out for the core fact rows.

Used on a simple product — for example a robust all-purpose rope — that looks like a short opening line, a break, a <ul> with the hard facts (dimensions, what it is suited for, what it is rated to), another break, and a closing benefit line. Same total word count as the wall of text; very different read.

Adapt the structure to the product and price

The list-and-break template is a default, not a law. A €4 commodity often only justifies a five-line description with one short list; a €200 appliance benefits from a longer breakdown with several mini-sections. The judgement call is: how many concrete facts does this product carry that a shopper could legitimately want to check before buying? Match the description's density to that answer. Either way, keep within the small HTML toolbox above.

Where the description physically sits — and why mobile hides it

The core problem with the field isn't writing it; it's that the shopper rarely sees it. On mobile, the description is folded behind a tap together with the bullets — and on many Vendor category templates it gets dumped at the very bottom of the detail page, below every related rail. Check the default rendering for your specific category before deciding how much polish the description deserves:

Some categories show the description high, with the bullets below.
Some show the bullets high, with the description below.
Some collapse both into a single combined information window.

Each of those positions earns a different amount of polish. The categories that bury the description three folds down don't deserve the same investment as the ones that put it directly under the buy box.

The A+ Content rule: when to leave the description (almost) empty

For Sellers running A+ Content (EBC), the description as a public-facing field effectively disappears — A+ modules render in its place. The question of how to write a long persuasive description doesn't apply: there is nowhere to show it. The field still exists in the backend, but it is no longer what shoppers read.

For Vendors running A+ (the equivalent of EMC / Enhanced Marketing Content), the same logic applies but with one extra wrinkle: in many category templates the description still renders somewhere — usually far down the page, in plain text. The pattern that works:

Either write a short, catchy, immediately comprehensible description — one paragraph, two at most, that names the product cleanly and repeats the most important synonym set.
Or leave the field essentially empty: a single character ("0" or "1"), or the brand name and slogan set as a large, plain line — without the rest of the "chicky-micky" prose underneath.

The empty / minimal route is not laziness — it's a deliberate choice not to spend resources on a field that nobody reads once the A+ modules are carrying the story. The synonyms that would otherwise live in the description are routed into the A+ alt-text and the backend search terms instead.

What this episode hands off

Episode 07's output is a description that fits the category it appears in: HTML-structured with the small tolerated tag set, broken every ~160 characters so the white-space rule doesn't lose the right-hand half, and either short-and-catchy or deliberately minimal when A+ content is live. Episode 08 picks up the synonyms that none of the visible fields could carry — the backend search terms, the invisible field where indexing happens without a single shopper ever seeing the words.

Writing the description — the long-form field that has become a backup channel.