lichtsturz
Forum Replies Created
-
We have opened the ticket also here: https://posimyth.ticksy.com/ticket/2837977
We have tested further and can confirm that videos (all IDs, even the standard apple video which gets defaulted when adding the video widget) are neither recognized by Google nor by Yoast.
Videos embedded with standard video widgets from Elementor or Smartslider will get recognized by Google and Yoast.
So this looks like a major bug. Kindly check on your platforms. You can test it easily by putting your test URL into Google Search Console or when you have Yoast Video installed to check whether your video gets recognized.
Hope that helps for further investigation.
Thank you James,
you will not encounter any problems unless you select for WPML in the Dashboard header all languages. This will not work with Google Site Kit.
Currently in search console all pages have been registered additionally manually by me for the root. So this is a workaround for me. When Google Sitekit is able to just connect the root while using WPML the workaround is not needed anymore.
For the time being Google Site Kit can only connect one language of multi-language pages.
That means in the Analytics of Google Site Kit you will only see the analytics of the connected language for example /en.- This reply was modified 4 years, 6 months ago by lichtsturz.
Hi James,
since /en is not the root only /en will reported not /de.
I have also manually connected the page with the root where I will get the correct report for both languages.
Yes, I can remove the site kit but not the language path. The language path is not visible. It is just url.com/wp-admin. The language path is coming from WPML.
See this threads:
https://github.com/google/site-kit-wp/issues/1116
https://github.com/google/site-kit-wp/issues/1520
https://github.com/google/site-kit-wp/pull/1449Google Site Kit was not able to strip that off. According to github it should now work but it does not work with latest version.
Can you please check with dev team?
In current set-up Google Site Kit cannot be used for WordPress users with multi-language set-up and there are plenty.
Thx for your patience and dedication to the topic.
All plugins are up-to-date.
So where the problem could come from that it stills gives not the root URL to Google Search Console but language folders like /en or /de.
What do you mean with Yoast settings? There are many.
I can also share WPML settings in case that helps.Yes, thx, this ticket can be closed.
I’m using the latest version of Yoast.
Is Google Site Kit dependent on Yoast which page will be connected to Google Site Kit?
In Yoast I have manually added the verification code of the root.
After resetting the Google Site Kit it will always pre-define the URL to connect with /en or /de dependent what language I have selected. When selecting all it will select automatically /all which is anyhow not available. This is also described in the github tickets.I just wonder what kind of solution has been or will be embedded in Google Site Kit.
Regarding WPML I also see this thread here:
https://github.com/google/site-kit-wp/issues/1116
https://github.com/google/site-kit-wp/issues/1520
https://github.com/google/site-kit-wp/pull/1449But apparently it is not included in version 1.8.0 right?
We could at least fix the error. There was a permalink error caused by Yoast.
We are now with one problem left.
The website uses WPML and has /de and /en folder.
Google Site Kit always connects to one version like /en to Google Search Console.We would like only connect the route to Search Console or Analytics.
Or do you think all content on /de is also connected and tracked when Google Site Kit only connects website.com/en to Search Console?I think I have already done it,
but I have done it again. You can look into it.
I have also added the health info already via form here: https://docs.google.com/forms/u/0/d/1lhjns2K7c0Ny7ME4gxTcsnYtNUtcMr8BvFpPQi23Y1E/viewform?edit_requested=true