I am trying to integrate the Google search engine resource to look at SEO statistics. The integration is not working and is telling me that I do not have permission for the website I am trying to pull data from despite being an owner of both the Google Cloud and Retool apps.
I get the following message after running a trial query:
Apologies for the issue. Very odd. It sounds like this is a permissions issue so you may need to double check that on the Google side.
Is this error coming from a Google Analytics Resource in Retool? If not, let me know what type of Resource as google has a couple, all with similar names
Maybe the Google account isn't registering that you own the https://www.henry.social domain. Is this domain hosted on Google? Is this the name of you Retool app?
Just wanted to circle back and check and see if you had a work around.
Retool apps do not allow for embedded script tags which has been a barrier to users integrate with Google search engine resource to look at SEO statistics.
We are working on improved Google Analytics support for monitoring app/website traffic so stay tuned for updates on those features!
Hey Jack, sorry for only just getting back to you regarding this. I was not able to find a workaround and no I was pretty certain it was not to do with the google side (i.e. domain is hosted on google and permissions were there).
Regarding your second point: so is there a way to look at SEO metrics through retool?
Alright Jack. We are back on this issue now and after running a /webmasters/v3/sites query. We are getting the following with the google search console integration in retool:
{
"siteEntry": [
{
"siteUrl": "sc-domain:henry.social",
"permissionLevel": "siteOwner"
}
]
}
Which suggests that everything under our domain should be accessible. However, whenever we try to make a POST search analytics query for a specific URL under that domain we get the same 403 error you see above. Let me know what you think may be the issue!
If you still need assistance with this, @Adrian_Eddy, I'm curious to know how the resource is configured and, in particular, authenticated. I'm guessing it's a REST API resource that is authenticated with OAuth2, but let me know if that's not the case.
Assuming the above, one place to look is the scopes that you are currently authenticating with.