I have our Odoo website (http://104.131.73.119) set up in both English and Spanish (written first in English then translated to Spanish), and I have set up the metadata for each page in the corresponding language. I have the Settings>Website Settings>Language>Default Language option now set to Spanish, but if I use the Facebook Object Debugger tool (https://developers.facebook.com/tools/debug/og/object/), the meta info from the English pages is what is getting extracted. The same applies if I use the "Free Online Sitemap Generator" at https://www.xml-sitemaps.com/crawl.html it only pulls back results from the the English section of the site: https://www.xml-sitemaps.com/download/104.7801617/sitemap.html?view=1
When testing, the default page I'm shown when I go to the root of the site is displayed Spanish. To confuse matters I believe Odoo does some location/browser language detection to determine what should be shown and this is then stored in a cookie for return visits. It took me a while to figure this out as I'm in Guatemala, but I'm using Chrome in English (only on clearing my cookies and changing Chrome to Spanish did I get the Spanish homepage off the bat). Alsothe Odoo install is hosted on a DigitalOcean droplet on a server in New York at the moment, I'm not sure if this complicates matters further or not!
The majority of my target audience are Spanish speaking, so I would prefer that google etc crawl my site and read the metadata in Spanish if I only have the choice of one language. However I also have clients in Belize which is English speaking, so it would be good if google searches made in English also yielded results from the metadata in the pages for the English language.
I'm at a bit of a loss as to how I can correct this and I need the site to go live on the droplet ASAP.
Update: Just set up Google webmaster tools and can confirm that google sees the site in English when it attempts to crawl it as well.
tested this with the live setup on odoo.com and it does the same thing. Im guessing by the lack of help on this this, it is a bug (or overlooked point) in the software and not a configuration issue, however with 56 views I think it must be affecting more than just me!