

Hopefully this information helps to save someone else from losing 32 coding hours of their life. This worked, but the solution is a band-aid workaround, and if the https issue is fixed and we go back to using the natural https domain, FB will have cached the images from a different website, complicating matters. We then had to go through FB Linter and run EVERY link to refresh the OG data. We referenced the coordinating image in og:image on each product page. To workaround, we placed a subdomain in a different NON-HTTPS website and dumped all images in it. Thanks to Keegan, we now know that this is a bug in Facebook. However, it would still pull any images that were referenced on the nonsecure main domain. Subdomain was We then put all images into the main subdomain folder and referenced those. We tried a test and added a subdomain to the NONSECURE website (from which images are actually visible through facebook). We tested all links it found for a single page. Using the "see what facebook sees" scraper tool, we were able to see the following: "image": [ In case you want it, here's a link to one of our product pages that we've been working on. But we can't find any precedent anywhere on the web for that.

It's also the only one on https, so we thought maybe that was the problem. This is the only one with og:image problems. We absolutely, positively cannot NOT have images. The issue is that this is an online store. If I said how much time myself and others have spent on this, you'd be shocked. Leaving any og:image or image_src off, FB does not find any images.

#Check my sites social media meta tags code
