Submitting URLs to Google Indexing API

I have been working a scenario that will watch for new WordPress posts and submit them to Google Indexing API so they can be crawled.

To me, Google’s API documentation is a hot mess but I did make some progress but stuck with the error relating to a redirect issue even though I have added it as an authorized redirect uri in the developer console.

Anyone had success with this?

Error 400: redirect_uri_mismatch

You can’t sign in to this app because it doesn’t comply with Google’s OAuth 2.0 policy.

If you’re the app developer, register the redirect URI in the Google Cloud Console.
Request details: redirect_uri=

Hey @Tim_B

I used this URL , this is working perfectly. You should try this.

Also check the scopes.

1 Like

I’m using for the scope. I also went ahead and added the url you provided, still getting the same error but Google states it could take a few hours for the change to take affect.

Quick update as I figured I gave it enough time after making the change in the dev console. Still getting the same redirect error referencing the same uri “redirect_uri=

Hey @Tim_B , your original redirect URL was correct. So keep using

Did you read Using OAuth 2.0 for Web Server Applications for the oauth setup? It seems like your authorize URL is not fully correct?
I believe it shoiuld be


I ended up creating a new client ID and got further when adding the redirect url to the authorized list but now I get the following message since I don’t own the domain. has not completed the Google verification process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access, contact the developer.

If you are a developer of, see error details.

Error 403: access_denied

1. Enable the API

Direct Link: Google Cloud console


2. Insert all the known Google Redirect URIs for your app

Direct Link:

How to create an OAuth app in GCP: ← FOLLOW THIS

Here are all the known redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.

Once you’ve set these up, you can use/reuse the same Make connection for all the supported Google apps & modules on Make - you’ll only have to enable the respective APIs for your custom app in Google Cloud.

According to the Make OAuth2 documentation, the main one you need to use for HTTP OAuth connection is

3. Publish your GCP OAuth2 app

Direct Link:

You might need to set your OAuth application to “Production”, otherwise the credentials expire very frequently.

1. To do this, go to menu item “OAuth consent screen”

or click here

2. Then click the button below if the Publishing status is not “In production”

4. Configure the HTTP OAuth2 module

You need a “Authorize parameters” key of redirect_uri with the above Make OAuth2 callback URL.

You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the 8 callback URLs in step 2:

The 403 access denied error was resolved by changing the mode from test to production.

No problem, glad I could help!

1. If you have a new question in the future, please start a new thread. This makes it easier for others with the same problem to search for the answers to specific questions, and you are more likely to receive help since newer questions are monitored closely.

2. The Make Community guidelines encourages users to try to mark helpful replies as solutions to help keep the Community organized.

This marks the topic as solved, so that:

others can save time when catching up with the latest activity here, and

  • allows others to quickly jump to the solution if they come across the same problem

To do this, simply click the checkbox at the bottom of the post that answers your question:

3. Don’t forget to like and bookmark this topic so you can get back to it easily in future!