opengraphprotocol | Open Graph protocol integration for Drupal

I'm going to make a few assumptions here, since your post doesn't contain enough information to generate a reproducible example.

First, I'm guessing that you are trying to scrape TripAdvisor, since the id and class fields match for that site and since your variable is called ta1.

Secondly, I'm assuming that you are trying to get the text of each review and the number of stars for each, since that is the relevant scrapable information in each of the classes you appear to be looking for.

I'll need to start by getting my own version of the ta1 variable, since that wasn't reproducible from your edited version.

In my case, it seems that the crawler is just having a bug. I have my own canonical answer in this question, hope that helps someone: FB OpenGraph og:image not pulling images (possibly https?)

"Accept-Encoding": "text/html;charset=utf-8" looks wrong. Try "Accept-Encoding": "gzip", or removing it altogether.

I figured out that the best way is to implement a different, light way version of ur page

for example: CNN has refereed to the amp version
view the source of this page: http://edition.cnn.com/2017/01/31/politics/donald-trump-supreme-court-announcement/index.html

and here is the amp version https://amp.cnn.com/cnn/2017/01/31/politics/donald-trump-supreme-court-announcement/index.html

So, for me I'll implement a new page without using thymeleaf

I also encountered the problem and i assured you, i did nothing with code as yoast seo does the work for Facebook sharing. The issue that i had was the featured image title description was not set properly. At first facebook did not had a strict policy on api for sharing, now facebook api want everything perfect.

Before

After i set the title,Caption,Alt text & Description properly to salman then the facebook accepted my blog post for sharing " Please try and let me know if it solves your problem

You should do that by postMessage like the following:

https to http redirecting issue. Solved.

Use response.text instead of response.content – as noted in the Requests documentation quoted below, this will decode the response content to a Unicode string, using the encoding information provided by the HTTP response:

content

Content of the response, in bytes.

text

Content of the response, in unicode.

If Response.encoding is None, encoding will be guessed using chardet.

The encoding of the response content is determined based solely on HTTP headers, following RFC 2616 to the letter. If you can take advantage of non-HTTP knowledge to make a better guess at the encoding, you should set r.encoding appropriately before accessing this property.

Example: