What is the purpose of using meta properties? is it a good idea to implement it on my site?
meta property=“og:title” is one of the open graph meta tags.
This properties define objects in a social graph. They are used by Facebook.
og:title stands for the title of your object as it should appear within the graph.
(Find more http://ogp.me/)
Related
I am talking about the Open Graph tag here. Can I put the og meta tag anywhere on the page?
I want to use my detail page image for the og tag, the easiest solution is putting the og:image tag in the body of my page.
Open Graph meta tags should always be nested between <head> tags.
To turn your web pages into graph objects, you need to add basic
metadata to your page. We've based the initial version of the protocol
on RDFa which means that you'll place additional <meta> tags in the
<head> of your web page.
http://ogp.me/#metadata
Additionally, keep in mind that order of the tags matters, especially when dealing with array tags (which includes og:image).
Open Graph Tag should be always always be placed on header tag until knowledge goes.. People please correct me if I am wrong..
Where should I put schema.org tags?
I have 3 options:
at detail page of article
at category page where are articles of
category
at search page
Should I put schema.org tags on all these pages or?
You can use Schema.org on all pages.
Various consumers might find it useful. Why should they have to visit a specific page to see your Schema.org markup for content they already see?
Just make sure that you don’t create several items for the same thing on the same page, unless you denote them as being about the same thing (e.g., with Microdata’s itemid or by using the same subject URI in RDFa).
You could use mainEntity/mainEntityOfPage to denote which item the page is primarily about.
the site that I'm working at is designed in a such way that CSS class is set for the tag on all the pages and the css classes used are different for all pages. Each page has common elements such as a header, a footer and a nav bar. I'd like to set up a single page template and include all common elements there but the body tag stands in the way. Is there a way to control a template from a content page? I know I can specify a code behind for content pages but i can't rely on content authors to enter it correctly each time they add a page. My current thinking is to set up multiple page template, one for each css class that is referenced in the body tag and put the common page elements into user controls. This is less than ideal because I will end up with lots of mostly identical templates and my user controls would not be editable easily. I guess I would have to use shared content items and such making the content authors hunt all over the site. I would have been much simpler to update the common header in a single page template.
Can someone please suggest a way?
I submitted a reply in the Sitefinity forums where you originally posted this, but just in case you check here first I'll ask the same question: how is the css class for body determined?
if it can be done programmatically you can use the code-behind of the Master Page for the template to set it so that it's handled automatically.
If this won't work, tell me more about how the css class is assigned and I will try to come up with an alternative.
hope this is helpful!
I have integrated the Google +1 button into a website ( http://www2.highpoint.edu ).
I tried to use schema.org <meta> tags to provide Name, Description, and Image for the +Snippets information, but it doesn't work.
When I use the +1 button and try to post to Google+ about the website, it picks an image that I don't want. And it won't pick the image I have set with the <meta> tag.
My questions:
How do I get the +Snippet data populated from schema.org metadata?
For a page with 2 or more +1 buttons, can I have different name/description/image for each +1 button? Or must every +1 button on the page use the same metadata?
EDIT
I think it is best to use Open Graph Protocol instead of schema.org. That is, schema.org shouldn't be used at all. Facebook supports Open Graph Protocol, so you can kill 2 birds with 1 stone this way.
More importantly, Facebook provides a great debugging tool that tells you what exactly is getting parsed for a given URL: http://developers.facebook.com/tools/debug
I am still not sure about having multiple +1 buttons on the same page with each +1 button having distinctly different meta data.
In response to question 1:
I checked your page. It looks like you have a normal meta title and description. This should work for the +1 button, but it may take some time for the +1 button to pick up the changes you've made.
If you'd like control of the image, though, you will need to use schema.org markup or open graph as described in the official FAQ: http://code.google.com/apis/+1button/#plus-snippet
And for question 2:
If you are using schema.org markup, the +1 button will read the content for the itemscope nearest the top of the page's source code.
It does not work for me either. I have both Schema.org and Open Graph in the web page (eg. http://r.mycrep.net/3Nkh/), Multiple validators (Facebook's and one other) read info correctly.
I guess that Google still does not support metadata for everybody :-(
I am using FAST For SharePoint to crawl a non SharepPoint website. The website crawled with no error, I can get the results of any keyword.
I want to create refiner on result page by html page meta tags. There must be two level refiner; category and sub category. If user clicks category, refiner panel must show all related sub categories.
The meta tags like this:
<meta name="Category" content="Products"/>
<meta name="SubCategory" content="Electronic"/>
How can I extract meta tags that crawled html page(s) with FAST For SharePoint Webcrawler?
I tried to add the meta tag names to FAST Search Administration > Managed Properties and configured refiner panel for those meta tags, but I could not get result. It does not work.
Thank you!
If you want to use custom Managed Property, you need to first bind them to a crawled property. Crawled properties are created automatically during the crawl, or you can create them in powershell, see the following link: http://msdn.microsoft.com/en-us/subscriptions/ff393776(v=office.14).aspx
If I understand well, what you are trying to do is getting information that is in the HTML of your page. In this case, you cannot use the out-of-the-box web crawler to get this information. I suggest you take a look on custom BDC connector, if you want to create a custom crawler to get the information you want: http://msdn.microsoft.com/en-us/library/ee557349(v=office.14).aspx