Switched to https, lost likes

Could you make sure the HTTP version of your posts redirects to HTTPS? Once you have a redirect in place, Facebook should follow it to get to the right post.

You can check what Facebook sees for a specific post thanks to the debugger:
https://developers.facebook.com/tools/debug/og/object/

It will also display sharing counts if there are any.

All HTTP direct to HTTPS and facebook sees this. Its OK though, don’t mind losing the likes. Just thought I’d see if you had any quick solutions.

I’m afraid I don’t have any other solutions. Facebook is usually able to follow redirections and grab likes from the original post. It might be worth bringing this up to Facebook as well.

The bigger problem is how I have to fetch new scrape every time I post so that facebook pics up my images

That seems like an issue indeed. Does Facebook’s Debugger provide you with any useful information as to why this may be happening?

If the debugger doesn’t help, you might indeed have to open a bug report:
https://developers.facebook.com/bugs/

I don’t remember setting these anywhere, but perhaps Yoast just does it and that’s why you suggested it?

Yoast does it indeed, you can set these up under SEO > Social > Facebook.

Now facebook says I have to set og:width and og:height

I’m not sure Yoast does that. Jetpack’s Open Graph Meta tags include that information though.

As per the issue with your likes, this is expected, and the way to fix it is to have the og:url point to the OLD url you were using, which has all your likes.

For example, if you were using HTTP, and just recently moved to HTTPS, you have to add:

<meta property=”og:url”
content=”http://www.myoldwebsite.com/&#8221; />

That makes sense, I understand now. The redirects I mentioned earlier won’t work, because it’s a redirect from the old site to the new one, and there are no likes on the new site yet.

Changing your site’s og:url values would work in bringing your Likes back, but it also means that all new likes will be attached to the old URL, and not the new one. You’d be stuck with attaching all likes to the old site URL forever if you want to keep the Likes.

I’m not sure I’d recommend it.

If you’d like to make that changes anyway, you’ll need to develop your own Open Graph Meta Tags, or edit Yoast or Jetpack’s existing tags, as neither of the plugins offer options to specify a different site URL in their settings.

But if I’m understanding correctly, I need both of these in order to not have to manually fetch new scrape every post. Feel like I must be missing something…

It’s actually only a warning, Facebook doesn’t require fb:admins and fb:app_id yet. It only recommends it.

If you’d like to use Jetpack’s Open Graph Meta Tags, but also have these 2 tags as well, you can add the following code to your theme’s functions.php file, or in a functionality plugin:

function jeherve_custom_app_admin_og( $tags ) {
	// Admin tag.
	// You can find your own ID here: http://findmyfbid.com/
	$tags['fb:admins'] = 'YOUR_ADMIN_ID';

	// App ID tag.
	// That's only necessary if you have a developer account and already created an app.
	// Find your APP ID here: https://developers.facebook.com/apps/
	$tags['fb:app_id'] = 'YOUR_APP_ID';

	return $tags;
}
add_filter( 'jetpack_open_graph_tags', 'jeherve_custom_app_admin_og' );

That will add these 2 custom tags at the end of your existing Jetpack Open Graph Meta Tags.

The tags are displayed properly, it seems:
http://i.wpne.ws/e0BB

Facebook doesn’t complain at the moment:
https://developers.facebook.com/tools/debug/og/object?q=https%3A%2F%2Ftall.life%2Fraised-kitchen-sink-alternative-for-tall-people-the-stool%2F

So it looks like you may be all set!