When I “fetch new scrape information” I still get the error I mention above… so I googled the “Curl Error” and found the following:
https://stackoverflow.com/questions/22461368/facebook-developer-tool-throw-curl-error-operation-timeouted-operation-timed
Essentially, this means the error isn’t an “Open Graph” error, but the call to the server times out (which IS what it says, but I wasn’t SEEING that, as I thought it was an Open Graph error! Grrrrrrrr.)
Here’s the complete quote for the solution:
“Sorry, this problem wasn’t related with Open Graph Tags. I was very confused because there were not enough information from Facebook about that. I thought that there was a problem in my code and Facebook debugger couldn’t read the Open Graph Tags, but the problem was really that my server spent a lot of time to response the requests, and then Facebook Debugger threw a Timeout.
I was so confused because the response of homepage and static pages were correct, and the problem happened only with posts pages.
This problem was solved using a plugin for caching post pages. In this case I am using “WP Super Cache” plugin. Now the response of post pages is about 2 second, and Facebook Debugger can analyse Open Graph Tags correctly.”