I had about 30000 likes for my page and decided to move it to HTTPS, made 301 redirection from HTTP to HTTPS and found out that all Likes are lost. Switched back to HTTP but still can't get back Likes.
Facebook API show the same Likes count for both URL
Old url https://graph.facebook.com/http://www.freepdfconvert.com
and
New https url https://graph.facebook.com/https://www.freepdfconvert.com
Maybe someone knows how to get Likes back?
The only thing you can do is use the http URL in the og:url tag and redirect to https with .htaccess.
More information can be found in this thread (and others): Switching from HTTP to HTTPS, lost all Facebook "Likes"
Related
Can you please help me debug this! Whenever we are sharing content links from our website in facebook; its not working. Redirection to content works if I'm using desktop browser or directly opening the link in mobile browser. But from facebook in app browser I can see either its loading 404 page or the video doesn't play. What could be the reason behind this? Please check below link from here
Either redirect from http to https in general or change the og:image to https instead of http. If you enter the URL into the browser, you get redirected: http://www.bioscopelive.com/bundles/bongoweb/images/oglogo.jpg
You can also add og:image:secure_url as metatag with the https URL of the image.
Make sure that everything is public and not locked by gelocation or login. Facebook servers need to be able to reach the URLs.
On April 12th, Facebook upgraded the FB App we use to share new articles to our page to API version 2.6. Since then, stories get posted, but the image is usually not added to the story.
When I check with the opengraph debugger, I see strange errors like:
Circular Redirect
We could not resolve the canonical URL because the redirect path contained a cycle.
With redirect paths of:
Redirect Path
Input URL arrow-right https://www.bleepingcomputer.com/news/government/34-tech-firms-sign-accord-not-to-assist-government-hacking-operations/
301 HTTP Redirect arrow-right https://www.bleepingcomputer.com/news/government/34-tech-firms-sign-accord-not-to-assist-government-hacking-operations/
Even stranger, sometimes the redirect paths show urls like below, which are not from my site:
Input URL arrow-right https://www.bleepingcomputer.com/news/security/crooks-hijack-router-dns-settings-to-redirect-users-to-android-malware/
301 HTTP Redirect arrow-right https://www.bleepingcomputer.com/news/security/crooks-hijack-router-dns-settings-to-redirect-users-to-android-malware/?utm_content=70198165&utm_medium=social&utm_source=facebook
og:url Meta Tag arrow-right https://www.bleepingcomputer.com/news/security/crooks-hijack-router-dns-settings-to-redirect-users-to-android-malware/
Once I click on the scrape button again, it gets rid of the error, but the images still do not show in the post on my FB page.
It is almost as if the scraper is targeting URLs that are not mine, even though I am sending them correctly and I have the same urls in my og:url and canonical tags.
Any ideas?
Since recently switching a website from http to https the News section on the website "which has a Facebook "Share" button" has lost all the counts for that URL.
I have tried the following:
Add og:url tag on the HEAD section of the website <meta property="og:url" content="http://www.example.com" />
Modifying the Facebook code to count http likes
Using the Facebook Developers sharing debugger - The client put the old URL it used to be before the switch and scraped the http version but there was no change to the share counter
Use 301 Redirect on web page for HTTP to HTTPS - anybody trying to go to a http URL is redirected to the new URL on https
Any help would be greatly appreciated.
Scenario of the problem:
We enforced HTTPS on a website. Any URL with HTTP now redirects (301 permanent redirect) to an appropriate HTTPS URL.
To avoid Facebook like/share buttons (that are placed on many pages of the website) loosing previous numbers of likes/shares, we made the buttons to "link" to the old HTTP URLs via the "data-href" property.
Additionally we placed the "og:url" meta tag on some pages, pointing to the old HTTP URLs.
I then scraped that pages at the Facebook debugger tool https://developers.facebook.com/tools/debug to make sure the Facebook gets the fresh data. According to the scraped data, canonical URLs were indeed pointing to the old HTTP URLs just as it should be according to our actions listed above. This was also reflected in the like/share buttons on our pages keeping the old numbers.
A few days later I discovered that some pages lose the old numbers of likes/shares. Checking the pages in the Facebook debugger shows that Facebook now takes HTTPS URLs as canonical. We did not make any changes on our pages, and the "og:url" tag is still pointing to the HTTP URLs. But the Facebook wrongly takes HTTPS URLs as canonical URLs. Now if I scrape the information again in the debugger, it agains becomes normal, showing HTTP as canonical and restoring the old number of likes/shares. But obviously it's not a solution to the problem, because we cannot constantly monitor all our pages and scrape them again and again.
Any ideas of what may causing the problem?
Facebook follows HTTP redirects as well. You need to make your old HTTP URLs available to the scraper, without redirecting it to the HTTPS version. (The scraper can be recognized by its User-Agent, see social plugins FAQ.)
The old HTTP URLs need to be available to the scraper, and not redirected to HTTPS, as the FAQ also mentions:
“This also requires that the old URL still renders a document with Open Graph tags and returns a HTTP 200 response, at least when loaded by Facebook's crawler. If you want other clients to redirect when they visit the URL, you must send your 301 HTTP response to all non-Facebook crawler clients. The old URL should contain its own og:url tag that points to itself.”
I created a site, but it went throught a increase in structure, and a new folder level was added in url. The site sends a 301 redirect to point users to new url.
The problem is: The facebook button with the Share count is zero. It was counting 408.
I know I can point the counter to the URL to old page, but How to do it correctly using the 301 redirect? I don't want the old url anymore, just to update the count to the new url.
old url:
http://biblia.apelosurgentes.com.br/biblia/
( http 301 )
new url:
http://biblia.apelosurgentes.com.br/pt-br/biblia/
I already Fetched new scrape information on the old url using the facebook debug tool https://developers.facebook.com/tools/debug/
But the count stills not getting transferred to new URL.
I see this as a facebook bug, because it is not following the 301 redirect rule. https://developers.facebook.com/bugs/589414401234160/