I made an error when bulk 301 redirecting from an old domain to new domain with same url structure.
Google bot followed the 301 redirect for each page on the old site to my new site, which gave a 404 error. I tested it browser in worked for a user but somehow did not work for the google bot and I detected it too late.
I fixed the error now and the pages could be (hopefully) accessed by google bot at their new urls.
Question: will google recrawl 301 redirects which led to 404?
They'll crawl it for a little while but eventually the 404 status will tell them the page is gone and they will stop crawling it and remove it from their index. If you fixed the error before they stopped crawling the original URL then they will follow the redirect and associate the new URL with the old URL.
Related
Recently email responses to FB comments are refused by FB's servers with the following message:
The error that the other server returned was:
554 5.7.1 POL-P6 http://postmaster.facebook.com/response_codes?ip=209.85.223.172#pol-m Message refused
POL-P6 The message contains a url that has been blocked by Facebook.
Now, the only URL in the message is a link to my home page (for my tree farm)
http://sherwoods-forests.com.
Going over this policy page (at http://postmaster.facebook.com/response_codes?ip=209.85.210.175#pol-m ) I can find no place that will explain why this is occuring.
To verify it was this URL, I 're-replied' to a message, but edited the link out of my signature. Sure enough that one went through without a problem.
In addition, I went and 'shared' this link on my status page to see if it was generally blocked. No, it was not. Had no problems.
I have searched through the web page for possible spam words -- and found nothing.
Q1. Is there a way to find out why a URL is blocked by facebook?
Q2. Is there a way to clear a blocked URL.
I too faced the same issue. So I used a url shortner like http://goo.gl/ instead of posting the exact link of the blocked url.
Facebook accepted the shortened url of the page. After which facebook started to accept all emails containing the page url normally like before. There was no further use of url shortener.
My homepage redirects to the URL listed below to open an oauth dialogue with Facebook to validate user credentials.
<meta http-equiv="refresh" content="0;URL=http://www.facebook.com/dialog/oauth/?client_id=myclientid&redirect_uri=http://www.mywebsite.com/home/index.php" />
The Site URL (Website with Facebook login) in my Facebook App profile is
http://www.mywebsite.com
Everything works great for HTTP but when I recently implemented an SSL certificate I struggled to convert everything to HTTPS (changing HTTP to HTTPS in my redirect URLs and the Site URL in my Facebook app profile. I get the following Facebook error:
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: Invalid redirect_uri: Given URL is not allowed by the Application configuration.
I've fought with this a few hours at a time but was never successful and always just changed the redirect URL and the Site URL in my app profile back to HTTP. Last night it worked! I published the code and tested it successfully on two separate computers in both IE and Chrome. This morning I woke up to the same error code I was getting before.
Does anyone have any ideas why my Facebook oauth dialogue seems to be fickle when it comes to HTTPS?
Make sure that you have a valid base domain specified in your app settings.
This is a working example of a website with Facebook connect. At the top I have added a code to:
Detect if the user is authenticated yet and if not it will...
Detect if SSL is being used
If SSL is in use it will check to makes sure that whatever the
current page is (gets dynamically) contains the URL you enter in the
first variable ('$sslurl' in the top settings); otherwise, it will
default back to $sslurl and add whatever page you were visiting to
the end of it.
It will then use the correct url to authorize the user using the
generated SSL url as the redirect_uri
The rest of the script is just a generic website with facebook
connect setup
It's too long to place inside code tags so I put them in a text file here:
http://o-e.us/ssl-facebook-connect.txt
Hopefully it helps, Good luck!
Google webmasters tools has a bunch crawl errors (404) for urls to non-existent pages on my site. I never link to these urls. How can I solve this problem ... it is affecting my adwords campaign? I tried to do a 302 redirect, but that did not work.
Today, I tried to post a link from my website on my wall, but no OG meta information was fetched. Therefore, I went on to Facebook URL Linter to check things for myself and see if OG meta tags are fetched properly.
To my surprise, every link on my website including the domain itself, generated Response code: 302.
My OG tags are well set and they were working fine a few days ago. Following is what the debugger shows for my domain : http://www.price-tag.org
Response Code: 302
Fetched URL: http://price-tag.org/
Canonical URL: http://price-tag.org/
Final URL: http://price-tag.org/WpjZW/
For every page from my website, facebook linter is adding an arbitrary string like above WpjZW.
Please let me know if this is a facebook error or something has gone wrong at my end.
It seems the linter is being sent on a circular redirect loop. It is seeing a 302 redirect.
For http://www.price-tag.org I don't see anything but a 200 response code when I navigate to your website using Firefox.
However, if I remove the www from the url and go to http://price-tag.org, I do see the strange behaviour of the 302s and then a random url like http://price-tag.org/UKXRN/
I would suggest you contact your server admin or web master to see what they have in place that is doing this 302 redirect and strange url characters.
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/