I have web page e.g.
bricks.com/list
with navigation bar, side bar and dozen of small articles on the page. I should make it so users can share on facebook just one of that articles from the page without open another page to show single article.
Some people says it is impossible :) . Is it?
Related
I have a website that I added the Facebook like button to it. Assume the website url is "www.xyz.com"
In this website I have articles, each of which has an id in the url like this "www.xyz.com/3/some-text-here"
In my website "www.xyz.com" and "www.xyz.com/3/title-here" refer to the same contents. My question is how to tell Facebook that these links are the same so if a user liked or shared one of these web pages then both of the pages will get the same numbers of likes and shares.
Thanks.
The solution is to set the data-href property, in one of the pages, to the other page.
reference: https://developers.facebook.com/docs/plugins/like-button
I'm trying to figure out why Facebook is creating fragmentation with its pages. I really don't understand it. Also is there anything that can be done about this.
Here is a perfect example I have my Facebook company page for "Scoreoid" (http://www.facebook.com/pages/Scoreoid/245182948843019) this has my content wall post's, photos ect..
Then I have this page which I guess is only connected to the Scoreoid website which is new and was automatically done http://www.facebook.com/pages/Scoreoid-the-ultimate-game-platform-for-developers/269861406410210
This is the page for the Scoreoid site which has 130 likes but of course on Facebook it only shows 15 another question either way why is there two pages why can't everything be connected to one page.
All this does is create fragmentation which is noting but bad user experiences.
It would max sense to have everything directed to the Facebook main page. Of course I have other questions for which do I run advertising on which should I update with content?
I've already answered you here two weeks ago:
Facebook Likes not showing on Facebook page but show up on site
Facebook pages like counts are NOT THE SAME as like counts for a web site. They cannot be joined by Facebook as they are two separate IDs. You can have your parsing scripts add together the two like counts yourself.
This has been my experience. If you add the open graph meta tags (og:url, og:image, og:type, etc.) Facebook will create a "facebook page", but this page will only be accessable by you. This is the message that facebook will show on this open graph page: http://snag.gy/z9UfG.jpg
If besides this you create another page then it will not be linked with this page. I recommend you use the page you created as that page is accessible by everyone.
If this is not your case then please clarify.
I would be grateful for some assistance with Facebook Social Plugins.
I have a bunch of portfolio items on my website that are rendered with a fb-comments-plugin at the bottom of the page.
At the top of the page (in the header) is a "like" button that is designed to cover the whole site (i.e. if you "like" the site - click the "like" at the top of the page). But, if you want to "like" the post - click the "like" alongside the post.
Anyway, every now and again - the comments plugin on one of the portfolio items indicates to me:
"Warning: {url} is not accessible"
This does not appear to be consistent across all items. For instance:
http://www.greensidefilms.com.au/portfolio/bride/
does not work, but:
http://www.greensidefilms.com.au/portfolio/twilight/
does work...
Confused I am, seeing as it is exactly the same code generating all these pages.
Is there something not quite right with the og meta tags that is causing the plugin to be confused?
Those links you provided are dead
I had some trouble when I first started working with the Facebook social plugins and found that the problem you are describing is with the APP ID, it is designed to work with a domain in your case yes it is the same domain however you should double check if the same APP ID is being used in all your plugins, using the wrong APP ID will cause that kind of behavior.
Please indulge my simplistic example:
Let's say I have 1 million pages on my site. Each page has an ID number (i.e. www.mysite.com/product.php?id=1 .... upto id=1,000,000
I want to make a page that allows users to email themselves the link to the page (or email a friend). This page is also dynamic and comes from the product.php, so like this:
www.mysite.com/email_a_friend.php?id=1 .... upto id=1,000,000
Imagine I do this and now google wants to crawl 2 million pages instead of 1 million. This seems pointless since the page doesn't have anything of any value on the email page. Also, consider that the email page would actually be a pop-up window on the product.php page.
What is the best way to handle this?
Should I block it (email_a_friend.php) through a robots.txt file?
Or should I perhaps used java or something else for the link that google would ignore anyway?
Thanks!!
If I'm understanding your question correctly, you have an e-commerce site and want to implement a share button for a particular product. What you don't want to happen is have google index the page that the share button goes to.
If that's the case, just add a rel="nofollow" to the link in your php that generates the link and you should have no problem.
Here is a google help article that explains how google does not follow links with the nofollow attribute: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=96569
I am looking to add social icons to our site, giving customers the ability to "like", tweet and share content on their facebook and twitter profiles. I have noticed to the left of this box, the facebook and twitter icons do exactly what I am trying to accomplish but I am not familiar with how to do this. Looking at the source code, there are JS references to:
<script type="text/javascript">
StackExchange.ready(function() {
var shareUrl = "http%3a%2f%2fstackoverflow.com%2fq%2f7505636%2f337690";
var shareMsg = "Advice+integrating+Facebook+%27share%27+and+link%2fimage+capabilities+with+our+site";
StackExchange.share.facebook($("#fb-share-7505636"), shareUrl, shareMsg);
StackExchange.share.twitter($("#twitter-share-7505636"), shareUrl, shareMsg);
});
</script>
Our site works this way: While anybody can visit the primary site at any time, individuals can sign up as representatives with their own unique URL that acts as a referrer to give 'credit' on rewards. I have reviewed the facebook developer site and to be honest I am slightly overwhelmed. I want to give our members the ability to click a Facebook icon from within their dashboard, prompting them to post on their wall with a set image, set title, and description. I have read in the documentation this is done by setting meta tags in the head but it does not seem to matter for my site (or I am clearly doing it wrong).
What if the URL facebook is looking for (share URL) is behind a password protected page or an area of the site which would not allow content based on a missing PHP SESSION variable?
Edit
I have also seen a lot on the net which says I have to integrate the Facebook JS SDK but then goes on to talk about authentication/permission to write on walls, etc. Yes the link to the left does not ask for permission to do anything other than to 1) log into the FB account, 2) post on the user's wall.
This site is a perfect example
The link above is great but it assumes I need to authorize a 'share' which does not occur on this site.
When you click on the share button, you call a script on facebook.com that will then in turn access the page pointed to in the querystring (?u=xxxxxx).
Facebook will parse that page and grab the first few images it finds, a description and title from the page. That is what it shows to you and allows you to add some additional text (as well as edit the title/description/and choose different images).
If that page contains the specific meta tags that facebook asks you to add to the page, then they'll use those to populate the title/description/image. This allows the webpage author to control how their page shows up in a facebook feed (although the user could still edit it before posting). These meta tags would need to be in that particular page to be used by facebook.
If facebook cannot access the page because it's password protected, etc. - then it cannot parse the meta tags and will then just show the user the URL as the title with no description and thumbnail.