A description too short to answer anything
One line where the customer expected dimensions, material and what is in the box. They either ask support or leave—both cost more than writing it would.
The symptom
The product page has a photograph, a price, an Add to cart button—and under it, one sentence. Sometimes the sentence is the product name again.
It usually is not laziness. It is what happens when a catalog is imported from a supplier feed that carried a name and a price and nothing else, or when the first fifty products were written properly and the next four hundred were not.
What it costs
Whatever the description does not say, someone has to say instead.
- Support answers it, one customer at a time. Dimensions, material, what fits what, what is in the box. Every one of those messages is a description that was not written once.
- Most people do not ask. They compare with the competitor whose page answered the question, and the sale is lost without leaving a trace anywhere you would look.
- There is nothing to rank. A page whose text is the product name has no content to match against anything but the exact name—which is the one query where you compete with every reseller of the same item.
- Feeds inherit the gap. Google Merchant Center, marketplaces and comparison engines take the description field. Thin in, thin out.
The threshold matters less than the trend. Merchlint uses 200 characters, roughly two sentences. That is deliberately low, because the aim is to find pages that answer nothing at all, not to grade prose.
How to check it yourself
WooCommerce has two description fields. This check measures the long description—the
Description tab under the product (post_content in the database). The short description next to
the photo is a separate field, post_excerpt.
What counts is the text the customer sees: no HTML tags or shortcodes, and a run of spaces or blank
lines counts as one space. CHAR_LENGTH(post_content) in the database is not enough here—a
description built in Divi holds hundreds of characters in the field while the customer reads one
sentence. This command counts the same way Merchlint does:
wp eval 'foreach ( wc_get_products( array( "status" => "publish", "limit" => -1 ) ) as $p ) {
$t = preg_replace( "~\[/?[a-z0-9_\-]+[^\]]*\]~i", " ", $p->get_description() );
$t = trim( preg_replace( "/\s+/u", " ", html_entity_decode( strip_tags( $t ) ) ) );
if ( mb_strlen( $t ) < 200 ) { echo $p->get_id(), "\t", mb_strlen( $t ), "\t", $p->get_name(), "\n"; }
}'
It prints the product ID, the number of characters and the name. On a large catalog it takes a few minutes. It does not see a description built in Elementor, because Elementor saves it outside the description field; Merchlint reads it from Elementor’s data.
How to fix it
- Sort by what the products earn, not alphabetically. Twenty descriptions on products that actually sell are worth more than four hundred written in catalog order.
- Write the answer to the question support gets. Open the last twenty messages about that category. The description writes itself from them, and it is the text customers actually need.
- Put the facts in attributes, the reasons in the description. Dimensions, material and weight belong in structured attributes where filters and feeds can read them. The description is for what the numbers do not say.
- Do not paste the supplier’s text. Every other store selling that item pasted the same paragraph. Duplicate descriptions are a problem of their own, with a separate check in the Pro add-on, which is still being prepared.
When it’s a false alarm
- Descriptions built with a page builder other than Elementor or Divi. Some builders save the text outside the description field, so the field is short while the page is full. Merchlint counts Elementor and Divi correctly. With another builder, open one product’s page before you work through the list.
- Catalogs where attributes carry everything—fasteners, electronic components, spare parts. A bolt does not need two paragraphs; it needs a correct spec table.
- Products deliberately kept minimal, such as gift cards or a single-line digital download.
In all three cases, hide the finding once and it stays hidden across scans and plugin updates.
How Merchlint finds it
Merchlint reads the long description of every published product. On Elementor products it also
reads the text Elementor keeps in its own data. It counts only what a customer sees: shortcodes and
HTML tags are removed, an entity such as counts as one character, and runs of whitespace
count as one. That length is compared with the threshold of 200 characters. The free plugin has no
setting to change it, but a developer can do it with the merchlint_scan_settings filter (the
c1_min_length key).
The finding shows the length it measured and the threshold, so you can see at a glance whether a product is at 12 characters or at 190. Those are very different problems.
Confidence: F—fact from the database. A length is compared with a fixed number.
The finding carries no revenue figure. If one of your best sellers has a short description, it also shows up under Where to start at the top of the audit.
Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com