OG properties not seen by Facebook

Fitzpatrick,
In either case, the 'final' URL is something along the lines of www.rasmussenlawfirm.com/public-safety-vs-housing-crash, which we'd recommend you post. Facebook will try to resolve any redirects before posting a URL to a wall, so it's possible the redirects are causing the problem. Additionally, on that page, the og:url tag points to the 'longer' URL, which is correct, but will also re-enforce Facebook's 'search' for the final destination.

Try posting the longer URL and see what happens.

We're still looking into possible causes from Fabram's issues above, but it's possible they issues are related, we just don't know yet.

Alex

Fitzpatrick,
I'm not saying you can't use that URL at all. Just that when you share it to Facebook, you should use the long URL that's going to get expanded out when someone visits /police anyways. Facebook doesn't like redirects, but that doesn't mean you can't use them in your marketing material or other places where someone would read and type-in. However, for links, it's best to use the final URL.

In general, when you post something, to Facebook or other sites, it's best to use the 'final' link. Even Google will give a slight search engine penalty to links that do a 301 redirect, so it can hurt you (cumulatively, overall) to only post the 'pretty' URL to a link that's going to redirected somewhere else.

Hope that makes sense,
Alex