Bugging out when creating staged site

Thanks for getting in touch @psypat. Site Kit when set up will register your site with a single domain name, while also creating OAuth credentials unique to your sites SALT keys. If you’re switching a WordPress site from a staging site to a production site, the best approach may be to reset Site Kit first, before migrating or changing site URL – from the staging URL to live URL. Without doing so, depending on how you’re migrating your site, the plugin may not always recognize a URL change, resulting in the errors you’re encountering.

What you may wish to do, if you’re using Site Kit on a staging environment, is to show data based on the production site using our Helper plugin. You’ll find more information on this here. This may not suit you if you happen to copy over/replace all files from your staging site to your production site. It may, however, be viable if the tool you’re using to push your latest updates from staging to live allow you to select what updates you wish to push (ie. only content, database changes, etc).

So to summarize, Site Kit set up is specific to a single site URL, which is registered for Search Console, Analytics and other data. If you’re switching URLs, it’s not uncommon to encounter errors if you didn’t reset Site Kit first, or if Site Kit doesn’t recognize a URL change (which is not uncommon based on all the different methods to change a site URL/migrate).

Let me know if you have any questions with the above.

Hi! Thnx for the answer.

My staging site is on the same domain, like example.com/stg_10231, and the error occurs on the live site, the one that has the right address, so there is no reason why it should bug out when the staging site is trying to access google..

It’s not like I’m switching sites, but it appears as the staging site is “taking over” instantly, since I don’t even have the time to login and disable the plugin

Thanks for the update @psypat. On the staging site, regardless of using a subdomain or subdirectory, Site Kit will recognize this as a different WordPress site. If you push updates from the staging site to the live site, errors can occur as the URLs don’t match.

Have you tried resetting Site Kit on the staging site before pushing the latest updates to the live site?

Alternatively, have you considered using Site Kit only on your live site, while showing data based on your live site on your staging site, via the Helper plugin as described in this guide?

You’ll need to use one of the 2 approaches above if your pushing updates from your staging site to your live site. Site Kit won’t remain connected if you change your site URLs.

Let me know if you have any questions with the above. Thank you.

As we didn’t receive a response I’ll mark this as resolved. Feel free to?open a new support topic?if you continue to encounter issues, or reopen this topic and we’d be happy to assist.