Here are some observations…
Regarding the Rich Results Test: I noticed on Yoast.com the Organization schema has several properties that aren’t on the schema on our site. I tested them to see if any are impacting this test. If I add a foundingDate property, which Yoast.com has, to the Organization schema, the Rich Results Test detects the Organization schema. I did this by manually editing the code and pasting it into the testing tool.
Here is a link to the results. You can see the foundingDate property added to the end of the code. That is the only change made to the code Yoast is outputting on our site.
As far as I can tell, there isn’t a way to set the foundingDate in the Yoast settings. Is that right? I guess I would need to use the schema api to correct this? If so, hopefully this could be changed in a future update.
Regarding the Schema Markup Validator results for Yoast.com: I inspected the Organization schema and clicked on the @type property. This revealed that on Yoast.com there is Organization schema is in a separate code block after the site’s footer. It’s not in the main Yoast code block in the head of the HTML. Here is the code I am referring to:
</footer>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Yoast",
"url": "https://yoast.com",
"logo": "https://yoast.com/app/uploads/2020/09/Yoast_Icon_SocialMedia_500x500.png"
}
</script>
This code block doesn’t exist on our site.
Is Yoast.com adding this with the schema api?