What are the pros and cons of annotating a personal home page with the http://schema.org/Person microformat?
Add a comment
|
1 Answer
If the homepage contains content about the person, then providing structured data about this person makes sense. And with the vocabulary Schema.org, the appropriate type would be Person.
For conveying that the page is authored by that person, you could use:
WebPageauthorPersonFor a page that is about the person (typically a separate "About" page, but sometimes the homepage is used for this), you could use:
WebPageaboutPersonIn that case it’s probably also the primary entity:
WebPagemainEntityPersonetc.
(And you should provide this structured data not only on the homepage if the person is also relevant to other pages on the site.)
As you tagged your question with privacy:
In general, using structured data can make your content more visible/prominent/accessible/popular/….
Either you want the world to know about the person (in which case using structured data can make this more effective), or you don’t (in which case you should probably not provide the content publicly in the first place).
-
I'm not sure you've listed any non-vague pros (or cons) of adopting schema.org. What do I actually get in real terms by participating? Who participates in it, and how do they benefit from it?– cnstMay 25, 2016 at 20:37
-
@cnst: I didn’t because you didn’t ask for it ;) (I thought your question is specifically about
Person, instead of other types, and the homepage, instead of other pages - with a privacy focus). -- Is your "What do I actually get" question aboutPersonon homepages, or about using Schema.org in general? Anyway, I think such a question would be too broad (open ended, and consumers come and go, and what they consume changes, too).– unorMay 25, 2016 at 20:47 -
I do not think it is fair to dismiss it as too general. It is specifically about
Person-- with a business/restaurant, I can see some potential value being somewhere, but what aboutPerson?– cnstMay 25, 2016 at 20:50