Is there any character limit or even suggested character limit for using Schema.org’s description property? For example, in Microdata: itemprop="description"

The Schema.org website reads, "A short description of the item.", but doesn’t specify what it considers short.

  • This shouldn't be more than a sentence or two long.
    – John Conde
    Commented Dec 2, 2013 at 13:55
  • @JohnConde right now its 49 words, 2 lengthy sentences which includes an itemprop='manufacturer' inside of it. Would that be okay? By character its 375 characters long.
    – Ryan
    Commented Dec 2, 2013 at 14:01
  • There is no cap on itemprop description. The short sentence is a mere recommendation only. Your sentences should be as long as it takes to describe what the item is about.. If its about car manufacturing in 1990 and its for Ford Cars and the inventor then your description should cover the year, ford and the inventor. Your sentences should however not use unessacary clutter, like the very best in car manufacturing is clutter. Avoid , and only have one . and your on the right track ;_ Commented Dec 2, 2013 at 14:01
  • Thanks @bybe if you post as answer and the community seems to agree I'll make it accepted.
    – Ryan
    Commented Dec 2, 2013 at 14:04

2 Answers 2


There is no character cap on the usage of itemprop description. The whole point of Schema is to provide correct additional information. By introducing a cap they would be defeating this objective. What they recommend is merely a recommedation and in otherwords they are informing you not to use words that don't describe what the item is about.

For example:

If you have an article about Car Manufacturing in 1990, talks about the company ford and the inventor then your description should be something like:

"A in depth look at Ford Car Manufacturing in the 1990s and the inventor William ford"

A bad description would be something like

"Ford was known for manufacturing the best cars in the 1990's, find out about how William ford made the best cars"

Large sentences generally have lots of , and . ideally you should only ever have one full stop and if possible avoid commas and then you can't go wrong.

  • Perhaps I'm confused in the first description, you're describing the article not a product. For example would something like, The Ford Fiesta is the top-ranked, small car for the last 4 years. Completely redesigned it offers excellent handling, speed, and luxury. be an acceptable Schema description?
    – Ryan
    Commented Dec 2, 2013 at 14:15
  • Well it depends, really you only want to describe what the article is about.. not what directly is in the article if that makes sense. So in your article if you refer to Ford being the best then this is something they find out when reading the article not the description.. It should attribute what the article is about. If it was comparing Ford to Nissan then you could have an description a look at why ford is better than Nissan because this focuses in what its about, you wouldn't say ford is better because it has this and that. Commented Dec 2, 2013 at 14:17
  • This isn't an article though or a blog. Its a website for a manufacturing company. We have 3 main products. On our products page we have the name of each along with a short description of each. Then a link to a product specific page with more information.
    – Ryan
    Commented Dec 2, 2013 at 14:23
  • You could use something like product information about 'make' 'model' or you could use product information about ``make model and some additional information`` or you could use ``make 'model' 'some features'` It's important to note that all methods are valid.. You should use one that makes sense with your page layout too.. Take a look at ebuyer.com/399222-quadcopter-black-white-h107eby they use the specifications as the description while Commented Dec 2, 2013 at 14:45
  • scan.co.uk/products/… use the h1 header... But if your using product then description should be a little longer with features of the product. Since you have a separate specification page you could use the description with the those specs inside and the other page a mere snippet.. Lots of people have different ways they use schema, sadly its not very well set out what you should and not doo. its still fairly new. Commented Dec 2, 2013 at 14:47

Google's example video schema has a description of 568 characters. You can see it here: https://search.google.com/structured-data/testing-tool

SEM Rush suggests 160 characters: https://www.semrush.com/blog/how-to-use-video-schema-markup-on-your-video-pages/

I had a hard time finding any sources that explain exactly how google uses the description and how to optimize it. Based on the above two data points, I'd keep it under 500 characters, aim for around 160, but do whatever most accurately describes the video. Personally I'd try to keep branding and keywords towards the beginning. In other contexts the longer the text the less weight the keywords have. That being said, I'd aim for closer to 160 characters.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.