Allowing schema.org markup
Since schema.org is aiming to make it easier for people to find content while searching on bing, google, and yahoo, it seems like a pretty valuable resource for wordpress users. I, for one, would love to be able to mark up my recipes with the schema.org/recipe markup so that I can get more traffic to my blog. This would require wordpress to add “itemscope” and “itemprop” as allowed markup. It seems like these markups have no possibility for introducing harmful code, and it would be an easy addition. Please look into schema.org and consider this – it would be a boon to many wordpress users!
The blog I need help with is seletsucre.wordpress.com.
I forgot to include “itemtype” which would also need to be added – but it looks like it is just those three tags.
excuse me! It is an Idea or advertisement?
An idea – I have no affiliation with schema.org, I just really want my recipes to show up on google recipes!
Search for a plugin called Schema for WordPress.
You’ll need to know how to upload date to a sql table then you’ll have all the schema available to insert in to your code via a button on the wysiwyg editor.
data, not date!
Thanks for the info, but unfortunately I’m on wordpress.com not wordpress.org so I can’t use plugins.
This seems like a good idea to me. It’s fairly trivial for them to add the necessary attributes and tags, it would just depend on whether it is deemed worth the security risk of adding them. Whenever you add more flexibility in what tags are allowed there is a theoretical reduction in security, but I can’t see these particular examples being of any consequence.
WordPress.com tags already function as Technorati tags; surely this would not be difficult to do, but why does it not happen automatically? Tags are tags: you’d think something whose business it was to scan for specific types of content would be able to read WordPress.com tags.
Not entirely an “easy” addition since it would require the editing of over 140 themes to add those to them and then the subsequent testing to make sure there were no “oops” that happened during the additions.
The topic ‘Allowing schema.org markup’ is closed to new replies.