Thanks Eugene,
Analytics: is that done from the same google Analytics acocunt, or does a new one need to be set up for the subdomain? If so, how, where would the tracking code go?
Console: Any word from your team?
Thanks!
Hey @Yaco
Analytics
To split the data between your different subdomains, you simply need to use “Hostname” as your “Secondary dimension”:
Result:
Google Search Console
It will work if you use the “domain property” to setup your Google Search Console. With this setup, all subdomains (including the ones you created for Weglot) are detected. More info here:
If you use the old “Url-prefix property”, your translated URLs will still be indexed on Google no problem, you just won’t be able to see/manage them on your Google Search Console.
Thanks Eugene, so it’s best to use Domain Property, correct? Or is there a trade-off / disadvantage versus using “Url-prefix property”?
Will connecting them this way pass on SEO value from te domain to the subdomain and viceversa, similar to subdirectories?
Thanks!
Hi @Yaco
I’m not a Google Search Console expert but it looks like Domain Property is the best way to integrate the Google Search Console.
The way you integrate Google Search Console shouldn’t have an impact on the way your pages ranked unless I’m mistaken. It can help you check if your pages are well indexed, for which keywords and see if you have some Google SEO issues. But you can be #1 on Google without using the GSC 
Sorry, I’m not an expert on this topic!
Hi! @eugene_weglot
What about Webflow Search Index?
Does webflow search feature works correctly on weglot subdomains?
Hi @Oleg_Kuzmenkov,
Yes, it should be possible to use the Webflow search feature with Weglot thanks to our #translate_search option detailed here:
If you need help, please contact our support team (support@weglot.com) with:
- Your website info
- The location of the search bar and especially the CSS id or class of the form so they can set up the search option
Hi @eugene_weglot!
Is there a solution for the hreflang tags in the main language?
Because the URL in the tag is always the root page and not the translated version of the current page.
If we insert this in Head Code:
It won’t point, for example, https://mysite.com/solutions/how-to-sell to https://es.mysite.com/solutions/how-to-sell when visiting the original site.
Hi @fgilio, unfortunately Weglot can’t know the current URL slug of a page when it’s loaded on the original website on Webflow for the moment. That’s why we put the homepage hreflang tags by default.
Our dev team did a quick tool to generate the correct hreflang tags automatically and add them to your Webflow pages. But you need to have basic coding knowledge to use it: GitHub - weglot/integration-hooks
We hope to be able to offer a better solution soon.
Thanks @eugene_weglot! Alexis from support sent me this info earlier today, it might be useful for us
1 Like
Great! Don’t hesitate if you have any other questions
Hi @eugene_weglot is there a solution for translating URL slugs yet?
Really, really need that. For WordPress it seems to be available.
Thanks!
Hi @Philip_Farbmacher , our URL translation feature is in beta right now and will be available soon (for Advanced plan and up)! Don’t hesitate to contact our support team if you want to try it out → support@weglot.com
Hi Ezra,
Could you share a sample of that setting? which should be the proper script for changing the filtering once you choose a language.
Thanks!
How do we handle image translation in the webflow cms? We are currently using 1 richt text element with all copy and images inside of it and it seems theres no way for the images to be translated with this setup. We have been using static landing pages for weglot translations from EN to French up until now perfectly fine but just started using webflow cms and it seems to require a different process for a blog to serve up translated images. Please help!!!