GSC (Google Search Console) [start] [ERROR] Search Console API Error for domain.com (30days) : 403 Bad Request #91
Replies: 6 comments 4 replies
-
Just to chime in here, I've been running into the same issue. Both through an instance hosted on PikaPods and on my own server. I've verified my GSC API is running, added the user to our GSC account, followed all the steps as outlined in the docs, and still get 403s. |
Beta Was this translation helpful? Give feedback.
-
As you know, 403 means permission error. Which means the API key you inserted does not have the permission to make the calls for that specific domain. Its working fine on my installation. Ensure that you have completed the Required Steps:
|
Beta Was this translation helpful? Give feedback.
-
Got it working. You need to give access to the service account to a "domain property" @ Google Search Console. |
Beta Was this translation helpful? Give feedback.
-
@sergiorodenas Great! Can you please check the documentation and see if I missed describing a step? https://docs.serpbear.com/miscellaneous/integrate-google-search-console |
Beta Was this translation helpful? Give feedback.
-
are there a way to get URL prefix property not Domain property datas? |
Beta Was this translation helpful? Give feedback.
-
This issue was caused by SerpBear's inability to add the URL properties of the Google Search Console. It only supported domain property. The ability to add URL property has been added in v1.0.0 so this issue should not occur anymore. If anyone is having this issue, try updating your SerpBear instance to the latest version. |
Beta Was this translation helpful? Give feedback.
-
Hey there Towfiqi,
Is there any update on this : [start] [ERROR] Search Console API Error for domain.com (30days) : 403 Bad Request.
been trying hard but it isnt working.
Beta Was this translation helpful? Give feedback.
All reactions