useFetch, await, SEO and og
Hello all 
I'm a bit concerned about some result I have using useFetch and useSeoMeta (or useServerSeoMeta), so I just want to confirm some stuff
Case 1 : useFetch without await and use(Server)SeoMeta
In the Google search console, it looks like the description/ogdescription is correct 100% of the time.
However, it's not working properly when sharing it over Discord, LinkedIn or else
Case 2 : useFetch WITH await and use(Server)SeoMeta
Now it works properly everywhere
I don't really understand how it appears replaced for Google while not working on social networks. I guess Google render it twice or something but Social Network don't.
Question
Can I be confident that useFetch without await will be fully seo-optimized and the issue is just with Social Networks ?
Or should I always use useFetch WITH await when I'm aiming for the best possible SEO ?
Thanks ^^
I'm a bit concerned about some result I have using useFetch and useSeoMeta (or useServerSeoMeta), so I just want to confirm some stuff
Case 1 : useFetch without await and use(Server)SeoMeta
In the Google search console, it looks like the description/ogdescription is correct 100% of the time.
However, it's not working properly when sharing it over Discord, LinkedIn or else
Case 2 : useFetch WITH await and use(Server)SeoMeta
Now it works properly everywhere
I don't really understand how it appears replaced for Google while not working on social networks. I guess Google render it twice or something but Social Network don't.
Question
Can I be confident that useFetch without await will be fully seo-optimized and the issue is just with Social Networks ?
Or should I always use useFetch WITH await when I'm aiming for the best possible SEO ?
Thanks ^^
