My Open Graph Social images for a new site are not showing and, according to Facebook Debugger, this is because:
The provided ‘og:image’ properties are not yet available because new images are processed asynchronously. To ensure shares of new URLs include an image, specify the dimensions using og:image:width and og:image:height tags.
As I understand these tags should be ‘nested’ within the image tag, how does one add them in Rapidweaver?
Hi @manofdogz,
Where and what page type are you trying to add these images to? Can you provide a link to the page where these images are so we can take a look?
Hi Dan - I’m adding the images in the Generate Social Tags area. 1200 x 630. Text fields are picked up but not images. I have tried jpg, png, webP. In addition to the issue raised, I have now had 2 other error types in FB Debug tool the main one now being “Invalid Content type”:
I have also had the height and width error as originally shown along with one about an app not being specified - which only happened once and I cant find now.
The tags appear fine - screen grab for ‘what Facebook scraper actually sees’:
I am noticing in the debug tool that both index.html and tidy links are referenced (with index.html being ‘canonical’) and wondered if the redirect has something to do with this?:
link for this page:. I should add I cant get the image to appear anywhere - not just Facebook.
Ok - so the URL being generated for the image is incorrect. No idea why or how but will look into it. Facebook is seeing:
https://gcvh.info/gcvh/resources/weddings-og-image.jpg
it should be:
Solution: dumb error on my part 
When I was building the site I had it on our development server. When I put it live, I added a new publishing destination but forgot to change the web address in general settings!
If Facebook had thrown an error saying the image was ‘not found’ I might have guessed but because it threw other inaccurate errors I got sent down the wrong rabbit hole.
I’ve deleted all and republished: all is good! 2 morals to this tale. 1) Follow a checklist when going live and 2) don’t expect error messages to be accurate!
