Thanks for reaching out. We have been looking into other similar issues, so your screenshots are helpful as we try to determine the root cause. Please share the following so we can investigate further:
- Your Site Health information, you can share privately using this form.
- Do this occur with only your Search Console and Analytics modules connected? To test please temporarily deactivate the other connected modules.
- Is there a particular action that results in this dashboard error appearing consistently (ie. Clicking on a particular setting)
when did you say module you mean inside your plugin?
btw is ok now… but still, i suspicious about that…
this the site health
Site Kit by Google
Versión
1.21.0
Versión de PHP
7.4.13
Versión de WordPress
5.5.3
URL de referencia del sitio
https://locksmithunit.es
Modo AMP
No
Estado del sitio
Conectado a través de las credenciales del sitio
Estado del usuario
Identificado
Recuento de usuarios conectados
1
Módulos activos
Verificación del sitio, Search Console, Analytics, PageSpeed Insights, Tag Manager
Ámbitos necesarios
openid: ✅
https://www.googleapis.com/auth/userinfo.profile: ✅
https://www.googleapis.com/auth/userinfo.email: ✅
https://www.googleapis.com/auth/siteverification: ✅
https://www.googleapis.com/auth/webmasters: ✅
https://www.googleapis.com/auth/analytics.readonly: ✅
https://www.googleapis.com/auth/tagmanager.readonly: ✅
Capacidades del usuario
googlesitekit_authenticate: ✅
googlesitekit_setup: ✅
googlesitekit_view_posts_insights: ✅
googlesitekit_view_dashboard: ✅
googlesitekit_view_module_details: ✅
googlesitekit_manage_options: ✅
googlesitekit_publish_posts: ✅
Propiedad de Search Console
https://locksmithunit.es/
ID de cuenta de Analytics
154482188
ID de propiedad de Analytics
UA-154482188-1
ID de vista de Analytics
207976318
Colocado el fragmento de código de Analytics
No
ID de cuenta de Tag Manager
6000235003
ID del contenedor de Tag Manager
GTM-587K9X4
ID del contenedor AMP de Tag Manager
Ninguno
Colocado el fragmento de código de Tag Manager
No
Thanks for the update. When I mentioned “Module” you are correct, I was referring the specific produce module (in this case Search Console) within the plugin.
Looking at your Site Health information your setup seems fine, nothing unusual stands out. When you mention everything is working fine now can you confirm the issue no longer occurs, and if so was this after checking from a browser incognito window?
is unpossible to get inside my console from an incognito mode.
my server not allowed that.
and this not connected the error sometimes show up sometimes not
is even affect ranking…
you see in SEMRUSH imidate drop when you play with the plugin in this site.
i don’t know why.
btw when i install the plugin, start issues with analytics.
( goals drops, is already over 6 mounts. i have one site without google tag manager
and this is gone but is not was before i install google site kit, google site kit slow the site and cause a lot of issues with integration )
when i go to talk analytics support they say everything fine, and go to google’s site kit.
when i coming talk to you guys, you said this google analytics support problem.
i think have some communication problem maybe API, and this connected to the issue we have now.
When i said everything is fine, is like you see.
after a couple of times, he passes and set the setting i need.
but all the time when i do it i see it once or twice…
specific in this site.
why?
this site drop in the ranking from the last issue dramatically.
i have 3 identical sites…
so is very easy to diagnose when you have a problem in one.
locksmithunit.cat
locksmithunit.com
but the problem is on
locksmithunit.es
the analytics issue i told you in the start is in the .com and the es domain.
this because they have a tag manager not install with google’s site kit.
before we install the google site kit. google analytics didn’t show any goal drops or any warning.
-
This reply was modified 3 years, 4 months ago by
123nadav.
@123nadav Thanks for the update. In relation to Site Kit impacting your site ranking Site Kit facilitates connecting a users website to the various Google products. It doesn’t have any content altering features that impact site performance.
If you add other services (by Site Kit or manually as you seem to have done with Tag Manager) your website makes additional https requests to these services. There may also be content or third party services being added to your site using Tag Manager. These are not part of the Site Kit product itself, they are features added by users of Tag Manager.
If you find your site isn’t ranking as it should be have you tried using the Search Central Community? They should be able to analyze your site better than we can here. We can only assist with Site Kit related issues.
You can also use a service such as web.dev to assist with site performance. Just bear in mind you may find it useful to compare your sites performance with all the Google products manually added, compared with connecting the Google products via Site Kit.
Going back to the original issue based on your previous comments can you confirm Analytics is working as expected without the “Failed to execute ‘removeChild’ on ‘Node’” error on your http://locksmithunit.es (and .com) sites? If so I’d be curious to know what tags you have inserted via Tag Manager, you mentioned SEM Rush already, do you have other third party services added?
i have only CLICK CASE BLOCKER FOR GOOGLE ADS inside google tag manager.
problem was before we put the ad clicker.
except that everything is normal in tag manager and belongs to google ads.
google tag manager was install before google sit kit and everything was fine.
but i sure google sit kit have some problem with his integration,
i will investigate that further and update you my freind.
Ok, i think i got it…
is the PHP…
google site kit not compile above PHP 73…
cause issues on all my sites when i update the PHP to 74.
and now i update that to PHP 80 and i got the issue in my analyzer on debug mode:
https://ibb.co/v42PSwJ
is a PHP problem i pretty sure…
C-Panel updates the PHP in all the consoles right now.
PHP 73, PHP 74 AND PHP 80.
SOON PHP 73 WILL REMOVE FROM C-PANEL.
Recommendation? what to do with this PHP error?
@123nadav sorry for the delay in response and thanks for the update.
Are you also seeing any abnormal behavior or errors in Site Kit’s admin pages when you update the PHP above 7.3?
If so, could you send any screenshots of that additionally and your Site Health information through this form? Thanks so much!
Versión
1.22.0
Versión de PHP
8.0.0
Versión de WordPress
5.6
URL de referencia del sitio
https://locksmithunit.es
Modo AMP
No
Estado del sitio
Conectado a través de las credenciales del sitio
Estado del usuario
Identificado
Recuento de usuarios conectados
1
Módulos activos
Verificación del sitio, Search Console, Analytics, PageSpeed Insights, Tag Manager
Ámbitos necesarios
openid: ✅
https://www.googleapis.com/auth/userinfo.profile: ✅
https://www.googleapis.com/auth/userinfo.email: ✅
https://www.googleapis.com/auth/siteverification: ✅
https://www.googleapis.com/auth/webmasters: ✅
https://www.googleapis.com/auth/analytics.readonly: ✅
https://www.googleapis.com/auth/tagmanager.readonly: ✅
Capacidades del usuario
googlesitekit_authenticate: ✅
googlesitekit_setup: ✅
googlesitekit_view_posts_insights: ✅
googlesitekit_view_dashboard: ✅
googlesitekit_view_module_details: ✅
googlesitekit_manage_options: ✅
googlesitekit_publish_posts: ✅
Propiedad de Search Console
https://locksmithunit.es/
ID de cuenta de Analytics
154482188
ID de propiedad de Analytics
UA-154482188-1
ID de vista de Analytics
207976318
Colocado el fragmento de código de Analytics
No
ID de cuenta de Tag Manager
6000235003
ID del contenedor de Tag Manager
GTM-587K9X4
ID del contenedor AMP de Tag Manager
Ninguno
Colocado el fragmento de código de Tag Manager
No
Just to inform you that we’ve identified the most likely cause of the issue you’ve been encountering and we’ll be making an update to the plugin as per the below GitHub issue:
https://github.com/google/site-kit-wp/issues/2280
We’ll keep you updated once this is released.
@123nadav This error has been addressed in our most recent release, 1.31.0, which is described here. Please try again and if you’re still experiencing any issues, let us know here and we can help. Thank you!
