Both are solutions for semantically annotating your content, but in very different ways:
Microdata extends HTML5 (e.g., by introducing new attributes like itemprop), while Microformats only uses existing HTML mechanisms (like class and rel attributes).
With Microdata, you can use almost any vocabulary (a popular one is Schema.org), with Microformats you can ...
There is this: https://schema.org/QAPage
and these: https://schema.org/Question + https://schema.org/Answer
Which you can indeed use …
and validate: https://search.google.com/structured-data/testing-tool
To build your own FAQ page.
<div itemscope itemtype="http://schema.org/Question">
<h1 itemprop="text">What does FAQ stand for?</h1>...
The vocabulary Schema.org has the types Question and Answer (added in version 1.1 from 2014-04-04).
This is not only for Q&A sites, but also for FAQs, as Question explicitly mentions (bold emphasis mine):
A specific question - e.g. from a user seeking answers online, or collected in a Frequently Asked Questions (FAQ) document.
Google recommends using microdata, but it does support three formats: microdata, microformats, and RDFa. A big reason to choose microdata would be that the examples that Google gives on it's website and those on schema.org are in the microdata format.
Here is a site that has a huge table of the various advantages and disadvantages of the three formats. ...
The W3C provides Semantic Web logos. Here are the versions without the W3C logo:
But in my experience, these logos are used to represent the concept, they don’t necessarily signal that structured data is available for that page.
For signaling that RDF is available, W3C’s RDF icons are commonly used. Here is the version ...
Here is your example HTML in the testing tool.
Works perfectly fine for me, with everything you say is a problem recognized, and no warning:
The example code from Google's docs does display the warning, but that's because of a syntax error which is breaking the markup:
<img class="photo" src="anvil_executive.jpg />
Note the src attribute is missing ...
May be this example will help you
<div itemscope itemtype="http://schema.org/VisualArtwork">
<link itemprop="sameAs" href="http://rdf.freebase.com/rdf/m.0439_q" />
<h1 itemprop="name" lang="fr">La trahison des images </h1>
A <span itemprop="artform">painting</span> also known as
This issue is rather common and found in mostly poorly edited or made WordPress themes. entry-title, updated and author are all related to the Hatom markup which requires hentry to included above the fold and ideally in the body.
It's likely that your website is missing author, updated and entry-title leaving hentry still within your code. View source and ...
There is no schema entry for FAQ, you most likely best of adding it as a 'WebPage'. or using the about. It's not required to use rich snippets for all pages. It holds little SEO weight if any. Google will be able to establish it as a FAQ page without any markup of this type.
Use this format: Replace Organization with Place use <span itemprop="thing"> Home For Sale
<div itemscope itemtype="http://schema.org/Organization">
<span itemprop="name">Beyond Window Cleaning</span>
Located at: div itemprop="address" itemscope itemtype="http://schema.org/PostalAddress">
Google supports a wide range of ratingValues should it be 1-5, 1-6, 1-10 or even a 1000. You do however have to use bestRating since Google assumes 5 by default. It's very flexible and can even start from zero, one or even ten using worstRating.
1-100 Example on Schema AggregateRating
There is no advantage of using unordered lists vs tables for SEO purposes, as far as my research has led me to believe.
On the other hand, since you are using list items to simulate table rows, I fail to see the logic behind this decision.
If the reasoning behind your decision is because "the tables are hard to render correctly in mobile devices," why not ...
Before structured data Google preferred microformats. They still do, but for things like last modified, quick overview of categories, site content update status, or other legacy knowns. It's almost real time, very quick index changes, with hubs to boot. Very much better to have these rather than ETAGS or 304 + AI trying to figure relevant changes.
Google has been promoting Schema.org as the preferred vocabulary for structured data. According to their Structured Data Policies:
The data may be embedded in your webpage using any of three supported formats: JSON-LD, RDFa, and microdata.
I seem to recall Google used to read Microformats as well but can no longer find reference to it in any of their ...
Google only wants you to mark up data that is visible to the user. See their Microformat quality guidelines:
Markup should not be used to hide content not visible to users in any form, since it might create a misleading or deceptive search experience.
If you want Google to use your marked up data, using meta elements or hidden elements is not allowed ...
@closetnoc appears to be right that these are not rich snippets but what are called featured snippets.
These snippets appear to be transitory as the "eve mattress" featured snippets have been replaced by site links. But looking at two worked examples on www.evemattress.co.uk & shop.silentnight.co.uk it looks like Google favours well structured html ...
Got a website where hAtom feed is implemented correctly - with author, update, published - and a website where I have removed all hentry classes.
I don't feel any difference, but seeing search console without errors brings me some satisfaction :D
Definitely add the http://schema.org/Person for the artist (use author property), including filling out the url property within http://schema.org/Person with a social media link (google plus or facebook ideally).
I don't see a link to related art works, related links can be set with the properties.
There's also no image property set inside ImageObject.
Showing content that you own in a couple places on your site will generally not hurt you. In the worst case, Google will not index one of the two places that content appears.
Duplicate content can become an issue that can get your whole site in trouble when
You have no content of your own, you are only syndicating content from other sources
Much of your ...
As of end August 2017 the FAQPage type was added to schema.org. It is a subtype of QAPage with the difference that each question has only one answer.
In the spring of 2019 the feature was added to google search and is supported by the Rich Results Tool.