Facebook adds a trailing slash to urls?

[Muhammad_Jabali]

Hey Guys,

we are facing a problem in our www.batuta.com with Facebook shares.

Seems like because we choose to set our preferred canonical version urls to end with a trailing slash ( / ), like this one e.g.:

www.batuta.com/الوجهات/إسبانيا/

Facebook adds automatically another ( / ) when trying to read the url on first share before its ever indexed in FB. Which makes Facebook think its a bad request! cause then the URL has two // at the end of it.

hope this was clear.

anyway, so first question: did anybody face this issue before? any solutions?

Second, and might be more important:

I might be forced to face the option of changing the canonical tags to be a url without a ( / )

if I will have to do this I will enforce a redirect on every url request with an ending trailing slash ( / ) to be redirected to the new canonical version without.

will this be enough? how big am I supposed to suffer here? am I facing a long time with double indexed urls?

wonder if anybody faced this problem before!

Best Regards

[EricaMcGillivray]

Are you seeing this when someone "likes" your page?

When I copied your link and posted it to my Facebook, it worked just fine, and I'm not seeing it.

In the Open Graph meta tags, used for better social sharing, you specific the URL there. Which means, you wouldn't need to change your canonicals, just your open graph tags.

Also, Facebook can be weird due to caching, and they have an entire debugging tool to help you make your page show up correctly.