Has everyone's indexing api been working since September 11th?

alex20cm

Newbie
Joined
Dec 24, 2023
Messages
21
Reaction score
12
Problem that the indexing api does not work (new service account, new domain, working domain zone, new IP, etc.).

I noticed that the Google response has changed and googlebot does not come. Has anyone encountered this problem?
 
Problem that the indexing api does not work (new service account, new domain, working domain zone, new IP, etc.).

I noticed that the Google response has changed and googlebot does not come. Has anyone encountered this problem?
This started to happen to me within the last 24 hours too.

What is your response you are receiving?
 
This started to happen to me within the last 24 hours too.

What is your response you are receiving?
"urlNotificationMetadata": {"url": "https://url"}

there is no longer a latestUpdate field and URL_UPDATED type.
 
Same for me
 

Attachments

  • IMG_5879.jpeg
    IMG_5879.jpeg
    60 KB · Views: 98
Yeah, been seeing similar issues lately with the indexing API. I think it’s not just you - Google has been tweaking things since early September.
 
Yes indexing API doesn't work right now. It will be okay very soon.
 
Google made changes to Indexing API yesterday

google-indexing-api-2.png


Description of the change

google-indexing-api.png
 
Google made changes to Indexing API yesterday

View attachment 376020

Description of the change

View attachment 376021
The problem is that it doesn't come after the first API call to a new domain. That is, there is nothing to ban for, since it has never crawled the pages.

That's why it's unclear. Either these are serious changes, or these are just temporary problems on Google's side.
 
The problem is that it doesn't come after the first API call to a new domain.
Yesterday, still during the day, I tested Indexing API for new domains and a new Google account - it worked.

Today I do the same thing - new domain, new Google account and it doesn't work. Same with you, it doesn't work. After this change Google.

What Google says and what is in reality are two different things.
 
That it would be the first time, Google often does this kind of action :D
Anyway I think I will stop using the API function, Google in the interview at the beginning of September said that the API function should be used only for sites with temporary posting of job ads or streaming videos. In all other cases it will not be taken into consideration and the sitemap must be used instead of the API.

John Mueller of Google said most sites wrongfully using the indexing API are spammy anyway. As a reminder, the Google Indexing API should just be used for job postings and live stream content - nothing else. Google has said if you use it for other purposes it won't work. Many who have tried it over the years said it works to get your content indexed fast but then it drops out of the index quickly after.

https://www.seroundtable.com/google-updates-indexing-api-spam-detection-38056.html

So I think it’s better to stop using it and use sitemap, or fetch as google inside GSC.
 
Problem that the indexing api does not work (new service account, new domain, working domain zone, new IP, etc.).

I noticed that the Google response has changed and googlebot does not come. Has anyone encountered this problem?
Most Welcome to the BHW!
The problem is that the indexing api does not work (new service account, new domain, working domain zone, new IP, etc.).

I noticed that the Google response has changed and Googlebot does not come. Has anyone encountered this problem?
 
Hi, who has information on how to work with Google Indexing API now? I am willing to pay for a consultation.
 
Anyone tried the schema they said it's working with? I tried Jobposting embedded in Videoobject, but this doesn't work either
 
Back
Top