I have a Website that typically describes an Organization/LocalBusiness/FurnitureStore and what it sells: brands (not owned), product categories, single products (not owned), service categories and single services (owned).
I need help to define the best/correct microdata structure for the whole website.
I would like to help a simple, clear example/tutorial for dummies.
Each WebPage has the following structure:
A. header - FurnitureStore: logo, name, nav.
B. main
C. footer - FurnitureStore: copyrightHolder of Website, vatID, url to "Contact us" WebPage (with address, telephone, email etc.), url to "Privacy policy" WebPage etc.
The website has the following structure:
1. Homepage/main:
1.1. FurnitureStore short description with url to "About us" WebPage.
1.2. FurnitureStore sold products and services categories list with name, image, url to single product/service WebPage.
1.3. FurnitureStore sold brands (Organizations) list with name, logo, url to single Organization WebPage (on this Website).
QUESTIONS:
a. is it better to directly use itemtype="FurnitureStore", or itemtype="LocalBusiness" and additionalType="FurnitureStore", or other solutions (WebSite?)?
b. In lists, is it better to put only the url to the item specific webpage, or also other details, like name, logo/image etc.
c. in products categories list is this code right?
Tables
d. In (not owned) brands list, is it correct itemprop="brand"?
2. "About us" WebPage/main:
2.1. FurnitureStore long description.
"Contact us" WebPage/main:
3.1. Google map
3.2. Contacts and address
3.3. "Contact"/"Request quote" Form
QUESTIONS:
e. Both "About us" and "Contact details" WebPage are describing the FurnitureStore. Is it right to apply itemscope itemtype="FurnitureStore" to the body, so that header and footer microdata are applied? Is it right to apply the itemprop="sameAs" to the links from/to Homepage/About us/Contact us.
4. Single “Product Category” WebPage/main:
4.1. name
4.2. description
4.3. images (products gallery)
QUESTIONS:
f. If main describes an Offer/Category or Product Is it right to apply itemscope itemtype="FurnitureStore" to the body, so that header and footer microdata are applied? Or is better to apply itemscope itemtype="Offer" to the body and itemprop="seller" to the header with itemref="footer"? mainEntityOfPage can help? Is there a better solution? What changes?
g. Obvious an Offer/Category and most Customized services have no fixed price: usually you must submit a request for quote. In Google snippets is it possible to show "submit a request for quote", or "starting from n EUR" or similar as price value?
5. Single “Brand” WebPage/main:
5.1. name
5.2. description
5.3. images (products gallery)
5.4. url to the official website of the brand
QUESTIONS:
h. If main describes a brand, is it right to apply itemscope itemtype="FurnitureStore" to the body, so that header and footer microdata are applied? Or is better to apply itemscope itemtype="Brand" or itemscope itemtype="Organization" to the body and another itemprop (seller?) to the header with itemref="footer"? mainEntityOfPage can help? Is there a better solution? What changes?
Related
I exported all the tags required by Facebook from my third-party online store (Lightspeed) and the data stream works as expected in terms of automatic updates, but products on my facebook page shop (Shop tab) are displayed with the brand name first — L'Oratoire Saint-Joseph — followed by the product title.
See it live : https://www.facebook.com/osaintjoseph/
The unfortunate result is that the text under many products is exactly the same. Is there a way to display the Product Title before the Brand Name?
Lightspeed support told me I had to take it up with Facebook. I am awaiting their reply. See my questions in the fb developer forum here : https://developers.facebook.com/settings/developer/community/
There are 3 ways to add products to Facebook Shop:
Manually
Data feed (e.g. CSV import)
Third party plugins (which you’re using).
Manually – the user is only able to enter 4 properties; title, description, image & variant. See facebook.com/business/help/293945421560847. There is no concept of product brand.
Data feed – this allows for additional properties, such as brand name. In the table, see example files and select product (csv, tsv or xml) facebook.com/business/help/120325381656392?id=725943027795860. However it looks like all Facebook does is concatenate string, that's the product title becomes "{brandName} – {productName}". It look like brand name is not used anywhere else. Nor is there an option to change the way it's displayed. If you edit the product, you should be able to see this in the Product Title.
Shop tab (third party plugin) – (May be it's me, but I found their documentation hard to follow) – They send an XML feed to Facebook support.shoptab.net/hc/en-us/articles/200583466-XML-Feed-for-Facebook-Storefront-with-ShopTab. They do not appear to have a concept of brand. Try and examine the data. I would expect the brand name to appear in the product title. Alternatively they allow for CSV, which also doesn't contain brand name support.shoptab.net/hc/en-us/articles/200583906-CCNow-Integration-with-ShopTab-s-Facebook-Store-App
Summary
If possible, examine the data that is sent from Shop tab to Facebook.
Try and find out if you’re able to exclude / alter the string concatenation of brand name from product title in Shop tab. If not raise a support ticket with them.
Alternatively see if you can manually edit the product title in Facebook. It’s not a long-term fix, but helps understand how the system are integrated.
In a web page each registered company has own profile page with a list of records belonging to a company. I'm using Schema.org Organization structured data for that page and that schema markup requires URL property. As I understand it should contain e.g company home page url. The problem is that we do not store that kind of information.
If company profile URL in our page is: www.mypage.com/unique-company-profile can I use same url in schema URL property or it has to be an URL with a different domain?
Schema.org doesn’t require the url property for Organization (it never requires any property). Consumers (like Google Search) require properties for their features (like rich results). So, it’s perfectly fine to have an Organization without url; you might just not get a certain feature in a certain search engine.
As far as Schema.org is concerned, the url property can have a site-internal URL as value. A common structure is to use url for your own page about the organization, and sameAs for the organization’s official site.
<link itemprop="url" href="/organizations/acme" />
<a itemprop="sameAs" href="https://acme.example/">official site</a>
That said, again, a consumer might have certain restrictions; if you care about the feature they offer, you have to check their documentation.
I have built a vacation rental website which allows users to add their home to my site, this will include all info, map, reviews and photos.
I am not sure how to mark up each property detail page with the correct Schema.org data.
I have been looking and LodgingBusiness looks close, but these are not hotels, just someone's home to rent for a few weeks. I would ideally tag the name, photo, description, map, reviews, location too, but unsure about the actual main category.
For the places which get rented, you can use the Accommodation type. There are more specific types, like Apartment, Suite, House etc.
It offers the properties you are looking for:
name, image, description
hasMap
review
address (or containedInPlace)
For documentation about all the accommodation-related types and properties, see Markup for Hotels.
I am marking up the content on my website with microdata. I am a Local Business and use this hierarchy:
Organization/LocalBusiness/TravelAgency/
Do I need to repeat all the relevant Properties for each category: PLace, Organization, Local Buisness and Travel Agency in each page of my website?
http://schema.org/TravelAgency
I have many sub-pages and it is over-kill to repeat everytime on the page the location, address, telephone, etc. of the business.
For specific sub-pages can I cut out the higher categories?
For example: If I have a page: Special Offer Weekend in New York
Do I add all the Properties or can I just add the ones relevant for TravelAgency and potentially Price?
http://schema.org/PriceSpecification
Thanks for your help
PS: I ask this because I have read that it is not good to have invisible content for the user.
Schema.org doesn’t define any required properties, so everything is optional.
But note that there is no concept of "website" in Microdata. The Microdata always gets parsed per document. So if a Microdata consumer parses your "Special Offer Weekend in New York" page, it will not get the telephone/address/etc. of the business, even if these would be specified on all of your other pages.
If you don’t want to markup all the visible content about your business on every page, you might want to link to a page where this data is marked up (e.g., the front page) by using an appropriate Schema.org property.
Example: On "Special Offer Weekend in New York" (Offer), you could use the seller property to link to your front page (TravelAgency).
It’s not defined in Microdata that those links should be followed for parsing Microdata, but that way parsers can (if they want to) understand that all these pages belong to the same TravelAgency.
After a bit of research I found recommendations as in:
<div itemscope itemtype="http://schema.org/Product">
<a itemprop="url" href="URLOFPRODUCT">Link</a>
</div>
But I am trying to avoid linking to the product, on the product page.
Another approach I've noticed is the use of meta tags but outside the head, which is a big 'no no'.
Any suggestions?
For providing a URL in Microdata, you must use "a URL property element". Currently these are:
a, area, audio, embed, iframe, img, link, object, source, track, and video.
a and link are the only "generic" elements from this set.
If you don’t want to provide a visual link (by using a), go with link (which is typically hidden in browser default stylesheets). This is not "a big 'no no'", as link elements are allowed in the body if used for Microdata.