• Resolved midigitalsolution

    (@midigitalsolution)


    Support Question and hopefully the beginning of a solution for folks that manage numerous Google Accounts

    – We launch our WP builds with a clean install of Google site kit. Within a spectrum of 300 websites I see our sites disconnecting often and and by often I mean Disconnect is almost guranteed with monthly WordPress and Elementor updates.

    Further – The disconnect creates an unnesecary burden on Google Site Kit plugin user to both confirm and reconnect proper Google account.

    – In addition we have tested latest verioning of Google site kit on a networthy stack and specifically it seems when activating Site kit and connecting to our ad teams accounts that have numerous accounts to select from some of our accounts will unpredictability be unavailable (not seen by plugin on connect) as far to include the user account for the URL relating directly to the site you are trying to connect to. In summary new plugin / new website while trying to connect to an agecly level Google account that has multiple listing will not see the account with the URL you are trying to connect to.

    We are now considering only using this plugin for Search Console as slip in proper account reconnect causes havoc.

    Hopefully someone can assist



    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    Hi @midigitalsolution and thanks for opening a support topic. This specific scenario has recently been discussed in this GitHub issue that was opened a few weeks ago. As explained in the issue there is a limit of?100 Analytics accounts?per Google account.

    When setting up Analytics in Site Kit we currently request the maximum number of accounts possible in a single request which is 200 so if your Google account has more than 200 you will run into issues where certain accounts can’t be listed in the selection dropdown. It sounds like this is what you may be experiencing. If however this is not the case then please could you explain your issue in more detail.

    The simplest workaround for the limitation above is to set up the Analytics module using a different Google account that has access to fewer total accounts as to not exceed the 200 account limit above. That may not be ideal, but would work today to unblock the setup flow.

    I hope this helps to answer your questions but as mentioned above, if there’s anything else I can help with then please let me know.

    Thread Starter midigitalsolution

    (@midigitalsolution)

    I understand from your reply that we’re not the only ones facing this issue, and the need for agencies to have primary umbrella accounts connected won’t be addressed. Given that agencies often represent multiple clients, and our agency wants to continue supporting your product, how can this be escalated for an official review?

    Restructuring an agency’s Google accounts to accommodate a plugin tweak isn’t ideal from a security perspective. I thought this plugin was designed with agencies in mind, and being recommended by agencies should carry weight. Is there any solution you can provide that doesn’t involve restructuring our entire agency to fit the plugin’s requirements?

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @midigitalsolution We have had a couple of other questions about this in the past and the recent GitHub issue which I linked to a few weeks ago. Once that was opened I discussed this with the internal team to see if there was anything we could do on the Site Kit side to help agencies such as yours with this.

    As mentioned above and in that issue, there is a limit on the number of accounts we can request. We are currently requesting the maximum limit here so there isn’t much we can do here. I have brought this to the attention of the team once more and please do feel free to add your thoughts or suggestions to the GitHub issue.

    I’m sorry that I can’t help you further at this time but hopefully the suggested workaround can be a benefit to you. Is there anything else I can help you with at this time?

    Thread Starter midigitalsolution

    (@midigitalsolution)

    Thank you for the clarification and for escalating this issue internally. I understand the current limitations due to the 200-account request limit imposed by Google, and that this constraint makes it challenging to manage numerous accounts under one primary Google umbrella, especially for agencies managing multiple clients.

    However, this limitation places a significant burden on agencies like ours, which manage hundreds of websites, as we face frequent disconnections—often following WordPress or Elementor updates. This leads to repeated manual interventions to reconnect the proper accounts, disrupting workflow and creating unnecessary overhead.

    We believe this challenge could be better addressed by:

    1.Enhancing Account Retrieval: Investigating if a more dynamic retrieval system can be implemented, such as allowing selective or paginated requests from the user’s account, rather than fetching the entire account list at once.

    2.Persisting Connections Post-Update: Exploring the possibility of persisting Google account connections even after plugin or CMS updates to avoid frequent disconnects.

    3.Offering an Agency Mode: Developing an “Agency Mode” in the plugin that supports multiple clients, tailored for large account structures, allowing for smoother management of multiple Google accounts under one agency.

    In the interim, we are considering limiting the plugin use to Search Console only, as frequent disconnections with Analytics accounts create havoc in our workflow. We appreciate the current workaround of using alternate Google accounts with fewer connections but feel this isn’t a sustainable solution for agencies working at scale.

    Could this issue be flagged for further review and potential roadmap consideration? Agency support is a critical aspect, and we believe improved functionality in this area would greatly enhance the plugin’s appeal to a significant user base.

    Thank you again for your support, and we hope for more robust solutions in the future.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @midigitalsolution Thank you for the follow up and your feedback it will certainly be noted and passed on to the team for their review. While I can’t make any guarantees, we are always looking at ways to improve the plugin. Please do feel free to follow the GitHub issue for this where any updates will be made here.

    Is there anything else I can help you with at this time?

    Plugin Support James Osborne

    (@jamesosborne)

    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.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.