Hi @Yang_9, I took a look and I am seeing something different for the OG image:
From the FB Debugger:
From an actual share in FB:
Is the issue still happening on your end?
As the Designer of a site project and making Design changes, it is often helpful to first try the following steps:
– Try to reproduce the behavior while using Webflow in Incognito mode/Private window mode with browser extensions turned off.
– It may be helpful to disable the browser cache so that updated files are always downloaded instead of pulling old content from browser cache.
Only Google Chrome or Apple Safari browser works for the designer, so one thing is to try another browser to see if that helps to isolate the issue root cause.
This kind of behavior can also happen if one one of your custom domains added in the hosting tab is having issues detected.
The issues detected for the custom domains is shown on the hosting tab of project settings.
The next step would be to check and update the DNS records on the domain(s) to point the DNS records at the correct servers.
The root domain (without www, like example.com) should have these two A-records:
Type: A
Name: @
Value: 75.2.70.75
Type: A
Name: @
Value: 99.83.190.102
The WWW subdomain should have a CNAME record and should use the following values:
Type: CNAME
Name: WWW
Value: proxy-ssl.webflow.com
If you happen to be using Cloudflare, the Status column on your DNS records that point to Webflow must be changed from “Proxied” to “DNS Only”.
After DNS changes are made, got to the hosting tab of project settings, set the
WWW domain as the default domain and then Publish your project.
I hope this helps to give you some things to check.
