Thread Starter
Igor
(@dzi022)
I contacted hosting support, and they told me something with this might be a problem, so I am sending you details to check.
I don’t know what the is problem after a couple of months, still having issues with the site.
When I try to setup up a new fresh WordPress installation, on the same domain, still have a problem, but when I try to setup a new installation to a subfolder (domain.com/newsite) Google site kit works normally. So I think something is wrong with the domain problem, but I don’t know what.
Thanks for sharing the additional details @dzi022, the recording was very useful to see what’s happening. As I can see you reset Site Kit, if the records are invalid this site. While I did request a site check previously, I’ll do so again considering you’re experiencing the same loop after resetting Site Kit. I’ll report back to you here when I have an update on this, hopefully at some stage this week. Thank you.
Thanks for your patience on this @dzi022. Your site records were checked on the service and all seems correct. From reviewing your recording the callback URL is not picked up. This could be caused by another plugin or a hosting configuration, but so far it doesn’t look like a site record issue. To troubleshoot this further, please follow the steps below:
- Temporarily deactivate your LoginPress plugins (both the pro and free versions), Transliterator, WP Rocket and Loco Translate.
- Switch to a core WordPress theme
- Reset Site Kit once more
- Attempt Site Kit setup
Let me know how you get on with the above.
Thread Starter
Igor
(@dzi022)
As I already told you.. I was doing everything that, still problem. It’s not a plugin problem, I try also on a fresh new installation of WordPress to set up a Google site kit on that domain, and it’s the same problem. But when I create domain.com/newsite i can connect to Google Site Kit. So the problem is something with the domain. i don’t know what. I can give you access to my hosting or to the WordPress site dashboard so you can check it if you want.. ??
Thanks for the update @dzi022, and sorry to hear that.
It’s not a plugin problem, I try also on a fresh new installation of WordPress to set up a Google site kit on that domain, and it’s the same problem.
If we can determine a bug or issue within the plugin, I’d certainly be happy to created a GitHub issue. At present we don’t have enough information to confirm this. There was a review of your recording and site records on the service also, where a team member confirmed all your site records are incorrect, but stated there may be something causing an invalid callback URL for your site at host level.
But when I create domain.com/newsite i can connect to Google Site Kit.
If there is no problem with connecting Site Kit on a subdirectory site on the same hosting platform, there are a couple of things we can try:
- Backup your .htaccess file and apply a based .htaccess file in your WordPress root directory. I mention this as I can see you have some additional rules applied when reviewing your Site Health information (
htaccess_extra_rules: true).
- Define Site Kit custom SALT keys as per this guide. This will ensure that any possible changes to your standard SALT keys are not impacting setup.
- Attempt Site Kit setup once more in troubleshooting mode.
I can also see you have debugging enabled via a plugin (WP Debugging). If you wish to share an errors specific to setup that may be uncovered here should the issue remain, I can open a GitHub issue to escalate this.
I can give you access to my hosting or to the WordPress site dashboard so you can check it if you want.. ??
Unfortunately we can’t login to users sites as per WordPress.org forum guidelines, but I will gather all details you’ve shared and escalate this should the issue remain. Please ask if you have any questions on this. If I am to escalate this it may be useful to share an updared recording of your current setup experience, after following the steps above. When doing so, please keep your developer tools open showing any browser console errors. You can use a service such as Loom or RecordIt to share a screen recording, while using the same form previously used to share this privately.
Thread Starter
Igor
(@dzi022)
Ok, i will try today and will let you know.
Great! Let me know how you get on after trying this.
Thread Starter
Igor
(@dzi022)
Hi, sorry for the late answer. I think I found the problem. There’s some problem with an account that is connected to Site Kit. Today, I installed a fresh WordPress website and tried connecting to a totally different Google account. It didn’t redirect me to the home page; it just took me to step 1 of the Google site kit setup. So please check my Google account that is linked to that domain to see what’s going on and why I can’t connect. Thank you
Thread Starter
Igor
(@dzi022)
Hi, I was waiting for your response, and in the meantime, I tried to connect with that friend’s email. Same problem. is it possible to access options to see where this domain is connected and disconnect that domain from any service?
Hi @dzi022, thanks for the update. Support is provided during weekdays only, hence I therefore missed your prior reply.
is it possible to access options to see where this domain is connected and disconnect that domain from any service?
Unfortunately it’s not possible for me to check the domain that is registered on the Site Kit service myself, along with the callbacks URLs. I am happy to request another check on your behalf. Note that as this will be the third site URL check, with the previous one not displaying any issue, please share a recording of your set up experience first, along with an updated version of your Site Health information (where you can include a link to your set up experience recording).
You can use a service such as Loom or RecordIt to share a screen recording, and what we’re looking for is the experience you face when attempting to set up Site Kit from a Chrome browser incognito window.
Thread Starter
Igor
(@dzi022)
After encountering several issues, I managed to connect Site Kit to my domain. Would you believe how? I removed the old website with the ‘www.’ prefix and installed a new one on ‘domain.com.’ Surprisingly, the plugin recognized this as a new domain and connected successfully. While this resolved my problem, it comes at the cost of losing my SEO ranking. However, there’s not much I can do about it now.
There seems to be an issue preventing the plugin from connecting when ‘www.’ is included, despite it being the same domain. It’s crucial to address this discrepancy to ensure seamless connectivity. Please investigate why it’s rejecting connections with ‘www.’ but accepting them without. Both versions should ideally link to the same domain. Your assistance in fixing this matter is greatly appreciated.
-
This reply was modified 1 year ago by
Igor.
Great to hear you were able to complete setup @dzi022. Site Kit can be set up with or without a www prefix, and in your case I can’t be sure what occurred. I do suspect there was something with your configuration or hosting impacting your connecting with the plugin, in particular when you mentioned “I try also on a fresh new installation of WordPress to set up a Google site kit on that domain, and it’s the same problem.” If you can reproduce this behaviour and share a recording of this I would certainly be happy to check this with the team further.
Note also that you’ll be happy to hear that whether you use a www or a non www prefix for your site, I don’t believe this impacts SEO. Just be sure to have submitted a sitemap for your only version, and you have redirection in place. You’ll find more details on this here.
Site Kit encountered an error
`report must be an array to partition.</p>
<pre class=”wp-block-code”><code>in Overview
in div
in div
in ForwardRef
in WithWidgetSlug
in SearchFunnelWidgetGA4
in WidgetRenderer
in div
in Cell
in WidgetCellWrapper
in div
in Row
in div
in div
in Grid
in WidgetAreaRenderer
in div
in WidgetContextRenderer
in DashboardMainApp
in DashboardEntryPoint
in RestoreSnapshots
in ErrorHandler
in ThemeProvider
in StrictMode
in Root`
@baskenthaber06 I can see that you’ve since opened a support topic for this. We’ll continue to communicate from there. Thank you!
