Geek Answers Handbook

What is the correct schema.org level microdata data type for the brand / company homepage?

I would like to hear what type of schema.org itemtype others would recommend to use or used when filling out microdata on a retail brand homepage. Take, for example, TOMS shoes :

Example # 1 - Using / Corporation as a high-level item can include many of the organization’s great microorganisms, but nothing relates to a retail store.

<html itemscope='itemscope' itemtype="http://schema.org/Website> <head></head> <body itemscope='itemscope' itemtype="http://schema.org/Corporation> various microdata here probably including Product microdata </body> </html>

NOTE: tickmaSymbol is the only schema.org-specific schema.org property, but TOMS is not.

Example # 2 - This code will work if TOMS starts its own channel of physical retail stores and each location has its own home page. However, for TOMS's.com, although accurate in schematic and more descriptive on the face, it is an incorrect microdata layout for TOMS.com because / ShoeStore comes from / LocalBusiness - which should represent the physical location.

 <html itemscope='itemscope' itemtype='http://schema.org/Website'> <head></head> <body itemscope='itemscope' itemtype='http://schema.org/ShoeStore'> a whole bunch of jabber here </body> </html>

NOTE. Since TOMS is virtual and therefore cannot be / Store, this means that you are losing really cool properties like "currenciesAccepted", "paymentAccepted" and "priceRange".

Is this a sit-and-wait situation until more schemes for virtual sites are approved or is there a way to go through validation to get the best of both worlds?

+4
source share
1 answer

Assuming that you look at it more or less from an SEO point of view, remember that the main search engines currently make only very limited use of microdata, and the schemes you are talking about (corporation and shoe store) are not used in my opinion for nothing (for now). So, to some extent, I think that at present all this is pretty much hypothetical.

However, I think it’s important to remember that you can use very different microdata depending on the function of the page. You ask about the home page, for which enough microdata may well be added to describe the name and category of the corresponding object. Detailed product data will be displayed on the product pages, more detailed organizational data on the contact or contact page, etc. In other words, use the layout that best allows you to encapsulate the main purpose of the page.

By the way, they recently added the GoodRelations dictionary to Schema.org, so the scope of product descriptions and other business data has simply grown significantly.

+1
source

More articles:


All Articles