Im trying to implement schema.org tags, we have coded a rule that every newly generated article should automatically mark author, date etc.
But for some reason it does not fully validate them :
Here is an example of a article we have made.
Related
I tried to add Schema.org markup on my site, with the type Article, then adding some properties on it, when checked on Google Structured Data Testing Tool, it said required certain properties, like dataPublished, author etc.
I can add some properties to meet the requirement, but not all of them. Is this requirement real? I mean really required by the rule? Or just Google rule? I came across this page https://developers.google.com/search/docs/data-types/articles It said for non-AMP, those requirements are only optional (ignored or recommended, non of them said required for non-AMP).
This get me confused, anyone knows about this, what's your opinion? Do Google Structured Data Testing Tool already include AMP requirement?
These are required/recommended for getting one of Google’s search features.
If you don’t want that Google search feature, or if you can’t provide all necessary properties, you can keep everything like it is and ignore the errors and warnings.
Related answers
Should Schema.org dateModified have some default value if not available?
Schema.org/Microdata markup for list of recent posts without providing “author” / “publisher”?
Do I have to create new visible elements to abide by Google's Microdata Schema.org requirements?
Omitting price property for sold products?
Use Schema.org for Article without image property?
Image missing and required - Wordpress AMP Structure doesn't add Image attribute
On Webmasters SE:
Schema.org BlogPosting and image required
Is it mandatory to have rich snippets for AMP pages?
I'm trying to learn how Microdata works and I was looking at the Schema.org website and I kinda get how the basics works because you can find some outlined examples online of the Navigations, Headers, Sidebars and Footers - but I don't understand what properties you can use with more complex item types.
Let's say I have an About page on my site.
Nothing fancy, you just talk about your business but there is a item type http://schema.org/AboutPage you can use.
So I visit that link but to be honest everything you see at that page isn't really written down for beginners I think.
Am I allowed to use all the item properties listed on that specific page or only the the selected few in the Thing section at the bottom of the page because the above two sections are part of WebPage and CreativeWork? I don't have the CreativeWork item type on my page, just the WebPage attached to my HTML body tag.
I always thought you could use those item types as snippets in your HTML to wrap pieces of HTML content together and you didn't need to work with an inherited workflow. Going from wrapped content inside WebPage → CreativeWork → AboutPage item types.
How to find the items types and which properties you can use within them?
First note, you can’t use the vocabulary Schema.org with Microformats. You probably confused it with Microdata, which is one of three syntaxes the Schema.org partners support (the other two are JSON-LD and RDFa). (I edited your question accordingly.)
You may use all properties that are listed on a type’s page.
A type in Schema.org always inherits from all its parent types, up to Thing. So, for example, the type AboutPage is also a WebPage, which is also a CreativeWork, which is also a Thing. You just have to use the most specific type that applies in your case.
For finding appropriate types, simply start at Thing and check the "More specific Types", linked on that page. And repeat.
Another way would be to search for some related keywords on the list of all types and check if a suitable type exists.
The problem is if you're unfamiliar with XML and Schemas because schema.org is as friendly as they can be without actually giving more examples of it, simply because stuff like this is indeed complex to make generic enough to reuse, while verbose enough to explain.
However there are some Google tools which can help you learn:
https://www.google.com/webmasters/markup-helper
https://developers.google.com/structured-data/testing-tool/
And register for Google Webmaster Tools account, and use their data highlighter and test.
Use that in combination with the schema.org examples and definitions, and then you'll properly relatively fast start learning which tags to use and how to nest them.
I have a project which will be using recommendations, not reviews. The only rich snippet that I can find that comes close is the Schema.org "review" but I don't have a "5 star" or anything like that to give it. These are plain text reviews.
Should I just fill in a 5 star since it's a recommendation and inform the poster that it will be displayed as such for ethical reasons or will I also run into problems with Google with having a site with nothing but 5 star reviews?
If your reviews don't have a rating, you shouldn't mark one up. According the the Schema.org FAQ there is no need to mark up every property:
Q: Do I have to mark up every property?
It is fine to mark up only some properties of an item - markup is not an all-or-nothing choice. However, marking up as much content as possible helps search engines use your information to present your page to users in the most useful way. As a general rule, you should mark up only the content that is visible to people who visit the web page and not content in hidden div's or other hidden page elements.
Giving everything a 5-star rating would be a misrepresentation of the content, and that would defeat the whole purpose of using structured data: to allow easier machine parsing of human content.
I get the following errors from the Google Rich Snippet Tool for my website http://iancrowther.co.uk/
hcard
Warning: This information will not appear as a rich snippet in search results results, because it seems to describe an organization. Google does not currently display organization information in rich snippets
Warning: At least one field must be set for Hcard.
Warning: Missing required field "name (fn)".
Im experimenting with vcard and Schema.org and am wondering if I'm missing something or the validator is playing up. I have added vcard and Schema.org markup to the body which may be causing confusion. Also, I am making the assumption I can use both methods to markup my code.
Update:
I guess with the body tag, I'm just trying to let Google discover the elements which make up the schema object within the page. I'm not sure if this is a good / bad way to approach things? However it lets my markup be free of specific blocks of markup. I guess this is open to discussion but I like the idea of having a natural flow to the content that's decorated in the background. Do you think there is any negative impact? I'm undecided.
I am in favour of the Person structure, this was a good call as this is more representative of the current site content. I am a freelance developer and as such use this page as my Organisation landing page, so I guess I have to make a stronger decision of the sites goals and tailor the content accordingly, ie Organisation or Person.
I understand that there is no immediate rich snippet gains, but im a web guy so have a keen interest in these kind of things.
With schema testing, I find it easiest to start from the most obvious problem, and try to work our way deeper from there. Note, I have zero experience with hcard, but I don't believe the error you mentioned actually has anything to do with your hcard properties.
The most obvious problem I see, is that your body tag has an itemtype of schema.org\Organization. When you set an itemtype on a dom element, you are saying that everything inside of that element is going to help describe that itemtype. Since you've placed this on your body element, you are quite literally telling Google that your entire page is about an organization.
From the content of your page, I would recommend changing that itemtype to schema.org\Person. This would seem to be a more accurate description. Once you make that change and run the scanner again, you may see more errors relating to the schema and we can work through those too (for example, you'll probably need to set familname and givenName).
With all of that said, you should know that currently there are no rich snippets that you will gain from adding this schema data. Properly setting this up on your page, is only good to do, especially since we don't know what rich snippets Google or others will expose in the future, but currently you won't see any additional rich snippets in Google search results from adding these tags. I don't want to discourage you from setting this up properly but I just want to set your expectations.
What is the actual procedure for attaching multiple tags to a particular content in a project development. What is this tagging all about???
I need to create a tag cloud for my project in .NET using c#. Help me out as a beginner for basic tagging concept.
Tags are key words add information about the item being tagged. Tags add semantic information about something in an effort to further it.
For instance, A picture of your father on his birthday could be tagged 'dad','family','event','birthday' etc...
By adding tags to the picture you add context and make the image more easily indexable, sortable and searchable.
Tags are purposely generic and flexible because different people can place different personal meaning to the same artifact, or the same person may apply different meaning in different contexts - like adding the same picture to a stock photography web site or checking it into a source code repository as part of a project.
Generally the procedure is to ask the owner of the item to add a list of tags in a text field. Some sites like stackoverflow constrain (most) users to use existing tags, others like delicious make the tags up to the user.
A tag in the software context typically means a meaningful name or attribute being assigned to that software. In version control scenarios a tag is a meaningful name given to a particular state of the files represented by that name. For example the tag 20090401 might be assigned to the source code as it looked on April 1, 2009. Tagging something can also mean describing it or categorizing it. For example software such as IE8, Chrome, or Firefox might all be tagged "Browsers" to categorize them on a download page. Allowing users to create tags and use existing tags is a powerful method to categorize content and help people zero in on items of interest. A tag is simply an extra tidbit of information a person can gain insight into data with.
Multiple tagging is useful for many reasons in software development. For example in my git repository I have a habit of creating tags based on date which can easily be ordered and parsed by a computer. I can also give changes a more human consumable name such as the tag "Deleted_Duplicates", or "RC1", or "V1_Delievered_To_Michigan". This allows for an understanding while also allowing for machine processing.