Descriptions

Product descriptions

feed attribute: description

Required on every item, plain text, and long enough to say what the product actually is.

2 checks on this requirement1 of them commonly suppresses a productenforced by Google Merchant Centerenforced by Meta

Google Merchant Center

Required attribute, plain text. Google also re-checks the description against your landing page.

Meta

Required for a catalogue item; Meta shows it on the product detail and drops items with an empty description.

What the requirement says

  • A description is required for every item. It should describe the product: what it is, what's in the box, materials, size, compatibility.
  • The value must be plain text. Shopify's product body is HTML, so a feed that submits the raw HTML body is submitting markup the platform has to parse around — we strip the tags before judging and fix it in the corrected CSV.
  • The description is matched against the landing page, so the page and the feed have to agree about the same product.
  • A description that is only a keyword list or a repeat of the title gives a shopper no reason to click and gives the platform nothing to match.

Why products lose visibility when it fails

  • No description is a required-attribute failure — items without one commonly lose visibility or get disapproved.
  • Thin descriptions (under 50 characters once the HTML is removed) hurt matching and click-through: the item competes against competitors with real copy.
  • Descriptions that carry HTML tags, escaped entities or stray markup are read as broken text by the platform and by shoppers.

The checks we run on it

Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.

CheckBasisRequirementWhat to do
Description missing
criticalcommonly suppressesdescription_missing
requiredDescription is required.Add a plain-text description that matches your product page.
Description too thin
minordescription_thin
data qualityDescription is too short to be useful — thin descriptions hurt click-through and matching.Write at least a sentence or two covering what the product is and what it includes.

Want to know which of your own products fail this requirement?

Audit my description free →

How to fix it in Shopify

  • Admin → Products → the Description field. Rich text is fine on the page, but export the text so the feed carries words rather than markup.
  • Bulk fix: Products → Export, clean the Body (HTML) column, then re-import — or set the description template in your feed app.
  • If you generate descriptions with a template, make them product-specific; a template that reads the same for every product matches nothing.

How to fix it in WooCommerce

  • Products → edit product → Product description (the long description) is the feed value. The short description is not a substitute for it.
  • Bulk fix through Products → Export / Import with the Description column.
  • If the description is built from page-builder shortcodes, submit a plain-text version: shortcodes are markup as far as the platform is concerned.

Worth knowing

  • Reusing one description across hundreds of products is a common matching problem, even though it is not a hard requirement.
  • Escape sequences like & and   count as characters; we decode the common ones for you.

How FeedGuard checks it

  • We strip HTML, escaped entities and stray markup before judging the description, exactly the way the platform reads it — so a page full of rich text is not mistaken for a complete description.
  • Descriptions under 50 characters after stripping are flagged as thin; the tags themselves are removed in the corrected CSV, and nothing is invented to fill the gap.

Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.

What each kind of scan can see

A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.

AttributeStore scan (Shopify)Your feed URL or CSV upload
description
read from the store
product body_html
read from your file
read from your file

Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.

Run the free audit on your store

Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.

Run the free audit on your store

A store scan reads the public catalogue and skips the attributes it cannot see (barcodes and platform-only fields among them); a feed URL or CSV gets the full audit.