Our CMS uses permalink, for example this one:
www.kingmagazine.se/artiklar/king-kroner/20120713/10-korthallare
When a user is trying to share this URL by pasting it into the "update status" field on their Facebook homepage, Facebook seems to try fetch a different URL to get the open graph info, as illustrated in this image:
http://i.imgur.com/NjYM9.png
The page fetched seems to be an error message from the site. The image is not relevant to the article specified but rather contained in the footer of all pages.
However the CMS also has internal URL:s, such as this one (for the same article):
www.kingmagazine.se/artiklar/?id=152539
When sharing that one on Facebook, the correct data is fetched, as illustrated here:
http://i.imgur.com/wV5q3.png
I have tried digging in our server logs to no avail - it seems like Facebook is requesting the wrong URL and not the complete permalink. I have also tried the Facebook Lint but haven't found any reason.
Has anyone got any ideas?
Sorry for the garbled links but Stackoverflow spam prevention said max 2 links and no images. :(
Just wanted to get back to this question if anyone else has the same problem, as we eventually found the solution.
The reason of the faulty information on Facebook was that the editors in the CMS had a preview function which showed the article as rendered to the visitor. These pages (as they included the site header/footer) also contained Facebook like buttons through the Facebook social plugin.
This meant that Facebook was 'pinged' of the article before it was actually published as the editor was previewing the changes. When Facebook tried to fetch the article, an error message (with an incorrect HTTP status code I might add) was returned which Facebook then cached.
Silly enough. :)
Related
This is in a way a followup of this question : Jetpack Publicize: Sharing only on Twitter for a category
I am currently working on a website in which one of the category only serves as a way to curate news on the net and then, share it on the front page and on Twitter.
The post itself is empty, I use a custom field to receive the URL from the user, grab a few things from the target website, update the permalink and save. Upon saving, SNAP publishes the post on Twitter.
My issue is that it is not using the permalink but the url of the post itself (which is absolutely empty). Having a look into the plugin's code, I saw that it was using post metas (most notably urlToUse, snap_MYURL) but couldn't determine if it was a priority issue or something else.
I also try to adjust my code to set these meta values to the url I want, to no avail.
Is there a way I could set my custom functions or the SNAP plugin so that the permalink is used ?
No answer after a week, neither here nor from SNAP's support. No problem.
The ugly patch I used :
Jetpack Publicize for all the Twitter updates
SNAP for the Facebook ones thanks to their ability of posting based on a specific category
It's bloated and I'd love to understand but, sometime, you have to ship
I have trouble sharing page URLs from the website http://www.waterlinedata.com/ on LinkedIn: the Open Graph title and Description are ignored .However, the Facebook Debug tool returns all the information correctly (so I assumed the og tags are correct)
ex: www.waterlinedata.com/careers/
With the FB Debug, the og:title ( Careers | Waterline Data is hiring ) is correctly returned. However when trying to share the same link on LinkedIn, the og:title is ignored and it seems that the last part of the URL 'careers' is displayed instead.
Here is a screenshot from Facebook Debug
And below is a screenshot of a share on LinkedIn :
AS you can notice the og:title is not displayed (instead is the word "career" which is the name of the WordPress page and the last part of the URL ...)
It is a WordPress website, running the SEO plugin by Yoast.
Could someone help me resolve this problem? Thanks.
LinkedIn provides the two following modes for the sharing API preview...
Level 1
You supply: og:image tags.
Preview shows: title, url, image.
Level 2
You supply: no og:image tags, but an og:description tag.
Preview shows: title, url, description.
Regardless of the applicable level, the og: tags for title and url always display fine.
Since you supply an image, the description will not display. The Official Microsoft LinkedIn Sharing Documentation, which mentions the four tags (title, url, description, image), is silent on this matter.
We can test it, though. Wikipedia has no image tag, but a description tag, and we only see the description when sharing Wikipedia. GitHub, on the other hand, has both image and description tags, and we only see the image when sharing GitHub.
A conversation with LinkedIn support over the course of two weeks yielded no result. (oh the humanity) So, I think we are stuck with just the image for now in the LinkedIn preview. Right now, it seems like nobody can fix this but Microsoft themselves.
Plugin: Facebook Open Graph, Google+ and Twitter Card Tags
Purpose: The plugin is supposed to provide ograph tags around your posted content. The options set should first point to the ograph image specified in the plugin's added image field. If not found, then the featured image. If not found then the default image (blank.gif for test purposes).
Issue: Sporadic results. Sometimes the ograph image specified appears (after several FB Debugger scrapes. Other times the default image appears.
In all test cases, the suggested image size of 1200x630 px in JPG format was specified in the plugins ograph image field.
FB Open Graph Object Debugger provides me with this:
*
The app (my app id) specified in fb:app_id meta tag is not published
yet. App attribution will be disabled when shared stories are
rendered. Please check the status in the app settings.
*
The FB App ID is specified in the plugin config. True, the FB App Id is not submitted to be published.
Would we need to publish the FB App ID? Not sure since we really aren't developing an app. If we must publish, which screens would I supply?
The domain's DNS is set up with an A record, not a CName. Some research suggests only CName will work - but no mention of that on FB documentation.
Test results:
GOOD
Military test for URL: wels(DOT)net/dev-military/heavenly-math/
BAD
Daily Dev test for URL: wels(DOT)net/dev-daily/20160608/
:) Once I get a solution, how do I get the entire site scraped if I have more than 3000 pages?
Note: Plugin author speaks another language and is inactive on his forum.
Ref.
I found the answer! The permalink structure on our site is domain/postname However, what has been entered into the permalink field (to make each post unique) was domain/post-type/date manually. Post-type is also the archive link.
Since Wordpress permalink structure is domain/postname... the postname MUST be unique. As soon as I added a prefix to the date, Facebook was able to grab the ograph.
Example:
BAD - domain/post-type/date
GOOD - domain/post-type/prefix-date
Why? Because we have multiple CPT's and they were all using date as the postname. Facebook didn't know how to resolve even though they were valid URLs.
On Bing & Yahoo our link is showing up on the first page, but I am having issues with it showing up on google search. Here are additional details:
The term is the title of the wordpress blog & it has been officially registered with the USPTO.
The site has been active since Jan 17,2016, so far we have 8 posts on it and we want to continue to post fun/relevant posts on the blog.
Thought a trademark association would be in Google Webmaster Tools, but it isn't there.
I looked at Ad Words and saw that it isn't a commonly searched term at all, so figured our blog would come up on the first page.
Been trying different SEO plugins & methods to improve the search for the term, but nothing seems to be working.
This seems to be a very odd issue. I been looking everywhere to figure this one out, but haven't found anything, and I am not sure who to turn to for help. Please help!
SEO is a tricky one,
but it works like this
Meta Description is number one (paste your url I can have a look at the code)
Meta Title (page Title)
Length the domain has been online
Number of crosslinks
Sitemap submission to google (then fetch url )
Make sure your robot.txt is not denying search engines
Make sure your website has content.
http://swiftmedia.ca/marketing.php
This is SO annoying.
The Issue is a matter of two scenarios behaving differently when I expect (and wish) them to be the same, these relate to the same webpage/article which features both Facebook Comment widget and a Share icon.
It's important to mention that the webpage is a Wordpress article, and we redirect:
from www.example.com/wordpress/articles/news/thearticle
to www.example.com/news/thearticle
The issue explained:
Scenario 1) I visit the article and type a facebook comment, I also click 'Also Post on Facebook'. When I view may facebook wall and see the share with the comment I just made, the link is linking back to the wordpress URL - I do not want this.
Scenario 2) I visit the article and share it through the Share icon. On my wall this time the linkback URL is the short one - this is good.
Important info regarding debugging
My OG URL tag is correct:
<meta property="og:url" content="http://www.example.com/news/thearticle"/>
Facebook debugger is picking up the correct desired URL as above,
also listing the desired Fetched URL and Canonical URL. All seems to
be what I want it to be.
This is true regardless of whether or not I
scrape the URL before or after I try this procedure.
Even if I then go back and do another comment with 'also post on FB' after doing a scrape with FB debugger, still the share links to the wrong/long format/original URL.
However, if I at any point share via the share icon, not the comment-share, the desired URL is present as per the OG URL.
If I do a comment-share, then an icon-share, then another comment-share, the comment share ones still have the wrong URL even though the icon-share had the correct one!
Any ideas? Thanks so much in advance to anyone who can help :)
It seems that the Comments FB plugin doesn't get the page info from OpenGraph, but expect a data-href attribute, or if not provided will use the current url by default.
From the doc:
data-href
Description : The absolute URL that comments posted in the plugin will be permanently associated with. Stories on Facebook about comments posted in the plugin will link to this URL.
Default : Current URL.
So what you need to do is to provide the valid URL as an HTML5 attribute on your plugin wrapper:
<div class="fb-comments" data-href="http://www.example.com/news/thearticle" data-numposts="5"></div>