I have a domain name and it had a wordpress cms in it, I re-created the website using another cms (not wordpress). When I try to share the articles or any page, it gives me in the FB sharer badge "page not found", but when clicking on the link .. it opens the page normally as expected.
I tried using Facebook Debug and it still gives me "Bad Response"
When clicking on the button "See exactly what our scraper sees for your URL" in the debugger, it shows me the source of the wordpress page, although I changed the name servers and it is pointing to the correct host.
Any ideas?
and it is pointing to the correct host
For both IPv4 and IPv6?
Facebook gives preference to the latter, so make sure that the records for both point at the new server now, resp. check that you got no old records for IPv6 still pointing to the old server somewhere, should the new one not support IPv6.
Related
I have a page http://46.39.131.94:53157/FacebookShare/Go/f80b86a2-0b18-44c9-9de0-42ca465112f2 (don't mind the IP address, this is my home computer running IIS Express, when the app is finished I will publish it with proper DNS name). When I try to share this page on Facebook, the share post is created normally, but og:site_name tag doesn't seem to be displayed anywhere. Instead, my IP address is displayed.
I have tried the Share debugger, it show zero errors or warnings. In the "Based on the raw tags, we constructed the following Open Graph properties" section the og:site_name tag is missing, but it is displayed when I click the "Show All Raw Tags".
I have tried to "Scrape again" and refresh. Changed the URL several times. I am out of ideas.
I would expect the "SHARE TEST" (the content of og:site_name) to appear in grey caps just below the description instead of the IP address.
Am I missing something?
I have written to Facebook support team and this is what they said:
That's correct, we don't currently show the "site_name" Open Graph parameter in the Share Dialog. We don't necessarily use all of the Open Graph tags on Facebook and in this instance we show the hostname or IP address from the shared URL.
All the best,
David
So, the og:site_name is not currently used by Facebook Share dialog.
That answers my question.
I'm facing a big problem with the Facebook debugger. I've read a tons of topics about the Facebook cache etc ... but nothing like mine.
I recently changed my server, so the new one runs perfectly, while the old one is closed.
The problem is Facebook don't see the change and keeps scanning the old server. I know it because the title is a 404 and when I click on "See exactly what our scraper sees for your URL" it returns "Document returned no data".
The problem is for every single pages but if you want to test one, for example :
http://sayitwithkittens.io/cat/40
What Facebook debugger see : https://developers.facebook.com/tools/debug/og/echo?q=http%3A%2F%2Fsayitwithkittens.io%2Fcat%2F40
I would like to upload a screen of the parsing but I don't have the necessary reputation yet..
Thank you for helping me :)
Resolved by Igy :
Did you update both the IPV4 and IPV6 records for your domain? When I check from my laptop i get an IPV6 address, which returns a 404 for that URL
I'm sharing content from a website and every time I paste the link into Facebook it says 'page not found'.
Sometimes it works when I manually add the 'www.' in front of the URL in the address bar.
EXAMPLE
Shows page not found:
http://roundreviews.co.uk/reviews/speakers/native-union-monocle-speaker/
Works when you manually place www. in front:
www.roundreviews.co.uk/reviews/speakers/native-union-monocle-speaker/
I honestly have no I idea why it's doing this, any thoughts on how it can be fixed on the web side?
Also...
I have tried with the link below with both the www. and without yet it doesn't work with either of them, this is all very strange. This is the only link I have tried and it doesn't work with both:
www.roundreviews.co.uk/microphones/spark-digital-microphone/
Any help is much appreciated, thanks.
For me what it worked was to access the Facebook Debugger, as Goose said.
I saw that the scrape was about 12 hours ago, looks like it fetches the first time and saves it as caché or whatsoever...
What it worked for me is to debug the url, then click "fetch new scrape information" after the previous information has been shown.
Hope it works!
For those running across this today, you might find that you also need to verify your domain and link it to your page.
To do this you need to
Set up a Facebook Business Account
Add your page to the business account
Verify your domain (using DNS TXT or adding a page facebook gives you)
Under domains, connect your page as an asset of that domain
Has anyone played with the new redirect feature in Ektron 8.6?
We tested it (in 8.6.0) before upgrading and were happy with it. But when it came time to do the upgrade, Ektron had released 8.6.1, so we upgraded directly to that.
Now we are having trouble with the redirect feature. (Yes, we should have tested everything again in 8.6.1 before upgrading)
Now if we try to add a redirect rule for an existing page in the CMS, it does not work.
But if we create a redirect rule for a page the does not exist, then try to hit that address, the redirect works fine.
We need the redirects to work for existing pages in the CMS.
To clarify what "working" and "not working" means...
If I have an existing page in the CMS with manual alias of "/erc/lucien.apsx", I can create an entry in the redirect table like this...
Adding this entry generates no errors, but when I visit the page, all I see is the regular old page I created. NOT the Google site it should be redirecting to. I do not get any 404 errors.
But if I create a redirect entry for a page that does not already exist, like this...
It works perfectly. If I try to visit the /erc/fake.apsx address, I end up on the Google site, as expected.
(FYI, we create a "fake" page in the CMS for external content so we can attach metadata to it and make it searchable in taxonomies, but then provide a link to the "real" page. I want to use redirects here so users don't have to do this extra click)
I suspect it might be cache related -- the original URL gets cached as an alias, then subsequent requests to that URL are redirected to the quicklink without the need for a db look up. When you add the redirect, it’s probably not clearing the old item from the cache. I'd try an IIS reset after you add the URL redirect and see if that clears up the issue.
An "outside the box" (of Ektron) answer to this is to place the redirect at the web server rather than in the Aliases section of the Ektron CMS.
The server I work on uses IIS and I have this set up for several pages.
In trying to create an "object" page for my first facebook app, I've run into some difficulty. I followed Facebook's Open Graph Tutorial nearly exactly.
After creating an "object" html page with the appropriate <meta property="og:... tags I tried running the URL through the Debugger Tool as suggested in the tutorial but I'm given the following error:
"Facebook URLs aren't scrapable by this Debugger. Try your own."
This page is in the same directory on my company's linux box as the canvas page, and is certainly not a "Facebook URL". If it matters, I'm using an IP instead of a domain name: xx.x.x.xxx/app/obj.html
...
I continued the tutorial anyway, but ultimately it does not seem to want to post a new action/object (is this even right?). I did however manage to get something to work, as in the app timeline view I apparently actioned one of those objects a couple hours ago. I assume this happened when I was pasting curl POST commands into the terminal.
I'm pretty new to the whole open graph, and facebook APIs, etc., so I'm probably operating under false assumptions of some sort, and I've been all over trying different things, but this error seems pretty bizarre to me and I can't seem to resolve it.
UPDATE
I just took the object page and put it on my own personal shared hosting acct. The debugger worked (inexplicably) fine on it, but I couldn't go too far since it's a different domain than the one authorized by my app.
Make sure og:url inside your html page does not point to facebook.
Also, make sure to look at the open graph protocol page (to see you formatted the og tags correctly.
Also, make sure the page is accessible to everyone, not just yourself.
Without knowing the URL it's hard to be sure, but it's most likely that your URL is either including a og:url tag pointing to a facebook.com address, or a HTTP 301/302 redirect to Facebook instead