description — Schema.org Property Guide

How to use description correctly

A concise textual description of the entity, not an invitation to insert unrelated marketing text.

Common mistake to avoid

Use information readers can verify on the page; do not copy a generic site-wide description onto every product.

Applied example and verification

A product description should reflect the actual item and its characteristics, while an Article description summarizes the written work. Repeating a generic marketing paragraph across every entity can make the markup less informative and may misrepresent the page. Read the surrounding content before choosing a description. If the page discusses limitations, variants or conditions, avoid writing a summary that conceals those important distinctions. Do not use an automated generator to add unsupported specifications, prices or claims. A useful description is accurate, concise and tied to the entity rather than the website as a whole. The example here is illustrative only; it is not a recommendation to paste the same description on every page.

Example property value

This snippet is illustrative and may not be sufficient markup on its own. Replace placeholders with real values.

"description": "Example description — placeholder"

Read the official Schema.org description definition. Google feature requirements, when relevant, must be checked separately against the official Search Gallery.