Hi @bjornharvold thanks for getting in touch and sorry to hear you’re having trouble installing Site Kit on your sub domains. Could I please ask you to share some further information:
- Your Site Health information. You can use this form to share privately if preferred. Please also include your hosting provider here.
- Which sub domain is this working on and which are you having troubles with? Please feel free to share here or in the form above.
- Any recording or screenshot of this happening.
- Do you see any warnings or errors when checking your Site Health status (Tools > Site Health > Status), which differs from your Site Health information? Such errors may include REST endpoint references.
Let me know if you have any questions on the above.
Hi Adam,
Google Site Kit works on https://stays.gay and https://miami.stays.gay as the video shows and were connected in that order. Unable to connect any of the other sub-domains we have like new-york-city.stays.gay, las-vegas.stays.gay, los-angeles.stays.gay.
No REST API errors.
Health: https://www.dropbox.com/s/zaasy3ursj1vlui/stays-health.png?dl=0
Video: https://www.dropbox.com/s/24lmd1irxci26l0/stays-recording.mov?dl=0
Let me know if you need anything else.
Cheers
@bjornharvold Thanks for sharing that is very helpful. Can I confirm that the setup for all subdomain sites you have follow a similar structure and there aren’t differences in where the WordPress folder is or different admin paths?
Can I also check that you are signing in to Site Kit using the same Google account as you have done for the previous 2 sites? Do you see any difference when trying to connect through an incognito browser?
Correct. They are identical.
Yes. Using the same Google Analytics account.
Yes. Same error in incognito mode.
@bjornharvold Thanks for confirming. I have so far been unable to recreate this on my own subdomain multisite setup. I will continue to test this and discuss with the team and update you as soon as we can.
Hi @adamdunnage
We are just getting set up with these sites. I can give you full access to both the site and the server if you’d like to take a closer look.
Email me at bjorn at wink dot travel
Thanks for the update @bjornharvold. As per WordPress.org forum guidelines we’re unable to login to users sites. We will, however, be performing some checks on this and report back to you at some stage early this week, most likely tomorrow. Thank you!
Appreciate your patience on this @bjornharvold. I’ve set up a couple of multisites similar to your own setup and in my case I was unable to recrate the same error.
Based on what you’re encountering, I suspect what may be happening is the plugin was setup on a site on a different domain before being added as a subsite within your network. An example of this may be whereby a site was migrated to a subdirectory, rather than having a new clean WordPress install for each subsite.
So we can ensure you can complete setup, can you share how you created the subsites? By this I mean did you migrate the parent domain or copy the files and database to your subdirectory, being modifying the details? If so, some of the site records may reference your parent domain. If this is the case, please let me know all the subdomains you are using.
On one of the subdomain sites you may also wish to change the site title, as this can trigger Site Kit to update the site records for this site. Even adding an underscore would trigger this change in Site Kit, which may allow you to proceed with setup.
Hi @jamesosborne
Our multi-site installation was actually super simple. It’s never been migrated. There was never any folder magic. We used WP UI the whole time. We set up the base site. Then we added our 5 sub-domain sites. Once they were all up and running, we connected them all to Google analytics using SiteKit. Probably one of your first versions of SiteKit. I do believe we connected all domains without issue because they were all viewable in the GA UI.
Then GA 4 came along and gave us warnings that GA UA would stop working. We removed all old GA properties and created new GA4 versions manually in GA. Then we went back to site kit to connect them all to the new GA4 properties we had just created. SiteKit insisted on making old GA UA properties as well. That worked for our base site and for Miami.stays.gay.
it did not work for new-york-city, los-angeles, las-vegas, san-francisco.
Many thanks for the update @bjornharvold, appreciate you sharing these insights. What we may be able to do in this case, is request a site reset for your subdomain sites. Before doing so, can you try changing the site title for one of the impacted sites (ie. new-york-city.stays.gay) and attempt Site Kit setup once more? This can trigger Site Kit to request new site records, which will only use your subdomain and not your parent domain records.
When changing the title, you can add a single extra character to the end (via Settings > General). After doing so, please attempt Site Kit setup from this site, without including Analytics as an option during set up. If the same occurs, please share a recording of your experience along and I’ll request a reset of site records for the subdomains that you listed. 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.
Let me know if you have any questions with the above.
Hi @jamesosborne
I added another ‘y’ to title: “New York City Stays Gayy”.
Same error: “a site with the given URL already exists”
Thanks for checking this. In that case what I’ll do is request a reset of your site records for your parent domain and also a check for any invalid records on your subdomains. Note that by doing so, you may need to set up Site Kit once more on your parent domain. Can you confirm that this is ok, if so I’ll request this today?
Please also confirm that the following are the subdomains to check:
- new-york-city.stays.gay
- los-angeles.stays.gay
- las-vegas.stays.gay
- san-francisco.stays.gay
Once you confirm the above I’ll forward the request to check and reset your site records. This will hopefully allow you to proceed.
Hi @jamesosborne,
Yes, confirmed on the reset.
Yes, confirmed on the sub-domains.
https://stays.gay works fine currently and so does https://miami.stays.gay. Not problem if we have to reconnect again. As I said earlier, we are just getting set up so “have at it!”.
Cheers
Many thanks for sharing the additional details @bjornharvold. I’ve requested a reset site. Hopefully this will be complete over the next few working days. Unfortunately I don’t have any workaround to get your subdomain sites connected in the meantime. You can certainly add Analytics manually to these sites while we’re awaiting a reset of your subdomain records.
We’ll keep you informed here as soon as we have an update on this. Thank you!
I just heard word back from your site check @bjornharvold. It looks like some of your multisite may have incorrect records. In order to resolve this can you please perform a reset (Tools > Available Tools > Reset Site Kit) firstly on miami.stays.gay as this seems to be the site that’s matched when you’re trying to setup your new-york-city.stays.gay site. You can then attempt Site Kit setup on the Miami site once more. If you encounter the same error on the Miami site please perform a reset on this site also.
Let me know how you get on with the above. We can then review your other sites afterwards.
