Thanks for reaching out @bounty_digital, and sharing details of what you’re experiencing. Based on the redirection to your login page of your old website, I suspect Site Kit was not reset before migrating your site to the new URL. Migrating a site afterwards can unfortunately mean your old site URL references remain on the service, and your new site is trying to connect with these.
To determine more on this and ensure you can connect the plugin, please share the following:
- Your Site Health information. You can use this form to share privately if preferred.
- What is the URL you land back on when attempting setup, the full URL on your old site? I ask as this may contain a callback URL, which we can use to identify your records.
Once we have the above we can advise further. Some troubleshooting we may then perform is adding or removing a www prefix for your site, or making changes on the Site Kit service to correct the site records.
Let me know if you have any questions with the above.
Thanks James! I’ve just sent it through privately using the Google form.
Thanks for sharing @bounty_digital. From reviewing the details I can see that the callback URL contains a previously used comingsoon path. There are a couple of things we can try in order for you to complete Site Kit set up successful. Firstly you can revert to your site using that path once more, and then connecting Site Kit. After a successful connection you can reset Site Kit at that point before resetting and removing that path. If this is a possibility for you, I’m happy to provide you with further details.
Another option is to add a www path to your site, which will allow Site Kit to register your site once more as a completely new site, not using any previously used callback URL. This would mean your site is using www, and reverting to that for all visits to your site.
Finally, another option is for me to request a reset of your site records on the Site Kit service, to reflect your site without the comingsoon path. This may take a few days as I have to submit a request, but it should allow you to complete set up successfully without any changes on your site.
Let me know what you prefer, or ask if you have any questions with the above.
Hi James, Could you please request a reset of site records. The sites gone live so we can’t make any changes to the current URL. Let me know when that’s been done and I can try SiteKit connection again! Thank you 🙂
Not a problem @bounty_digital! I’ve done so now. Unfortunately this typically does take a few days, but as soon as I have an update I’ll let you know here, hopefully early or mid next week. Until then, you can view your Analytics data from analytics.google.com. Thank you.
Just a quick update on this, it looks like you’re using a full path for your WordPress files, is this correct? I ask as when we’re updating your site records, we will need to use a valid callback URL. Please confirm the following:
- You are using a
full path for your WordPress files and this won’t change in the next week.
- After logging in, you’re using a standard WordPress wp-admin path?
Hi! Yes using full for the WordPress files AND also the wp-admin url .. its just the site URL that is the root file. So the callback URL just needs to be full instead of comingsoon
Thank you!
Perfect, thanks for the update. I’ll let you know here as soon as I have more news regarding your site check. Thank you!
Thanks for your patience on this @bounty_digital. Your site records are now updated to reflect your current settings. Can you try to set up Site Kit once more and let me know how you get on?
Perfect!! Setup was successful. Thanks so much for your help @jamesosborne 🙂
Glad to hear it @bounty_digital, thanks for the update. If you encounter the same error after any further changes to your WordPress path, or if you have any queries, be sure to get in touch. If you have a moment free please also consider leaving a review , in particular as a user for some time. We’d love to hear your feedback.
